The SDK from Silicon Labs (the people behind Z-Wave) had many issues. Z-Wave.me has been good at releasing firmware updates after Silicon Labs updates their SDK. The latest firmware fixed many issues. The issues you faced, we all have had. Which is why the goto is update the firmware rather than trying to use a bandaid fix resetting something. Resetting might make things work again, but doesn't fix the root cause of them.
I had alerts everyday of loss communication and the latest firmware has resolved all of them.
Needing a hard reset after certain z-way-server crashes
Re: Needing a hard reset after certain z-way-server crashes
The distant Fibarro motion sensor has now settled down and the last 6 wake-up communications have all been 60 msec except one at 150. So all much much better.
I also upgraded ZWay to v4.1.4 (from something like v4.1.0 but I didn't check). I tried upgrading a year ago and found that both my Fibarro motion sensors were not triggering the software that switched on the heating. I reverted. This time it works, so the bug is fixed.
I also upgraded ZWay to v4.1.4 (from something like v4.1.0 but I didn't check). I tried upgrading a year ago and found that both my Fibarro motion sensors were not triggering the software that switched on the heating. I reverted. This time it works, so the bug is fixed.