I have a C8 Pro (purchased around this past Black Friday). Latest platform unless something released today. Woke up this morning and found that the web interface was not working.
I've tried different network and power cables.
I tried connecting to the diagnostic port (no response).
I had the hub IP setup static on my router but not in the hub settings. The router still showed the hub at the set IP address until I rebooted the router and now it's gone.
I tried the mobile app but it doesn't load fully (seemingly not connecting to the hub).
I tried the hidden button underneath the hub (no change)
I tried different browsers on different devices
I tried removing the static IP on the router, then reboot the hub and then the button underneath (hoping maybe the router has some other IP or was really using and by removing the IP assignment then the router would show the hub like it was a new device (with the actual IP)
I tried pinging the static IP (before that last bullet) and got not response
I tried find my hub, which discovered my hub at its static address but then can't connect
I tried hubitat.local with no luck
I tried remote admin from mobile app with no luck
The green light comes on and zwave related automations are running fine. I just cannot connect to it to administrate anything.
I have Hub Protect and should have cloud backups (like I said, I just got it in November and before that I didn't have the protect on my C7), but I haven't been checking.
Where do I go from here? Thanks in advance for the assistant.
If your hub is not available on your network, then access from the mobile app, and remote admin will not be available.
What device have you been using to attempt a connection to your hub (phone, PC, etc.). Is this device connected by ethernet or Wi-Fi?. Is this connection on the same VLAN/subnet as the hub? Is it on a guest Wi-Fi network?
If for some reason, the hub cannot connect to a router over the ethernet cable, it will create a Wi-Fi AP called mynewhubitat. Can you search for this SSID (using your phone). If it is found, it will confirm the hub is operational, and we can concentrate on why the ethernet connection is not working.
Chrome browser on my android phone. Had my wife try whatever browser she has on iPhone. Edge on my laptop (work). I get a "can't reach this page" error.
The hub is on Ethernet. No VLAN or subnet. I've been meaning to try and look into how to do that but I've not ventured into it yet. Not on the guest Network either.
From my phone I do see the mynewhubitat SSID. I was pretty sure the hub was operating based on the fact that lights were turning on with motion sensors and fans were turning on with humidity sensors and things like that. So I'm glad to see that there's a positive sign when it comes to that SSID. I'm all ears for what to do next.
You didn't say if these attempts were made over Wi-Fi or over ethernet.
I missed that information during my first read. That indicates that your hub is functioning.
If the mynewhubitat SSID is being broadcast, it suggests that your hub's ethernet interface has been unable to obtain a DHCP address from the router.
That may be because the cable is defective (I know you tried others), the port on the router is defective, or the router is not handing out a DHCP address for some reason.
You can test for all these possibilities with a single test. Plug that same cable into a PC, and confirm the PC gets a DHCP address, and is able to access the Internet . Of course the NIC in the PC must be configured to obtain a DHCP address, and it must not be configured with a static address.
EDIT: If the PC also has Wi-Fi access, disable it to make sure your Internet access is over the cable, and not over Wi-Fi. Alternatively, issue the "ipconfig" command at the command prompt, if you are familiar with interpreting the output.
Oops. The phone attempts were Wi-Fi. The laptop was Ethernet.
I'm following you on the component swapping to rule out whether it's the cable (and also the ipconfig to confirm which network adapter is connecting).
Will report back a little later
I seem to rely very heavily on setting my computers up with static IP addresses, so I didn't find one that wasn't static. I did remove the static setup in the router for the laptop, but it wouldn't change to a new IP (even with /release /renew and rebooting the router and the laptop).
I did swap the cable to my laptop (when I tried it before it was with my dock that is also wired, so it wasn't the same adapter). It gets an IP on the laptop quickly and I can ping internally and externally from the laptop. ipconfig shows it connecting to the ethernet and not Wi-Fi. I can also ping the laptop's IP from the ping tool in the router interface.
Out of curiosity I connected on the cell to that mynewhubitat SSID and it connected, but I was leery of continuing before getting further instructions...so here I am.
Edit: does this mean the NIC in the hub isn't working?
Just want to make sure the Ethernet cable was connected to the hub when you performed the network reset procedure
So just to be clear, you configured your laptops ETHERNET interface to use a DHCP address, and you removed the Ethernet cable from the Hubitat, and plugged that same cable into the laptop.
After restarting the laptop, the ipconfig command showed that both the Wi-Fi and Ethernet had both obtained addresses from your LAN, for example both were 192.168.1.x, and both showed the same gateway and netmask.
If that is the case, it appears that your Hubitat is not obtaining the address as it should.
You can try connecting to the mynewhubitat captive portal, and configuring the Hubitat to use Wi-Fi, or assign a static IP to the Ethernet port and see if it will work that way
Yes. It's fully coming back up and automations like motion lighting are working. Also, as the troubleshooting @Ricktronic pointed out, it's creating an SSID that can be seen in my phone's Wi-Fi settings called mynewhubitat which I took to mean it finished booting.
Yes. Both times (before and after attempting to remove the hub from my static IP listing in the router).
Yes, just like I tried to do with the hub this morning. The laptop never seemed to release the IP even though it is no longer static in the router (ipconfig said 'preferred' next to the IP address).
I turned off the Wi-Fi with the Windows interface, so Wi-Fi didn't pickup any IP, but basically, yes.
I'll try the Wi-Fi connection, but I presume that for a month-old device I probably should look into warranty?
Sounds like a good plan. If you can get the hub connected via WiFi, I would make sure to create a new Cloud Backup and also download a Local Backup to your laptop. Always good to have multiple backups.
(Note: the local backup file does not include the data needed to restore your Z-Wave and Zigbee radios - only the cloud backup does.)
If you cannot get the Ethernet port working again, I would then fill out a Hub Warranty request from the main Hubitat.com website Support section.
First... The SSID was a little finicky because it kept disappearing from the network list on my phone. I pressed the secret button a couple times, but once I timed it right, I could connect the hub to my Wi-Fi. It picked up a new IP address.
In the network settings I found the transfer from my older C7 had left a static IP setup in the hub as the old IP I used for the other hub. I changed this to the one I had been using for the new hub and then in the router matched it up and set it static there too. After this, it's connecting again on the IP that is using ethernet.
I'm not sure why this conflict of router static IP and hub static IP didn't show up for about a month, but maybe it happened after some sort of expiration of the IP address lease on the router? I get the impression you all probably know more about that than I do. I hadn't remembered setting up the static IP on the hub.
Now I see that both an ethernet and Wi-Fi address are running for the hub. Is this ok? Should I disconnect the Wi-Fi address again?
Thanks for all the help! I'm so glad it's just my oversight from the migration and not the hardware.
Although it is currently working with both connections for local access, this will cause problems in the future. Remote Admin, and Cloud dashboards, will likely become intermittent because the address registered at my.hubitat.com will be switching back and forth.
Both hub and router are configured static again (this time to the same address...again had no idea I had set it static on the old hub for it to get migrated over in the settings to the new one).
Resetting the hub, with the hidden button, should have cleared any existing network settings. Also If that static IP was within your LAN, then your new hub should have worked fine, unless of course the old hub was still connected, resulting in an IP conflict. So it appears that something "deeper" was going on, which will probably remain as unknown.
If your hub has a static IP, then it will not make a request to the router to obtain a DHCP address. Which makes the DHCP reservation redundant.
Well...I thought it was fixed, but the same problem seems to be occurring a week later (connecting to the web interface - presumably, at this point, due to the IP address having problems).
I've been trying to connect to the MyNewHubitat SSID. * If I connect too early (light is still blue, but the SSID appears on the phone) I get forwarded to a page showing the status of the hub rebooting, but then once it gets to 100% it hits a "page not found" error.
If I connect just after it turns green, my phone says "connected but no internet access" and it never takes me to the network's sign in page (the one that loaded before with the prompt to pick a Wi-Fi network).
I tried to reset with the button underneath 4 times this way, but no success connecting so that I could connect it to the Wi-Fi network. I have to head to work and can't troubleshoot until later today, but wanted to get the message added here. I wonder if there's something to make of the fact this seemed to happen a week apart (I can't say exactly a week but if it was, maybe that also helps in the troubleshooting).
