I have dug around the forum and cant seen to find a solution that fits my problem. I have a kwikset lock about 12 ft from my vera2 UI4 but it always reports locked. I can control it without a problem but if I change to another page then back to the lock it always shows locked. Anybody else having this problem? Thoughts?
Hi,
I have a kwikset lever lock which is about the same distance away from the vera2. I have not had it report the wrong status except a single time where it behaved a little differently. I think I locked the door via the UI4 interface and it kept some status message on the box that describes the lock and the area was tinted green. Usually it doesn’t do that. I have not had it repeat but will watch it more closely and report back if it repeats.
I have a Kwikset lock as well maybe 20 feet away and the lock functions but the status rarely updates. Also in the ogs sometime the door open door close logs are created other time they are not using UI4 1.1.1062.
I have it set up to poll it ever 6 min. I guess ill remove it and re-add it. If that dont work maybe the new firmware will fix it.
You don’t want to change the polling default as you’ll get through batteries awfully quickly!
I recommend moving vera back very close the lock and trying a configure first! If you first configured the lock when it was near to vera, then you should also do a neighbor node update also when Vera is in its normal position!
Strangely when you say a neighbor node update you mean on the lock itself? or repair network sorry little after vera is back in normal location sorry a little new to zwave
Thank you
You want to go into the lock’s settings on Vera itself, after the lock is in its permanent home, and click on ‘update neighbor nodes’. This basically asks the lock to look around, and see what other z-wave devices are nearby. It will then be able to use those to communicate with Vera.
Hope this helps.
After up dating the neighbors it is working great thank you and updating the status now to work on a scene when door opens turn on light
That seemed to fix 90% of the problem for me too. Thanks! The UI and SQ remote update great. iVera…not so much. I think I remember seeing a thread about ivera and the kwickset lock acting up.
Do you have many other devices? It could be that you need to optimize your network a bit more elsewhere, and also perhaps think about adding another device such as switch thats “beaming” capable as close as possible to the switch.
12 Feet isn’t that far, but RF is a funny beast sometimes, and you might be in a bit of dead spot!
FYI though, even after doing all this, then you might find that the lock/vera still get confused about it’s status occasionally, and the only way to be sure if there is any doubt, is perhaps to poll the lock! The status is most often incorrect when the lock has been locked or unlocked manually!
I have about 13 other devices. My only problem I have now is with the iVera. Everything else updates the status amazingly well. I did find a thread about a bug in iVera that someone else found that was causing the same problem for them.
Thanks for all the help.
Looks like its an known iVera issue that should be fixed soon.