Originally posted by Blade
View Post
I ran a test last night with the following adjacent events in one calendar (TESTINGS)
EventName Start Date/Time End Date/Time
TEST2 17.10.2018 00:00:00 17.10.2018 01:00:00
TEST3 17.10.2018 01:00:00 17.10.2018 02:00:00
TEST4 17.10.2018 02:00:00 17.10.2018 03:00:00
The handler that I used looks like this:
Trigger: TEST
Calendar selected: "TESTINGS"
Regular expression: No
Offset before: 15 minutes
Offset after: 15 minutes
Calendars selected: Yes
Use End time: Yes
Execute Commands at Start Time: No
The events before and after was executed according to the settings in the handler at the time they should:
okt-16 23:45:03 Info BLGData Event start TEST2 - OK
okt-17 00:44:33 Info BLGData Event start TEST3 - OK
okt-17 01:14:55 Info BLGData Event end TEST2 - NOT OK - this event will trigger the after command in the period for TEST3 01:00-02:00
okt-17 01:44:44 Info BLGData Event start TEST4 - OK
okt-17 02:14:57 Info BLGData Event end TEST3 - NOT OK - this event will trigger the after command in the period for TEST4 02:00-03:00
okt-17 03:14:47 Info BLGData Event end TEST4 - OK
As you can see the problem here is really the After commands triggered by the End time in the event. Because of the offset values, the end time will be inside the active time for another event. We are using another embedded system for controlling lights for our indoor Tennis Courts. This system is also controlled by separate Google Calendars (one for each court). If there are adjacent events the software in the controller will merge all the adjacent events into one to avoid the offset end time (5 mins. before and after) to interfere into another adjacent event.
The first attachment (black) shows how the 3 adjacent events today from 1600-1900 hrs has been merged into one event to avoid problems with the offset time by the embedded system controlling the lights based on events from a Google Calendar. The other attachment shows the events in the Google Calendar
Comment