Can't connect to C8 hub after new router

Why Hubitat Elevation Ask Anything
1

I attempted to contact Hubitat via email and received an auto-reply stating the mailbox is unmonitored.

I need assistance with a hub issue and require direct support.

Hub model: C8
I installed a new router and all was working fine for several day. Yesterday the hub stopped working. Hub boots to solid green.
Main UI intermittently loads but times out on backup.
Direct PC connection verified (manual IP).
findmyhub detects hub.
Diagnostic mode (:8081) times out even after forced reset attempts.
LED previously alternated red/green for >15 minutes.
Issue started after router reset and multiple power cycles.

I am at a loss and I will be going away for an extended time and all devices will not be working. Please help. Thank you

2

Are you using WiFi or Ethernet?
Are you using static IP address? If so, configured on the router or in the hub's network setup page?
Have you tried a network reset on the hub Network Setup | Hubitat Documentation

2 Likes
3

I am using ethernet. I have the ip address. I have even connected the pc to the hub with ethernet. I have tried to get the recovery tool but that times out also. This has never happened to me before. I also didn't know that when you do an update HE does a backup but it is not on my drive. Fortunately, I have an LZF file but from April 2025. I don't know what to do next. I have emailed support but the first email said that it doesn't monitor the box. So I am at a lost.

4

It is likely your hub is not at the IP address that the router expects it to be at. Or the hub has an APIPA address.

This is easy to resolve. Follow the network reset directions linked to earlier by @CaptWoody. The relevant section is cut & paste below as a screenshot.

image
image1920×986 99.8 KB

4 Likes
5

“I’ve tried all network isolation and direct PC connection steps. The hub boots to solid green, UI partially loads but times out, and backups are inaccessible. I’m pausing further action to avoid data loss and am requesting staff guidance on recovery mode or confirmation of corruption.”
I have reset it several times. I have done find my hub. I was able to open briefly HE and showed me my IP address. To reset I unplugged waited a minute plugged back in while holding reset for 15 seconds. I got to the point where the led would change from green to red. I believe that the hub is trying to reset. I waited 20 minutes but it went to solid green. I was expecting solid red.

6

Solid green is good.
Solid red is BAD.

2 Likes
7

This is not the reset procedure described above.

Also, have you tried a different network cable. They have been known to go bad.

5 Likes
8

I believe that is the way the lights are when you do a Recovery Process. I have had solid green but hub won't connect.

9

I think Hubitat Support will be the only ones that can help. If they don't reply I don't know what to do.

10

@aaiyar is next best thing to support but if you insist on waiting support will more than likely tell you to do the same thing. Again, that 7 second reset will reset your network settings which is more than likely the issue. If you search many people have had similar issues after changing routers. But again it is up to you if you want to wait for @support-agent

4 Likes
11

Thanks. I’ve already tested direct PC-to-hub Ethernet (APIPA), confirmed link and partial UI access. Given persistent UI timeouts and backup failures, I’m pausing resets and waiting for staff guidance on recovery mode.

12

No problem.

Could very well be your issue now as @aaiyar stated above. That is why the network reset was suggested.

Good luck.

3 Likes
13

There is no support email, I am not sure where you found such an email?

That is not true.

Maybe follow the suggestions from the experienced community members who have helpfully replied to you?

Please try that network reset as posted above. It doesn't sound like you did the correct procedure by holding the reset button for at least 7 seconds, releasing the button, then wait until the hub reboots.

4 Likes
14

Since this problem occurred after changing the router, it is almost certain to be that the IP address of the hub changed after connecting to the new router.

This would only occur if your Hub was configured to use a DHCP address, and not a static address. It would help in the diagnosis if you let us know more about the original configuration (static, DHCP, or DHCP reserved). Also are you running multiple LAN's or VLAN's or using any guest Wi-Fi networks (perhaps the PC is on a guest Wi-Fi network).

When the Hub was flashing red/green originally, that indicates the hub was not able to receive a DHCP address from the router. When the light turned solid green light, it indicates the Hub is connected to the network.

Assuming the hub was configured to obtain a DHCP address, I think the following happened.

You had reserved a DHCP address for the Hub on the old router, and that is why you always had access to it in the past, even after reboots. When you installed the new router, the Hub held the IP for "several days", but when it was time to renew the DHCP lease, your new router assigned a random address that you may not be aware of.

Although "findmyhub" should detect the hub, it may be providing some cached information, which also explains the partial loads of the UI.

  • You could login to the router and look at the DHCP assignments to locate the new IP
  • You could run Angry IP Scanner on a PC to find the new address
  • You could connect to my.hubitat,com to verify that your hub is on-line (Recent Last Checkin time), and what address it is using.

Checkin

When you connected the PC directly to the Hub, you shouldn't expect that to work, unless you had a static IP on the Hub and on the PC (each within the same subnet). You are aware of APIPA, but I have no idea how you would know the APIPA address of the Hub in order to establish a connection.

Also, after all the things you have done with your hub, we have no idea what state it is currently in. If you followed the proper instructions for resetting the network card, we would at least be in a known state to begin further trouble shooting.

4 Likes
15

Agree completely with your diagnosis. Also, unless the network reset button on this particular hub is not functional, there's no reason why an appropriately performed network reset would not have worked.

May also be from the browser cache.

3 Likes
16

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.