I don't know why I still try to use Lock Code Manager anymore. I think it's because I forget that it doesn't work that well with Schlage Z-Wave Connect locks (unlike the Smart Things and HA, which never had any problems)
After LCM kept failing, I removed a code from one lock using the driver interface fine. Then I tried to remove it from the other lock, and the request has been in the queue for hours. All the log entries seem consist of it trying to fetch code 5 over and over and over and over and over again.
Never mind that I've never used that one before...
I've rebooted the hub and power cycled the lock a couple times, most recently 3 hours ago and the entries continue. No others... just 5.
Is the inability to fetch this code the reason why nothing else can be done on this lock?
Thanks!
I have a completely different lock (Yale Assure2 ZWave) but have also noticed this behavior before using Lock Code Manager.
I have also had several other random problems. Sometimes when I lock the door manually it does not report locked status. Sometimes when I use Rule Machine to set codes for guests, the "Name" part gets omitted, and the code shows up in the lock as "code-4", where the number represents the code slot it was input into, which then breaks automations that function off of the lastCodeName attribute.
I suspect ZWave mesh issues to be the problem. I had no issues for a long time, and then my ZWave started to collapse after a device reset itself somehow and these issues started popping up on the lock with a slew if other ZWave related issues.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
