Overnight my Eero mesh Wi-Fi system performed a firmware update. All of my devices have static IP reservations assigned through Eero.
This morning I discovered that I can no longer connect to the cloud portion of Hubitat. My local dashboards and local access are working fine, but all cloud dashboards and cloud connectivity appear to be down.
So far I have:
Power cycled the modem/router and Eero mesh network
Unplugged the Hubitat C-7 for approximately 10 minutes
Performed a Hubitat network reset
Performed a DNS reset
Rebooted the hub
Restored a backup
Performed a database rebuild and history cleanup
Despite all of that, the issue persists.
All other devices on my network are connecting to the internet and cloud services without any problems.
One additional observation: when I perform a network discovery, Hubitat reports a 169.x.x.x address. However, I am still able to access and configure the hub locally using its assigned IP address of 192.168.4.103.
Has anyone experienced something similar after an Eero update, or is there anything else I should check?
This address simply means it assigned itself an IP address because it was unable to request and receive an IP address from the DHCP server (your router).
What version of eero did you update to? Mine seems fine, but may not have updated yet.
I just now did that update for my Eero (small house, so we have just a single Max 7), and it went fine... All my stuff has reconnected OK, including my HE’s cloud connection.
Are you using both a DHCP reservation (set in Eero) and a Static IP (set in HE)?
IIRC, doing both can be problematic (not an issue unique to Eero)…. I’ve only ever used DHCP reservations for all my stuff on Eero – I’ve never messed with Static IPs for anything.
I’ve done every test possible, but thanks for responding and all my other devices came back online as well after the update. This has been my setup for 7 years.
Only DHCP reservations is on all my stuff on Eero, not on the device, but I did troubleshoot by DHCP on Eero and Static on the Hubitat device same results.
What concerns me is that screenshot you have for “Switch to Static IP”. I’ve never seen it. The whole point of DHCP is to have the host do the client configuration. I’d think any attempt to designate an IP address, gateway, DNS server, etc. on the client itself is only asking for trouble.
The reason I suggested trying wi-fi is to simulate the situation where nothing is configured on the client side and it should just work. You could even set a reservation on the router for it and run that way for a while.
I will be upgrading my eeroOS to v7.15.0-9714 overnight. Is that the version that started this problem for you?
So the Static IP set was during one of the troubleshooting steps, it has since been released in both Eero and Hubitat. Yes its version eeroOS v7.15.0-9714
Your ping test to google.com is saying your DNS server is not providing the IP for google.com.
That could be because your DNS server is not providing the information, or the Internet is not accessible, and a DNS server cannot be reached.
You need to determine if you only have a DNS problem, or if you truly have no access to the Internet.
First test if you have access to the Internet by pinging 8.8.8.8. If that works then you have confirmed Internet access is available, and your problem is with the DNS server
Normally another way of confirming Internet access is to go to https://my.hubitat.com. After logging in, click on Registered Hubs, and then Hub Details. Scroll down to "Last Check in" to see if recent communication has taken place. However if your DNS server is not working, as I expect, then "Last Checkin" will be quite old.
Your traceroute test also shows you have a double NAT situation. Depending on how you use your network, that is normally something you don't want. You have probably had this all along, and therefore I don't believe that is causing this problem.
I have re-read your original post, and I don't see any mention if you are using an Ethernet or a Wi-Fi connection. When @HAL9000 suggested switching to Wi-Fi you still didn't say what you were using.
Either way, open network settings and confirm hubs IP address, and if the address has been obtained by DHCP (if you are using an ethernet connection)
Also open the "Override DNS Settings" section and make sure you are using the router provided DNS servers.
.
.
.
The extra hub is because of the self-assigned IP address. Once the hub is able to pick up its proper IP address from the router, that one should go away.
My eero mesh is now running 7.15.0-9714 and not having issues.
Here’s my Advanced Networking on the eero if you want to compare. The eero gets its gateway address on the ISP side from the ISP. It presents a non-routable local IP address for the gateway to the local network side.
As I said earlier, the error regarding DNS may be because of a bad DNS configuration or DNS server, or your hub may not have Internet access at all, preventing a connection to a DNS server.
Please try pinging an IP such as 8.8.8.8 rather than google.com like you did before.
Your traceroute test seems to show that you do have access to your ISP router and the Internet.
That proves that all aspects of networking are correct except DNS. If you had previously overrode the DNS server settings with 8.8.8.8, then the problem would definitely be the hub, because now we know the DNS server is available.
Alternatively, since your hub is using DHCP, simply plug it into the Verizon router to determine if the problem is in the Eero, or in the hub (most likely)
If the problem proves to be in the hub, then reset the network settings again. If the problem only occurs on the Eero connection, we will worry about that later.
