Renamed ESPHome entities cause endless 'potentially due to IP reassignment' Error in HA log

ESPHome
1

let me try here too, as an additional source for the issue I filed at renamed ESPHome entities cause endless 'potentially due to IP reassignment' Error in HA log · Issue #79917 · home-assistant/core · GitHub

somehow the renaming confuses either Esphome, or HA, but the errors are constant, while the backend data seems ok. The naming is understood, and the device_tracker has the correct IP address.

and yet:

Logger: homeassistant.components.esphome
Source: components/esphome/__init__.py:263 
Integration: ESPHome (documentation, issues) 
First occurred: October 9, 2022, 22:59:50 (829 occurrences) 
Last logged: 09:59:54

Name of device olimex-bluetooth-proxy-277564 changed to bluetooth-proxy-centraal, potentially due to IP reassignment
Name of device olimex-bluetooth-proxy-288d84 changed to bluetooth-proxy-aanbouw, potentially due to IP reassignment

Id appreciate any suggestions to fix this.
thanks for having a look!

2

I’m having the same problem after renaming the bluetooth proxy device.

3

Aw should have posted my find:

delete the device tracker in the ESPHome integration panel, and restart, so they are rediscovered with the new names.

sorry for forgetting that.
see what I did post in the issue :wink: renamed ESPHome entities cause endless 'potentially due to IP reassignment' Error in HA log · Issue #79917 · home-assistant/core · GitHub