Skip to content
English
  • There are no suggestions because the search field is empty.

Juno Tracker Lorawan Payload Description

Are you looking for Juno Tracker Lorawan Payload description ?

You can view the PDF above or download it here .

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 has 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 payload decoding example
Figure 1: Uplink payload decoding.

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

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 + RSSI data are transmitted for localization.
Regular telemetry data 1 Regular payload data from the sensor, such as temperature, relative humidity, angle, battery voltage, etc.

Example of the WIFI SSID scan payload:

WIFI SSID scan payload example
Figure 2: WIFI SSID scan payload example.

6. Decoding of WIFI SSID Scan and GNSS Scan Data

The following providers can be recommended for decoding the 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.

7. Juno LoRaWAN TH Tracker Payload Description

Item number Radio standard Functions
S-JUNO(-iX)-LOEU-TH-TRACK LoRaWAN® Temperature, relative humidity, tilt detection, activity detection, opening and motion detection
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. FW of the same major version but larger minor version remain compatible with older decoders. However, the number of bytes may change!

Byte 2:
4-bit MSB: Minor version. New SW 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 connected sensors.
module_key XXX1 module_key
3 Uplink counter Uplink counter: Protocol-independent uplink counter that reaches a maximum of 255. After that, the counter starts again at 0. uplink_counter XXX1 uplink_counter
4 - 5 Battery voltage Current voltage of the battery in millivolts. Voltage in volts: battery_voltage: (dataBytes[3] << 8 | dataBytes[4])/1000.0 mV battery_voltage XXX1 battery_voltage
6 Internal temperature Temperature of the sensor: Internal_temperature = | bytes[6] - 128; This value is the temperature value of the controller for this sensor and an inaccurate temperature value +/-2°C. °C internal_temperature XXX1 internal_temperature
7 Alarms The alarms are coded as follows. Caution: Several alarms can be active at the same time!
DEZ 1, BIN 0000 0001: Temperature High limit value exceeded
DEZ 2, BIN 0000 0010: Temperature low below limit value
DEZ 4, BIN 0000 0100: Delta alarm temperature
DEZ 8, BIN 0000 1000: Relative humidity High limit value exceeded
DEZ 16, BIN 0001 0000: Relative humidity Low below limit value
DEZ 32, BIN 0010 0000: Delta alarm rel. humidity
humidity XXX1 humidity
8 - 9 Temperature Exact temperature of the SHT40, as described in the data sheet. decoded.temperature = ((bytes[idx++] << 8) | bytes[idx++]) / 10 - 100; °C temperature XXX1 temperature
10 Relative humidity Relative humidity of the SHT40, as described in the data sheet. %RH humidity XXX1 humidity
11 Acceleration sensor status 0: Acceleration sensor without error, other: Acceleration sensor error acc_status XXX1 acc_status
12 - 15 Timestamp start of a movement Returns the timestamp in seconds at the start of the movement. s move_start XXX1 move_start
16 - 19 Timestamp end of a movement Returns the timestamp in seconds at the end of the movement. s move_end XXX1 move_end
20 Object is currently moving Returns whether the object is currently in motion: 0: No activity, 1: Object in motion. moving XXX1 moving
21 - 22 Number of activities counted Counts the number of activities. move_cnt XXX1 move_cnt
23 Angle Returns the angle in °, resolution 1°. ° angle XXX1 angle

8. Juno LoRaWAN TH Tracker Payload Description (Without TH)

Item number Radio standard Functions
S-JUNO(-iX)-LOEU-TRACK LoRaWAN® Tilt detection, activity detection, opening and motion detection
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. FW of the same major version but larger minor version remain compatible with older decoders. However, the number of bytes may change!

Byte 2:
4-bit MSB: Minor version. New SW 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 connected sensors.
module_key XXX1 module_key
3 Uplink counter Uplink counter: Protocol-independent uplink counter that reaches a maximum of 255. After that, the counter starts again at 0. uplink_counter XXX1 uplink_counter
4 - 5 Battery voltage Current voltage of the battery in millivolts. Voltage in volts: battery_voltage: (dataBytes[3] << 8 | dataBytes[4])/1000.0 mV battery_voltage XXX1 battery_voltage
6 Internal temperature Temperature of the sensor: Internal_temperature = | bytes[6] - 128; For this sensor, this value is the temperature value of the controller and an inaccurate temperature value +/-2°C. °C internal_temperature XXX1 internal_temperature
7 Acceleration sensor status 0: Acceleration sensor without error, other: Acceleration sensor error acc_status XXX1 acc_status
8 - 11 Timestamp start of a movement Returns the timestamp in seconds at the start of the movement. s move_start XXX1 move_start
12 - 15 Timestamp end of a movement Returns the timestamp in seconds at the end of the movement. s move_end XXX1 move_end
16 Object is currently moving Returns whether the object is currently in motion: 0: No activity, 1: Object in motion. moving XXX1 moving
17 - 18 Number of activities counted Counts the number of activities. move_cnt XXX1 move_cnt
19 Angle Returns the angle in °, resolution 1°. ° angle XXX1 angle


Supported radio technologies
trash bin Logo