Skip to content

Exceptions to Stateless API 6 features

With most uplinks, you can tell the state device is in without any previous knowledge of the how the device is set up. E.g. you can tell from the uplink payload that the device is in Reed switch on/off mode, therefore it will send you a Reed switch on message when there's a magnet near the sensor and a Reed switch off message when it's taken away.

However, there a few exceptions to this. Let's have a look at them.


  1. Hot bit turned on. This feature shifts the reported temperature values by +35°C without any hint in the payload. With the hot bit turned on and the measured temperature being 0°C, the device will report 35°C.

  2. Monitor me measurement window changed from default. The time interval between each measurement will be different but there's no way to know this from the payload.

  3. Sensor detection delay different from 0 (default). Some sensors allow you to setup a detection delay, where the change in state (e.g. Reed switch on) is reported after the duration of this interval.

  4. Alert repetition interval & number of repetitions - if this feature is turned on, uplink messages assigned as mode alerts will be repeated x times with an interval of y between each repetition. You cannot tell if the messages you receive are new e.g. sensor state change detections or repeated previous detections from the payload.

  5. Alert assignment override. You can assign any uplink to alert 1, 2 and 3 functionality regardless of mode. Once this is done, independent alerts can have the functionality of assigned alert without being a predefined alert of the mode your device is in.

  6. Reed Counter messages trigger. The device will send you a Reed Counter event and the count, you cannot tell if the event was triggered by time or if a threshold count was reached.

  7. Hot/cold sensor setup in Legionella mode. If this setup is changed from default, you cannot decode which sensor is which from the payload.

  8. GPIO settings. You can assign the functionality of e.g. the button to a different sensor - the reed switch for example, as is done with the SimpleIndustry and SimpleMeter devices. Once this is done, you have to know GPIO settings to decode uplink payload messages properly.


Please do not change GPIO registers 0xC0-0xC4 without consulting with us first!

Features that require additional messages/information to fully decode

  1. Heartbeat 1, 2 and 3 interval period. The heartbeat uplink payload doesn't carry the interval setup information in it, in order to know how often you will receive your heartbeat, you have to wait for more heartbeats to come and determine the period from the uplink message timestamp.

  2. Most time-based events such as the Tracing tag message sent while the device is moving in Trace me mode. Again, you cannot know the interval from one uplink message, you have to wait for more messages to determine how often these are sent.

  3. Periodic temperature/gas/analog events. These messages are controlled by the time interval in which data is collected and aggregation of how many new data bytes are sent in one message. From the payload, you can only tell the time interval period (3rd byte), you have to determine the aggregation from how often you receive the messages.


You can always use the register readout feature to find out what the values of certain registers are. Send FEAABBCCDDEE0000 to the device where AA, BB, CC, DD and EE are the downlink register pointers. The device will return the values of these registers in one 0xFE uplink message. If you want to readout less than 5 registers, just replace the pointers with zeros, e.g. FE3C000000000000 reads out only the value of register 0x3C.