You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I use two battery-state-cards in my dashboard because they are amazing, however I've been having issues, especially on mobile devices with bloat. Looking at the console logs over a 5 minute period I received nearly a thousand "warn" messages from this card. I do not have anything specifying "state_map" for "unavailable" yet the message is [battery-state-card] Missing option for 'unavailable' in 'state_map.' See screenshot as well.
How to reproduce
have the browser_mod installed, use the following or something similar, any time a browser_mod entity goes "Unavailable" it doesn't matter what you do these "warnings" pop up. You can get rid of the entities showing by using the below but the warnings still continue. So the exclude is just excluding them from view not the processing part of the card. (Should be considered a bug in itself)
`
exclude:
name: state
value: 'Unavailable'
`
Expected behavior
Exclude should happen before card processing and after include/entities. And entities that report 'unavailable' should not be included.
Describe the bug
I use two battery-state-cards in my dashboard because they are amazing, however I've been having issues, especially on mobile devices with bloat. Looking at the console logs over a 5 minute period I received nearly a thousand "warn" messages from this card. I do not have anything specifying "state_map" for "unavailable" yet the message is
[battery-state-card] Missing option for 'unavailable' in 'state_map.'
See screenshot as well.How to reproduce
have the browser_mod installed, use the following or something similar, any time a browser_mod entity goes "Unavailable" it doesn't matter what you do these "warnings" pop up. You can get rid of the entities showing by using the below but the warnings still continue. So the exclude is just excluding them from view not the processing part of the card. (Should be considered a bug in itself)
`
exclude:
value: 'Unavailable'
`
Expected behavior
Exclude should happen before card processing and after include/entities. And entities that report 'unavailable' should not be included.
YAML configuration
Entity debug data
Dev console errors
See screenshot and description
Screenshots
Version
3.2.1
The text was updated successfully, but these errors were encountered: