I’ve fixed the problem.
The problem was caused by old calendar entries.
Clearing the howl calendar made the error disappeared.
So Thread could be closed.
Thx for your answer!
Appointment time on calendar is off by an hour
I am facing the same problem so let me provide some more (reproducable) insight:
Timezone Android: (GMT+1)
Timezone Server: Europe/Berlin (which is GMT+1)
@fraschi Thanks for your report. What is your server software (to reproduce the problem, I have to use the same server in the same version)? Or can you provide a test account on this server? Is there any indication that this might be a DAVdroid problem?
its an All-inkl.com account. They offer free test accounts.
@fraschi Did you try other clients with Europe/Berlin time zone? Did you already ask server support?
@rfc2822 I am also using the Google calendar on both desktop and Android with no such issues and had been using other server based calendars in the past. This is the first time I am using a caldavs-sync, though.
In the meantime I have checked with the server support and they reconfirmed that the server time/zone is set correctly to GMT+1 =CET).
What strikes me that Android calls the local time “Central European Standard Time” which is afaic wrong. Is it possible you are checking the local time using the ISO abbreviation? If so, then CEST is wrong (and would explain the offset) as it stands for Central European Summertime and not Standard Time…?
@fraschi I have tested it and can confirm that this is a server bug. When creating an event on 22 Feb 2017 in the Webmail interface, the server sends this CalDAV event:
BEGIN:VCALENDAR PRODID:-//WMAPI iCALENDAR// VERSION:2.0 METHOD:PUBLISH BEGIN:VTIMEZONE TZID:Europe/Berlin X-LIC-LOCATION:Europe/Berlin BEGIN:STANDARD DTSTART:20171029T030000 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET END:STANDARD BEGIN:DAYLIGHT DTSTART:20170326T020000 TZOFFSETFROM:+0100 TZOFFSETTO:+0200 TZNAME:CEST END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT CREATED:20170205T145357Z LAST-MODIFIED:20170205T145357Z DTSTAMP:20170205T145357Z UID:5e0849bd-08e6-4ec1-a6b3-1367b3e0f0b2 SUMMARY:abc DTSTART;TZID=Europe/Berlin:20170222T210000 DTEND;TZID=Europe/Berlin:20170222T233000 END:VEVENT END:VCALENDAR
Please note the timezone definitions:
BEGIN:STANDARD DTSTART:20171029T030000 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET END:STANDARD
So, Berlin standard time (CET) begins on 29 Oct 2017 and is not applicable.
BEGIN:DAYLIGHT DTSTART:20170326T020000 TZOFFSETFROM:+0100 TZOFFSETTO:+0200 TZNAME:CEST END:DAYLIGHT
DST begins on 26 Mar 2017 and thus is also not applicable to the event on 22 Feb.
So, the time zone definition is not usable and results are unpredictable.
Can you please report this server bug to all-inkl.com?
@rfc2822 Thanks a lot! I will forward this and keep you posted.
@rfc2822 Thanks again, I can confirm that this was a server issue which has been fixed accordingly. Since then Davroid is working flawlessly.
It would be great if a user could perform the same checks you had performed using the debug approach. Is this an option?