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.
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:
and follow that process. That's the one that will detect the missing Platform OS and fetch another copy.
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."
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.
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?
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.
@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.
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?
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"
@tralexan thank you for the update yesterday in the email. I looked at your hub and based on the details provided and our preliminary research, you have successfully completed the factory recovery. Your hub joined your local network but when you click "register" to go out to download the platform, your hub never reaches the cloud to do so. This is likely restricted by your firewall settings or ISP. If you cannot get passed this problem, we could ship you another hub that has the platform pre-loaded so you don't have to go through this frustrating experience.
No, only the platform. The underlying Linux OS is not touched. I did a factory recovery last week (or maybe the week before), and the HE was pingable throughout the process - so there was at least a TCP/IP stack loaded, which I presume indicates the underlying OS.
I think I'm ready to double down on: The Factory Recover did not (yet) get an image because of a network issue.
I'm certainly not convinced I know what it is, but it's the elephant in the room at the moment.
Can you detail how your Hub is connected and the path it must take to the Internet? Is the hub directly connected to your ISP provided router, for example. Can it be? and so on...
