v1.19

You can now use guess_mode on entities like alarms whose start_time is best estimated by the time of last modification. There was a restriction that previously prevented this, but I've removed that restriction in this release.

v1.18

This release adds two new features:

1. Support for the Paper Buttons Row card! This card allows you to add buttons to the side of the timer, so you have even more flexibility with your dashboard layout. Check the README for an example.
2. Support for state through attributes. In the rare cases where you have an entity whose state is inaccurate but has a descriptive attribute representing its state, you can use that attribute to compute active_state, pause_state, etc. See the new state_attribute option.

v1.17

The updates never stop! I've added two new configuration options: bar_radius and invert.

The bar_radius option controls the border radius (i.e. rounding of corners) of the bars. But if you configured your progress bar to shrink with time, you'll see this:

That's no good! So I've added another option invert, which is meant to replace the hacky adjustment of bar_foreground, bar_background, and bar_direction needed to invert the bar colors. Now, adding invert: true will achieve the same thing, and it will work corrrectly with bar_radius!

v1.16

I've added a new layout option. It takes values normal (default), full_row (for hiding the name and icon, making the timer take up the full width of the card) and hide_name (hides only the name).

If you are a huge fan of this card like I am, you might remember there already was a full_row option. The full_row option is still supported, but it's meant to be replaced by the layout option.

In the case you've configured the card with filter: true and there are no timers running at the moment, the card will now hide itself from your dashboard and reappear once a timer starts running.

Finally, another debugging improvement: 🐛 This release adds a warning message if the card is not functioning as intended because you forgot to set active_state. Don't panic! If your card already works, you don't need to set active_state!

v1.15

The latest Home Assistant release broke the layout of this card (you may have not seen the progress bar). That's because the card depends on the layout of one of the components that ships with Home Assistant. I've removed this dependency, so the code is a little bigger but the card should be more stable in the future!

v1.14

Two big improvements have landed!

1. I reworked how entities with guess_mode set are handled, and they should now both update more reliably and also show up when putting them in a card with filter: true!
2. BREAKING CHANGE: I've edited the modifications syntax to be more intuitive and flexible. You can quickly upgrade by replacing greater_than with elapsed and adding a percentage symbol to your numbers (greater_than: 40 becomes elapsed: 40%), but I suggest you checkout the full syntax in the readme! You can now additionally pass durations in addition to percentages, and filter on both remaining and elapsed time!

Because of that BREAKING CHANGE I've skipped version 1.13 and went straight to version 1.14. Or maybe that was an accident...

v1.12

Fixes a bug where entity names might be blank, and for debugging purposes the card version will now be logged to the console!

v1.12.0rc0

This release might fix a bug with setting the entity name within the card, and for debugging purposes the card version will now be logged to the console!

v1.11

This release adds a tiny new feature: before you could have configured durations and end time to pull information from attribute, fixed, and entity, but now there's a fourth option: state!

This is useful if you are using this card for alarms! Let's say your alarm's state is set to the time it will go off. You can use end_time: { state: true } together with guess_mode: true to get the card working!

Yes, you could have done this before with the entity attribute, but this way will make your configuration nicer!

v1.10

If your entity has a wacky state that doesn't fit the active_state option, you can now set guess_mode to true—enabling advanced AI† to guess whether the timer is active or idle!‡

That's all! There's not much else in this release, save for modificationss to the debug pane.

† Sorry; it's simply a few if statements
‡ As long as your entity does not rely on using the last-changed-time when computing time remaining.