home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.34k stars 29.88k forks source link

Deleted/Changed entities result in entities that are no longer exposed. #98794

Open M-See opened 1 year ago

M-See commented 1 year ago

The problem

If you change the list of exposed entities or delete entities in the configuration.yaml, some previously functioning entities are suddenly no longer recognised/working with the error "Entity not exposed: number XY".

This seems to be because the emulated_hue.ids in the /config/storage folder is NOT adjusted/overwritten according to the changed configuration.yaml script. One must then manually delete the no longer existing entities from the emulated_hue.ids so that entities are exposed and recognised again at all.

See here for discussion in the community: Link

(besides, exposed input_booleans seem also not to work on voice commands. Alexa plays a sound but nothings is executed..)

What version of Home Assistant Core has the issue?

2023.8.3

What was the last working version of Home Assistant Core?

2023.8.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

emulated_hue

Link to integration documentation on our website

https://www.home-assistant.io/integrations/emulated_hue/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-08-21 19:40:17.811 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Entity not found: 6
2023-08-21 19:40:34.717 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Entity not found: 11
2023-08-21 19:40:52.021 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Entity not found: 2

Additional information

Thank you for your help!

home-assistant[bot] commented 1 year ago

Hey there @bdraco, @tho85, mind taking a look at this issue as it has been labeled with an integration (emulated_hue) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `emulated_hue` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign emulated_hue` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


emulated_hue documentation emulated_hue source (message by IssueLinks)

M-See commented 1 year ago

Also, after editing the emulated_hue.ids and deleting the entities that are not defined in the configuration.yaml anymore, in the Alexa App ALL (even all deleted and previously defined entities) are exposed there (so sometimes double entities as well)..

There seems to be something wrong for sure.

popy2k14 commented 1 year ago

Same issue here after removing from tghe emulated hue yaml. Manually removing the lines from /config/.storage/emulated_hue.ids did the trick.

issue-triage-workflows[bot] commented 9 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment šŸ‘ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

popy2k14 commented 9 months ago

bump

systematicallyrandom commented 8 months ago

Old entries still showing up in emulated_hue.ids in HA 2024.1.0.

mfryczke commented 6 months ago

Hello. I have a problem that i could not find emulated_hue.ids. There are no such a file Have someone had that problem ??

issue-triage-workflows[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment šŸ‘ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

M-See commented 3 months ago

Hello. I have a problem that i could not find emulated_hue.ids. There are no such a file Have someone had that problem ??

bump

and you should find the emulatedhue.ids in ~config/.storage_ from the terminal. Hope this helps.

issue-triage-workflows[bot] commented 2 weeks ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment šŸ‘ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

popy2k14 commented 2 weeks ago

bump