36: Device Time

Device time information, if known. Currently the best available time will be provided. Moving forward we will be able to provide different times (GPS, GSM etc.)

Header

Field	Name	Description	Type
5	Method	Request a service to be perform an action Possible values: 1: SET— Set one or more values that are provided in the message payload. 2: GET— Get values for the associated message type. 3: SUBSCRIBE— Subscribe to values for the associated message type. Can be used in conjunction with other header fields to define the subscription parameters, such as Interval, Duration, Timeout, Storage Level and Message Level. If no interval is provided, messages will be sent as and when new data is available. Some data, such as GPS position, may require a set interval to be provided. 5: UNSUBSCRIBE— Unsubscribe from a previous subscription.	uint8

This is an extract of header fields that are relevant to this message type, you can find them all documented in the Headers section.

Payload

Field	Name	Description	Type	Unit
1	Unix Time	Unix time	uint32	s since epoch
2	Year	Year	uint16
3	Month	Month	uint8
4	Date	Date in month	uint8
5	Weekday	Weekday (0 = sunday, 1 = monday etc)	uint8
6	Hour	Hour	uint8
7	Minute	Minute	uint8
8	Second	Second	uint8

Examples

GET request for device time

Protocol

3

3

Length

200

20 bytes

Type

360

36 (Device Time)

Header Count

20

2

Header Types

51

5, 1

Method

12

2 (GET)

Message ID

495144132158

2659487839

Payload Count

00

0

Checksum

127117

30079

📡 Real example from RH2 ESP32 Toit on 2025-10-10This example is captured from an RH2 device as part of normal communications over I2C with the ESP32 co-processor, where Toit on the ESP32 make the request.

Device Time response

Protocol

03

3

Length

4800

48 bytes

Type

3600

36 (Device Time)

Header Count

0200

2

Header Types

0304

3, 4

Response to

0495144132158

2659487839

Status

0100

0 (OK)

Payload Count

0800

8

Payload Types

0102030405060708

1, 2, 3, 4, 5, 6, 7, 8

Unix Time

040182233104

2025-10-10 18:35:45 UTC

Year

0223307

2025

Month

0110

10

Date

0110

10

Weekday

0100

0

Hour

0118

18

Minute

0135

35

Second

0145

45

Checksum

131230

59011

📡 Real example from RH2 P1 v2287 on 2025-10-10This example is captured from an RH2 device as part of normal communications over I2C with the ESP32 co-processor, where P1 responses to a request from Toit on the ESP32.

Code

For convenience, the following constants can be used to reference this message type.