We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe. Whenever a battery sensor entity is unavailable, the batter card shows a strange state.
For example, I have some miflora sensors that are unavailable upon startup and only become available once a scan is successful:
And a sonos roam that doesn't report its battery status when it's powered off.
Describe the solution you'd like
It would be good to show a more readable unknown state and use the same icon the entities card uses for unavailable battery entities.
Something like this (a bad mock up using the chrome css editor and gimp) would be good:
The text was updated successfully, but these errors were encountered:
closed with #756
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem? Please describe.
Whenever a battery sensor entity is unavailable, the batter card shows a strange state.
For example, I have some miflora sensors that are unavailable upon startup and only become available once a scan is successful:
And a sonos roam that doesn't report its battery status when it's powered off.
Describe the solution you'd like
It would be good to show a more readable unknown state and use the same icon the entities card uses for unavailable battery entities.
Something like this (a bad mock up using the chrome css editor and gimp) would be good:
The text was updated successfully, but these errors were encountered: