Local Calendar feature request 5 - Recognise overlapping events

[AndySymons]

@123

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

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

@Tinkerer

Somebody’s answer solved it!

Fantastic!

Now, before you go… please take the time to mark that as the answer, you do that by selecting the three dots under the post:

Then select the check box:

Don’t forget too while you’re down there to click the heart to like the post, as a way of saying thank you.

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.