Calculated attribute “vibration” triggers when ignition is turned off after recent updates
How did it work before? Does your device send motion attribute? Or do you use the server-calculated one?
It has always worked this way; the only difference now is that when the vehicle is turned off, it activates instantly.
These are attributes calculated by the server.
There is probably a more optimal way to handle this vibration alert—perhaps using an accelerometer or something more reliable than this calculated attribute.
Thank you.
Please answer all of the questions.
I believe I answered everything correctly, but perhaps I misunderstood it.
How did it work before? Just as I showed with the calculated attribute:
motion == true && ignition == false ? "vibration" : alarm
Does your device send the motion attribute? It sends vibration, yes.
Or do you use the server-calculated one? It is a calculated attribute of type “string.”
It sends vibration, yes.
Vibration and motion are different things, so something already doesn't add up.
It is a calculated attribute of type “string.”
So is it sent or is it calculated?
I have a calculated attribute configured as follows:
This string attribute is used to trigger a notification when the vehicle detects vibration while it is turned off. It worked correctly for a long time, but after several recent Traccar updates, the alarm is triggered when the vehicle is turned off, causing false activations.
I understand that, logically, the conditions are met when the ignition is turned off, but this behavior did not occur before. I would like to know if anyone else has experienced this issue after recent updates and whether there is a better way to define this attribute to detect real vibrations and avoid false alarms, especially since in my case it activates a 110 dB audible alarm.