#but after you fixed what petro mentioned

1 messages · Page 1 of 1 (latest)

ornate carbon
#

Thx - I think that's what I want - the source entity is polled every 30 minutes via an API. The data is fed to the API from a sat-nav. If the sat nav is off, then the data will always be the same. If the sat nav is on, then it changes.

quaint orbit
#

but if it's polled, and there is no state change because the car is on the same spot, there will be no change of the entity, and therefor no trigger

#

it will only trigger if either the state or one of the attributes changes, and if that happens, it's most likely that the location changed, so the binary sensor will be on

ornate carbon
#

The lat and long have 6 decimals of precision and there's always a bit of jitter in the last 1 or two digits (I think - yet to be proved), but this is a slightly stripped back example - I actually want the binary sensor to be "is car moving" and I'll round(3) and subtract the from and to values

#

I've been stuck on the object syntax for a little while, should be able to actaully test now 🙂

quaint orbit
#

you might be better of if you do a time pattern trigger, and each time store the lat and lon of your device trigger

#

then on the time pattern, check if there has been a significant change, using the distance() function