I have a Schlage Connect (zwave) doorlock installed, and it is working (mostly). But sometimes when I try to unlock it froma webhook, it doesn’t unlock. This is almost always the case when I’m testing it. I’ll lock it, then withing 5-10 seconds try to unlock it via a webhook automation (which also includes sending a notification and toggle a lamp module). The notification and lamp do their thing, but the lock doesn’t unlock. It’s as if there’s a timer lockout for the Schlage, is that the case? I dont see any lockout setting for it.
Have you tried unlocking it in other ways to see what the response time is?
Locks are usually at the fringes of our homes. Is it possible that the Zwave connectivity is not great, so that sometimes messages to the lock get lost?
Lock is like 10’ form HomeAssistant hub. I’ve come to realize that it probably takes longer than the 5s between lock and unlock phases to propagate the lock state back to HomeAssistant. If I wait a bit longer, 20-30s, the process all works.
HomeAssistant seems to realize the state change very quickly (almost instant), so I’m not convince it’s the lock that’s the timing issue. But doesn’t explain why the other 2 items (in the same automation) execute but the unlock doesn’t (without a wait).
An update: if I lock the door lock using the HomeAssistant app, or pressing the Schlage Lock and Leave button. Then the webhook to unlock works immediately.
BUT, if I use the interior door knob to lock the door, then the webhook needs some delay before it can unlock the door. So it seems using the door lock knob inserts some delay before a zwave unlock command will be accepted. Which isn’t really an issue, as one can’t physically use the interior knob to lock the door when leaving. This only arose during testing.
UPDATE: seems related to other issue I’m having with dead keypad. Unit is going back for replacement.
Doorlock just dies a couple times a day (node status dead). Turning the knob manually seems to bring it alive. What could be the cause of this?