#Z- Wave Devices Become Unavailable

1 messages · Page 1 of 1 (latest)

crisp canopy
#

Hi all, I’m running Z-Wave JS UI with a network of around 40 devices, many of which are wired. I’ve been experiencing an issue where devices frequently become unavailable, causing automations to fail as commands can’t be sent during that time. Manually pinging the devices after they become available resolves the issue, but I’d like to find a more permanent solution.

So far, I’ve tried running a network heal, but the issue persists.
1. Is there a good way to further troubleshoot this issue?
2. Are there best practices or tools within Z-Wave JS UI to help diagnose what’s causing devices to go unavailable?
3. Does anyone have a good script that pings any device when the status becomes unavailable?

Thanks in advance for any suggestions or insights!

polar hollow
#

there are ping automations in the community forums

ember helm
#

Many of the devices have additional settings ( click configure under device info ) some of which configure their report frequency. Often if battery powered they ping every 1800 sec, it's possible to reduce it to 900sec or lower if you're willing to take a hit on battery life. Have you tried this to see if it resolves the lost nodes issue?