A clear and concise description of what the feature should do.
I would like to be able to replace the screensaver with a dimmed version of one of my other cards.
Ideally I could either set screensaver: false and it would just use the first card as the default, or perhaps I would define it as:
screensaver:
type: card
target: cardKey
A bonus would be able to choose a different screensaver card based on conditional logic.
ADDITIONAL CONTEXT
Add any other context about the problem here.
I've found that guests don't realize they can interact with the panel, so if I were able to have it show a cardGrid by default, then it might be clearer to them that they can look up wifi info, adjust a thermostat, or operate lights, etc. I think that most of my guests assume it is only a clock or weather station, so they never touch the screen.
For my own use, being able to operate common entities with one tap would be great - with the screensaver, I have to tap at least twice to do anything.
I would also use more of these panels in other places if I could do things like default to a cardThermo (to use it as a thermostat for an IR-controlled mini-split). Or if there were an ability to conditionally set the screensaver card, I might want to set it to a cardAlarm when my alarm is engaged or to a cardGrid when the alarm is off, etc.
I am using sairon's ESPHome component, which provides a service command to disable the screensaver as well as a service to navigate to a particular card. However, I find that if I use those service calls to programmatically switch to my preferred card, then it does not auto-dim, and once I interact with the touch-screen again, the default screensaver is re-enabled.
PANEL / FIRMWARE VERION
Please add the Panel/Firmware Version you are using (EU, US-L or US-P)
FEATURE DESCRIPTION
A clear and concise description of what the feature should do.
I would like to be able to replace the screensaver with a dimmed version of one of my other cards.
Ideally I could either set
screensaver: false
and it would just use the first card as the default, or perhaps I would define it as:A bonus would be able to choose a different screensaver card based on conditional logic.
ADDITIONAL CONTEXT
Add any other context about the problem here.
I've found that guests don't realize they can interact with the panel, so if I were able to have it show a
cardGrid
by default, then it might be clearer to them that they can look up wifi info, adjust a thermostat, or operate lights, etc. I think that most of my guests assume it is only a clock or weather station, so they never touch the screen.For my own use, being able to operate common entities with one tap would be great - with the screensaver, I have to tap at least twice to do anything.
I would also use more of these panels in other places if I could do things like default to a
cardThermo
(to use it as a thermostat for an IR-controlled mini-split). Or if there were an ability to conditionally set the screensaver card, I might want to set it to acardAlarm
when my alarm is engaged or to acardGrid
when the alarm is off, etc.I am using sairon's ESPHome component, which provides a service command to disable the screensaver as well as a service to navigate to a particular card. However, I find that if I use those service calls to programmatically switch to my preferred card, then it does not auto-dim, and once I interact with the touch-screen again, the default screensaver is re-enabled.
PANEL / FIRMWARE VERION
Please add the Panel/Firmware Version you are using (EU, US-L or US-P)
US-P