Hi maxwroc, thank you so much for this wonderfull card.
This is exaclty the way i want my batteries to be showed, i’m trying to include in the less than 30% state batteries section that are not visible for the past 7 days, is it possible?
Hi maxwroc, thank you so much for this wonderfull card.
This is exaclty the way i want my batteries to be showed, i’m trying to include in the less than 30% state batteries section that are not visible for the past 7 days, is it possible?
Hello. Is there any way (other than using pre-defined groups, as the idea is precisely not to have to specify a fixed list of entities) of, after applying the first filter in a macro way custom:battery-state-card, reapplying a second filter for each collapse, filtering by name of the entity. I know the code below doesn’t work, but I added it just to illustrate what i need. I tried to do it with a template but I couldn’t.
- type: custom:battery-state-card
title: "All Battery"
filter:
include:
- name: "attributes.device_class"
value: "battery"
collapse:
- name: 'Door Sensors (Qt: {count})'
filter:
include:
- name: entity_id
value: '*_door_*'
- name: 'Temperature sensors (Qt: {count})'
filter:
include:
- name: entity_id
value: '*_temp_*'
- name: 'Presence sensors (Qt: {count})'
filter:
include:
- name: entity_id
value: '*_presence_*'
Is it possible to change the background of this card? Can’t seem to figure it out.
You can change the line-height and I would assume you will need to reduce the line-height of the secondary info line. I haven’t figured it out myself but I would also like to do this so will report back if I figure it out
That would be great! Thanks!
Hi maxwroc, Is it possible to feed the min/max values in the Group Object sections by Helpers ?
Many Thanks,
|min|number||v1.4.0|Minimal battery level. Batteries below that level won’t be assigned to this group.|
|max|number||v1.4.0|Maximal battery level. Batteries above that level won’t be assigned to this group.|
thank you for sharing
Unfortunately group name and secondary_info support now only fixed set of keywords. But it make sense to change the logic and use “KString” which would mean you could use any value, from any other entity. I think this is something what you’re looking for, right?
You can add an issue on github with such proposal
First, thank you for this card. Brand new user. Wondering why I’m getting duplicates with the + sign. If it matters, I’m also using the Battery Notes custom integration.
Hello,
I am really liking this card. i currently have one card for all my batteries and one for our door sensors. I am trying to have the collapse field change based on the number of doors open but i keep getting this error:
Ive tried a couuple different versions of the code and i keep getting this error.
Hello all,
is there a way to place entities with ‘unknown’ state at the end of the list instead of the beginning?
Thank you
Not sure what you mean. Did you see my example from above? 🔋 Lovelace: Battery state card - #280 by ThomDietrich