**✨ Smart Light Timer**
One automation handles both motion and manual control seamlessly — no conflicts, no workarounds, no separate automations needed.
Author: LTek
🚀 Version 2026.02.25.33c
- NEW: Per-profile Light Control settings (brightness, transition, colour) in separate UI sections
- FIX: minor visual bugs
- RECENT: Cooldown options
- RECENT: Profile-specific Additional Actions
** 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
- 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
