first: you have a wrong indent: (look at action:)
secondly: seems like you as above poster neither read the github-documentation
third: you donāt have any include, your mushroom wont be applied, beside your card-mod does nothing.
fourth: Use The Power of Auto-entities ( thatās what itās build for )
Hopefully somebody can help me out here because Iām beating my head against a wall.
I want to have a hold action on my scenes to add/remove them from a favorites list.
I can easily add the hold_action option when I use the āincludeā filter. But for the life of me I canāt figure out how to do this for a template.
thanks for taking the time to reply - much appreciated
first: you have a wrong indent: (look at action:) - thanks again, had not picked that up
secondly: seems like you as above poster neither read the github-documentation - if youāre referring to the auto-entities github, then yes I have read it, but do not claim to understand all of it - is there a particular section that youāre referring to?
third: you donāt have any include, your mushroom wont be applied, beside your card-mod does nothing - correct it does not have an include - Iām trying to build the code based on this example, which does work, and also does not have an include
fourth: Use The Power of Auto-entities ( thatās what itās build for ) - as above I have the āincludes & excludesā in a template sensor - just trying to streamline the yaml
Ok, however your code, doesnāt looks anywhere near/like the code-example you refers to. ( i.e no mushroom-card(s), however a "base-card / type: custom:fold-entity-row "
It also donāt have an āoptionā tag
And i believe there are simple example codes, in the cards-github-page, which people can start with, to get an understanding of how the card works.
Beside if you look at my answer to you, and above poster, you got all āingredientsā to accomplice, what your are asking for.
Yes iāve seen other examples where people using template-sensors ( free choice ) and not needed for i.e a simple solution, as you are asking for
Top to Bottom , donāt scroll to fast through the examples, they tell/show in pictures whats stated in the text
Hi Thomas,
I have a card set up with show_empty:false, but it still shows up when there are no results.
The card is meant to show up when there are HACS updates due, but go away when there are none.
I have a template entity defined for this:
Iām trying to put together a small gaming dashboard with Steam shortcuts. This works quite well with auto entities mushroom and card mod. But what I canāt quite manage are the automatic background images for the mushroom cards. if I set them statically, it works, but not dynamically.
With the mushroom image it works with the variable, but not with the background:
type: custom:auto-entities
filter:
include:
- entity_id: '*game_*'
device: TEST
name: '*Favorites*'
options:
type: custom:mushroom-template-card
primary: ''
secondary: ''
picture: >-
https://cdn.cloudflare.steamstatic.com/steam/apps/{% set str =
state_attr(entity, 'friendly_name') %}{% set sub = str.split('_')[2]
%}{{sub}}/header.jpg
tap_action:
action: toggle
layout: vertical
card_mod:
style: |
ha-card {
background-image: url('https://cdn.cloudflare.steamstatic.com/steam/apps/{% set str = state_attr(entity, 'friendly_name') %}{% set sub = str.split('_')[2]%}{{sub}}/header.jpg')!important;
}
sort:
method: friendly_name
card:
square: false
type: grid
columns: 7
title: Favorites
card_param: cards
show_empty: true
view_layout:
position: main
The horizontal-stack is mandatory, otherwise the shutter will be shown vertically.
Iām wondering if its possible to use this in any way / respectively to use the auto-entities to hand over the result to the shutter-card in a horizontal-stack type?
because you removed the - under include ( and i dont even know whether your ārolladenā works as i donāt have such )
PS: Knowledge you get by compare and read the Docs of the specific Cards/Integrations
Card_params
options
Hardly anything right, so obviously your first code you posted, is copied somewhere from, and you donāt understand it, and you havenāt looked at the examples in the Docs, so you wont understand my code either
I agree - Iāll consult the documentation more in detail and try to understand the correct syntax format.
For this special case I assume it is a limitation from shutter-card side. It seems that this card always need a direct entity. So, back to my first question, I see there s no possibility to hand the entity result(s) from the auto-entities to the shutter-card.
So for now it looks like there is now resolution.
I agree - Iāll consult the documentation more in detail and try to understand the correct syntax format.
For this special case I assume it is a limitation from shutter-card side. It seems that this card always need a direct entity. So, back to my first question, I see there s no possibility to hand the entity result(s) from the auto-entities to the shutter-card.
So for now it looks like there is now resolution.
My suspicions are confirmed with the final test (thank you for providing the example code!)