Installed new Release 2.4.2.138 and both of my Yale locks did not work right.
I have a automation to lock locks when i leave my house. With the new release locks would lock and then unlock and lock. Then after a minute or so they would both unlock and stay unlocked.
I thought it may be the ZwaveJS so i switched back to the Zwave and that did not help.
Rebooted Hub and that didn't help. Then I rolled back to Release 2.4.2.134 and Yale locks worked like they should.
Investigating
Do you have any more detail? .. Does it not respond to commands and/or missing reporting?
Responds to commands and will lock or unlock and then the lock like goes haywire. lock will lock and then by itself it will unlock and lock then stay unlocked.
is command retry enabled, or disabled on these locks
I am using Webcor for my automations. 1 other thing i tried was i built a automation in rule machine and had the same effect.
I may know what this is... Does the lock actually do that or is it just the reporting?
No the lock is actually locking and unlocking and yes the command retry is enabled.
Ok.. I'm pretty sure I know what's going on.. About to test..
3 Likes
Having the same issue with my Kwikest 620 locks, lock/unlock cycling. Had to remove the battery to get it to stop.
What did you Find out?
I have a C-8 Pro on 2.4.2.138 with a Z-wave Yale Assure 2 that started creating weird redundant log entries. I haven't noticed any strange or unwanted locking or unlocking, but I've never seen the redundant (but strangely also woreded differently) logs when unlocking the door. I also seem to see way more battery status entries in the logs than I used to see. Not sure why. Nothing seems to function poorly. See image below:
Having a similar issue with my C-8 and iBlinds. Retry was enable and it keep sending and old command minutes later. Rolled back to .134 and it stopped.
Piling on. I only observed minor nuisances after updating to x.138. Mainly, some Zooz dimmers that stayed on after being commanded off (via webCoRE). The device page showed the incorrect switch state. I recall clicking a few times to resolve, but it was the middle of the night and I may have just been sloppy in my tapping.
I tried rebooting with database rebuild, but no luck. So, I also rolled back to x.134.
A kwikset lock cycled on me too, Turning off command retry solved it.
There's a patch coming in the next build for lock related command retry issues
3 Likes
Turning off command retry does fix the Yale locks with version 2.4.2.138
