Is your feature request related to a problem? Please describe.
I am currently using the adapter to control my heaters. For that I use a nextcloud calendar in which I add events for the whole duration on when the heater should be turned on (e.g. 7:00 to 11:30). This works as expected. My problem is that alll those multi-hour events look awfull in die calendar UI.
I would prefer to only have trigger events (start == end) but those are not recognized by the adapter.
"now" seems only to consider events that are running by the time the calendar gets queried. So if my adapter pulls at 7:00 and 07:05 the event that starts and ends at 7:03 does not get recognized.
Describe the solution you'd like
The adapter knows at which intervals its beeing triggered (does it?). So it should be able to recognize events that start and end before the next query to mark them active until the next query.
The blue event starts and ends between two queries. So it should be considered active at the first query. Event 2 starts between the first two queries but ends after the second and should only be considered active at the second query.
Describe alternatives you've considered
For now I will set up my events to be longer then the query interval but as short as possible to not clutter my calendar UI. That will work as long as I am the only user of the system and as long as I remember the current query interval of the adapter.
Is your feature request related to a problem? Please describe. I am currently using the adapter to control my heaters. For that I use a nextcloud calendar in which I add events for the whole duration on when the heater should be turned on (e.g. 7:00 to 11:30). This works as expected. My problem is that alll those multi-hour events look awfull in die calendar UI. I would prefer to only have trigger events (start == end) but those are not recognized by the adapter. "now" seems only to consider events that are running by the time the calendar gets queried. So if my adapter pulls at 7:00 and 07:05 the event that starts and ends at 7:03 does not get recognized.
Describe the solution you'd like The adapter knows at which intervals its beeing triggered (does it?). So it should be able to recognize events that start and end before the next query to mark them active until the next query.
The blue event starts and ends between two queries. So it should be considered active at the first query. Event 2 starts between the first two queries but ends after the second and should only be considered active at the second query.
Describe alternatives you've considered For now I will set up my events to be longer then the query interval but as short as possible to not clutter my calendar UI. That will work as long as I am the only user of the system and as long as I remember the current query interval of the adapter.