I have tried both Firefox & Chrome, cleared cache many a time, powered off/on the hub (lost count), changed network cable three times -- no dice. The portal "Find Hub" fails. No luck with IP address nor with MAC. The blue light comes on within a minute of power on. My laptop runs Fedora version 32.
The hub is connected to TP Link Deco m9 Plus through a switch. The Deco tool shows the hub's MAC & gives it an unused IP address. The Deco tool does show no in/out traffic for the hub even when the "find" is churning.
Do I have a brick?
The blue light on a C-7 isn't promising; after the hub software loads, it should turn green. It seems like you know your hub's IP address or can find it in your router's management interface, so one thing you could try is the diagnostic tool instead of the main UI: http://YourHubIP:8081 (so port 8081 instead of the default). If you can get to the diagnostic tool, one of the tools available there might help, though otherwise it's at least a way to rule out most network problems since you can get to the hub.
This could explain why discovery also isn't working, though if you're using Chrome, I know there were problems with that a while back that I'm not sure if are fixed yet. Using another browser might help with that (but you don't need this tool if you already have the IP address). However, it still wouldn't explain why your LED never turns green.
If nothing helps, I'd suggest formally reaching out to support so they can assist further (and consider pointing them to this thread too), unless anyone else has other ideas you haven't tried.
1 Like
Thanks for the quick response. I was able to access the "http://IP:8081" page. I set the time to the current Zulu and rebooted the hub. I was able to "find" the hub through advanced discovery specifying the subnet. Pressing the hubitat icon brings "Unable to connect" to "https://192.168.68.104". Where does that put me?
Which browser? Connections are over http, not https
Some browsers will let you override and connect to http when you have specially tried to visit a secure page. Others might just reject your connection.
Firefox "found" the hub and refuses to let me use "http". Any idea how I could wiggle through? Pretty strange that hubitat cannot do "https". Chrome does not find the hub and does not allow me to use "http".
You could try http://yourHubIP:80, which might force your browser to use the correct protocol (and port) if you type the whole thing, but I've noticed new versions of Firefox look like they try HTTPS automatically if HTTPS fails. But I'm pretty sure Hubitat should respond on either, unless something changed recently (besides the ability to use your own cert so you don't get warnings).
I'm still concerned about the blue light. If it's not green, there is likely a problem.
1 Like
http://IP:80 -- nope. Firefox promptly puts https. I can get to port 8081 via http but not to 80. Light is blue, as it has always been. Power on was a few hours ago.
Tagging @gopher.ny in support, he will get you going.
Why is that strange? You are on your local lan. You don't need https.
Chrome doesn't block unsecured connections on the local lan. Just type the IP of the hub. Forget about http vs https
This is one of my four hubs connecting over http in Chrome.
However, all that aside, if you haven't got a green light on your hub, then it sounds like you're going to need to wait for further assistance from support.
5 Likes
Sent email to support. They sent me steps which got me through. Thanks (community) for the advice.
6 Likes
