Juno
      Back to home
      1. Help-Desk
      2. Sensors & Product Lines
      3. Juno

      Juno ID TILT payload description

      Are you lppking for the Juno ID TILT payload description?

      📄 You can view the PDF above or download it here.

      This section 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.

      Payload Field Description

      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

      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 

      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 Tempera-ture Alarm Flag Alarm Flag Measurement status Pressure mbar Pressure mbar

      SENTIFACE: TELEMETRY PAYLOAD STRUCTURE

      Byte number Alias name Unit Designation in decoder Module key Datahub .json key
      1 - 2 Module key module_key XXX1 module_key
      Description:
      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.
      3 Uplink counter uplink_counter XXX1 uplink_counter
      Description:
      Uplink counter: Protocol-independent uplink counter that reaches a maximum of 255. After that, the counter starts again at 0.
      4 - 5 Battery voltage mV battery_voltage XXX1 battery_voltage
      Description:
      Current voltage of the battery in millivolts //Voltage in volts battery_voltage: (dataBytes[3] << 8 | dataBytes[4])/1000.0.
      6 Internal temperature °C internal_temperature XXX1 internal_temperature
      Description:
      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
      7 Acceleration sensor status acc_status XXX1 acc_status
      Description:
      • 0: Acceleration sensor without error
      • Other: Acceleration sensor error
      8 Orientation of the sensor orientation XXX1 orientation
      Description:
      Displays the orientation of the sensor
      • 0: Vertical: Lies on its side
      • 1: Face Up
      • 2: Face Down
      • 3: Error
      9 Angle ° angle XXX1 angle
      Description:
      Returns the angle in °, resolution 1°
      10 Open is_open XXX1 is_open
      Description:
      Indicates whether the flap is open or closed
      11 Opening counter relative open_cnt_rel XXX1 open_cnt_rel
      Description:
      Indicates how many openings have been performed since the last uplink
      12 Lifetime opening counter open_cnt_total XXX1 open_cnt_total
      Description:
      Indicates how many openings were carried out in the entire company

       

      Specifications subject to change without notice. All information provided without guarantee.