Re: DanalockBTZE100Square status report issue
Posted: 06 Jun 2023 20:51
Your previous posts described lock status being updated/displayed with intermittent success when operated remotely. To rule out a mesh routing problem as the cause, please consider moving either the controller or lock so that they are in direct communication with each other (and do a network reorganization to update the routing table). Once the controller and lock(s) are in direct communication, remotely lock and unlock via the Z-Way UI and then use the Z-Way diagnostic tools (timing, packet stats and Zniffer history) to verify Z-Wave packets are being transmitted and received as expected. The Z-Way log file (/var/log/z-way-server.log) will show packet processing details.
The approach I use when a Z-Wave device is operating intermittently is as follows:
1. Eliminate mesh routing as the culprit.
2. Verify messages to the device are being transmitted and received as expected using Z-Way's diagnostic tools.
3. Use the Z-Way log file to see if there are any packet processing issues.
In other words, moving your Pi to be within direct communication of the door lock might not solve the problem. This step serves to eliminate mesh routing as a potential problem and makes it easier to troubleshoot the problem. I have 2 guesses about what you're experiencing with the door lock: (1) Door lock status messages are being mesh routed through your legacy Z-Wave devices and those legacy devices are not consistently routing the messages correctly. (2) There's an interoperability issue in Z-Way software processing the door lock status messages.
I am confident that if you take the time to learn how to use Z-Way's diagnostic tools, you'll be able to solve the door lock mystery.
On a tangent, I find it interesting that the newest Z-Wave RF interface (called Long Range) has abandoned mesh routing and has adopted a star topology (similar to Wi-Fi, where the access point replaces the Z-Wave controller), using a direct sequence spread spectrum modulation scheme that is less sensitive to interference, operates at 100 kbps and has much longer range. Unfortunately, Z-Wave Long Range requires series-700 and newer Z-Wave devices.
If you're still stuck, please reply with a Zniffer history screenshot showing messages for devices 2, 4 or 5, packet stats with non-zero counts for devices 2, 4 or 5, timing info with non-zero counts for devices 2, 4 or 5 and the relevant part of the log file when you were operating a door lock.
Good luck.
The approach I use when a Z-Wave device is operating intermittently is as follows:
1. Eliminate mesh routing as the culprit.
2. Verify messages to the device are being transmitted and received as expected using Z-Way's diagnostic tools.
3. Use the Z-Way log file to see if there are any packet processing issues.
In other words, moving your Pi to be within direct communication of the door lock might not solve the problem. This step serves to eliminate mesh routing as a potential problem and makes it easier to troubleshoot the problem. I have 2 guesses about what you're experiencing with the door lock: (1) Door lock status messages are being mesh routed through your legacy Z-Wave devices and those legacy devices are not consistently routing the messages correctly. (2) There's an interoperability issue in Z-Way software processing the door lock status messages.
I am confident that if you take the time to learn how to use Z-Way's diagnostic tools, you'll be able to solve the door lock mystery.
On a tangent, I find it interesting that the newest Z-Wave RF interface (called Long Range) has abandoned mesh routing and has adopted a star topology (similar to Wi-Fi, where the access point replaces the Z-Wave controller), using a direct sequence spread spectrum modulation scheme that is less sensitive to interference, operates at 100 kbps and has much longer range. Unfortunately, Z-Wave Long Range requires series-700 and newer Z-Wave devices.
If you're still stuck, please reply with a Zniffer history screenshot showing messages for devices 2, 4 or 5, packet stats with non-zero counts for devices 2, 4 or 5, timing info with non-zero counts for devices 2, 4 or 5 and the relevant part of the log file when you were operating a door lock.
Good luck.