Need help with a simple piston (presence)


#1

1) Give a description of the problem
Very simple presence based piston isn’t firing, but I’m new so it’s probably user error!

2) What is the expected behaviour?
When my son leaves the house, two switches should turn off.

3) What is happening/not happening?
Nothing lol. The piston hasn’t fired. The device history for all presence sensors (Life360) show that they are functioning properly.

Edits: Mentioned that presence works in ST app and added log after removing PPI

**4) Post a Green Snapshot of the piston!

5) Attach logs after turning logging level to Full
10/30/2020, 5:59:44 PM +47ms
+1ms ╔Starting piston… (v0.3.110.20191009)
+987ms ║Subscribing to Marco .presence…
+1102ms ╚Piston successfully started (1102ms)
10/30/2020, 5:58:16 PM +832ms
+1ms ╔Starting piston… (v0.3.110.20191009)
+947ms ║Subscribing to Marco .presence…
+1035ms ╚Piston successfully started (1034ms)
10/28/2020, 4:27:45 PM +498ms
+1ms ╔Starting piston… (v0.3.110.20191009)
+1110ms ║Subscribing to Marco .presence…
+1303ms ╚Piston successfully started (1302ms)
10/28/2020, 4:27:26 PM +79ms
+1ms ╔Starting piston… (v0.3.110.20191009)
+971ms ║Subscribing to Brad.presence…
+986ms ║Subscribing to Marco .presence…
+1088ms ╚Piston successfully started (1088ms)
10/28/2020, 4:14:20 PM +417ms
+0ms ╔Starting piston… (v0.3.110.20191009)
+987ms ║Subscribing to Marco .presence…
+1124ms ╚Piston successfully started (1124ms)
10/28/2020, 2:33:02 PM +597ms
+1ms ╔Starting piston… (v0.3.110.20191009)
+923ms ║Subscribing to Marco .presence…
+1046ms ╚Piston successfully started (1046ms)
10/28/2020, 9:19:36 AM +758ms
+1ms ╔Starting piston… (v0.3.110.20191009)
+873ms ║Subscribing to Marco .presence…
+993ms ╚Piston successfully started (993ms)
10/28/2020, 8:59:04 AM +777ms
+1ms ╔Received event [site].test = 1603889944774 with a delay of 3ms
+92ms ╚Event processed successfully (92ms)
10/28/2020, 8:42:51 AM +371ms
+1ms ╔Starting piston… (v0.3.110.20191009)
+871ms ║Subscribing to Marco .presence…
+1011ms ╚Piston successfully started (1011ms)
10/26/2020, 3:27:05 PM +107ms
+1ms ╔Received event [Marco ].presence = not present with a delay of 34ms
+99ms ╚Event processed successfully (99ms)
10/25/2020, 1:43:34 PM +988ms
+1ms ╔Received event [Marco ].presence = present with a delay of 35ms
+91ms ╚Event processed successfully (91ms)
10/25/2020, 1:05:10 PM +178ms
+1ms ╔Received event [Marco ].presence = not present with a delay of 36ms
+100ms ╚Event processed successfully (99ms)
10/24/2020, 6:10:16 PM +297ms
+1ms ╔Received event [Marco ].presence = present with a delay of 31ms
+85ms ╚Event processed successfully (85ms)
10/24/2020, 6:02:46 PM +969ms
+1ms ╔Received event [Marco ].presence = not present with a delay of 37ms
+113ms ╚Event processed successfully (113ms)


#2

Doed the presence sensor work?


#3

Yes. Sorry, I’ll update my post. The device history for all presence sensors (Life360) show that they are functioning properly.


#4

Finally got it sorted thanks to some info in this thread: Issue list for Webcore on New App

Essentially, I recently migrated to the new SmartThings app and updated the community Life360 SmartApp and DTH from GitHub. The presence sensors worked fine for native SmartThings and they appeared in webCoRE just fine. If I changed names in SmartThings, they changed in webCoRE as well, so things appeared to be syncing. But their status wasn’t syncing.

The fix was to completely remove the Life360 SmartApp and DTH from SmartThings and use the newer version by tmleafs, https://github.com/tmleafs/life360-smartthings-refresh/blob/master/devicetypes/tmleafs/life360-user.src/life360-user.groovy

Now Life360 shows up in the list of SmartApps rather than in the list of Linked Services.

Anyway, thanks to everyone who keeps this community active. I’ve been learning a lot from posts, even really old ones