I've noticed what I can only describe as a state flicker.
The two states that I have noticed are "member_within_geofence" and "member_closest_address"
While setting up triggers, I tried using "member_closest_address" and found that the reported address will sometimes flash "geocode error" This example isn't too bad because I was able to work around it by using conditions in the trigger: member_closest_address" does contain "geocode" and now that trigger works fine.
With the geofences, I've had some fun figuring out the differences between indigo-geofences and places-geofences. I set a trigger to watch a member device (me) and trigger if "member_within_geofence" becomes not equal to "Home-Wide" <- an indigo-geofence larger radius around my places-geofence for "Home". This one truly flickers. My trigger repeatedly fires. I changed the trigger to "has any change" and added a pushover message to give me the string when it fires. All it says (in the pushover message) is "Home-Wide". It's like the state changes off-on-off-on so quickly that by the time the pushover message goes, it's back to on? Debug didn't provide me any clues.
- Code: Select all
Life360 Debug Updating device: William
Trigger L360 - Bill Arrives Home-Wide
Trigger L360 - Bill Arrives Home-Wide
Trigger L360 - Bill Arrives Home-Wide
Trigger L360 - Bill Arrives Home-Wide
Life360 Debug Updating device: Harper
I'm still testing a lot, ran into several hardware issues and possibly a software issue. The life360 app didn't update 2 of the phones.... they were home from school for about a half hour before they updated. Then they updated immediately for both phones once I opened the app on one of the two phones.