fix: HomeAssistant: add default_entity_id to discovery message
#28560
Conversation
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
Nerivec
approved these changes
Sep 9, 2025
Collaborator
|
@jbouwh can you confirm that adding default_entity_id will stop the warning logs, even if object_id is still present too? (Seems to be triggering rate limiting for some users.) |
Contributor
|
Yes, with home-assistant/core#151996 the warnings are suppressed if the new option is used. So it is backwards compatible. |
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.
Adds the
default_entity_idimplemented in home-assistant/core#151775 to the discovery payload.For now
object_idis also send to give users a chance to migrate.CC: @jbouwh