Help
Pairing a temperature sensor
How to add an ELA Blue PUCK T to a tracker, and what odd readings like +327 °C mean.
What you need
The sensor's MAC address. It is on the label, and you can also read it with the ELA Device Manager app over NFC, or with the btgetlist command sent to the tracker, which returns the Bluetooth devices it can see with their MAC and signal strength.
Configuring the tracker
In Teltonika Configurator, under Bluetooth 4.0, enable BLE and Non Stop Scan and set the scan duration to 10 seconds. With power from the vehicle a continuous scan costs nothing, and the sensor broadcasts infrequently.
Then under BLE Sensors → Connection #1: Advanced mode, the sensor's MAC, then Presets → ELA T (Temperature) → Load. The preset sets the offsets and the multiplier and routes the reading to AVL 25, with the battery level on AVL 29. Save and wait two or three minutes.
Checking it in the panel
Vehicles → Devices → Device diagnostics. The IO table should show ble_temp_1_c with a realistic temperature and ble_battery_1 with a battery percentage. Only then assign the sensor to a vehicle in its card and set the thresholds.
Where to mount the sensor
- at the warmest point of the compartment, usually near the doors – not at the evaporator outlet
- not directly on the wall next to the fridge unit, where the reading will be skewed
- not in the cold air stream, or the alert will come too late
- for a body split into zones: one sensor per zone, up to four per vehicle
A reading of +327 °C and other special values
When the tracker cannot see the sensor it does not send an empty field but a special value. On firmware from 03.28.00 that is 32767 for a missing sensor, 32766 for a read error and 32765 for an abnormal state. On older versions, 3000, 2000 and 4000 respectively.
Trackomo recognises these numbers and stores them as a sensor state, never as a temperature, so they never reach a chart or a HACCP report. The vehicle card shows the state instead of a reading. On old firmware 3000 would convert to +30.00 °C and look like an ordinary measurement, which is the main reason we ask you to update.
The sensor has gone quiet
- check in the panel whether ble_battery_1 has dropped below 15 %
- send btgetlist and see whether the sensor's MAC is listed, and at what RSSI
- if it is not listed, move it closer to the cab and check again: cold room walls absorb the signal heavily
- the no-reading rule reacts after 30 minutes of silence by default
Try it on your own vehicles
You set the account up yourself, without talking to us. The first 30 days cost nothing.