After few days i deleted this integration directly from HACS, but the created sensor is still there and too often creates errors in the logfile. I tried to delete it from the entity list but cannot do it is an entity without ID and cannot be deleted from the UI.
I tried also to find this entity inside the various files listed in the .storage folder but unsuccesfully. It is impossible to find it.
My questions are: How to delete it? And where the hell is located this file inside home assistant?
I am running HaOS 2022.1.10 in a RPi 4.
if you have a state with playlists, then the sensor still exists in configuration.yaml or through config flow (The UI). If it’s configured through the UI, then it exists in .storage. You must not be searching for the correct information. Are you searching by eye or actually using a ‘find in files’ function supplied by VSCode or Notepad++?
There’s no way the entity exists without it being in these files or integrated through some other means. Your entity still has an active state and it’s not unavailable. No unique_id indicates that it’s coming from yaml typically.
Not sure whatelse to tell you because it’s going to be located in your config somewhere. Either in .storage and one of the many files there or in your configuration file.
I am trying to locate this entity since months, i read topics about entities without ID and other users seems to have the same problem… I am sure i checked all my yaml files many times, i checked .storage folder and all the files inside it many times… No way to find this entity !
I’m sorry, but that’s just not how the system works. It’s in your system somewhere. Post your entire configuration folder in github if you can and I’ll find it for you.
That sensor is populated by your spotify playlists. Change your playlists on spotify.
BTW it only grabs 10 playlists. I was going to put in a PR to make that limit a configurable option but never got around to it. I just change the limit on my local copy. I grab 40 playlists and I’ve not had any issues.
I just read the release notes in the spotcast github and there is no entry regarding this sensor.
Instead if you go to the github link i posted, there you can see all about that sensor.