Skip to content

⚠️POSSIBLE BREAKING CHANGE ⚠️

Choose a tag to compare

View all tags
@cataseven cataseven released this 02 May 08:22
v1.2.0
fbb573b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

⚠️⚙️ Behavior change — Stop button & automation mode

When timer_and_entity_connected_via_automation: true (the default), the README has always stated:

"the card will not call these services; it will only start/stop the timer and display progress. Your automations must handle turning the device on/off."

Until now, this was only true for Start. The Stop button still called turn_off on the device, which contradicted the docs and could double-fire alongside your own automation.

In v1.2.0, Stop now respects the flag the same way Start does:

Mode Start button Stop button
timer_and_entity_connected_via_automation: true (default) Starts the timer only Finishes the timer only
timer_and_entity_connected_via_automation: false Turns device on + starts the timer Finishes the timer + turns device off

Do I need to change anything?

For the vast majority of users — no.

If you happen to rely on the old buggy behavior (i.e., your automation only handles start and silently leaned on the card to do the stop), add a step to your automation that turns the device off on the timer.finished event (and optionally on timer.cancelled):

trigger:
  - platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.your_timer
  - platform: event
    event_type: timer.cancelled
    event_data:
      entity_id: timer.your_timer
action:
  - service: switch.turn_off   # or your domain's stop service
    target:
      entity_id: switch.your_switch

✨ What's new

Shared-device support (multiple timers, one device)

You can now use the same switch (or any other controllable entity) across multiple entity cards — each with its own timer. The classic use case is a heating boost:

type: custom:switch-and-timer-bar-card
title: ♨️ Central Heating
entities:
  - name: 15 Minute Boost
    switch: switch.boiler
    timer: timer.boost_15m
    timer_and_entity_connected_via_automation: false
  - name: 30 Minute Boost
    switch: switch.boiler
    timer: timer.boost_30m
    timer_and_entity_connected_via_automation: false
  - name: 60 Minute Boost
    switch: switch.boiler
    timer: timer.boost_60m
    timer_and_entity_connected_via_automation: false

Each card now reflects its own timer independently:

  • Press Start on the 30-min boost → only that card shows "Heating" and a counting progress bar. The 15-min and 60-min cards stay "Idle". ✅
  • The card no longer turns the device off if another timer on the same device is still running. So if you start the 30-min boost while the 15-min boost finishes, the boiler stays on until the 30-min one is also done.
  • Press Stop on an active boost → the device turns off only if no other boost is running for the same device.

The card detects this scenario automatically when it sees the same switch entity used in more than one card. No new config option needed.

Assets 3
Loading