Chronic Blue Light / Not connecting - Solved

I started writing this before I eventually solved the issue, and thought I would share it with the community in case it helps someone else experiencing the same issue.

Problem Statement
Plugged in Hubitat, and status light stuck on blue, never turned green.

My Network

  1. I have a Netgear Nighthawk router and have a gest network enabled.
  2. "Allow guests to see each other and access my local networks" was unchecked (off)
  3. The hubitat was connected to my router via a network switch.

Additional Symptoms / Troubleshooting

  1. Using find.hubitat.com would not find the hub, including the advanced methods.
  2. I could see that the hubitat was connected to my router and had an IP address assigned.
  3. The MAC address was also listed in my router
  4. Using the ip address, I could access diagnostics page at 192.168.1.27:8081 (your local ip address will be different)
  5. I could "log into" the diagnostics page with the MAC address.
  6. I could see the date time was set to Jan 1, 2015, and was able to update it and read it back.
  7. I was able to run the procedure documented in the FAQ page under "My hub shows a permanent blue light, now what?" (https://community.hubitat.com/t/frequently-asked-question-faq/5)
  8. A few times that "Update Failed", however, after a few power cycling, and using the "Reboot Hub", The update would Download (counting percent), and turned to "You will be automatically redirected to your Hubitat Elevation" , However unplugging for 15 seconds and re-plugging - still had blue light.
  9. I was on Platform version: 2.3.4.132 and Diagnostics version 1.0.92
  10. When I went to the ip address of the hubitat (without the 8081 port number), I would get a connection refused error with guidance to check firewall and router settings.
  11. I reserved the ip address of the hub in my router settings and rebooted both router and hub - did not make a difference.

What eventually worked
I was able to update to the latest version of the diagnostics tool by entering this into my browser
http://192.168.1.27/hub/cloud/updateDiagnosticTool (again, your IP will be different).

Note:

  • The address does not need the port number (8081), which surprised me.
  • The browser will appear to loading the page and not doing much for a minute or so (internet speed dependent). Eventually, the browser returned
    {"success":true,"message":"Diagnostics tool successfully updated."}
  • I could see the diagnostics page looked different and updated to 1.0.97
  • Abut the same time, I also decided to turn on ""Allow guests to see each other and access my local networks" from my router and save the changes.

... and voila, I was able to go through the find.hubitate.com page, it found the hub... and in disbelief, I walked over to where the hub was located, and the light was green

So, I am not 100% sure if was updating the diagnostics or the change to the gest network. I think it was the diagnostics update, as I changed the router back to keep my guest network isolated... and the guest network is wireless only.

I hope this experience helps at least one other user. Pictures attached. I blocked out the hub id. The ip address is local, no no real risk there.

I have screenshots, but since I am a new community member, I cannot include them. If I get "upgraded", I will try to update the post with links and screenshots.



2 Likes

Welcome!
If you join the owners group it should then let you post images: Hub owners - Hubitat
I believe it is to prevent any spam bots that get in here from posting images.

3 Likes

While updating the diagnostics certainly doesn’t hurt. this change would have been the one that made it possible to “speak” to your hub. Think of it this way: with the option turned off your hub was in a padded room with one window way up high to get light and sound; with the option turned on the hub would find itself in an auditorium with hundreds of its closest friends all chattering away….

2 Likes

I just find it strange. None of the other 44 devices on my network, including smart thermostats, smart vacuum, Phillips hue bulbs, SiliconDust HD HomeRun, Tesla Wall charger, computers, tv's, etc ever required changes to how I configured the guest network to be discovered and operate. None of my in home devices are connected to the guest network - the guest network is only for people who visit our home - i.e. for their phones to connect.

I would also think that a significant proportion of users have a guest network, and those that do have one, likely want to keep it isolated so guests don't go snooping around, looking for shared drives, home NAS or other devices. So it seams very risky that Hubitat would require that a guest network to be open, even when the hub itself is hard wired into a homes main (non guest) network.

I may do some experimentation. I did turn back on the guest network isolation from my home network, and I can still reach the hub. May try a hard reset and just see if the constant blue light problem re-appears.

The only other possibility was perhaps impatience. I did wit for probably 10 min for the blue to turn green. I assumed that was enough... Is it? Some more visual cues on would help - say a blink blue light would mean "hang on, I am still in some booting ot stage"...

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.