Juno IX BSX Payload description
Are you looking for the Juno IX BSX payload description ?
1. General description
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 measurement value. This measurement value can simply be assumed to be the current measurement value.
The header is followed by an additional payload section that contains further information, such as special parameters for the measurement principle or settings for position and opening detection. Not every sensor has an additional payload section.
2. Terminology
| Term | Description |
|---|---|
| Byte No. | Byte number starting at 1 |
| Alias | Comprehensible name of the variable |
| Description | Description of the variable |
| Designation | Designation in the data converter |
| Unit | Unit of the variable |
| Data hub .json key | Key in the .json file 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 |
|
Base 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, etc.) |
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.
4. Uplink example (not applicable for JUNO)
Figure 1: Example of an uplink payload (Helios pressure sensor)
5. Port assignment for WIFI SSID SCAN payload, GNSS SCAN payload and regular payload
| Feature | LoRaWAN port | Description |
|---|---|---|
| GNSS Scan Payload | 192 | Raw data (satellite ID, time, etc.) is sent to the geolocation backend. |
| WIFI SSID Scan Payload | 197 | Scanned MAC addresses and RSSI data are transmitted for location tracking. |
| Regular telemetry data | 1 | Regular payload data of the sensor, such as temperature, relative humidity, angle, battery voltage, etc. |
Example of the WIFI SSID scan payload:
Figure 2: Example of a WIFI SSID scan payload
6. Decoding of WIFI SSID SCAN and GNSS scan data
The following providers can be recommended for decoding WIFI SSID SCAN and GNSS SCAN data:
- Semtech LoRa Cloud (discontinued at the end of July 2025)
- AWS
- Tencent
- Traxmate
- Sentinum
Local databases can be used for on‑prem applications.
Juno BSX operating hours counter LoRaWAN payload description
| Item code | Features |
|---|---|
| S-JUNO-iX-LOEU-BSX-BM | INDUSTRIAL JUNO IP69k Operating Hours Counter with Magnetic Field Sensor LoRaWAN® |
| S-JUNO-iX-MIOTY-BSX-BM | INDUSTRIAL JUNO IP69k Operating hours counter with magnetic field sensor mioty® |
| S-JUNO-iX-NBM1-BSX-BM | INDUSTRIAL JUNO IP69k Operating hours counter with magnetic field sensor Cellular |
| S-JUNO-iX-LOEU-BSX-BM-TH | INDUSTRIAL JUNO IP67 operating hours counter and TH sensor, temperature and relative humidity with magnetic field sensor LoRaWAN® – only available on request and MOQ |
| S-JUNO-iX-MIOTY-BSX-BM-TH | INDUSTRIAL JUNO IP67 operating hours counter and TH sensor, temperature and relative humidity with magnetic field sensor mioty® – only available on request and MOQ |
| S-JUNO-iX-NBM1-BSX-BM-TH | INDUSTRIAL JUNO IP67 operating hours counter and TH sensor, temperature and relative humidity with magnetic field sensor Cellular – only available on request and MOQ |
| S-JUNO-iX-LOEU-BSX | INDUSTRIAL JUNO IP69k operating hours counter and TH sensor, temperature and relative humidity with magnetic field sensor LoRaWAN® |
| S-JUNO-iX-MIOTY-BSX | INDUSTRIAL JUNO IP69k operating hours counter with vibration and magnetic field sensor mioty® |
| S-JUNO-iX-NBM1-BSX | INDUSTRIAL JUNO IP69k Operating hours counter with vibration and magnetic field sensor Cellular |
| S-JUNO-iX-LOEU-BSX-TH | INDUSTRIAL JUNO IP67 operating hours counter with vibration and magnetic field sensor LoRaWAN® – only available on request and MOQ |
| S-JUNO-iX-MIOTY-BSX-TH | INDUSTRIAL JUNO IP67 operating hours counter with vibration and magnetic field sensor mioty® – only available on request and MOQ |
| S-JUNO-iX-NBM1-BSX-TH | INDUSTRIAL JUNO IP67 operating hours counter with vibration and magnetic field sensor Cellular – only available on request and MOQ |
7. LoRaWAN payload field description
| Byte number | Alias name | Description | Unit | Designation in payload decoder | Module key | Datahub .json key |
|---|---|---|---|---|---|---|
| 1 – 2 | Module key |
Byte 1: 4 bits MSB: Module code. For Mioty, exclusively "Sentiface" telemetry module, i.e. always 0x1. 4 bits LSB: Major version. Firmware with the same major version but higher minor version remains compatible with older decoders. However, the number of bytes may change. Byte 2: 4 bits MSB: Minor version. New software versions may incrementally add new telemetry to the data packet. 4 bits LSB: Sub / product version. For Helios, these bits encode the specific configuration of the connected sensors. |
module_key | XXX1 | module_key | |
| 3 | Uplink counter | Protocol‑independent uplink counter that increments up to 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:
battery_voltage =
(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] - 128For this sensor, the value represents the controller temperature and is an approximate value with an accuracy of ±2 °C. |
°C | internal_temperature | XXX1 | internal_temperature |
| 7 – 10 | Operating time | Operating time in seconds until reset via command or battery replacement. | operating_seconds | XXX1 | operating_seconds | |
| 11 – 14 | Cycles | Number of cycles indicating how often the machine has been started or activated. | cycles | XXX1 | cycles | |
| 15 – 16 | ON/OFF rate | Ratio between ON time and OFF time since the last uplink, e.g. 10 (/100) → 0.1 %. | utilization_rate | XXX1 | utilization_rate | |
| 17 | Activity | Indicates whether an activity has been detected. | is_active | XXX1 | is_active | |
| 18 – 19 | Temperature |
Exact temperature value calculated as:
decoded.temperature =
((bytes[idx++] << 8) | bytes[idx++]) / 10 – 100
ONLY FOR TH VERSION |
°C | temperature | XXX1 | temperature |
| 20 | Relative humidity |
Relative humidity. ONLY FOR TH VERSION |
%RH | humidity | XXX1 | humidity |
© Sentinum GmbH – All rights reserved.
All contents of this document, including text, tables, and images, are protected by copyright and are the property of Sentinum GmbH.
All images are subject to the copyright of Sentinum GmbH unless otherwise stated.
Reproduction, distribution, or use — even in excerpts — is not permitted without explicit written permission.
Specifications are subject to change without notice. All information is provided without warranty.