**✨ Smart Light Timer**
Handles both motion and manual control seamlessly — no conflicts, no workarounds, no separate automations needed.
Author: LTek
🚀 Version 2026.31.07.39
- FIX: Bypass "Keep Lights at Current State" stop-check only verified that bypass_condition_stop was configured, not that it was actually true — the automation was stopping on every run regardless of the bypass entity's state.
- FIX: Bypass for Keep Lights at Current State was not always working.
📖 HOW IT WORKS
- Enabled profiles are checked in order 1 → 2 → 3 → 4 (create your Profiles in order of priority)
- The first profile conditions to be true AND trigger restrictions match is the only profile that is ran/used.
- If no profiles are true, no actions are taken.
- Profile's Additional Actions run AFTER the main light control actions
- Additional Actions only run if the profile's conditions are met AND the profile is selected
- Additional Actions run in the order they are defined
- Conditional Selectors for Bypasses
- Cooldown options
- Profile-specific Additional Actions & Light Contols
- Trigger Types
- Controlled... Lights/switches that both trigger and are controlled by the automation
- Motion... Sensors that trigger and turn on all controlled lights
- Additional... Entities that trigger but aren't controlled (locks, covers, etc.)
**NOTE** the blueprint prevents using the same entity in both as a Trigger and as a Bypass; to avoid conflicts.
**FEATURES**
🎯 4 Profiles — Each with day/time schedules, conditions, trigger restrictions, and custom actions
⏱️ Configurable Timeouts — Per-profile time delays to keep lights on
🚧 Bypass System — Temporarily override automation to keep on, keep off, or keep as-is
⏸️ Motion Grace Period — Lights turn back on if motion detected shortly after turning off
🧊 Cooldown — Prevents rapid retriggering from motion sensors or physical switches
💫 Synchronize Entities — Turn all controlled lights on/off together, or let them operate independently
⌛ Timer Helper — Survives Home Assistant restarts
Why this blueprint is unique...
One unified automation that handles both motion control and manual override, seamlessly without conflicts and no "stepping on each other" issues that occur when multiple automations control the same entities. With other blueprints, it requires two separate automations and careful planning to do make it work properly.
This blueprint eliminates the need for complex workarounds like input_booleans, separate automation groups, or template sensors that are typically required to achieve similar functionality. It provides a clean, maintainable solution that handles the most common home automation use case: "I want my lights to turn on with motion, but also control them manually without breaking the automation."
The design ensures that manual interaction is respected while still maintaining automated control, creating a seamless user experience that feels natural rather than fighting against the automation system
Thanks for this, looks like it should be just what I was looking for.
So far I have it turning on lights when my cameras detect a person, although it doesn't turn them off again. I'm using a timer helper, the debug looks okay, but the lights never turn off. If relevant, the light in question is a group helper.
What's the best way to trigger one of the profiles manually from another automation? Specifically, I have a script that runs when I arrive home that disables my alarm and a bunch of other stuff. At the moment it turns on the lights as part of the script, then at the end of the script pauses 10 minutes and then turns them off again. I'd like to change that to use this blueprint so that there aren't interaction issues between multiple things controlling the same lights. Do I need to create a dummy template input boolean to trigger an "additional trigger", or is there a cleaner way to programmatically execute a profile?
It would be great if the time restrictions could be relative to the Sun entity so it's appropriate throughout the year. I'm sure I could write an "additional condition" to evaluate whether the current time is between (dusk-1 hour) and (dawn+1 hour), but I'm guessing the intention of the "time" restrictions was for making some lights only operate at night anyway, so maybe this would be a nice feature to add. e.g. select a sun entity, specify offsets relative to dawn and dusk.
If the automation Trace says it is turning off the light entity, it is telling HA to turn off the entity so you may have something else causing the problem. I have 8 automations (some complex, some simple) using this blueprint and a few use Light Group Helpers. They have all been working without issue. Recommendation: install an MCP and Claude Desktop. This is the best (in every way) troubleshooting tool I've found. It can find these odd types of issues in two minutes. Its helped me many times like this.
To trigger an automation from another automation in Home Assistant, add a new action in the first automation using the Automation: Trigger service. This allows you to select the target automation and execute it, entirely bypassing its initial triggers.
Parameters for Day and Time of Day in the blueprint UI was meant to be basic. Conditions selector is for everything else.
🚀 Version 2026.31.07.39
- FIX: Bypass "Keep Lights at Current State" stop-check only verified that bypass_condition_stop was configured, not that it was actually true — the automation was stopping on every run regardless of the bypass entity's state.
- FIX: Bypass for Keep Lights at Current State was not always working.
