Just switched from Wink, New HE hub. Out of the box got a solid blue light, chrome and edge unable to find hub on web interface. Searched this community and found the (awesome) wiki style instructions for diagnostic tool... Through router saw that an IP was assigned to the hub, so I entered the IP into browser... nothing. Then entered IP:8081 (diagnostic tool) and it 'worked', meaning I got the diagnostic home screen. After attempted reboot, the status is stuck on "Waiting for hub to reboot". Help!
Not the best out of box experience. [eek!]
Try pulling power on the hub at the wall (USB port on the hub can be a little fragile) and wait 30s then plug it in again.
2 Likes
Report back if pulling the plug worked or not. There are some further steps you can try if that doesn't do the trick.
Edit: and once you get it up and running normal, don't pull the plug again. There is a way to do a graceful shutdown or reboot. Pulling the plug can corrupt the database, so it isn't suggested to regularly do so. This is an "emergency" and a blank hub, so it is probably OK to do.
2 Likes
Absolutely correct, I should have mentioned that this normally is a bad thing to do! 
When it comes up, if it sticks on blue, go back to the diagnostic page at 8081 and tell us what version the hub says it's on.
2 Likes
And Diagnostic tool version too. There was an update a while back for that.
2 Likes
Here's the version(s)... Yes I saw that about power when researching what was going on initially. About 10m since plugged back in and still blue light:
Hub Information
Platform Version:
hub-2.2.4.158
Hardware Version:
Rev C-7
Hub ID:
XXREMOVEDXX
IP Address:
192.168.1.24
Diagnostic Tool Version:
1.0.75
Try updating the diagnostic tool. 192.168.1.24/hub/cloud/updateDiagnosticTool
Then reboot from the :8081 menu.
1 Like
"Refused to Connect" error, but still can access :8081 menu after attempt
Hmm.
Try a soft reset. It won't hurt to do this, but might help.
I was assuming your IP was 192.168.1.24 by your screenshot, but if your hub is actually on a different address, use that instead if and when you get done trying the soft reset.
You should have got something more like this from the diagnostic tool update.
{"success":true,"message":"No Update for Diagnostic Tool Available."}
At some point you should remove your Hub ID from the post - best not to share that to the interweb. 
2 Likes
Just doublechecked; I've got the IP correct.... Soft reset yields "Unknown Error Occurred" and spinning green wheel.
I usually have the best of luck with 'new toys', I guess it was just my time haha.
1 Like
How is this connected to the internet? Can you try direct to the modem, or another port on the router, or a different router or something?
I have it on a Netgear mesh satellite; the same satellite as the PC I'm working from (my home office). I'll try from the 'main' router and see if that changes anything. My network is pretty simple, Cable modem->Netgear Orbi Router- - - ->Satellites
Sometimes Netgear doesn't play nice initially with Hubitat. There is a setting to change that, but I don't know if it works without the hub running. Try the main router first and see what happens.
Same result, "Unknown Error Occurred"
I should have clarified; Put on main router and opened :8081 menu, then tried soft reset
HMM. I am pretty much out of tricks. @danabw anything from you?
@support_team probably would be the best option at this point. They should see this, but I would also start a trouble ticket by emailing support@hubitat.com with the information you posted above and what steps you took.
Hang tight, it usually isn't like this! Things will get better, trust me.
1 Like
