Time offset Horde/New York



  • I'm having the same problem on my self-hosted Horde server. Logs for a test event (at 10am America/New_York -- which is converted to 9am when created on my phone and synced via Davdroid) below......

    BEGIN:VCALENDAR
    VERSION:2.0
    PRODID:+//IDN bitfire.at//DAVdroid/1.4.0.1-ose ical4android ical4j/2.x
    BEGIN:VEVENT
    DTSTAMP:20170213T134133Z
    UID:1297c5fd-05be-4b2a-bbcd-71cefeacfea9
    DTSTART;TZID=America/New_York:20170213T100000
    DTEND;TZID=America/New_York:20170213T110000
    SUMMARY:Test for Davdroid debug 10am
    STATUS:CONFIRMED
    END:VEVENT
    BEGIN:VTIMEZONE
    TZID:America/New_York
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    DTSTART:19180331T020000
    RRULE:FREQ=YEARLY;UNTIL=19190330T070000Z;BYMONTH=3;BYDAY=-1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    DTSTART:19181027T020000
    RRULE:FREQ=YEARLY;UNTIL=19191026T070000Z;BYMONTH=10;BYDAY=-1SU
    TZNAME:EST
    END:STANDARD
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    DTSTART:19200328T020000
    RRULE:FREQ=YEARLY;UNTIL=19200328T070000Z;BYMONTH=3;BYDAY=-1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    DTSTART:19201031T020000
    RRULE:FREQ=YEARLY;UNTIL=19201031T070000Z;BYMONTH=10;BYDAY=-1SU
    TZNAME:EST
    END:STANDARD
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    DTSTART:19210424T020000
    RRULE:FREQ=YEARLY;UNTIL=19660424T070000Z;BYMONTH=4;BYDAY=-1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    DTSTART:19210925T020000
    RRULE:FREQ=YEARLY;UNTIL=19540926T070000Z;BYMONTH=9;BYDAY=-1SU
    TZNAME:EST
    END:STANDARD
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    DTSTART:19420209T020000
    TZNAME:EWT
    END:DAYLIGHT
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0400
    DTSTART:19450814T230000
    TZNAME:EPT
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    DTSTART:19450930T020000
    RRULE:FREQ=YEARLY;UNTIL=19450930T070000Z;BYMONTH=9;BYDAY=-1SU
    TZNAME:EST
    END:STANDARD
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    DTSTART:19460428T020000
    RRULE:FREQ=YEARLY;UNTIL=19660424T070000Z;BYMONTH=4;BYDAY=-1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    DTSTART:19460929T020000
    RRULE:FREQ=YEARLY;UNTIL=19540926T070000Z;BYMONTH=9;BYDAY=-1SU
    TZNAME:EST
    END:STANDARD
    BEGIN:STANDARD
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0500
    DTSTART:19551030T020000
    RRULE:FREQ=YEARLY;UNTIL=19661030T070000Z;BYMONTH=10;BYDAY=-1SU
    TZNAME:EST
    END:STANDARD
    BEGIN:STANDARD
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0500
    DTSTART:19671029T020000
    RRULE:FREQ=YEARLY;UNTIL=20061029T070000Z;BYMONTH=10;BYDAY=-1SU
    TZNAME:EST
    END:STANDARD
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    DTSTART:19670430T020000
    RRULE:FREQ=YEARLY;UNTIL=19730429T070000Z;BYMONTH=4;BYDAY=-1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0400
    DTSTART:19740106T020000
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0400
    DTSTART:19750223T020000
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0400
    DTSTART:19760425T020000
    RRULE:FREQ=YEARLY;UNTIL=19860427T070000Z;BYMONTH=4;BYDAY=-1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0400
    DTSTART:19870405T020000
    RRULE:FREQ=YEARLY;UNTIL=20060402T070000Z;BYMONTH=4;BYDAY=1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0400
    DTSTART:20070311T020000
    RRULE:FREQ=YEARLY;BYMONTH=3;BYMONTHDAY=8,9,10,11,12,13,14;BYDAY=1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    DTSTART:20071104T020000
    RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
    TZNAME:EST
    END:STANDARD
    END:VTIMEZONE
    END:VCALENDAR


  • developer

    Hello,

    We have received reports about incorrect timezone definitions of Horde earlier. Could you please check whether the VTIMEZONE definition is correct / what Horde people say about that? I guess it's not a DAVdroid problem.



  • I see bugs filed w/Horde re timezone definitions, but all appear to be resolved. And not quite clear what I should be checking re the VTIMEZONE variable. Also FWIW, I tried DAVdroid w/SOGo on the same (Debian) box and had the same problem. So I suppose it might be a problem in some Debian package (tzdata? php-sabre-dav?). But it seems somewhat unlikely to be Horde specific.


  • developer

    @skug67 Ok, can you please provide verbose instructions what I can do to reproduce the problem (including Android version, server and version, exact event information) so that I can have a look at it?



  • Android = 7.0
    Android calendar set to use "Eastern Standard Time GMT-5"
    Horde framework = 5.2.13
    Horde kronolith (calendar) = 4.2.19
    Horde timeobjects (relevant?) = 2.1.3
    Server OS = debian jessie
    tzdata = 2016j-0+deb8u1
    php-date = 1.4.7-2

    On Android create any event. Before sync shows on device with correct time. Then sync to server. After sync shows on both device and server one hour earlier than when created.


  • developer

    When uploading an event at 16 Feb 2017 10:00 Eastern standard time, DAVdroid puts this event + ical4j timezone definition to the server:

    BEGIN:VCALENDAR
    VERSION:2.0
    PRODID:+//IDN bitfire.at//DAVdroid/1.4.0.2 ical4android ical4j/2.x
    
    BEGIN:VEVENT
    DTSTAMP:20170219T175556Z
    UID:20170219T175554Z-b17c600e48506c59
    DTSTART;TZID=America/New_York:20170216T100000
    DTEND;TZID=America/New_York:20170216T110000
    SUMMARY:Test
    STATUS:TENTATIVE
    END:VEVENT
    
    BEGIN:VTIMEZONE
    TZID:America/New_York
    TZURL:http://tzurl.org/zoneinfo/America/New_York
    X-LIC-LOCATION:America/New_York
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    TZNAME:EDT
    DTSTART:20070311T020000
    RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    TZNAME:EST
    DTSTART:20071104T020000
    RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
    END:STANDARD
    
    END:VTIMEZONE
    END:VCALENDAR
    

    (empty lines for visual separation)

    Then, Horde converts this to this and sends it back (as an updated event):

    BEGIN:VCALENDAR
    VERSION:2.0
    X-WR-CALNAME:Cal Of Thrones
    PRODID:-//The Horde Project//Horde iCalendar Library//EN
    
    BEGIN:VEVENT
    DTSTART;TZID=America/New_York:20170216T090000
    DTEND;TZID=America/New_York:20170216T100000
    DTSTAMP:20170219T175649Z
    UID:20170219T175554Z-b17c600e48506c59
    CREATED:20170219T175634Z
    LAST-MODIFIED:20170219T175634Z
    SUMMARY:Test
    CLASS:PUBLIC
    STATUS:TENTATIVE
    TRANSP:OPAQUE
    END:VEVENT
    
    BEGIN:VTIMEZONE
    TZID:America/New_York
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0400       !!!!
    TZOFFSETTO:-0400
    DTSTART:20070311T020000
    RRULE:FREQ=YEARLY;BYMONTH=3;BYMONTHDAY=8,9,10,11,12,13,14;BYDAY=1SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    DTSTART:20071104T020000
    RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
    TZNAME:EST
    END:STANDARD
    END:VTIMEZONE
    
    END:VCALENDAR
    

    As you can see, the daylight definition switches from a -4:00 offset to -4:00, while standard time switches from -4 to -5.

    So this is a timezone problem of Horde (specifically in the DAYLIGHT definition) and not a DAVdroid problem. Please contact Horde regarding this.

    I don't know why SOGo has this problem, too. Maybe there's a problem with the tzdata, but in this case, I can't do anything, too.

    If there are any indications that this could be a DAVdroid problem, feel free to post here again.


Log in to reply
 

Looks like your connection to Bitfire App Forums was lost, please wait while we try to reconnect.