I recently swapped out my network equipment. I was using UniFi APs, switches, and a UDM-Pro. I am now using Eero Pro 6 and an unmanaged switch.
ESPHome now shows all of my nodes as “Offline”. If I use the visit button on each node from the dashboard, it opens the page correctly and I can interact with the node.
I can click the logs button on the dashboard and it will connect and show me logs directly from the node. The node responds to ping and nslookup via hostname from my computer on the same network. The node can also be seen by and controlled from HA regardless of IP address (static or DHCP). It’s just the dashboard for ESPHome is saying the node is offline which is preventing me from doing OTA updates.
My setup is this:
- ESPHome (2022.3.0) and HA (2022.3.5) in docker on a Synology NAS
- ESPHome docker using ports (opened 6123 and 6052)
- ESPHome docker with variable
- HA docker using
- “Flat” network architecture, no VLANs, no guest wireless networks, everything in the same subnet
- ESPHome nodes are a mix of ESP8266 and ESP32
- ESPHome nodes have a DHCP reservation
Things I have tried:
- All nodes have static IP addresses assigned through a DHCP reservation, but this also occurs when they just receive a random IP address. HA can still talk to them, but ESPHome dashboard shows it is offline
- Reconfigured ESPHome docker container to use
--net=host, but there was no change and nodes still show as offline
- created a brand new node with a basic configuration. it connects to my WiFi and HA says it found a new device, but ESPHome dashboard still shows it is offline.
- downgraded ESPHome docker to 2022.2.5 which is what I was running before I swapped my network equipment and the dashboard still shows the nodes as offline.
I’m starting to think Eero is doing something with mDNS/Avahi. Has anyone else encountered this before or have any ideas I can try out?
The error I get when attempting an OTA update is:
======================== [SUCCESS] Took 124.96 seconds ======================== INFO Successfully compiled program. INFO Resolving IP address of office_cabinet_lights.local ERROR Error resolving IP address of office_cabinet_lights.local. Is it connected to WiFi? ERROR (If this error persists, please set a static IP address: https://esphome.io/components/wifi.html#manual-ips) ERROR Error resolving IP address: Error resolving address with mDNS: Did not respond. Maybe the device is offline., [Errno -2] Name or service not known
If I go to the node “office_cabinet_lights.local” in a browser, it connects and I can interact with the node. I have also tried this with a node that has a one word name (I’ve seen the warnings about using underscores in a name) and the dashboard still cannot find the node or resolve the name, but otherwise the node is working.
This is the error when trying to connect to view logs from the ESPHome dashboard:
INFO Starting log output from office_cabinet_lights.local using esphome API WARNING Can't connect to ESPHome API for office_cabinet_lights.local: Error resolving IP address: [Errno -2] Name or service not known INFO Trying to reconnect to office_cabinet_lights.local in the background