Always send sensor registration device class + entity category to prevent errors due to old registration #3977
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.
Summary
Fixes #3202, fixes home-assistant/core#102853
Always send the values for
device_class
andentity_category
when registering sensors to make sure they match the app value. Some sensors were changed in the past based on feedback, but users with existing registrations wouldn't have seen this updated in core as the app didn't sendnull
values instead of sending that it should benull
. To make this possible, registrations and updates need to be split as the app currently depends on usingnull
as "don't send".Example before/after payloads:
Screenshots
n/a
Link to pull request in Documentation repository
n/a
Any other notes
Requires home-assistant/core#86965, which was first included in 2023.2.0.