Treat entity "unknown" states in the same way as "unavailable"#245
Open
borreeero wants to merge 1 commit into
Open
Treat entity "unknown" states in the same way as "unavailable"#245borreeero wants to merge 1 commit into
borreeero wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Should fix #244. When an entity state is unknown, the card currently displays an error (even with
debug: true). I noticed that the functionnullifyStateis not returningnullin this case, as only handlesunknown.This happened for me with a LG diswasher with the official LG ThingQ integration, where most of the entities have an unknown state shortly after the cycle has finished, and interestingly unavailable from Home Assistant start until you turn it on.