I recently broke my Z-Wave.me UZB stick and instead of getting a new Gen5 I decided to go for Gen7. The only problem is it’s virtually impossible to get for example an Aeotec Z-Stick 7 in Sweden right now, so I bit the bullet and got me a Silabs UZB-7 one instead. I knew there would be some caveats, but still. It was quite easy to get going and shows up perfectly fine in zwavejs2mqtt and HA, and I’ve paired up almost all my devices with S2 (which I had not really bothered with before).
The problem now is that I get intermittent outages on several of my Z-Wave endpoint devices. And it’s not just ones from a single manufacturer, but it can vary from time to time. It’s not uncommon for the devices to come back if I do a re-interview, but not always. I’ve now also had for example wall plugs (Qubino and Neo Coolcam) where if I push the physical “action button” on the breaker, it switches between on/off and it reports back to HA which also switches in the HA interface. But, if I use HA to toggle the switch, nothing happens on the physical switch, and then a few seconds later the interface in HA switches back.
I know the UZB-7 is meant to be used as a devboard, and as such is not intended to be used by end users. So with that in mind, I was wondering if anyone here has been using the UZB-7 as their “daily driver” and if so, have you tweaked any settings to improve reliability?
Does the controller see any “ghost nodes” that actually do not exist on the network? That can mess up the mesh routing and cause intermittent problems as devices try to route through non existent nodes.
UZB7 has been flawless for me for as long as I’ve been using it, which is probably nearly 10 months now.
There is a known issue with all 700-series controllers. I’m not sure the problem you’ve described is the same thing, but you might want to take a look and see if any of the criteria and symptoms apply to your situation. This problem would affect the entire network, not just some individual devices.
You could also try re-including the problematic devices insecurely, and see if it makes a difference, since you’ve changed at least two variables, insecure → S2 and 500-series to 700-series. Maybe the Qubino and Neo Coolcam devices have bad S2 implementations.
Thank you for the link! Yes, that looks very much like what I’m experiencing. I will go ahead and re-include some of the devices that I’ve had multiple problems with and hope for the best!
wow, so thankful I found your post (and thanks OP for starting this). This has been driving me bonkers! Only workaround for me is to unplug the Zooz 700 stick, plug it back in and restart the Z-Wave JS integration. But having to do this several times a day is a real problem.
I’m not sure how to proceed, but I’d like to see this some reference to this problem within the ZWave JS integration UI.
Thank you for that! I was in the later stages of migrating my network from a Zooz 500 Series to a Zooz 700 Series. I had just done minor testing on the 700 Series. I have decided to reverse course and wait for this 700 Series issue to play out first,
I am using a ZooZ 700 series controller and noticed in the last several weeks I’d have seemingly random nodes get marked as “dead” – and they nearly always come back with a simple “Ping” command on them from the ZWave JS to MQTT control panel UI. I’ve been pulling my hair out trying to find a cause in the logs and coming up short.
The weird thing is, my ZWave JS set-up had been the most reliable part of my entire set-up until this started happening a few weeks back. Nothing else really changed in my configuration.
Does this sound like it could be related to the issues with the 700-series controllers? Thanks all!
What you’re all describing sounds exactly like the problems I had in my Z-Wave network as well.
Fortunately, I happened upon an old Aeotec Z-Stick Gen5 (not plus, sadly) which I’ve migrated all my devices over to, and everything seems to be working again. I’ll be closely monitoring the Gen7 problem thread as I’d like to move back to my Gen7 stick again once they’re fixed.