Lightbug Documentation

Appearance

41: Temperature ​

Temperature information

FieldNameDescriptionType
5MethodRequest 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 ​

FieldNameDescriptionTypeUnit
1TemperatureTemperature in Celsiusfloat32C

Examples ​

GET request for device temperature
Protocol
03
3
Length
2000
20 bytes
Type
4100
41 (Temperature)
Header Count
0200
2
Header Types
0501
5, 1
Method
0102
2 (GET)
Message ID
0447152218214
3604650031
Payload Count
0000
0
Checksum
16867
17320
📡 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 temperature response
Protocol
3
3
Length
260
26 bytes
Type
410
41 (Temperature)
Header Count
20
2
Header Types
34
3, 4
Response to
447152218214
3604650031
Status
10
0 (OK)
Payload Count
10
1
Payload Types
1
1
Temperature
410210221065
26.299999237060547 Unit: C
Checksum
13340
10373
📡 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.