search

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
69.86k stars 28.96k forks source link

Missing Unique ID in Meteoallarm enities #103132

Open SiriosDev opened 8 months ago

SiriosDev commented 8 months ago

The problem

Entities provided by Meteoallarm integration are missing unique IDs

What version of Home Assistant Core has the issue?

core-2023.10.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

MeteoAlarm

Link to integration documentation on our website

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

Additional information

If there is no way to determine a Unique ID algorithmically, I suggest at least adding an entry to the configuration so that the user can determine it manually

home-assistant[bot] commented 8 months ago

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

Code owner commands Code owners of `meteoalarm` 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 meteoalarm` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)

meteoalarm documentation meteoalarm source (message by IssueLinks)

issue-triage-workflows[bot] commented 5 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.

SiriosDev commented 5 months ago

Nope

issue-triage-workflows[bot] commented 2 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.

SiriosDev commented 2 months ago

Nope