It’s case sensitive… use arrivingAtPlace not ArrivingAtPlace
WebCoRE follows industry norms using lower camelCase where The first word is always lower case, subsequent words have uppercase first letter, no spaces.
You might do better using currentPlace though.
Good to know! That explains why some (currentPlace) worked and others (leavingPlace) didn’t.
Just curious… would you happen to know why LeavingPlace doesnt use camelCase?
Thats really strange… When I look at the DTH itself it shows leavingPlace but in the webCoRE script its displayed as LeavingPlace.
Is there a thread or post that provides the finer details of when each value (currentPlace, leavingPlace, previousPlace, arrivingAtPlace, presence) is updated and to what?
Can you post screenshots of where you are seeing differences?
There isn’t any specific guidance covering when each attribute gets updated but from my understanding.
Crossing an inner or outer radius triggers instant update of currentPlace, arriving, leaving etc.
Otherwise, outside of radius areas, it will update things like speed, direction, altitude every 5 minutes or 500 meters.
The issue Im having is that currentPlace gets nulled out when leaving the inner circle. I think using changes away from will solve my current problem. I was also trying to setup a push notification that included the arrivingAtPlace and previousPlace (i.e. Mary Jane has arrived home from work), but without having an understanding of when those values change with data and when they get nulled out its been driving me crazy so I just 86’d that idea for now.
If using changes away from works then the last thing I need to confirm is that the piston is optimized and wont trip over itself around the timers. Not to mention what its going to do when two or more of us are coming/going at or near the same time. I havent even started looking at that area yet.
PS - I have a single global variable that includes 4 iPhones.
The one below you can see how the scripts displays leavingPlace as LeavingPlace.
