Zwave devices get unavailable

Configuration
1

Hello,

I do have a strange problem with zwave. I did find a kind of work-around, but I would like to know if there is a permanent solution.

I run HA in vm virtual box (on windows 10)
Home Assistant 2023.3.5
Supervisor 2023.03.2
Operating System 9.5
Zwave JS newest version (I think 0.1.77), but older versions did the same
Zwave stick: Aeotec Z-Wave USB Stick Z-stick 7, upgraded to 7.17.2

Every now and then connected devices get unavailable in HA. Specially when for example a switch has to go on or off.
My workaround is an automation that detects the unavailable state and then ping the device, what makes it available again, and turn the switch again on/off.
That works, but I think that should not be necessary, it should be stable in one or else way.

Had anyone this problem too and fixed it?
How can I fix this?

2

Problem seems to be fixed.

In zwave js UI I changed some unlogical routes. For example, one node was about 1 meter away from the controller and took a route all over the house; changed it to direct connect to controller).
Did do that more than a week ago and since then no problem anymore.

Maybe this helps somebody else too

3

Got here because I’m having the same problem with Zwave JS losing some nodes periodically, usually battery operated ones and ones on the edge of the Zwave network. Also using the Zooz 700. I’m not using the Zwave JS UI yet. Sounds like the UI gives the ability to modify the route, so worth switching to that.