First off — thanks for merging the Portuguese translation so quickly! 🙏
Feature request
When the card shows a recommendation like Run Air Purifier or Ventilate Now, it would be useful to act on it directly from the card with a single tap, without having to navigate elsewhere.
Proposed UX: a small action button (or tappable icon) appears alongside the recommendation text when an action entity is configured for it. Tapping it toggles the entity.
Proposed config (in the existing editor)
Add optional entity fields under a new Actions section — one per actionable recommendation:
action_air_purifier: fan.purificador_jantar # shown when recommendation is Run Air Purifier
action_ventilate: switch.ventilador_sala # shown when recommendation is Ventilate Now / Open Window
Supported domains would be fan, switch, input_boolean, and script — all toggled via homeassistant.toggle (or script.turn_on).
Use case
I have a fan entity mapped to my dining room air purifier. When the card recommends Run Air Purifier, I'd love a one-tap button to turn it on right there.
I'm happy to implement this if the direction sounds good. One open question: would you prefer the simpler entity toggle approach above, or the full HA action selector pattern (like tap_action: { action: call-service, ... }) that other Lovelace cards use? The latter is more flexible but heavier to implement.
First off — thanks for merging the Portuguese translation so quickly! 🙏
Feature request
When the card shows a recommendation like Run Air Purifier or Ventilate Now, it would be useful to act on it directly from the card with a single tap, without having to navigate elsewhere.
Proposed UX: a small action button (or tappable icon) appears alongside the recommendation text when an action entity is configured for it. Tapping it toggles the entity.
Proposed config (in the existing editor)
Add optional entity fields under a new Actions section — one per actionable recommendation:
Supported domains would be
fan,switch,input_boolean, andscript— all toggled viahomeassistant.toggle(orscript.turn_on).Use case
I have a fan entity mapped to my dining room air purifier. When the card recommends Run Air Purifier, I'd love a one-tap button to turn it on right there.
I'm happy to implement this if the direction sounds good. One open question: would you prefer the simpler entity toggle approach above, or the full HA action selector pattern (like
tap_action: { action: call-service, ... }) that other Lovelace cards use? The latter is more flexible but heavier to implement.