I'm re-pinging every 10 minutes.
Would that be good?
Like most things, I tend to adopt the POV that.... it's complicated.... Not to say you have to adopt the same viewpoint...
If, for example, you take the hardline approach, that even a single miss of a ping response, what happens if you restart the hub manually after a platform release... And the ping check kicks in...
I give you an easy answer, at least one that I can easily construct at the moment... I would encourage you to think about it some more and once you feel you have something that handles some common scenarios you have faced in the past, then look at how to handle those. Don't rush into it....
1 Like
I felt that way with my gate automation, until it got crumpled by a truck while closing!
1 Like
But seriously, it's very hard to dream up all the different scenarios. This rule would be by definition drastic, since there would be no question of gracefully shutting down the production hub-it would be a brute force power cycle.
Perhaps, rather than doing a last ditch power cycle autonomously, it would be better to have the C-7 do a Pushover notification and let the operator, (me), remotely power cycle the C-8 production hub.
On a side note, what does the alternating red/green light on the hub actually mean?
It seemed that it continued to flash even while reconnected, but went solid green when I brought up a page for that hub.
Exactly.... 
On another side note, it's cool that I can't tell that the hub is disconnected from the web. Everything works as it should (except maybe Envisalink, my only cloud based integration.
Similar to my earlier comments, connectivity of any kind can be affected or report as down for various reasons that don't always mean what you expect them to be. Being unable to connect to one cloud service does not mean you don't have any cloud connectivity.
1 Like
I can tend to come across as a little negative or downplay others ideas in this situation. I'd re-interate my comment earlier that I don't want to completely dismiss the idea of monitoring and responding to that. It is not wrong or somehow a waste of time to keep tabs on the status of various aspects of the HE hub's access or responsiveness to requests. It is just that I suggest understanding or expecting limitations in what some kinds of monitoring can deliver, accepting this and accounting for it in how these approaches are implemented.
That sounds really wordy.... No solution is perfect, try something, post about it, seek comments here on the Community and evolve the solution. It's nothing new in this space....
1 Like
I've just seen a fair number of "I'm out of town and my hub is non-responsive" kind of comments. An autonomous graceful shutdown (where the hub can still communicate) and power cycle seems to be hard to come by. Many people might have a spare hub laying around. So....
This ping thing would be a last ditch thing.
1 Like
Just go in with your eyes wide open, so-to-speek... which I think you are now... Keep an eye on whatever you decide to setup and review any "incidents" to see how the logic holds up for your setup.
2 Likes
I have chosen a solution very much in line with what @sburke781 has suggested. I have Node-RED running on a separate platform. It monitors all of my Hubitat hubs and then simply sends me a Pushover notification to let me know there may be a problem with a hub not responding. (Note: I use Pushover directly within Node-RED, so as not to need to rely on Hubitat for anything.)
When I get a notification (usually only when I am doing some HE hub maintenance), I can then connect into my UniFi home network (via Wireguard VPN if offsite), and then troubleshoot the issue. If necessary, I can power cycle my Hubitat hubs via the UniFi console as I use PoE splitters to power each HE hub, as well as my Lutron Caseta and Phlips Hue hubs. And since my UniFi network hardware is on UPS, so are my home automation hubs.
Like @sburke781, I am not trying to dissuade you from your goal. Just trying to point out that what initially may seem like a simple task, often ends up to be much, much more complicated due to all of the edge cases that are hard to foresee. This is exactly why my garage door openers have no automation whatsoever as well. Too much risk with them either opening or closing when not desired. However, I do have manual control over them via Hubitat.
2 Likes
I agree, however, I would think that something like a Z-wave radio crash would be a little more cut and dried. I haven't been able to simulate that.
ZigbeeRadioOff, yes, that can be induced. But if it were permanent, say > 10 minutes, I think it also would be straightforward.
Not so the Ping Thing.
You have Node Red on a separate platform. I have a spare Hub.
I think I'll wire up a spare ZEN16 relay. Power the relay with 5vdc usb from a battery, then hook up a separate 5vdc usb from the battery that is interrupted by the relay.
Well, I did it without smoking the hub.
Onward to the rules...later.
I have a switch on the C-8 dashboard to gracefully shut it down and then power cycle.
Next stop, rules.
I figure Z-wave crash for sure.
And Zigbee radio off for more than a minute.
1 Like
As an update:
I have Z-Wave crash and Zigbee radio off for more than five minutes. It took 1.5 minutes to reboot once, so I extended it.
I just added a memory low rule. I'm reluctant to use the fine Hub Info app because I'm paranoid about using too much memory, I don't know what I'm doing with it, and I'm only interested, for now, in memory.
I read in another thread about doing a GET for the free memory and storing it in a local string variable. I converted it to a hub variable number and made a rule so that if it went below 175000, it would do its thing.
I'm including the stuff below not only for others, because I'm sure it's not that complex, but for my future reference.
1 Like
I also have a tile that refreshes hourly:
Can you provide some detail on the adapters you used for PoE to the Caseta, Hue and HE hubs? I am all UniFi and really like this idea...
I have been using the Utronics PoE Splitters found on Amazon.
For USB-C - https://www.amazon.com/gp/product/B087F4QCTR (Hubitat C-8 Hub)
For microUSB - https://www.amazon.com/gp/product/B07CNKX14C (Hubitat C-5/C-7 Hub, Lutron Caseta Smartbridge Pro)
The Philips Hue bridge needs a barrel connector, I bought some microUSB to Barrel adapters. I found them on eBay - similar to DC 5.5x2.1mm Male Plug To Micro USB Female Connector Adapter Charge Converter-r- | eBay (the exact ones that I bought are no longer being sold.)
These days, I would probably try to buy USB-C to 5.5/2.1mm barrel connector adapters to be used with USB-C PoE adapters, as more and more devices are now USB-C instead of microUSB.
