Ah, the template syntax probably uses "==" and what I wrote is an assignment. Trying it out...
No, that wasn't it. Alarm is still active with this condition:
Wait, now it's gone. When are they recalculated? With every incoming message? So basically every time the "Last Update" column shows "0 minutes"?
Ok, it now repeatedly works, so I guess I might not have refreshed the state the first time. Everything works as expected when using the correct syntax.
Computed attributes are only calculated for new data, so when you change it, existing data won't be recalculated.
I was testing out the alarm/notifications function. I configured a computed attribute like this:
That worked and the alarm is now active:
To disable my test alarm I changed the condition to:
But the alarm stays active:
Shouldn't it be removed? The device has sent several position updates since I changed the condition.