Just tested this entry from the list: "Europe/Berlin","CET-1CEST,M3.5.0,M10.5.0/3" Same problem as with other public examples: local time is correct, but file dates are offset 1 hour into the future. # con set vehicle timezone "CET-1CEST,M3.5.0,M10.5.0/3" Parameter has been set. # time stat Time Zone: CET-1CEST;M3.5.0;M10.5.0/3 UTC Time: 2018-06-06 08:15:18 UTC Local Time: 2018-06-06 10:15:18 CEST Provider: ntp PROVIDER STRATUM UPDATE TIME gsm-nmea 2 12 Wed Jun 6 08:15:18 2018 *ntp 1 53 Wed Jun 6 08:15:17 2018 # vfs ls /sd … 5 06-Jun-2018 11:14 testdate Maybe this is a bug in the vfs. "CET-2,M3.5.0/02:00:00,M10.5.0/03:00:00" works correctly now but I haven't tested if it would adapt to winter time. Regards, Michael Am 06.06.2018 um 08:56 schrieb Mark Webb-Johnson:
A topic on esp32.com <http://esp32.com> brought up this:
https://github.com/nayarsystems/posix_tz_db
The approach seems similar to what I spoke about before (scrape tzdata, although they scrape install zone files directly in /usr/share/zoneinfo). I’ve attached the csv output of that. 460 time zones, about 15KB code size. That is up-to-date with tzdata 2018d-1. Including a simple library wrapper, to (a) iterate over the zone names, and (b) return the posix string for a particular name, probably less than 20KB overhead.
I live in such a simple timezone, it is hard for me to judge. Is this any use?
Regards, Mark.
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26