Over the last 2 days - I've been having strange behavior - Hub app on the android reporting in debug that cloud.hubitat can't be found (android presence failure) and other things but this one seems more strange:
However, hub is showing an update available (see sys msg in top right):
This could be to do with the pulling of update 123. I noticed that my hubs were showing the red (1) dot in the System messages, but when you click on it, it would then detect no update available (I'm running 2.3.0.121). I considered raising it with the HE dev's, but thought I'd leave it for now, it is Christmas
Oh, I didn't mean anything by my comment, for you or Bruce, only that I didn't want the dev's to feel it needed to be fixed straight away. In hindsight I should have just raised it and explained the urgency from my end, leaving it to HE to decide how quickly it should be fixed.
Have added the option to allow Hub Monitor to reboot the hub if the IP address changes to 169.254.x.x. Option is a per hub setting and appears after setting the Alert on IP Change to true.
To make sure you really want to do this, the Hub Information Driver must also have it's preference set to true.
Is there any way the status of the Zigbee and Z-wave radios could be included? I had my hub’s Zigbee radio go down and would like to auto reboot the hub in that circumstance.
Ah, just realized this rule is in legacy. I guess this is yet another case where I have to rebuild a rule to make use of the latest functionality. Grrr. Irritating.