Ok, I’m embarrassed to be asking this, but I’m hoping for some sympathy. SmartThings finally did it and pulled the trigger on the Groovy smart apps. I’ve been expecting and preparing for this for at least the last year. All is good… Except for my presence sensing in SharpTools.
Thank you for your service Life360…
I’ve got myself, wife, and kids as users in SmarThings using our phones as presence sensors. SmartThings routines can see that, and I can create rules inside SmartThings for us. But I can’t seem to figure out how to create the users as sensors that SharpTools can use.
I would not make such a global statement. My native SmartThings presence on Android is working just fine today, as it has been consistently over the last several years. I left and came back earlier today and it worked as expected.
If you have been relying upon L360 then that may have been deprecated
ST app location was working for me this morning for 3 departures/arrivals. I would guess most of the complaints are people that were using other 3rd party solutions like Life360 or webcore presence sensors that both stopped functioning yesterday/today.
That is certainly possible. They are however aware of a large number of Complaints due to the native Geo location not working. They Asked that I Grant them access to 2 weeks worth of data to help them resolve the problem. Perhaps it depends on the location in the country.
Next you will need to use the SmartThings API to interact with your presence sensor. Since you can’t make one in the IDE as the write up above states. You will need to use the vEdge drive to make a vEdge presence sensor.
Finally you will need to use the SmartThings Rest API to toggle you new vEdge presence sensor on/off(present/not present). Here’s a link to a thread about using the API and tasker. SmartThings Rest API using Tasker