My z-wave mesh is solid and my Hubitat is awesome. I have several Zooz wall remotes. Sometime after a recent upgrade, possibly before the "Enable Command Retry Logic" and "Multiple Conditional Triggers on the same device" updates, the behavior for these wall remotes changed.... only after a reboot.
After my Hubitat is rebooted, it ALWAYS takes two or three presses on EACH wall remote for any action to be triggered for that specific wall remote. Even if I wait one hour or more after reboot, each wall-remote press does not work on the first try. In fact, the first one or two presses on the wall remote do not show in the "Live Logs" or "Past Logs". After the first one or two presses, everything is good again and the wall remotes work exactly as they should (logging the press and instantly triggering actions). This issue is consistently repeatable and only occurs after a hub reboot.
Is anyone else experiencing this same behavior after a hub reboot? Is there a solution?
Configuration: C-8, Firmware 2.4.1.177, Built-In Driver "Zooz Remote Switch Zen34", User Driver "Zen37 Wall Remote Advanced", Button Controller 5.1
@Teraflop
Yep...sounds very familiar. I do think there is some issue with the C-8 Hub or the software.
Let me know if you get any help or figure out how to fix it.
I assume since its not a Pro hub you have not switched to Zwave JS?
Are the devices paired to the hub as Mesh devices or Long Range?
If mesh, this could simply be the case of the device trying to reroute after reboot.
Obligatory request for more information:
I have not switched to ZwaveJS because this is not a Pro hub.
The 700 series are paired as mesh and the LR devices are paired LR. Both exhibit the same behavior.
The hub will run for more than 2 weeks without any issues. The hub has been up without a reboot or more than 24 hours. The only issue occurs after reboot. All of the Zooz wall switches must be pressed two or three times before any trigger events occur or events show in the log file.
Below are the Z-Wave details. Note those devices that have not responded are disabled.
Thank you for taking the time to review this issue.
It does not look like the stats are refreshed. No RTT and route changes are all 0. May not tell us anything useful though.
All those devices are active? You hid the device names so it’s impossible to tell on the ones with no messages.
Don’t have any other advice but that info is good for staff to see to help understand what the issue might be.
Thanks for reviewing the data. Yes, all of those devices are active with the exception of those with no messages that are "disabled" in the devices list.
All that does is prevent the hub from processing messages from it. So they are essentially the same a ghost/dead node like this.
Can you plug all the mesh ones in for a test (any that are mains powered)?
Not sure why it would be impacting the LR devices but for sure the mesh ones I could see the hub taking a few tries of re routing to figure things out with all those devices missing.
Just updated the firmware on my C8Pro to latest.
Should do a reboot as part of process.
No problem with a ZEN34LR device I tried.
I use 4 Zen 34s. The hub is a C8-Pro with ZWJS enabled. The 34s are included using LR. Made sense to do LR for devices which can move around. They all work first time after a hub reboot.
On a side note, I use one as a gate/garage opener. Great range.
