Hub Not Reachable

🛎️ Get Help
1

Hi All,

Today my hub became unreachable, and HomeKit went unresponsive. And I have to restart the Hub to make all devices activate.

Now again, it went not reachable; when I entered the Hub IP nothing opened. But HomeKit is working. Also, I get the notification HPM package update is available, but when I click that, nothing opens, and that is how I discovered it is not reachable via IP.

How to find what is causing this issue and how to report this bug as well?

2

If the hub is unreachable via its IP how are you getting a notification from HPM? Is it just a stale browser session that's still open? That would make sense if the hub is no longer responding on the same IP address.

What color is the hub's LED? Can you ping the hub at its last known IP address? And do you have a reservation for the hub configured in your router's DHCP server? And are your automations still running as far as you can tell?

In most cases like this the issue is the hub has grabbed a different IP address. It's still running fine, but the URL has changed. If that's the case the best way is to open your router's DHCP table and make sure the hub has a reserved IP address. This will prevent it from changing periodically.

If that's not the issue we'll need to look further.

2 Likes
3

I believe the notification is from cache may be as like you said.

And Yes, it grabbed a new IP. But none of my other devices keep changing IP. Any idea why it changed the IP ?

4

Could be lots of things. But the way to avoid it is just to create a DHCP reservation. That way it will always grab the same IP address. Good practice for any other hubs you have too.

2 Likes
5

Your router assigned the hub a new ip address when you cycled the power to the hub.
Set a static ip address with your router.

1 Like
6

Static

DHCP reservation and static IP address aren’t exactly the same thing.

Of the two, @brad5’s suggestion is simpler and likely the right solution for most users.

2 Likes
7

@Siddharth If you do set a static ip, make sure you set your DNS to 1.1.1.1, 8.8.8.8 (or other valid DNS setting) manually as it may look like it's in there but it's not. If you don't do this for the static setting you won't get to the internet.

1 Like
8

I used to use the two terms interchangeably too. The practical difference is a static IP is set at the client level and a DHCP reservation is set at the DHCP server level. Setting it at the DHCP server level allows all of your fixed IPs to be administered and tracked from one location and avoids the situation where you inadvertently assign a device a static IP within the DHCP range and poof - duplicate IPs.

6 Likes
9

This is one reason why I suggest using DHCP reservation. No need to worry about the DNS server assignments, DHCP does that automatically.

@brad5 brings up another good point. It’s possible to inadvertently set a conflicting address when configuring static IPs on individual devices. With DHCP reservations, the router won’t do that.

2 Likes
10

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