Remote temperature sensor


Declaration of conformity

Download the declaration of conformity


The Remote temperature  sensor is LoRaWAN class A sensor, it manages two different power supplies, one is external and may range from 9V to 24V, the other one is internal on the battery. It also integrates an internal antenna.

The sensor includes a 5 meters temperature probe.


The Remote temperature sensor allows the measure of temperature in a large set. It can mesure from -40°C to +90°C at a precision of 1°C.

The table below represents the precision of each temperature range:

Temperature rangePrecision
[-40°C ; -34°C]+/-1.5°C
[-33°C ; +9°C]+/-1.0°C
[+10°C ; +37°C] +/-0.5°C
[+38°C ; +64°C]+/-1.0°C
[+65°C ; +82°C]+/-1.5°C
[+83°C ; +90°C]+/-2.0°C

The measure step is defined in the minimum field of a frame.

The housing is compatible with the following DIN rail adapter:


For more information about the casing, visit:

Family code:

The family code of Remote temperature devices is: 50-70-043-xxx

Propagation radio

In order for the sensor to function correctly, it is better to limit the number of obstacles in order to avoid excessive attenuation of the radio wave, it is also important to put the sensor as high as possible. The cable gland should be positionned downward.



The information in the table below represents how long the battery can last. It is  based on the default configuration at ambient temperature (+25°C) within the optimal use of the sensor throught LoRaWAN network (one uplink frame), and when  the spreading factor used is SF12.

The capacity of the disposable battery is 3.6Ah, 85% of it is used.

Transmission periodicityBattery life
1 frame/ 2 hours12 years

Human Machine Interface

The Remote temperature sensor has a buzzer that allows it to “communicate” with the user.

After installing the device, switch ON the power to start-up the device.The buzzer rings until an association.

When the sensor is trying to associate to a network, it emits the following sound:

At the moment of association, the buzzer make the following sound:

A reed switch (or magnetic switch) is available. It is possible to use a magnet to activate it and make specific actions on the sensor (Switch off, switch on, Re-associtation…).

  • Configuration: « void » frames are sent every minute for 10 minutes.

Standard reports are not functioning during this mode.

Configuration mode
Way to trigger itOne passage of the magnet near the reed switch or specific ZCL command
Way to stop it Another passage of the magnet or specific ZCL command
Effects on the sensor
Time durationThe configuration mode lasts 10 minutes
  • It is possible to ask a ReAssociation procedure if no down frame is received by the sensor during a given periodicity (4 days by default) or if a given number (100 by default) or failure (no acquittement is received) are reached by sending an applicative frame to the sensor or by the IHM of the sensor.

The sensor keeps the AppEUi and DevAddr configured, Confirmed/Unconfirmed  configuration and all applicative configurations. On the other hand, LoRaWAN configuration (channel, datarate …) are lost

ReAssociation Mode
Way to trigger itThree passages of the magnet near the reed switch or ZCL command from LoRaWAN cluster.
Effects on the sensor
  • A factory reset is available on nke Watteco’s sensors. It deletes all the applicative settings saved in the flash memory (i.e.: the configured batches and reports will be deleted).

The sensor keeps the AppEUi and DevAddr configured. On the other hand, LoRaWAN configurations (channel, datarate …) and applicative configurations are lost.

Factory reset
Way to trigger itTwo quick passages and a very long passage (until the sensor rings for the reset) of the magnet near the reed switch
Effects on the sensor

Applicative layer

Codec are available to decode frame: Downloads

The Remote temperature sensor integrates the following clusters:

ClusterCluster nameManaged attributes
0x0402Temperature MeasurementAll

Default configuration

A default configuration is set:

  • The device reports each 2 hours the temperature (EndPoint 0 / Cluster Temperature Measurement /Attribut Measuredvalue).

Every change on the default configuration must respect the legal duty cycle. (For example the most restrictive in EU is 0.1%, so in SF12 it is around 1 frame each hour)

Measurement periodicity

The measurement periodicity depends on the minimum, the maximum recording interval and the delta.

If the value of the minimum and the delta is 0, then the maximum value is the periodicity. However, if the value of delta is different than 0, then the periodicity is 1 second.

If the value of the minimum is different than 0, then this value is the same as the periodicity.

Frame examples

All frames have to be sent on the port 125

Standard report



Report of the temperature of the remote sensor

→ Applicative payload is: 11 0a 04 02 00 00 29 00 64

 00 64: Measured value 1°C (Temperature (°C) = Measured value/100)




Configure a standard report on the temperature

Report immediately the temperature all the 11°C of variation. This measure has to be reported at least each hour.

→The temperature is on the End Point 0, Cluster “Temperature Measurement” is 0x0402, Attribut “MeasuredValue” is 0x0000.

The maximum field has to be 0x0e10 to have a report all one hour and the minimum field has to be 0x0000 to have a report immediately after the right variation.

The delta has to be configured to 1100=0x044c for a report all the 11 °C of variation.

Applicative payload is: 11 06 04 02 00 00 00 29 00 1e 0e 10 04 4c

00 1e:minimum reporting interval (30 seconds)

0e 10: maximum reporting interval (1 hour)

04 4c: reportable change (11°C)

→Response: 11 07 04 02 00 00 00 00

To disable the previous configuration, change the value of the minimum and maximum sending interval and the delta to 0: 11 06 04 02 00 00 00 29 00 00 00 00 00 00


Batch report

• Configure a batch report on Temperature and Battery voltage:

Timestamp and record the temperature with a resolution of 0.1°C, a value has to be saved at least every 6 hours or on a variation of 1°C.

Timestamp and record all voltage power sources with a resolution of 0.1V, a value has to be saved at least all the 24 hours. All datas have to be concatenated and sent at maximum all the 24 hours.

→The solution to concatenate several different physical values in the same frame is to use the batch reporting. For the batch it is necessary to know the number of physical measure that will be sent to choose a label for each of them and the size of these labels. There are only 1 power source in the sensor (Disposable battery). So, with the temperature and this power source, it is necessary to manage 2 different labels.

Number of labelTag labelTag size
1 or 20/11
3 or 400/01/11/102
5 or 6 or 7 or 8000/001/010/011/100/101/110/1113

The Tag Size to use for 2 labels is 1. Label 0 can be used for Temperature and Label 1 for level of Disposable Battery. To configure the batch, it is necessary to send a command of “Configure reporting” at each cluster.

For temperature the delta has to be set to 100=0x0064 (1°C), minimum to 30=0x001e (30 seconds), the maximum to 6*60=360=0x8168 (6 hours), the resolution to 10=0x000A (0.1°C) and the tag to 0b00000001=0x01 (size 1 and label 0). The cluster to report is 0x0402 and the attribut 0x0000 (MeasuredValue).

For Disposable Battery power source the delta has to be set to 200=0x00c8 (0.2V), minimum to 10=0x800a (10 minutes), the maximum to 24*60=1440=0x85A0 (24 hours), the resolution to 200=0x0064 (0.1V), the tag to 0b00001001=0x0a (size 1 and label 1), the field to 4=0x04. The cluster to report is 0x0050 and the attribut 0x0006 (Node power descriptor).

Power sources (Bits field)Description
0x01Constant (main) or External power
0x02Rechargeable battery
0x04Diposable battery
0x08Solar harvesting
0x10TIC harvesting
0x00Undefined: should not occur

Applicative payload of the temperature

11 06 04 02 15 00 00 00 00 1e 81 68 00 64 00 0A 01

15:  0b00010101 => 0001010: size of configuration string after attribute ID (10 bytes)

00 1e: minimum reporting interval (30 seconds)

81 68: maximum reporting interval (6 hours)

00 64: required delta value (size: 2 bytes for attribute MeasuredValue => attribute type = 29; 1°C)

00 0A: required resolution (0.1°C)

01: tag value (ob00000001 => 00000: tag label, 001: tag size)

→Response: 11 07 04 02 00 01 00 00


Applicative payload of the battery voltage

11 06 00 50 29 00 06 04 80 0a 85 a0 00 c8 00 64 09

29: 0b00101001 => 0010100: size of configuration string after attribute ID (20 bytes)

04: index of required field (Rechargeable battery)

80 0a: minimum reporting interval (10 minutes)

85 a0: maximum reporting interval (24 hours)

00 c8: required delta value (size: 2 bytes for attribute NodePowerDescriptor => attribute type = 41; 0.2V)

00 64: required resolution (0.1V)

09tag value (ob00001001 => 00001: tag label, 001: tag size)

→Response: 11 07 00 50 00 01 00 06


To decode the batch reception, use the br_uncompress. Type for Temperature is I16 (7) and for others the type is U16 (6), so it is necessary to use this command:

echo « 200200606025410d271ce80441ff9d230083ff6787f5b30f68b72cef9228 » | br_uncompress -a 1 0,10,7  1,100,6



cnt: 2   # Counter of the batch (from 0 to 7)

18450  # Timestamp in second of sending of the frame

# Format of data is: TimeStamp of Measure | Label | Value

811 0 2410    # TimeStamp: 811 s     Label 0: Temperature                   Value: 24,1°C

841 0 2550   # TimeStamp: 841 s     Label 0: Temperature                    Value: 25.5°C

911 0 -1250   # TimeStamp: 911 s     Label 0: Temperature                    Value:-12.5°C

941 0 -1370   # TimeStamp: 941 s     Label 0: Temperature                    Value:-13.7°C

12011 0 -1230  # TimeStamp: 12011 s     Label 0: Temperature                    Value:-12.3°C

844 1 3700  # TimeStamp: 840 s      Label 1: Disposable battery            Value: 3.7V

1444 1 3500  # TimeStamp: 840 s      Label 1: Disposable battery            Value: 3.5V


Print Friendly