Advanced Use Cases Bedroom Sleep Mode

Bedroom sleep mode

Keep blinds closed from bedtime until just before your alarm, overriding sunrise. A template binary sensor computes whether you're inside the sleep window, and a Custom Position slot holds the cover at 0% for as long as that sensor is on.

Once the sensor turns off, at the wake-up offset you configure, the custom position slot steps aside and the integration resumes normal adaptive tracking.

---

How the window works

The sleep window spans midnight, so the template has two halves:

• Evening portion: sensor turns on when the clock reaches the configured bedtime (22:00 in the example below)
• Morning portion: sensor stays on from midnight until the offset-adjusted alarm time, but only if the alarm is set for today (not a future date), preventing false positives after the alarm fires

If no alarm is set or the alarm sensor is unavailable, the sensor stays on from bedtime until midnight only, a safe fallback that keeps the cover closed overnight even without an alarm entity.

---

Step 1: Create the template binary sensor

Add the following to configuration.yaml, then restart Home Assistant or reload the Template integration:

template:
  - binary_sensor:
      - name: "Bedroom Sleep Mode"
        device_class: occupancy
        state: >
          {% set t = now() %}
          {% set alarm = states('sensor.mobile_app_phone_next_alarm') %}
          {% if alarm in ('unavailable', 'unknown') %}
            {{ t.hour >= 22 }}
          {% else %}
            {% set wake_dt = (alarm | as_datetime | as_local) - timedelta(minutes=10) %}
            {% set in_evening = t.hour >= 22 %}
            {% set in_morning = t.hour < 12 and t < wake_dt and wake_dt.date() == t.date() %}
            {{ in_evening or in_morning }}
          {% endif %}

Replace sensor.mobile_app_phone_next_alarm with your actual alarm entity, typically provided by the Home Assistant Companion App.

The timedelta(minutes=10) is the wake-up offset. Increase it if you want the cover to start brightening earlier; set it to timedelta(minutes=0) to open exactly when the alarm fires.

To shift bedtime away from 22:00, change t.hour >= 22. For example, t.hour >= 23 delays the window to 23:00.

Fixed wake-up time (no alarm sensor)

If you use a fixed wake-up time rather than a phone alarm, the template is simpler:

template:
  - binary_sensor:
      - name: "Bedroom Sleep Mode"
        device_class: occupancy
        state: >
          {% set h = now().hour %}
          {{ h >= 22 or h < 7 }}

This keeps the blind closed from 22:00 to 07:00 every day. Replace 22 and 7 with your schedule. Note there is no wake-up offset here; add or (h == 6 and now().minute < 50) style logic if you want a window before 07:00.

---

Step 2: Configure the Custom Position slot

Open the integration's options for your bedroom cover and configure one of the four Custom Position slots:

Setting	Value
Custom Position Sensor	binary_sensor.bedroom_sleep_mode
Custom Position	0%
Priority	77 (default)

At priority 77, the sleep mode sits above the solar (40), climate (50), cloud suppression (60), and motion timeout (75) handlers, so it overrides all of those. Manual Override runs at priority 80 and Weather Override at 90, both still take precedence, so you can open the blind manually during sleep hours if needed, and weather safety remains active.

If you want the sleep mode to hold regardless of manual interaction, raise the priority to 81. You would then need Force Override (priority 100) or disabling the integration entirely to open the blind during sleep hours.

---

How it fits in the pipeline

Force(100) → Weather(90) → Manual(80) → Sleep Mode Custom(77) → Motion(75) → Cloud(60) → Climate(50) → Glare(45) → Solar(40) → Default(0)

While binary_sensor.bedroom_sleep_mode is on, the Custom Position handler fires at priority 77 and holds the cover at 0%. Solar, climate, and glare handlers run but don't claim the position. The decision trace in the dashboard card or diagnostics panel will show custom_position as the active handler with the sensor name.

When the sensor turns off at the wake-up offset, the Custom Position handler produces no result. The pipeline falls through to whichever handler is next, typically solar, which picks up the current sun position and moves the cover into its tracking position before the alarm rings.

---

Related pages

• Custom Position: full slot configuration reference and additional examples
• How It Decides: full priority chain explanation
• Panel Card: decision trace visualization
• Advanced Use Cases: all advanced use case recipes