Custom alarm by computed attributes to be triggered only once per period
It might be possible. You can have another attribute to mark the fact that you had a alarm. Then you use attribute copying to copy that attribute to the new position, then you can use that flag to avoid triggering duplicate alarm.
Thank you for pointing me in the right direction.
I read somewhere that computed attributes shouldn't rely on other computed attributes so I tried to avoid it, but in my current setup it seems to work.
Your reply helped me to solve 1. and 2.
For 3. & 4.:
I implemented the event forwarding and I realised that only computed attributes defined as "alarm" and the predefines events are being forwarded. So it seems that a computed attribute defined as "event" is only showing up in the state window and is recorded in the attributes but doesn't forward anything.
Please correct me if I am wrong.
Yes, event is just an attribute. Alarm is what triggers event on the server side.
Hi Anton,
I created a computed attribute which triggers an alarm if a vehicle exceeds the speed limit (30km/h) during the night time (8pm-5am). Of course the alarm is being triggered every time the condition is true.
Is there a way to restrict it to only once per period, something like "event.overspeed.notRepeat"?
Can this be achieved with computed attributes?
If I create an alarm with computed attributes, it shows in the Events-Report and in the Events-Window. If I create an event, it doesn't.
Which is the main difference between an event and alarm?
One of my next steps is to enable the event forwarding from traccar to another web server.
Will this feature forward only events or also alarms?
Thank you so much for this awesome platform.