now i need to figure out how to fix my zigbee crash rule as apparently what you do to handle the situation on firmware update and zigbee being hosed (you can see your fix kicked in here on my problem hub), caused it to sense the zigbee down and reboot while rebooted lol..
1 Like
If you intend to keep this rule, you might want to insert a Wait for event (zigbeeOn) with a timeout (say 30 seconds) ... dunno about you but usually I see zigbeeOff followed by zigbeeOn 7-9 seconds later (a.k.a. zigbee "reboot"), and also usually happens during a cloud backup which may not be the greatest time to restart the hub
i would agree with you except this is a c7 not a c8 .... i have that rule on my c8.. but here never needed it.
I think Victor said (at some point recently) that his fix would have Zigbee back up within a minute or so. Maybe a 1m wait would be sufficient to catch a persistent loss of Zigbee...but really should wait for Victor's input...
I decided to do something like that...
But, after the timeout, I also check the "Hub Information" device's "zigbeeChannel" for "Not Available". If, for some reason, the on event doesn't get detected during the wait, I figure I'll throw out a message saying to check things out rather than restart.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
