We are testing the use of Teltonika Custom Scenarios (which work fine) and these scenarios generate parameter IDs.
I have a Computed Attribute set up as a String, but it does not appear to be decoding.
io1163 ? (io1163 ==1 ? "Scenario Triggered" : null) : null
My suspicion is because parameter 1163 is being sent twice within the same AVL record, once for when the DOUT is set high and then again when the DOUT is set low.
Here's the original undecoded record with Xs replacing my location. The hex code is 48b for this parameter and you can see it listed twice, with the newest occurrence first and the oldest occurrence last.
00000000000000798e01000001952c4fb8a801XXXXXXXXe9XXXXXXXX0028009e0e0000048b0014000a00ef0000f00000150500c80000450100010000020000030000ed03048b01000700b5000f00b600070042365800430ff8004400000009000000060000000200f10000c5450010000000510001004e000000000000000000000100004594
I suppose my real question here is if the double sending of the parameter is confusing Traccar?
Can you provide the breakdown of the HEX showing that it's sent twice?
To date I've been using ChatGPT to decode but the reliability is low enough that I've asked my Teltonika account manager for access to their parser tool. I'll use that in the next few days when I receive it to provide a full decode.
We are testing the use of Teltonika Custom Scenarios (which work fine) and these scenarios generate parameter IDs.
I have a Computed Attribute set up as a String, but it does not appear to be decoding.
My suspicion is because parameter 1163 is being sent twice within the same AVL record, once for when the DOUT is set high and then again when the DOUT is set low.
Here's the original undecoded record with Xs replacing my location. The hex code is 48b for this parameter and you can see it listed twice, with the newest occurrence first and the oldest occurrence last.
I suppose my real question here is if the double sending of the parameter is confusing Traccar?