How do you use a calendar offset in a Condition?

Configuration
1

Hi
I have 3 automated lights in my bedroom.
LEDs under the bed, a soft lamp and a brighter main lamp.

I’m stuck on trying to figure out how to set date offsets relative to a google calendar entry as a condition (not a trigger)

The calendar entry puts the home into “sleep” and the event’s times often change depending on work schedule, weekends etc. The sleep event also runs a sleep profile on mobile devices (on/off mute w. tasker) so we don’t get disturbed.

What I’m stuck with is setting a condition on 2 sets of distinct times offset against the calendar entry.

The following are all triggered on motion:
LED lights that come on low during “sleep” (this works atm)
The soft lamp from 2hrs pre event start and up to 2hrs after sleep end.
The bright lamp up to 2hrs before the sleep starts and from 2hrs after it ends.

This graphic may make it easier to explain what I’m trying to achieve

image
image998×230 24.5 KB

Can this be done in a condition (template?) with the single calendar entry?

With the old Calendar system I think I could have created an extra calendar entity for “Near Sleep” offsetting against the main sleep event, but my original setup using google_calendars.yaml broke a couple of releases ago.
I think that that may be working again (?) but I’ve lost trust in that after it broke - esp as it ran my heating schedule among other thing and I’ve since split events into multiple calendars

3

I think I may have worked out a way of making the calendar offset in a template.
The only thing is that I had to re-introduce my google_calendar.yaml to get each event type back into it’s own unique calendar entity.

{% set datenow = (as_timestamp(now())| float() | round (0)) %}
{% set sleeping_near_start = (as_timestamp(state_attr("calendar.sleeping","start_time")) - 120*60 | float() | round (0)) %}
{% set sleeping_near_end = (as_timestamp(state_attr("calendar.sleeping","end_time")) + 120*60 | float() | round (0)) %}
{% if (datenow >= sleeping_near_start) and (datenow <= sleeping_near_end) %}
True
{% else %}
False
{% endif %}
4

Agh, I just realised that doesn’t work.
While it does detect the offset 2hrs in advance, as soon as the calendar entry ends it ignores that entry and applies the +2hr offset to the next event (tomorrow)

… balls

5

Have you considered using trigger-based Template sensors? Something like the following:

template:
  - trigger:
      - platform: calendar
        event: start
        entity_id: calendar.sleeping
        id: sleep
      - platform: calendar
        event: start
        entity_id: calendar.sleeping
        offset: "-02:00:00"
        id: soft
      - platform: calendar
        event: end
        entity_id: calendar.sleeping
        id: soft
      - platform: calendar
        event: end
        entity_id: calendar.sleeping
        offset: "2:00:00"
        id: bright
     sensor:
      - name: Active Light Profile
        state: "{{ trigger.id | default('bright', 1) }}"
6

Yea, I’m thinking a custom automation to set a toggle will be the way to go with this.
Thanks for the reply :slight_smile:

7

I created a boolean and did it this way with an automation.
There are already some other actions when the house goes into “sleep”, so I tagged these onto that automation.
Cut down version below

alias: Toggle - Sleeping
description: ""
trigger:
  - platform: calendar
    event: start
    offset: "-2:0:0"
    entity_id: calendar.sleeping
    id: near-pre
  - platform: calendar
    event: end
    offset: "2:0:0"
    entity_id: calendar.sleeping
    id: near-post
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id: near-pre
        sequence:
          - service: input_boolean.turn_on
            data: {}
            target:
              entity_id: input_boolean.near_sleeping
      - conditions:
          - condition: trigger
            id: near-post
        sequence:
          - service: input_boolean.turn_off
            data: {}
            target:
              entity_id: input_boolean.near_sleeping
mode: restart

As I also have the sleeping state, this gives me 3 combinations of on/off that I was looking for to work the lights.

image
image1612×238 19.4 KB