> For the complete documentation index, see [llms.txt](https://docs.dnt.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dnt.de/dnt-lw-etrv/kommunikationsprotokoll/3.-geratezeit.md). # 3. Gerätezeit ## 3.1 Gerätezeit {% tabs %} {% tab title="GET DEVICE TIME" %} Abfrage der lokalen Gerätezeit. **Downlink** | Byte | Bit(s) | Value | | :--: | :----: | :-----------------: | | 0 | 7 | IR | | 0 | 6:0 | `0x08` (Command ID) | **Uplink** | Byte | Bit(s) | Value | | :----------: | :----: | :---------------------: | | 0 | 7 | Res. | | 0 | 6:0 | `0x08` (Command ID) | | 1 | 7:6 | Res. | | 1 | 5:0 | `ID_LOCAL_TIME_SECOND` | | 2 | 7:2 | `ID_LOCAL_TIME_MINUTE` | | 2 | 1:0 | `ID_LOCAL_TIME_HOUR` | | 3 | 7:5 | `ID_LOCAL_TIME_HOUR` | | 3 | 4:0 | `ID_LOCAL_TIME_DAY` | | 4 | 7 | `ID_LOCAL_TIME_DST` | | 4 | 6:4 | `ID_LOCAL_TIME_WEEKDAY` | | 4 | 3:0 | `ID_LOCAL_TIME_MONTH` | | 5 | 7:0 | `ID_LOCAL_TIME_YEAR` | | 6 | 7:0 | `ID_UTC(_DST)_OFFSET` | | {% endtab %} | | | {% tab title="SET DEVICE TIME" %} Setzen der globalen Gerätezeit. **Beispiel** ``` 097A6F031Ah = 15.04.2026, 14:30 UTC ``` | Byte | Bit(s) | Value | | :-----------: | :----: | :---------------------: | | 0 | 7 | Res. | | 0 | 6:0 | `0x09` (Command ID) | | 1 | 7:2 | `ID_GLOBAL_TIME_MINUTE` | | 1 | 1:0 | `ID_GLOBAL_TIME_HOUR` | | 2 | 7:5 | `ID_GLOBAL_TIME_HOUR` | | 2 | 4:0 | `ID_GLOBAL_TIME_DAY` | | 3 | 7:4 | Res. | | 3 | 3:0 | `ID_GLOBAL_TIME_MONTH` | | 4 | 7:0 | `ID_GLOBAL_TIME_YEAR` | | {% endtab %} | | | | {% endtabs %} | | |

ID_LOCAL_TIME_SECOND

y = x

\[y] = s

ID_LOCAL_TIME_MINUTE

y = x

\[y] = min

ID_LOCAL_TIME_HOUR

y = x

\[y] = h

ID_LOCAL_TIME_DAY

y = x

\[y] = d

ID_LOCAL_TIME_WEEKDAY

0 → Montag

1 → Dienstag

2 → Mittwoch

3 → Donnerstag

4 → Freitag

5 → Samstag

6 → Sonntag

ID_LOCAL_TIME_MONTH

y = x + 1

\[y] = Monat

ID_LOCAL_TIME_YEAR

y = x + 2000

\[y] = a

ID_LOCAL_TIME_DST

0 → Sommerzeit aktiv

1 → Winterzeit aktiv

ID_UTC(_DST)_OFFSET

y = x \* 0,25 - 12

\[y] = h

ID_GLOBAL_TIME_MINUTE

y = x

\[y] = min

ID_GLOBAL_TIME_HOUR

y = x

\[y] = h

ID_GLOBAL_TIME_DAY

y = x

\[y] = d

ID_GLOBAL_TIME_MONTH

y = x + 1

\[y] = Monat

ID_GLOBAL_TIME_YEAR

y = x + 2000

\[y] = a

*** ## 3.2 Gerätezeit Konfiguration {% tabs %} {% tab title="GET DEVICE TIME CONFIG" %} Abfrage der Gerätezeitkonfiguration. **Downlink** | Byte | Bit(s) | Value | | :--: | :----: | :-----------------: | | 0 | 7 | IR | | 0 | 6:0 | `0x0A` (Command ID) | **Uplink**

Byte	Bit(s)	Value
0	7	Res.
0	6:0	`0x0A` (Command ID)
1	7	`ID_AUTO_TIME_SYNC_EN`
1	6:0	`ID_UTC_OFFSET`
2	7	Res.
2	6:4	`ID_UTC_DST_START_WEEK_OF_MONTH`
2	3:0	`ID_UTC_DST_START_MONTH`
3	7:5	`ID_UTC_DST_START_WEEKDAY`
3	4:0	`ID_UTC_DST_START_HOUR`
4	7	Res.
4	6:0	`ID_UTC_DST_OFFSET`
5	7	Res.
5	6:4	`ID_UTC_DST_STOP_WEEK_OF_MONTH`
5	3:0	`ID_UTC_DST_STOP_MONTH`
6	7:5	`ID_UTC_DST_STOP_WEEKDAY`
6	4:0	`ID_UTC_DST_STOP_HOUR`
7	7:4	`ID_UTC_DST_START_MINUTE`
7	3:0	`ID_UTC_DST_STOP_MINUTE`

{% endtab %} {% tab title="SET DEVICE TIME CONFIG" %} Setzen der Gerätezeitkonfiguration. **Beispiel** ``` 0BB4520238590300h = Auto-Sync aktiv, UTC+1 im Winter, UTC+2 im Sommer, Umstellung am letzten Sonntag im März bzw. Oktober ```

Byte	Bit(s)	Value
0	7	Res.
0	6:0	`0x0B` (Command ID)
1	7	`ID_AUTO_TIME_SYNC_EN`
1	6:0	`ID_UTC_OFFSET`
2	7	Res.
2	6:4	`ID_UTC_DST_START_WEEK_OF_MONTH`
2	3:0	`ID_UTC_DST_START_MONTH`
3	7:5	`ID_UTC_DST_START_WEEKDAY`
3	4:0	`ID_UTC_DST_START_HOUR`
4	7	Res.
4	6:0	`ID_UTC_DST_OFFSET`
5	7	Res.
5	6:4	`ID_UTC_DST_STOP_WEEK_OF_MONTH`,
5	3:0	`ID_UTC_DST_STOP_MONTH`
6	7:5	`ID_UTC_DST_STOP_WEEKDAY`
6	4:0	`ID_UTC_DST_STOP_HOUR`
7	7:4	`ID_UTC_DST_START_MINUTE`
7	3:0	`ID_UTC_DST_STOP_MINUTE`

{% endtab %} {% endtabs %}

ID_AUTO_TIME_SYNC_EN

0 → deaktiviert

1 → aktiviert

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_OFFSET

y = x \* 0,25 - 12

\[y] = h

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_START_WEEK_OF_MONTH

1 → 1. Wochentag

2 → 2. Wochentag

3 → 3. Wochentag

4 → 4. Wochentag

5 → letzter Wochentag

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_START_MONTH

y = x + 1

\[y] = Monat

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_START_WEEKDAY

0 → Sonntag

1 → Montag

2 → Dienstag

3 → Mittwoch

4 → Donnerstag

5 → Freitag

6 → Samstag

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_START_HOUR

y = x

\[y] = h

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_OFFSET

y = x \* 0,25 - 12

\[y] = h

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_STOP_WEEK_OF_MONTH

1 → 1. Wochentag

2 → 2. Wochentag

3 → 3. Wochentag

4 → 4. Wochentag

5 → letzter Wochentag

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_STOP_MONTH

y = x + 1

\[y] = Monat

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_STOP_WEEKDAY

0 → Sonntag

1 → Montag

2 → Dienstag

3 → Mittwoch

4 → Donnerstag

5 → Freitag

6 → Samstag

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_STOP_HOUR

y = x

\[y] = h

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_START_MINUTE

y = x \* 5

\[y] = min

| | Persistent | Ja | | Zugriff | r/w |

ID_UTC_DST_STOP_MINUTE

y = x \* 5

\[y] = min

| | Persistent | Ja | | Zugriff | r/w |

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dnt.de/dnt-lw-etrv/kommunikationsprotokoll/3.-geratezeit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.