Hub: Hubitat C-8 Pro Firmware: 2.5.2.139 Z-Wave stack: Z-Wave JS
I've experienced problems with three different Zooz devices and am wondering whether there may be a Z-Wave JS or platform issue in the 2.5.2.x firmware series.
These devices have been rock solid for over a year, then after the FW update to 2.5.2.x they each failed.
The three incidents were:
Zooz ZEN52: The device went offline and would not recover until I power-cycled it.
Zooz ZEN51: The device somehow became excluded from my Z-Wave network. I don't know what caused the exclusion.
Zooz garage-door controller (Zen17): The #2 contact sensor stopped reporting its state correctly and required a power cycle to restore normal operation.
All of these devices are LR inclusion.
All three issues involved Zooz devices, and two required power cycling to recover.
Has anyone else running a C-8 Pro with Z-Wave JS experienced similar problems on 2.5.2.139 or earlier 2.5.2.x releases?
I'm particularly interested in whether there are any known Z-Wave JS issues involving devices becoming unresponsive, unexpected exclusions, or contact-state reports stopping or becoming incorrect.
>>> 1. go through Z-Wave power cycle. Shut down Hubitat, unplug for 20 seconds, plug it back in.
I've done this already, here was my sequence:
Upgraded the hub to 2.5.2.x (I'm not sure exactly which firmware version I was running before the upgrade).
The next day or so, I noticed that a ZEN52 wasn't responding.
Shut down the hub, unplugged it for over a minute, and rebooted.
Later, I noticed the same problem with the ZEN51 and ZEN17.
>>> 2. Make sure your Zooz device firmware is up to date. They've released a lot of new firmware this year.
Yes, I keep a pretty close eye on the Zooz firmware release page, and all of my Zooz devices are running the latest firmware.
I also wanted to add that all three of these devices are included via Z-Wave Long Range (LR).
It's been a few days now without any additional failures, but I'm still concerned that these unexplained failures could happen again.
Given the long history of stability and the fact that these failures started shortly after the firmware update, I'm wondering if there could be an issue with the 2.5.2.x firmware or its handling of LR devices.
I'd suggest asking for help from the staff before downgrading. They'd probably ask for Z-Wave logs from the failure time. They keep on making Z-Wave JS better and there is even more new stuff in the beta releases (you could also join the beta channel)
@bcopeland@bill.d - I've downgraded to 2.5.1.183 just to re-establish a baseline. I'll let it run for a week. If it's stable again, I can upgrade back to the latest 2.5.2.x and see if the failures start happening again.
To tell you a little bit about my z-wave network, I have a total of 76 devices, 58 are LR, 18 are mesh. Of the 76 devices, 55 of them are Zooz.
I've had trouble in the past with some of the Zooz devices going offline, but have worked with Zooz directly and for the past year or so, they have been very stable. I frequently look at the Settings=>Z-wave Details page and sort it by status to see if there are any "Pending" devices. I will monitor this closing for the next 7 days. From time to time, there is a pending device, but if I click "Refresh" is will change to a check mark.
The difference with Pending devices on 2.5.2.x is that the refresh was never able to recover the devices and I had to power cycle the device to get it to recover. One of the ZEN52 devices when it failed, didn't respond to the physical light switch, which indicates it's FW is in a bad state. So it feel like something in the new FW/ZWave-JS version is doing something that the Zooz devices don't like and getting them in a bad state (or even causing them to become excluded). It's interesting that it has only affect the ZEN51 and ZEN52 devices (which the exception of my garage door controller ZEN17).