Repository navigation
Rename entities in place on an entity id change - #24
Merged
Merged
Conversation
From Home Assistant 2026.11 an entity whose class overrides an add method without async_entity_id_changed is still removed and added again; nothing of ours is keyed on the entity id.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From Home Assistant 2026.11 a changed entity id moves the entity in place.
An entity class from outside Home Assistant that overrides an add or remove
method without
async_entity_id_changedis still removed and added again,until that fallback goes in 2027.11. Three of ours did; none of them keys
anything on the entity id, so each gets the hook with nothing to move.
A guard test applies Home Assistant's rule to every entity class of the
package, so a class added later cannot miss it.