Use unavailable and unknown states consistently when dealing with sensors and entities #3821
Conversation
This file contains 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
dshokouhi
force-pushed
the
consistent_unavailable_unknown_usage
branch
from
cce2553 to
3f6e782
Compare
jpelgrom
approved these changes
Aug 27, 2023
JBassett
approved these changes
Aug 28, 2023
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.
Summary
Breaking change:
Unavailableis nowunavailableandUnknownis nowunknownfor all sensors that report those states. Phone SIM, Next Alarm, Media Session, Geocoded locationScreenshots
Link to pull request in Documentation repository
Documentation: home-assistant/companion.home-assistant#
Any other notes