Ever since I updated my C8 to 2.5.1.152 I have had the hardest time connecting to the hub. Both from phone app and from browser.....both local and remote it times out or has the hardest time connecting. Once it is connceted it works totaly fine and normal. And then maybe a day later, gives me a hard time to make the inital connection.
I have rebooted and no luck. Anyone else have this issue?
Is your hub on ethernet or wifi?
Do you have an address reservation set in your router for the Hubitat?
What are you using for network equipment in your home?
How do you fix the connection once it is down?
Ethernet
No address reservation set, but it does keep the same IP address after reboots.....every time I update, it does have a new IP address.
I have an Eero mesh network. All nodes have ethernet backhaul and are connected to eachother that way.
Time and repeated attempts is all I've sorted out how to fix it. Usually after about 5 mins of attempted connecting it works just fine.
I would definitely start with doing an address reservation.
So I have 2 hubs....a C8 and a C8 Pro (the pro is still on a slightly older HE OS version)
I just went into the Eero, and discovered the C8 has it's IP address listed with an IPv6 address only while the C8Pro is an IPV4 and an IPv6.
Having said that I am 100% able to access troublsome C8 the hub via a IPv4 address in a web browser.
I'm wondering if this is something to do with the issue. Somewhere in the update did the ethernet settings get a little out of whack?
Ok.....it wasn't letting me connect this morning. But I did figure out a way to get it to fix immedicatly.
From the Findmyhub.hubitat.com, I clicke on the "Discover hubs via mDNS search.
My 2 hubs were already listed below, but then 2 more popped up: "hubitat-1.lcoal" and hubitat.local".
Clicke the -1 one and it immediatly opened up my C8 at the IP address.....And then from there I could jsut use the IP addres again.
It is almost like the hub goes asleep and accessing it via IP address doesn't wont work until the hub is "awake"
I also have "Cloud connection is unavailable." as an alert.
Discovery #2.....it seems as if my software version reverted....partially.
After a reboot, it now shows my version as 5.1.147.......and No Updates Available.
FWIW, there are plenty of Hubitat users, like @Sebastien, who has eero mesh networks, and do not experience the issues described here.
One difference is that they have DHCP reservations for their Hubitat hubs. The Hubitat documentation recommends having a fixed IP address for the hub - be it via static assignment on a DHCP reservation.
I would encourage you to be persuaded by @neonturbo's suggestion, and the Hubitat documentation, to give your hubs fixed IP addresses - either via DHCP reservation (preferred) or static assignment.
I did the IP reservation immediately after his recommendation.
I'm now wonderig if i was never actually updated to 5.1.152.
Every once and a while my hub will say that it DOES see that update, but when I go to update it, it never is able to fully download the OS. I'm guessing when I "updated" to .152, it faild and I never went and checked.
Regardless of what version, this is really weird.
I'm going to try connecting via wifi and see if that changes how the hub operates.
Ok....connected via wifi and the hub was able to immediatly download and run the update. The "Cloud connection is unavailable" error went away too....Somthing weird with my ethernet setup.....odd thing it it has been untouched and unchanged for a few years now with never this issue.
Hmmmm..
