Hi Stephen,
Indeed, grep does not find anything. In my ESPhome integration, all devices have “1”
Hi Tom, this is the error message:
And this is the list of devices in the ESPhome integration:
As stated below, searching the entire filesystem using ‘grep’ did not result in any matches. I have no idea how to find this supposed duplicate. I only see the error, warning me that my HA will stop working next year.
Remove airco-zolder and readd it.
1 Like
I’m confused. Would that not mean I lose all automations and statistics associated with that device?
I will create a full backup before attempting to delete the airco device. We use the airco for heating, so I don’t want to lose access. Will removing / re-adding ‘airco-zolder’ also remove this elusive ‘pana-climate’ device that is nowhere to be found?
Apologies for my ‘frustration’, I must say the 2024.11 release is the most problematic that I encountered since starting with HA… Backups did not work due to missing backups.json, local_file starts complaining about provably correct file paths, upgrade to 2024.11.1 failed miserably necessitating a restore to 2024.11.0 and now there is an invisible duplicate ESPhome device somewhere… aargh
I’ve spent the last several days attempting to fix multiple things that were not broken until I upgraded to 2024.11 
I believe that when you re-add it, the entities will come back named exactly the same, and ask will be well. But of course backing up is recommended
My experience is that when you delete a device from ESPHome, you don’t have to re-add it. Home Assistant will discover it when you restart Home Assistant. (Assuming the device is online).
If you click on each ‘entities’ in ESPHome (your second screenshot in post 21), you may find that one of them is pana-climate.
I clicked all the entries, performed a grep across the entire filesystem and still no match for “pana-climate”. I hope the UX will be improved in the future, because it’s completely unclear to me where and how this duplicate was detected by HA.
In the upcoming weekend I’ll try removing the “correct” device, in the hopes that the “duplicate” magically disappears. During the weekend I’ll have the time to properly create and restore a backup
[quote=“EdV, post:29, topic:791405”]
In the upcoming weekend I’ll try removing the “correct” device, in the hopes that the “duplicate” magically disappears.[/quote]
That’s what happened in my case.
Why aren’t you doing a nightly full backup? I use Samba Backup to an NAS. Others backup to OneDrive.There
Hi Stephen, the full backup is an extra one just in case
I went into Settings - Integrations - ESPhome and removed the “airco-zolder” device. Then, performed a restart of HA.
The “duplicate” warning is (still) gone, but so is my “airco-zolder” 
I can see “airco-zolder” in the ESPhome Device Compiler dashboard, showing Online, but it is not automatically adopted by HA.
Not sure how to proceed now. If I manually add it using the IP address I’m afraid there will be another duplicate. Honestly, this part of HA is not user-friendly at all.
After waiting for approx. 15 minutes, still no sight of the “airco-zolder” so now I’m performing a full reboot of the HA machine. Who knows if that helps.
If you have an api: component in your device configuration file then Home Assistant should discover your device pretty quickly. Sometimes it’s necessary to reset/restart the device to remind your routers mDNS table that it’s online. Using the IP address is safe.
Hi Stephen,
All my ESphome devices work via API. The device was visible, showing “online” in the ESPhome device compiler page, but never showed up via auto-discovery. Restart/reboot of HA did not make a difference. I had to manually add it via hostname/IP. This fixed the automations, fortunately.
Strange though that the firmware update for my remaining 2 airco units showed in Updates, but not for the re-added “airco-zolder” although they all run the same version. Hopefully that glitch also resolves itself with a future update.