Well, in general Zwave is a rather reliable technology and does mesh, and you only use mains powered devices. There’s an only smallish probability that this is due to HW radio problems. So you need to find out why your specific installation shows that many that severe problems.
Most people use the Zwave binding and don’t have these problems. To me, it is likely that the z-way binding and layer is actually causing the problem.
Move over to the ZWave binding to see if problems persist. You could also start by deploying the dev version of the binding.
Migrating should be a rather simple task as you already have the OH items and the zwave network itself is not stored in the binding or other software entity but inside the controller (so all the nodes will still be there, no need for in/exclusion).
I’d also force a network heal from within habmin and display the network routes, but I’d assume it’s alright. Most devices will likely be able to directly talk to the controller.
If your problems persist after the move, you can enable binding debugging to start looking for the reason.
Chris (the zwave binding maintainer) has an online tool to dissect these logs and display the communication in graphical form. Helps tremendously to find out if there’s messages not being answered, repeated or delayed.
1 Like