Solid Blue Light

[tralexan]

I have sent the following to Hubitat support 3 times over the past 2-3 weeks and have received no response. Can someone here please help:

We recently closed ticket #16152 after you sent me a replacement hub. But, I'm having problems getting the new one to install.

The hub is displaying a solid blue light without ever going to green and "find my hub" doesn't automatically find it. However, my router lists it at address 192.168.50.196 and if I go back to portal.hubitat.com and enter that IP under "advanced discovery", it says it finds it, displays a "Discovered Hub (192.168.50.196)" , but selecting it results in "Unable to Connect." And, it's never displayed under "my hubs."

I have changed the ethernet cable and used a different port on my switch and the results remain the same. Any other ideas?

all help would be appreciated,

[csteele]

You have a rare hub that doesn't believe it has the Platform OS available. It's an easy cure, although a bit time consuming.

[content modified by Hubitat Staff - if your hub displays a blue light, please first check our FAQ or send a PM to @support]

I detailed the steps, with screenshots here:

C5 Hub Can't be Discovered

I'm running the process again now.. hopefully I document it well THIS time It starts here: [Screen Shot 2020-05-19 at 1.40.06 PM] You click the button and you get this for under a minute: [Screen Shot 2020-05-19 at 1.37.12 PM] Then: [Screen Shot 2020-05-19 at 1.37.26 PM] After which, it returns to : [Screen Shot 2020-05-19 at 1.37.50 PM] Step one is done, time for... Step Two, power cycle - 30 seconds. I'm at the Blue LED so far... The Diagnostic Menu shows and it has …

C5 Hub Can't be Discovered

Glad to hear that you were able to get started. We are aware that a small number of users may experience this problem when setting up a new hub, and are actively investigating the root cause. This is certainly not the first impression we would like our users to have when registering their hubs. We are very sorry for the inconvenience that this may have caused to you or your family. Please let us know here in the community or via email at support@hubitat.com if you have any further questions or…

[kevin]

@tralexan

The hub is displaying a solid blue light without ever going to green

Is green even possible - all my 4 hubs show blue (plus one that doesn't light up at all since receipt) ?

[csteele]

C-5 vs C-4

C-4's only have Red and Blue

C-5's have Red, Blue and Green.

I've no idea why adding a 3rd color didn't go in the middle.. Engineers.. sheesh, right?

Working should be working and if that's blue, it should be Blue in all iterations.

But that's not how it is. Maybe Hubitat will fix this egregious error (LOL.. facetious, of course.)

[kevin]

ahh explains it - no C5's here (and no slowdowns...)

.. but yes ... inconsistent..

[SmartHomePrimer]

Has this replacement hub been registered?

https://docs.hubitat.com/index.php?title=Registration_and_setup

[tralexan]

I got the hub discovered by looking up the ip in my router.

I then used the link provided by csteele and managed a successful a factory reset followed by a OS update. Then the screen froze here ( I allowed over 30 minutes for something to happen) . . .

I then tried to access the hub using the ip and got this . . .

So, I am able successfully discover the hub by using the exact ip address in advanced discovery. I am able to access and do a factory reset when using the ip address along with a port number. But, accessing the hub after all is said and done fails.

And . . .the stubborn constant blue light is still there.

Any ideas are most welcome indeed.

--rick

[csteele]

The Hub doesn't need a static IP address, it's quite happy to use whatever address is available. Portal will tell you what it's using at the moment. However, things around it might care.. You for example. Hunting for an IP each time can be exhausting. So a Static IP helps you as well as other integrations you may eventually build out.

Factory RESET is not what we suggested and in this case, probably wouldn't help.... which is your conclusion too I think.

The blue light means the Platform OS is "missing". To get it back you perform the Factory RECOVERY (not reset) The "Update Tool" page you are showing is NOT part of the RECOVERY process.

Visit:
http:<yourHubIP>:8081 and observe the top most button. If it's:

Then click that and see if it streamlines the process.. If, after 30 mins you don't see the "Get Started" green page, then please go back to:

C5 Hub Can't be Discovered

I'm running the process again now.. hopefully I document it well THIS time It starts here: [Screen Shot 2020-05-19 at 1.40.06 PM] You click the button and you get this for under a minute: [Screen Shot 2020-05-19 at 1.37.12 PM] Then: [Screen Shot 2020-05-19 at 1.37.26 PM] After which, it returns to : [Screen Shot 2020-05-19 at 1.37.50 PM] Step one is done, time for... Step Two, power cycle - 30 seconds. I'm at the Blue LED so far... The Diagnostic Menu shows and it has …

and follow that process. That's the one that will detect the missing Platform OS and fetch another copy.

[tralexan]

I apologize, I did run "recovery" and not "reset." After "Download Latest Version" the diagnostic page appears as . . .

I do not, however, see the "Get Started" screen as shown in your example. and any attempt to access the hub using "http://192.168.50.196" without specifying a port results in "Unable to Connect."

[csteele]

Ok, the Hub is correct. It has an IP, it has a Platform OS.

The LED is???

using Portal.hubitat you can connect?

[tralexan]

The LED is blue.

At the portal, the hub is not listed at My Hubs . . .

It is listed at "Find Hubs" . . .

However, selecting "Found a New Hub" results an "Unable to Connect" message from the browser as shown in an image in a previous post.

thanks for your willingness to help,
--rick

[csteele]

Winner of the Weirdest Problem of the Week

http://192.168.50.196:80 fails
http://192.168.50.196:8081 works

For that to be true, something has to be blocking port 80 specifically. It's a network problem, you can leave the Hub alone for the next step.

In some form or another you have a 'firewall' functioning. Either on the PC you use to browse OR in some other piece of equipment. (You could have a Proxy set and it captures port 80 traffic but does not let that traffic 'u-turn' back into your network, for example.)

Can you please describe your 192.168.50.xx network?

[aaiyar]

@csteele

For that to be true, something has to be blocking port 80 specifically.

Huh? Or the platform isn't loaded. Unless I'm not understanding something (which is entirely possible). From my recollection port 80 and 8080 become available only after the platform is loaded.

[csteele]

the screen cap just a few posts above shows the platform is there:

Solid Blue Light

I apologize, I did run "recovery" and not "reset." After "Download Latest Version" the diagnostic page appears as . . . [diagnostic] I do not, however, see the "Get Started" screen as shown in your example. and any attempt to access the hub using "http://192.168.50.196" without specifying a port results in "Unable to Connect."

v2.2.1.116 seems acceptable

[aaiyar]

@csteele

v2.2.1.116 seems acceptable

Yup - I missed that. So the platform has downloaded, but isn't running?

[csteele]

@SmartHomePrimer suggests Registration is required to get Green. I have no idea on that. Because I've done the /factory/recovery from already registered hubs.. re-registering is darn near invisible, for me.

[markus]

Does http://192.168.50.196:8080 work? I don't see above if that was tested, don't know how the platform is implemented, but worth trying that on top of port 80?

Do https://192.168.50.196:8443 work?

[aaiyar]

@csteele

@SmartHomePrimer suggests Registration is required to get Green.

Doug is right. I had to do that .....

[csteele]

Ok, I think it's time for a review.

The (this year) reason for an always on Blue LED is the Platform OS is missing or corrupted.

Visiting http://192.168.50.196:8081/factory/recovery is going to delete/erase [everything Hubitat] from the hub including the platform os. It then visits Hubitat to get a new platform and register. So at the end of this step, you have no Platform OS.

Given what we're seeing, I'm wondering if the Hub is unable to reach Hubitat and never getting the Platform OS. That the Screen cap is just a cached detail.

The "found new hub" potentially is a result.. the Hub got to the Portal once, and never again.

We're still swirling around "There's a network problem"

[markus]

@csteele

including the platform os.

Is this confirmed? Does it really rewrite the whole OS? That can be a risky and complicated thing to do.

@csteele

"There's a network problem"

This would make a lot of sense