Calculated attribute alarms are not working for me

Joystick10 months ago

@Andres Petrillo
Thanks, this sort of cleared it up for me as well. Just need to confirm below.
I have a computed attribute linked to my main group and have teltonika and meitrack devices in the same group.
Teltonika devices include ignition flag in messages but for meitrack devices I use computed attribute to flag it for various reasons.
Using example 1 makes ignition flag for teltonika device disappear but example 2 work. Have I done it correctly?

Example 1
Attribute: ignition
Expression: protocol=="meitrack"?power?power>="10":null:null

Example 2
Attribute: ignition
protocol=="meitrack"?power?power>="10":null:(ignition?ignition:null)

Thanks for the help

FBoscarato6 months ago

Hello, in this moment i'm still using Traccar 6.2 because i can't understand how change computed attributes in Traccar 6.4 and newer for Teltonika device.
I'm using Teltonika FMC920 and the following is one of my computed attibute

Movement - FMC920
alarm

event ? (motion == 1 && ignition == 0 ? "movement" : null) : null

How to modify it for use with Traccar 6.6?

Screenshot 2025-03-29 alle 13.55.35.png

Thank you

Anton Tananaev6 months ago
  1. Why are you comparing booleans to numbers?
  2. Have you checked whether you have all the attributes available?
FBoscarato6 months ago

Hello Anton,
thank you very much for you fast reply.
I wrote it wrong in the previous post, the calculated attribute works in traccar 6.2 and earlier.

event ? (motion == 1 && ignition == 0 ? "movement" : null) : null

Screenshot_20250329-152438.png

So i understand point 1 and i will check it, but how can modify computed attribute that works in 6.2 for using in 6.6?

Thank you very much

Anton Tananaev6 months ago

You shouldn't modify anything. You should check first what attributes you're getting.

FBoscarato6 months ago

Ok well. But in your opinin, why does it work in 6.2 although attributes or comparisons aren't correct?

Anton Tananaev6 months ago

To provide an answer, I'm requesting this information from you.

FBoscarato6 months ago

may i kindly ask yoy what steps i need to take to analyze the problem?

FBoscaratoa day ago

Hello @Anton, i'm back.

I found Teltonika Data Parser for analizer HEX data, here an example:

000000000000005b8e0100000199511b13680007669a9e1b35934e000b00430e000000f0000d000600ef0000f00000150500c80000450100fc00000500b5000d00b60008004230b30043100800440000000200f1000056c20010011a6f0700000000010000154c

Teltonika parser.jpg

Can you help me with computed attributes? now i have upgrade to lastest Traccar version 6.9

Thank you very much

Anton Tananaev20 hours ago

And which ones are the attributes that you need?

FBoscarato13 hours ago

Hello Anton!
With Traccar < 6.3 i used this computed attributes for notify movement:

event ? (motion == 1 && ignition == 0 ? "movement" : null) : null

with Traccar > 6.2 it doesn' work and i can't undestand why.

The io240 correspond to Movement
the io239 correspond to Ignition

id.jpg

As you said, i shouldn't modify anything, but i need a suggestion because i can't understand what changed for teltonita from traccar 6.2 to 6.3 ad upper.

Thank you very much.

FBoscarato13 hours ago

In the GitHub changelog, I noticed that in Traccar 6.3, the Teltonika FMC920 model was introduced, the same device I use.
Yesterday i added model 'FMC920' in my device configuration.

FBoscaratoan hour ago

Ok, I found the problem. The attributes were correct, but the semantic expression was wrong.