Repository navigation
Time Zones
Tasmota does not know zone names like "Europe/Berlin". It can only
- apply a fixed offset (e.g.
Timezone +01:00) – then there is no daylight-saving switch, or - switch between two offsets with
Timezone 99, following the rules inTimeStdandTimeDst.
Many devices run with a fixed offset. Their clock is then an hour off for half the year – and timed rules fire an hour early or late.
On every status refresh the app reads the device clock and compares it with the zone under Settings → Timezone. Status refreshes run automatically with the reachability check (Settings → Reachability) or on click via Refresh status. A backup does not read the clock – if the reachability check is set to 0, click Refresh status after a change. The device list then shows a 🕒 hint below the name:
| Hint | Meaning |
|---|---|
| clock +1 h (or similar) | the device clock is wrong right now |
| fixed offset | the clock happens to be right today, but the device uses a fixed offset – after the next changeover it will be an hour off |
- Click the 🕒 hint (or Edit).
- The Time & time zone section shows what the device reports, what the server expects and which commands will be sent.
- Click Set to Europe/Berlin (or your zone).
For Europe/Berlin the app sends in one go:
Backlog TimeDst 0,0,3,1,2,120; TimeStd 0,0,10,1,3,60; Timezone 99
It then reads the device again (up to three times, since Tasmota applies commands with a short delay) and shows what actually took effect.
Note
The rules are derived from the time zone database – southern-hemisphere zones, zones without DST and half-hour offsets come out correctly too. Nothing is sent to a device without your click.