I’m excited to share my first Home Assistant integration with the community - Simple Timer!
What it does
A simple Home Assistant integration that turns entities on and off with a precise countdown timer and daily runtime tracking. Currently supported entity types: switch, fan, light and input Booleans.
Key Features
Out-of-the-box pre-packaged timer solution, eliminating manual creation of multiple Home Assistant entities, sensors, helpers and automations.
Countdown timers from 1-1000 minutes
Daily usage tracking in HH:MM format
Built-in timer card with customizable buttons
Optional notifications for timer events
Auto-cancel when device is turned off externally
Midnight reset for daily statistics
Installation
Available in HACS! The timer card installs automatically - no manual setup needed.
Great work. I like the integration & card.
Would be nice to have options to customize the look of the card (elements position and size, compact version, combine multiple timers in the same card, etc.) Uses a lot of screen estate if you have multiple timers.
Thanks for the feedback! I’m really glad you’re finding the integration useful.
Card size is definitely an issue that I will address in future version as I got similar feedback from other users.
This is really great and makes having timers really convenient. The card is really nice but options to remove the daily usage and make it more compact/modern would be nice.
Unfortunately, climate entities aren’t supported yet, but hopefully they will be soon. Someone told me that they use an input helper and an automation to control the device. While it’s not ideal, it is a useful workaround for now.
A really good timer card. The delayed start is great. A delayed start of a timer would also be brilliant. Example. 10 second delayed to start an irrigation timer (with existing configurable timer duration). Scenario: this would protect an irrigation solenoid if someone quickly presses the timer button on and off a few times. The delay would protect surging.
Climate is a bit trickier than a standard on/off entity.
Climate entities use modes like heat, cool, auto, etc. rather than a simple on/off, so we’d need to either let the user choose which mode “on” should map to by default or track and restore the climate entity’s most recent mode.
In the end, it’s all doable, but it takes more time and can add code complexity that I’m trying to avoid.