Today there is NO indication that the hub is unable to communicate with the internet.
I know that all the zigbee and zwave stuff will continue to run but it would be great to
have a quick visual that there is something wrong. I don't care if its a different color
or what.... just that I can tell that its not connected.
1 Like
Could setup a rule to do a periodic ping to somewhere on the net and if the ping fails then the connection is probably down.
Similar to this. I use it as a power outage tester. I ping a kasa wifi plug if it fails to reply I then ping my bond hub. If they both are failing I assume it's the power and not one device that is upgrading or just down at the moment. You could do the same with some internet addresses instead of local devices.
1 Like
To add on to @tivomaniac automation, you can add a HSM 200 to the hub and flash it’s light green if you’ld like. Plus put in into an outlet that’s more visible then where your hub lives.
https://docs.homeseer.com/products/sensors/hsm200/hsm200-user-guide
1 Like
Thanks for the ideas! I never heard of the HSM200 ....looked it up... around $50-60
Hoping the hub can do the work for me for free : ) (has all the info to do).
I am thinking in the mean time I could flash a zwave light in the kitchen when the hub cannot ping.
Thx!
Yup you could blink any light at all. So fun to experiment. 
Setup @thebearmay 's ping utility. On failure of something like 1.1.1.1 or 8.8.8.8 for more than 4 tries, flash every single light in the house until muted. (Not responsible for spousal vocality rising)
3 Likes
This would of course only happen when said spouse is home and you are not.
2 Likes
Shhhhhh....
2 Likes
Meh - flash them until internet connectivity is restored. And plan the outage to occur while you're on a work trip.
3 Likes
What we really need is some automatic internet/name resolution check, sometimes you can ping an IP but not resolve a name. I assume the hub reaches out and tries to connect to the cloud systems at a regular interval? Some sort of warning that it cannot connect might be useful. This would test connection and DNS at the same time. It could be a setting that can be disabled in the networking settings for people who dont want it or run totally offline.
It could probably be setup with the ping, just ping a domain and not an IP.
Something built in though would help with all the new people who manage to setup a static IP wrong and break DNS.
8.8.8.8 (Google) does not respond to ping, but 1.1.1.1 (cloudflare) will.
Or ping the domain one.one.one.one which will also test if DNS is working.
Guess I never tried it from my PC, but from the hub it does not for some reason. Anything else I try from the hub works but never 8.8.8.8, I just figured google was blocking it.
Hmmm. Me too. Never noticed that before. @gopher.ny Any insight?
I just learned something useful and I will be implementing this idea.
I was thinking of pinging 1.1.1.1 to keep an eye on the internet status. Is pinging at 5-minute intervals too much? What would be a preferred interval, if it is?
I created the Hubitat ping device to 8.8.8.8 and then use "The Flasher" app with the ping device not present as a trigger to flash the kitchen light... I tried to write a webcore to flash the light but "The Flasher" app was exactly what I needed.
I would ping one.one.one.one which will test DNS and also the connection at the same time.
Every 5 minutes should be fine.
If you want to exercise the DNS lookup, might try:
https://raw.githubusercontent.com/thebearmay/hubitat/main/nslookup.groovy
1 Like
Great shares. Thank you.
1 Like
