![Logo_quer_farbig.png]](https://docs.sentinum.de/hs-fs/hubfs/Logo_quer_farbig.png?height=40&name=Logo_quer_farbig.png){kind=logo}
1. Version History
| Version | Date | Revision |
|---|---|---|
| 1.0.0 | 18.02.2025 | Creation |
| 1.0.1 | 24.04.2026 | Formatting, version history |
2. Overview
This chapter describes the structure of the telemetry data. The number of bytes in the payload depends on the configuration of the sensor. The structure of the data depends on which sensors are present in your product.
In principle, each version has a header. This header contains information about the version and status of the sensor and also contains a master measured value. This measured value can simply be assumed to be the current measured value.
The header is followed by an additional payload part that contains further information, such as special parameters for the measuring principle or settings for position and opening detection. Not every sensor has an additional payload part.
| Terms | Description |
|---|---|
| Byte No. | Byte number starting at 1 |
| Alias | Comprehensible name of the variable |
| Description | Description of the variables |
| Designation | Designation in the Dataconverter |
| Unit | Unit of the variables |
| Datahub .json key | Key in the .json when using the data hub |
3. Structure of the module key
| Byte 1 | Byte 2 | ||
|---|---|---|---|
| Bit 7 - 4 | Bit 3 - 0 | Bit 7 - 4 | Bit 3 - 0 |
|
Basic ID module e.g. Sentiface, Senticom, Sentivisor |
Major version (SW/HW version) |
Minor version (SW/HW version) |
Product version (sensors, e.g. TH, THL, ACC, ...) |
The module key of the SENTIFACE module can be taken from the first 2 bytes of each uplink. The module key is required for the downlink.
Uplink example (not applicable for Juno)
The following payload example is given for the Helios pressure sensor:
11 11 FE 1A D5 95 06 03 00 23 BE
| Bytes | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| HEX | 11 | 11 | FE | 1A | D5 | 95 | 06 | 03 | 00 | 23 | BE |
| Description | Module key | Module key | Uplink Counter | Battery Voltage | Battery Voltage | Temperature | Alarm Flag | Alarm Flag | Measurement status | Pressure mbar | Pressure mbar |
4. Juno Payload Description
| Byte number | Alias name | Description | Unit | Designation in the payload decoder | Module key | Datahub .json key |
|---|---|---|---|---|---|---|
| 1 – 2 | Module key |
Byte 1: 4‑bit MSB: Module code. For Mioty exclusively "Sentiface" telemetry module, i.e. always 0x1.4‑bit LSB: Major version. Firmware with the same major version but larger minor version remains compatible with older decoders. However, the number of bytes may change. Byte 2: 4‑bit MSB: Minor version. New software versions may incrementally add new telemetry to the data packet. 4‑bit LSB: Sub / product version. With Helios, these bits encode the specific configuration of the connected sensors. |
module_key | XXX1 | module_key | |
| 3 | Uplink counter | Protocol‑independent uplink counter that reaches a maximum value of 255. After that, the counter starts again at 0. | uplink_counter | XXX1 | uplink_counter | |
| 4 – 5 | Battery voltage |
Current battery voltage in millivolts. Voltage in volts calculated as: (dataBytes[3] << 8 | dataBytes[4]) / 1000.0
|
mV | battery_voltage | XXX1 | battery_voltage |
| 6 | Internal temperature |
Temperature of the sensor controller.internal_temperature = bytes[6] - 128This value represents the controller temperature and is an approximate value with an accuracy of ±2 °C. |
°C | internal_temperature | XXX1 | internal_temperature |
| 7 | Acceleration sensor status |
0: Acceleration sensor without errorOther: Acceleration sensor error |
acc_status | XXX1 | acc_status | |
| 8 | Orientation of the sensor |
Displays the orientation of the sensor:0: Vertical (lies on its side)1: Face up2: Face down3: Error
|
orientation | XXX1 | orientation | |
| 9 | Angle | Returns the angle in degrees (°), resolution 1°. | ° | angle | XXX1 | angle |
| 10 | Open | Indicates whether the flap is open or closed. | is_open | XXX1 | is_open | |
| 11 | Opening counter (relative) | Indicates how many openings have been performed since the last uplink. | open_cnt_rel | XXX1 | open_cnt_rel | |
| 12 | Lifetime opening counter | Indicates how many openings were carried out in the entire company. | open_cnt_total | XXX1 | open_cnt_total |
