core icon indicating copy to clipboard operation
core copied to clipboard

duplicate and or orphaned entities in aurora integration after upgrade

Open johangus65 opened this issue 1 year ago • 2 comments

The problem

After upgrading to 2024.10.2 the already configured aurora entities are messed up as the unique_id was changed.

This PR caused the problem: https://github.com/home-assistant/core/pull/127740 The latitude and longitude configured for the entities are used for building the unique id. In the PR this was changed from int() to round() of entered values, thus causing the issue.

A workaround is to delete and re-add the entities.

Not sure how to fix this problem in code.

What version of Home Assistant Core has the issue?

2024.10.2

What was the last working version of Home Assistant Core?

2024.10.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

aurora

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

johangus65 avatar Oct 12 '24 04:10 johangus65

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

Code owner commands

Code owners of aurora 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 aurora Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


aurora documentation aurora source (message by IssueLinks)

home-assistant[bot] avatar Oct 12 '24 04:10 home-assistant[bot]

After removing and re-adding, the entity id's are also pretty badly named:

  • binary_sensor.aurora_visibility_visibility_alert
  • sensor.aurora_visibility_visibility

You might want to check https://developers.home-assistant.io/docs/config_entries_config_flow_handler/?_highlight=migration#config-entry-migration

golles avatar Oct 12 '24 10:10 golles

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.