Bugfix schedule: Together with removing codec12 command on December 1st, there will be change in parsing for BLE temperature sensor values for categories of: Easy, Advanced, Special trackers from here
AVL IDs 25 to 28 responsible for indexed parameters ble.sensor.temperature.1 to ble.sensor.temperature.4 parsing multiplier will be changed from 0.1 to 0.01. The change is caused by update in Teltonika documentation . It might be so that older FW version of trackers or sensors will still report value multiplied by 0.1 . If this is the case for you, you may revert back old values by multiplying new values by 10 via this plugin:
{
"required": true,
"enabled": true,
"validate_message": "",
"item_type": 11,
"name": "pvm-plugin",
"configuration": {
"code": "optional .ble.sensor.temperature.1[number] ==> this * 10 ==> #ble.sensor.temperature.1\noptional .ble.sensor.temperature.2[number] ==> this * 10 ==> #ble.sensor.temperature.2\noptional .ble.sensor.temperature.3[number] ==> this * 10 ==> #ble.sensor.temperature.3\noptional .ble.sensor.temperature.4[number] ==> this * 10 ==> #ble.sensor.temperature.4"
},
"priority": 0,
"type_id": 1,
"timezone": "UTC"
}
Another note: there are several error codes specified for the sensor values:
4000 - abnormal sensor state
3000 - sensor not found
2000 - failed sensor data parsing
But according to Teltonika support, there is no way to tell temperature 20 from error code 2000 with multiplier 0.01. So flespi will not process error codes, this will be user's responsibility. Usually, sensor can be treated in error state when its value is not changed for long period of time in one of the error codes state.
