UPDATE: No resolution for me yet, but I've been trying lots of things this weekend...
- Moved the hub to each lock
- Manually reset each lock, then excluded each lock, then reset the lock again, then included each lock
- The locks will respond pretty fast when initially after inclusion, but after a few locks/unlocks things start to get bad again where the lock wont respond for 30 seconds to a few minutes before locking/unlocking.
I now have the hub back in its original location, and performed a Z-Wave network refresh. I have tried a bunch of steps to get the issue potentially reproducible, and here is what I have found.
Reproduction steps (frequently, but not 100%):
- Do not do anything with any Z-Wave device for 5 minutes
- Unlock ONE lock directly via the "Devices" page - any of the 3 locks selected will unlock within 1-3 seconds which is acceptable.
- For the next 1-5 minutes are where it becomes difficult to do one or more of the following:
a) Lock the lock that was unlocked, via the Devices page, or any dashboard
b) Unlock any other lock, via the devices page, or any dashboard - During this time, sometimes the locks respond quickly, but more often the locks do not respond at all to one or frequent lock/unlock/refresh queries via the devices page or dashboard.
- After waiting for 5 minutes or so with no Z-Wave activity, the next time a lock/unlock command is sent to a single lock it will respond within 1-3 seconds as expected. However, if any further lock commands are sent to any locks then the process repeats from step 2 above. Again - this is not true 100% of the time, sometimes the locks simply wont respond to lock/unlock commands even if it's only to 1 lock at a time and nothing else has happened on my z-wave network within a 5 minute time-frame before the lock/unlock attempt.
Impact: I have a few rules setup which trigger 2 or 3 locks simultaneously. Such as when I am leaving home in the morning. I run a triggered rule which should unlock my side (house) door and my garage door. At night I have a rule that triggers all 3 locks to lock themselves. Whenever I use these rules, I experience the issues starting at step 2 above, which appears to be a correlation.
Note : I have been watching my logs, and have not seen anything strange such as excessive lock/unlock commands or anything that I can visually identify such as commands flooding the network. It is possible that the locks/hub/mesh/repeaters are flooding my network with commands during lock/unlock events but none of that is showing up in the logs I have visibility into.
