Hubitat Hub Controller

Ok... so do you currently see any ZigbeeOff location events in the Logs > Location tab?

That should be the only way the rule would trigger, and thus the only way the rule would reboot the hub.

I am not saying there is not an issue, but I fail to see how that virtual device driver is causing the issue when you already have determined it is something with the rule causing the reboots. Either the update is causing a false ZigbeeOff event, or the update broke your rule in some other way.

If you change over to Hub Info v3, it is going to give you access to the exact same reboot command which will not solve whatever problem you are having with the rule. Its going to do the exact same thing.

1 Like