Can someone point me in the right direction. I have 2 entities that I don’t use anymore, and I thought, I removed them back before HA switched from the OG config files, to the Lovelace config file. But, since I updated to 2022.2.0, their are now showing up in the home-assistant.log file. the following is what the log shows;
The second error is the same, except it is for the entity is for led_pole_1. I went thru all my config files, and I can’t find any thing, that references these 2 entities.
Also, the 2 entities do not show up in the Configration/Entities or Device List
My advice for you is to backup all the configuration and rebuild Home Assistant from scratch. I’m not sure if you use the find/search feature to search anything that relates to led_pole_1 and led_pole_2. In my Linux machine or server, I can use the command as follows:
grep -r "led_pole_2" name-of-directory/
The grep -r command in Linux will list files within directories starting with name-of-directory and outputs the line from files that contains led_pole_2. The -r flag specifies recursive. Here is an output without the -r flag:
gpeddie@epcotcenter
~
$ grep "test" Documents/
grep: Documents/: Is a directory
If the two methods failed, perhaps there’s something publishing in the MQTT server? I have never used an MQTT server. I mean, I tried it before but I don’t have a use-case for it.
Before you do that- are these entities from an integration? If so, delete the integration, restart Home Assistant and those ghost entities will be gone. If you have other entities from that integration, Home Assistant will discover them again and you will see a notification on the home page.
Go to configuration ==> entities tab, then you can either filter out “disabled” entities so that it does not bother you or find the entity and should be able to delete the entity once you click on it like the screenshot below.
@PanMat The two entities are listed in the Config==>entities tab, But, I can’t do anything with them, because they Hassio, long before the Lovelace Dashboard upgrade, and there was No Need for “Entity Id’s”. So, when I click on either entity, I get the following message:
This entity ('light.ledpole3') does not have a unique ID, therefore its settings cannot be managed from the UI. See the [documentation](https://www.home-assistant.io/faq/unique_id) for more detail.
Additional Note: I have combed thru the nearly 30,000 lines, of the core.entity_registry file, and could not find the offending entities.
That’s what contains the topics that create your devices. However something is putting those topics in there. You have to figure out what. You can try removing the topics but they may reappear if you don’t find the source
@reste_narquois Thanks, I give it a try… That did the trick, once I connected with “MQTT Explorer”. The program, flagged
my to ghost entities. Thanks again!
