Whit the Icalendar app things went well for a while with appointments at 00:00 of a new day. Lately I’ve only been getting it back at 02:00 just like before the update a while back. What happened ? I haven’t done the Homey beta update yet.
???
This is a very unclear information. So we can only guess.
Which IcalCalender app version is installed?
I am aware that for the new Homey firmware v7.4.0 some apps need to be adjusted to use the correct local time.
My guess is that the IcaCalender app has been revised to do this, but now uses the wrong time (UTC) in combination with the Homey firmware v7.3.0. But it’s just a guess.
Maybe @runely can clarify it?
Btw, because the question refers specifically to the IcalCalender app and actually has nothing to do with the thread topic, it might have made more sense to create a new thread.
@DirkG
Yes, I also think that it has already been updated to the new time in Homey.
Homey: 7.3.0
I use ical 1.0.3 there is no test version.
Sorry for the confusion I couldn’t find the correct topic.
No confusion. And afaik there is no “official” IcalCalender topic.
The only reason whyI suggested this is because this topic is relatively old and actually involves a different question.
With a new and separate topic, the range in the community would probably be much greater. Do you understand what I mean? 
Back to the question. Since App version v1.0.0, changes have definitively been made regarding SDK3, which I believe is necessary for the Homey FW v7.4.0.
Maybe Rune will explain the background.
1 Like
You can view/track/add issues @ iCalCalendar github.
The changelog has this entry, seems to be related
- 0.14.2
26 feb. 2022
Bugfixes: Recurring events starting at 00:00 was misread
And 0:00h UTC = 02:00h Dutch local (summer)time, so it looks like a similar issue.
About v7.4.0-rc firmware:
iCalCalendar seems to run fine on it:
As stated by @DirkG, IcalCalendar was rewritten from SDK2 to SDK3 in version 1.0.0.
As of SDK3, Athom has changed Homey to always work in UTC timezone…
IcalCalendar then does its best to parse calendar events from UTC to the timezone your Homey is set to use.
Is this a problem only for recurring events starting at 00:00? Or do you see this problem with regular one-time events starting at 00:00 aswell?
1 Like
It is mainly with all day events.
For example today is a day off, which of course starts at 00:00 but I only get that message at 02:00 So it seems that the time is 2 hours wrong what @Peter_Kawa said.
I don’t have the Homey beta so maybe that’s the difference ?
It worked well before the update of Icalcalender 1.03. It works normal with 1.02
so I’m getting more and more apps that break because the New Beta use different timestamp. strange change of athom
That’s caused by a different problem, the “different timestamp” issue was introduced with SDKv3, which was already some time ago. Homey supports both SDKv2 and SDKv3 apps, and only SDKv3 apps are affected by it, that’s why different versions of the same app can be differently affected (if one version was written for SDKv2 and the other version for SDKv3).
1 Like
And is these all day events regular one-time events or recurring events?
It seems very strange that this doesn’t work in 1.0.3 but works in 1.0.2. The only difference between these versions has nothing to do with datetime / timezone.
I see it on recurring events and all day.
I have now put a test in my agenda for tomorrow at a time. Will follow tomorrow if it comes on time or if there is also a 2 hour difference.
@runely
I tested it at 10 o’clock in the day and then it works well and on time. Strange that Homey with events from 00:00 only runs well after 02:00 in the night. and for 02:00 the logic tag is also misread.
The rest of the day is going well.
Which worked fine before so something is wrong between twelve and two o’clock in the night the new day.
What worked well before so maybe because of that beta that I don’t have ?
Here are some nice tests. When the new day begins, it is already 02:00. Because he doesn’t give a message until 01:00 that it will start in an hour from Quinsday. So a new day. It will run nice on time during the rest off the day.
In google settings the time is on gmt2 so plus two hours which is normal in the Netherlands.
Really strange that there is a two hour delay at night, what could be the cause ?
I wonder if it may be caused by this line: calendar-homey/get-active-events.js at 3b8204a5aa1af28ff3965c58836c3735a05a0f2f · runely/calendar-homey · GitHub (and/or these two: calendar-homey/get-active-events.js at 3b8204a5aa1af28ff3965c58836c3735a05a0f2f · runely/calendar-homey · GitHub)
1 Like
It could be that it is. What can I do about this ?
I am not familiar with json. Still waiting for the maker of app answer.
That’s all you can do.
OK, so this is only happening with whole day events
Can you download your .ics file (open the link in a browser)
Search for the event by summary (Koninginnedag)
And copy everyhing between BEGIN:VEVENT and END:VEVENT for that event and paste it here (remove any identifiable information before posting)
Will be interesting to see how that event is presented in the .ics file.
My whole day events are presented with a date only (no time information), like this (for both one-time and recurring events): DTSTART;VALUE=DATE:20220501
yes, especially full day events. Or events that are between 00:00 and 02:00. After 02:00 on the clock, things are going well again
SUMMARY:Koninginnedag
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20220430
DTEND;VALUE=DATE:20220501
DTSTAMP:20220430T171857Z
UID:040000008200E00074C5B7101A82E00800000000B0F03984AFE6D101000000000000000
0100000007857E1B0D402E041B4371594442A89D3
CREATED:20160726T174357Z
DESCRIPTION:
LAST-MODIFIED:20160726T174357Z
LOCATION:Nederland
SEQUENCE:0
STATUS:CONFIRMED
This wone is good it is on daytime
SUMMARY:
kapper
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART:20220501T200000Z
DTEND:20220501T210000Z
DTSTAMP:20220430T171857Z
UID:
CREATED:20220427T183722Z
DESCRIPTION:
LAST-MODIFIED:20220429T190836Z
LOCATION:
SEQUENCE:3
STATUS:CONFIRMED
Which event belongs where?
Please post the whole event (everything between BEGIN:VEVENT and END:VEVENT ). And a bonus if you format them 
I dont understand ?
This is all I see in the ical file. it’s in unicode8 There’s nothing in between what you say.
SUMMARY:Koninginnedag
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20220430
DTEND;VALUE=DATE:20220501
DTSTAMP:20220430T171857Z
UID:040000008200E00074C5B7101A82E00800000000B0F03984AFE6D101000000000000000
0100000007857E1B0D402E041B4371594442A89D3
CREATED:20160726T174357Z
DESCRIPTION:
LAST-MODIFIED:20160726T174357Z
LOCATION:Nederland
SEQUENCE:0
STATUS:CONFIRMED
If that is your whole ics file, and it’s presented like this, it seems broken!
However, this event works fine when i apply the timezone Europe/Amsterdam:
BEGIN:VEVENT
DTSTART;VALUE=DATE:20220430
DTEND;VALUE=DATE:20220501
DTSTAMP:20220430T171857Z
UID:040000008200E00074C5B7101A82E00800000000B0F03984AFE6D101000000000000000
0100000007857E1B0D402E041B4371594442A89D3
CREATED:20160726T174357Z
DESCRIPTION:
LAST-MODIFIED:20160726T174357Z
LOCATION:Nederland
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Koninginnedag
TRANSP:TRANSPARENT
END:VEVENT
Type: 'Regular' -- Summary: 'Koninginnedag' -- Start: 'Sat Apr 30 2022 00:00:00 GMT+0000' -- End: 'Sun May 01 2022 00:00:00 GMT+0000' -- Timezone: 'Europe/Amsterdam'
Can you confirm that you have set the correct position for your Homey in the Homey app settings?
- More
- Settings
- Position
Make sure Find Homey position automatically is activated or that you have selected the correct location in the map.
This is the timezone used by IcalCalendar to get the correct datetime for your events.
