GeraldPape
(Gerald Pape)
September 14, 2023, 7:23am
1
Seeing this message in the log, but I did not change the hardware.
What can I do to let esphome accept the new MAC ?
WallyR
(Wally)
September 14, 2023, 7:42am
2
Read breaking changes in the Home Assistant release notes for the september update.
GeraldPape
(Gerald Pape)
September 14, 2023, 7:43am
3
Hi, yes, saw this. But its the same board. It was never changed. The MAC address changed “magically”.
So I guess, delete from homeassistant/esphome and flash new?
WallyR
(Wally)
September 14, 2023, 7:47am
4
If the mac address change, then it is a different board to HA, so you will have to follow the guidelines.
robertito
(Robert)
September 30, 2023, 11:16am
5
Hi
I have the same problem!
I’ve did not made any hardware changes, all boards are the same… but HA does not see any of my boards. All of them are connected to the same network as HA server.
The only change was an update.
In the logs I got:
"Unexpected device found at… ". what strange is, that is that the system is expecting for example “hallway-esp” board mac under “kallax-esp” name…
WallyR
(Wally)
September 30, 2023, 7:52pm
6
Sounds like your config files for ESPHome has gotten mixed up.
Try to reflash one board at a time.
FarkiR
(FarkiR)
October 2, 2023, 8:35pm
7
me to…
how to delete old MAC from HA ?
WallyR
(Wally)
October 3, 2023, 2:37am
8
Delete the device under the integration.
mmiller7
(Matt Miller)
December 14, 2023, 12:39am
9
Anyone know what is going on with this?
I had to do a reset/restore on my router and suddenly almost ALL of my esphome stuff is broken with this error…I don’t understand why?
Its all the same devices, with the same firmware, on the same network as before. They were all using DHCP and connecting by name, so the IPs shouldn’t matter. ESPHome dashboard shows them all working, but almost everything is unavailable in Home Assistant.
I don’t understand how this can happen when its the same boards with the same firmware on the same network?!
Its almost like HA is improperly caching DNS and not refreshing it (even after a complete reboot)?!
EDIT: I think I found the problem…sounds like it was a bug for a while where ESPHome entities were being saved by IP instead of DNS name facepalm
opened 01:22PM - 24 Aug 20 UTC
closed 10:30PM - 28 Oct 20 UTC
Connection Issue
<!-- Thanks for reporting a bug for this project. READ THIS FIRST:
- Provide … as many details as possible. Simply saying "X gives bug" or "X gives error" is not enough!
- Paste logs, configuration sample and code into the backticks (```).
- Read through the template carefully and fill out all missing details.
- Please also search for similar issues in this issue tracker first and read through the ESPHome FAQ.
DO NOT DELETE ANY TEXT from this template! Otherwise the issue may be closed without a comment.
-->
**Operating environment/Installation (Hass.io/Docker/pip/etc.):**
<!--
Please provide details about your environment below this line. -->
HASSOS v0.114.3 running in VirtualBox
Network Wi-Fi router: ZXHN H298A
**ESP (ESP32/ESP8266, Board/Sonoff):**
<!--
Please provide details about which ESP you're using below.
-->
(irrelevant) ESP8266 (Sonoff, Wemos, etc)
**ESPHome version (latest production, beta, dev branch)**
<!--
ESPHome version like v1.14 or 1.15-dev
-->
(irrelevant) beta 1.15.0b4
**Affected component:**
<!--
Please add the link to the documentation at https://esphome.io/index.html of the component in question.
-->
https://github.com/home-assistant/core/blob/dev/homeassistant/components/esphome/config_flow.py
**Description of problem:**
- Upon local IP renewals (i.e. house power cut & restore) the nodes appear as "unavailable" in Home Assistant.
- This happens because when setting up integrations, the IPs are being stored instead of the node host names.
- (irrelevant) In the ESPHome plugin the devices are still visible & connected.
**Problem-relevant YAML-configuration entries:**
**Logs (if applicable):**
<!--
Please copy the debug log here. If possible, also connect to the ESP over USB and copy those logs into the backticks.
-->
**Additional information and things you've tried:**
- The problem isn't so evident until you get a Wi-Fi router with lax DHCP management.
- Deleting the nodes in HASS and manually adding them, makes them available again.
- It's also possible to set up a fixed DHCP lease for each node, but it is tedious. I don't think this is the intended behavior.
- In `core.config_entries` I see that some devices are stored by IP and others by host name. The latter seem to be the ones that were added manually rather than using the "new devices found" discovery prompt.
- **To solve the issue, the integration tool could ensure nodes are stored by their host name instead of their IP.**
Related threads:
https://github.com/home-assistant/core/issues/38860
https://github.com/esphome/issues/issues/176
https://www.reddit.com/r/homeassistant/comments/a3ptqf/devices_show_in_ha_as_unavailable_when_theyre/
https://community.home-assistant.io/t/solved-some-esphome-nodes-show-unavailable-in-home-assistant-but-show-online-in-esphome-gui/125840
https://community.home-assistant.io/t/esp32-connected-but-unavailable-in-frontend/183062
Functionality that would allow to ensure host names are used:
https://community.home-assistant.io/t/configure-esphome-in-configuration-yaml/110904
https://community.home-assistant.io/t/reproducible-configuration-for-modern-setups/170309