Kwikset lock showing incorrect status

I have searched the forums on this and I have sent a message to tech support as well. The problem I am having is not that the door lock won’t report, or reports intermittently. It reports every time and the status is incorrect. The lock is right side up, but when it is locked, the status shows unlocked on the dashboard and my mobile app. When I unlock the door, it reports immediately in the locked state. I am very confused on how to fix this issue since there is very little documentation that came with the vera 3. The only thing I have found online was to add id_code 305 with a value of a “1”, but this didn’t do anything either. I have played with the status settings in the advanced section as well. It will change the status in the dashboard, but as soon as i lock or unlock the device, it goes right back to the wrong status. If anyone has any information, please let me know.

What is your battery status level? I have found that the lock reports the wrong status when battery is low (otherwise it seams to still respond and work). Try keeping batteries above 70%.

Probably not your case but I have found that when the dead bolt does not fully extend it sometimes reports the wrong status (re opening and closing the lock sometimes fixed this problem).

Hi!

How far away is Vera from your lock?
I had exactly the same problem. Moving Vera closer to the lock (although it was a pain since I had to get a router to use as a wireless bridge to connect vera to) solved the issue and it is now working 100% fine.

Florian

You can also try and put some devices that support “Beaming” dimmable modules etc close to the lock and see if that corrects that status issue. The problem with locks is that when a command gets sent to the lock, it is encrypted. After the lock gets that command it does it’s thing and then sends a status back to the controller also encrypted. The encrypted message is only good for a few seconds. if vera does not get that message in time, it ignores it and keeps the current status it has.

  • Garrett

I am having exactly the same problem. Note that this issue did not occur with UI4. I only occured for me when I upgraded to UI5. I have a dimmer switch less than a foot from the door and the Vera 2/UI5 is approximately 30 feet away. Fresh batteries make no difference. Does anyone have more ideas on how to resolve this? Can we extend the reply signal timeout length to see if that’s the root cause?

you run latest ui5 1.5.322 ? it solved some updating issues of devices for me, where the former version didnt update some devices all the time

I have noticed that if the Zwave network is busy, I don’t get lock status updates.

For instance, I have 2 locks, both of which Vera can talk to directly, and they can reply directly. I had a “locked” scene which immediately locks both locks. 70% of the time, the status do not update for one or the other. I see Vera showing “Transmit was ok” and the locks will lock.

What I changed was added delays to get around this. The first lock is locked immediately, and I give it time to respond (10 seconds) before I lock the other one. Since I moved to this sequence, my lock status is MUCH closer to being right 99% of the time.

I still notice issues if I lock/unlock (or unlock/lock) them too quickly.

Again, I think it goes back to the encrypted communication taking longer, and it could be the messages are considered “stale” by the time Vera can process them, and therefore discards them.

Occasionally my Kwickset locks will show an incorrect status. When this happens I will do a manual poll of the node and it will reach out and get the current status of the lock. This normally corrects the issue. Have you tried this? It would be interesting to see what a manual poll results in.

Settings>Poll Now.

A manual poll does update the status. However, I have indicators lights on zone controllers indicating lock status. I don’t want to poll that often, because it could affect battery life.

Thank you! Just upgraded and that fixed the status reporting for the locks.

If any devs are following this thread, I’d recommend that the lock/unlock icon be changed so that the lock shape changes to an locked/unlocked position rather than using an almost inperceptible color change on lock surface for the status change.

:slight_smile: Something like so? That’s UI4… ;D

Yes. :slight_smile:

:slight_smile: Something like so? That’s UI4… ;D[/quote]I do miss the old icons…but as long as they are going to change it, I’d want something even more dramatic. Maybe swing the lock arm the other way or something. Make it blatantly obvious that it’s unlocked.

The current icon is awful, the old one is way better, but even that could be improved.

Any way we can replace a file on Vera with a new image? Or is it locked down?

I agree 100%.

+1 , the “unlocked” icon should be dramatically different from “locked”!

Looks like they did a decent job of distinguishing between locked and unlocked icons in the latest UI5 build (1.5.345), and they fixed the incorrect icon status in the Overview module.

yu :slight_smile:

[quote=“knewmania, post:16, topic:170641”]Looks like they did a decent job of distinguishing between locked and unlocked icons in the latest UI5 build (1.5.345), and they fixed the incorrect icon status in the Overview module.[/quote]I am on 1.5.346, and I still have the red/yellow icons.

Thats odd. I’m on a Vera2. Dumb question but is it a browser cache issue?

[quote=“knewmania, post:19, topic:170641”]Thats odd. I’m on a Vera2. Dumb question but is it a browser cache issue?[/quote]I’m on a Vera2 as well. I thought that, and cleared the cache in Safari, with no luck. Even my new iPad was showing the old ones. Tried it with the TouchPad for a sanity check, and it won’t even load!

I guess I can try a “reset” of Safari and see if that forces it.

Mobile Safari needed a “Clear cookies and data” not just “Clear History” to get it to work.
Desktop Safari this time needed a “reset”…odd that “empty cache” didn’t seem to work. shrug

At any rate, I now have better (but still not great!) lock icons! Thanks!