No guarantee that the location on hubitat will work.
And we core isn’t available anymore if you didn’t install it previously (which I didn’t) since you can no longer add smartapps on IDE.
Just sucks a bit that functionality that was (maybe still is for some?) built in has just disintegrated and I have to look to buying other things to make it work or watch hours of tutorials and coding just to get home assistant to talk to smartthings (and the only reason that doesn’t cost me something specifically is because I had a rasp pi 3 laying around)
Webcore is no longer operational on SmartThings no matter when you installed it since it was turned off with all the other custom groovy SmartApps this week. But it IS available on Hubitat: in fact, they just recently announced it’s going to be included as an official feature.
There are two different community-built methods for mirroring devices attached to a smartthings hub over to hubitat so you don’t even have to rebuild your network if you don’t want to. You can find these on the quick browse lists in the community-created wiki on the “edge services“ list.
My wife’s phone (Pixel 5a) constantly have issues acting as a presence sensor.
It’s not working for a week now while my OnePlus working as usual.
Even when it used to work it was something I cannot rely on.
Any advise what can be done?
Already deleted cache and data, disabled and then enabled the phone as presence sensor, nothing seems to do the trick.
Interesting. Both my wife and I have OnePlus 7T’s. Mine works fine. Hers quit working totally about 4 months ago. Almost seems like only one presence sensor per family. I’m sure that’s not it though.
Does she have a separate ST account? If not, then multiple presence sensors in the same account are all assigned to the owner of the account for the purposes of Member Location.
Does she have a separate ST account? If not, then multiple presence sensors in the same account are all assigned to the owner of the account for the purposes of Member Location.
Also, I found that phone presence has been completely unreliable of late and switched to using Alexa for my location tracking needs. How I have it set up is documented here. You can also use the same method substituting IFTTT for Alexa.
I did not know that. My wife is signed in to my account. So I need to create a separate ST account in my wifes name? If so how do I tie it into my home account?
If you look in Member Location of a Routine and don’t see two distinct people like in the screenshot, then you have multiple presence sensors for one person. If that’s the case, you need to create an account for your wife and then invite her to the Home from the existing account from the Manage Home screen.
Now, that being said, if you create virtual presence sensors for each of you and use those in Routines vs Member location, then you can get away with using a single account on each of your phones, provided, you don’t need Alexa linked from both of your phones to that single account.
I find things work a little more elegantly if you do but it shouldn’t make any functional difference to Member Location for you as the ‘any’ or ‘all’ applies to the selected devices.
The Android app has got much better at checking that it can access the location services whenever it wants and won’t get put to sleep so if you haven’t disabled and reenabled the location checking on your wife’s app it may be worth doing. I often find presence sensing just stops working after an app update on a particular phone but not on others.
Hi, my Wife has different account,
I’m registered as the “house owner” and I invited her as a “member” to join my house.
As stated sometimes it works and sometimes it doesn’t.
You can’t rely on it in terms of the Home monitor that will switch from Home (Disarmed) to Away (Armed) based on the location of our cell phones.
With the same phones I don’t have such a problem while using the same method in Home Assistant so I guess the problem is behind the scene and not related specifically to our phones.
And it did it again this month. The presence was working very well, then after the update it stopped working across three places. I turned the app location usage off and on again and updated the device ID in the Rules and it is back working.
