Local Calendar feature request 5 - Recognise overlapping events

Couple of days? Your tutoring must have been good because I did it in a couple of hours!

The relevant code is the following fragment, which appears at the start of the automation, so runs whatever the trigger is (start_event, end_event and several others).

  local_room_calendar: !input room_calendar 

## -------------------------------------------------------------------------------------------------
## Current event is the one that started last
## -------------------------------------------------------------------------------------------------
  - service: calendar.get_events
      entity_id: !input room_calendar
        hours: 0
        minutes: 0
        seconds: 1
    response_variable: active_events

  - service: calendar.get_events
      entity_id: !input room_calendar
        hours: 24
        minutes: 0
        seconds: 0
    response_variable: future_events

  - variables:
      any_event_active: >
        {{ active_events[local_room_calendar].events | count > 0 }}
      current_event: >
        {{ active_events[local_room_calendar].events | sort(attribute ='start') | list | last | default("") }}
      any_future_event: >
        {{ future_events[local_room_calendar].events | count > 0 }}
      next_event: >
        {{ future_events[local_room_calendar].events | sort(attribute ='start') | list | first | default ("") }} 

The rest of the automation uses the four variables I set.

  • any_event_active and any_future_event are booleans used in condition templates.

Other templates refer to


… and similarly for next_event

I have the required temperature in the description between two hashes, so that is extracted as


UPDATE 25-Feb: the code above is streamlined to one template line per variable, and a default is added to stop warnings in the error log file when there are no events.

For the full code see Heating X2 blueprint


It’s the custom of this community to assign the Solution tag to the first post that answers/solves the original question/problem.

Despite first having to be convinced your FR wasn’t necessary and was already achievable, receiving numerous detailed explanations on how to do it, including a tutorial on how to handle a response_variable, you ultimately chose to mark your own post as the Solution.

You may wish to familiarize yourself with guideline 21 in the FAQ.

The guidance says
Continuing the discussion from How to help us help you - or How to ask a good question:

I solved the overlapping events problem with a lot of help from you, a little from Drew, and some from Allenporter on what tuned out to be a related issue on Githubi. The final code took a fair bit of experimentation and further research once you had set me on the right track. I found List of Builtin Filters particularly useful.

I transferred the code to my context (in an automation, using local variables), streamlined the code (using first and last filters), used two calendar.get_events calls for current and future events, and added the default filter to eliminate warnings in the log file when there are no events.

Your help was invaluable and I am happy to acknowledge that formally if there is a means of doing so beyond ‘liking’ your postings. For a reader of the thread, however, the actual solution to the problem is in the posting that I indicated.

I can only tick one posting as the ‘solution’. Which one do you propose?

BTW I am not convinced that my FR wasn’t necessary. It was made in good faith based on the existing documentation and would still be a much simpler solution if adopted.

This one:

Because it spells out what is the recommended way of currently achieving the FR’s goal.

The majority of the topic is me tutoring you on how to implement it, including fundamentals like how a dictionary can be represented and how to access the keys and values of the dictionary within a response_variable.