-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sensors are always the first four items in my calendar #60
Comments
This is the way it should work. |
Issue is I'm not seeing it updated at all _0 is always the first event of the day, even at 4pm when I'm leaving work. How often does the plugin request the ical from the server? Even if it only requested it once I would think it would still change through out the day. |
I think you are right. We don't check the start-time, only start-date when populating the sensors. So _0 is always the first event with an end-datetime after midnight today. |
I had a look at the code, and this is not very trivial to do.... I think it should be possible to replace this
With a call to And I don't have a proper development setup at the moment, as I don't have much time to do develoment for now. |
From the description:
This integration will create sensors for the next few future calendar events, called:
sensor.ical_my_calendar_event_0
sensor.ical_my_calendar_event_1
sensor.ical_my_calendar_event_2 (...)
I would assume Next Few would mean that event 0 would become the value of event 1 once event 0 was over, is this not the way it should occur?
The text was updated successfully, but these errors were encountered: