Since head expect only one thing, and not a list, you should remove the dash.
any feedback on those questions?
-
Is there a way to use auto-entity card with media control or custom miniplayer cards? (ex: display all media-player.plex* playing in mini player or media control cards, works fine in entity mode)
-
Could you show us an example of the lovelace code to combine auto-entity with fold entity? Tried a few ways but cannot make this work…
-
Is it normal it doesn’t show up in the custom updater card?
-
Is there a sort option for auto-entity cards?
Thanks in advance, love yours cards|
Very nice! Could we get the Lovelace yaml snippet to make the screen shot you attached? Struggling to nest this inside the folding-entity like you display.
- Not at this point. Adding several cards in a bunch is a bit tough, due to the layouting and stuff…
- I’ve added the code to the end of the readme on github (ping @jwelter, too)
- As discussed right between your two messages, the custom tracker updates once per day.
- Not yet. I’ll make sure to add one, though.
Thanks, this is great stuff!
card-loader
Some people have experienced problems with custom cards that wrap other custom cards (such as putting mini-media-player in vertical-stack-in-card.
I haven’t experienced this myself, so I can’t test this, but I believe card-loader could be used as a workaround until the card developers fix it.
Thanks for that… I would never in a million years have stumbled on that code. Cheers.
Hi Thomas -
Does this support putting a attribute on the second_line display? For example battery_level for zwave devices for the battery check would be helpful?
Hi Thomas,
Your custom cards are absolutely awesome! May I ask about feature request:
- Say, I have monster-card that filters out some entities.
- I’d like to apply a custom popup-card on each of these entities
- In popup I’d like to display:
– history-graph card displaying current entity’s state changes with custom interval (10 days)
– useful-markdown-card displaying text containing current entity’s attributes
Config might be smth like this:
- type: custom:monster-card
card:
type: entities
filter:
include:
- entity_id: sensor.prefix*
- type: custom:popup-card
entity:
- <same entities defined in monster. filtered with wildcard?>
card:
type: vertical-stack
cards:
- type: history-graph
hours_to_show: 240
entities:
- <entity_id displayed in the popup>
- type: custom:useful-markdown-card
content: 'More details: [[ sensor.<entity_id displayed in the popup>.attributes.Attribute ]]'
Hope explanation abode makes sense. What could you advice?
@cjsimmons I will not “hijack” @thomasloven 's thread, if you want more info about it please open an issue in one of the repos for it
That’s an interesting project.
Unfortunately monster-card (or my reimplementation auto-entities) can’t be used to create one card per entity due to layouting concerns.
If I were to do it, I’d probably try to make some kind of jinja script that could design the popup-cards automatically based on a for-loop over all entities, run it in /dev-template and then copy the results into the lovelace config.
@thomasloven - can fold-entity-row
be made to ‘fold’ or ‘un-fold’ from code?
For example, I have more than one instance of using a schedule when an input_boolean
is on
.
It would be great to be able to keep the schedule part of the UI ‘folded’ or ‘un-folded’ based on the state of the input_boolean
.
I usually recommend that people use the conditional card instead.
Yeah, I thought of that. A conditional folding card would be cool though
EDIT: Just in case you want to know exactly why I’d like it here is what I am working on right now…
It would be great if turning on the Boolean unfolds the entites.
Thanks for looking and whatever, I am loving your cards…
Great plugin! i do have a request tho… for the fold-entity-row
Is it possible to align the items under the fold as the same as the rest outside of it?
I hope you know what i mean by looking at the pics…
IMO i think it will look a lot neater. Especialy when controlling from mobile
Do you know how to get rid of this error (started when I switched from the markdown card to the useful-markdown-card):
element.setconfig is not a function
All the cards on the page produce the same error. Error go away but then come back after a few browser refreshes.
Maybe this is another clue: the padding option does nothing and sometimes the padding automatically switches between 0px and what looks like 16px.
I move the card’s resource URL call from the bottom to the top and now the errors went away:
resources:
- url: /local/custom-lovelace/useful-markdown-card/useful-markdown-card.js?v=0
type: js
- url: /local/custom-lovelace/mini-media-player/mini-media-player.js?v=0.9.8
type: module
- url: /local/custom-lovelace/tracker-card/tracker-card.js?v=0
type: js
- url: /local/custom-lovelace/compact-custom-header/compact-custom-header.js?v0
type: js
- url: /local/custom-lovelace/monster-card/monster-card.js?v=1
type: js
- url: /local/custom-lovelace/vertical-stack-in-card/vertical-stack-in-card.js?v=0.0.9
type: js
The padding issue still exists.
That’s because of a problem in vertical-stack-in-card. I made a special card specifically for dealing with that: My Lovelace Plugins
@thomasloven Am I right in believing that fold-entity-row
doesn’t use unit_of_measurement
when it displays an input_number
?
I ask because it doesn’t show up for me.
EDIT: There must have been some sort of cache issue going on because it appears now