What are the issues you are experiencing by not being able to limit the circles below the set limits?
Please see my initial post on the size limitation of the arrival/departure:
If you make the circles smaller then the false arrivals/departures go up. Logic will then need to be added so doors are not opening/closing, heating and cooling is not turning on/off.
Why not add logic to resolve the issue you are currently having?
Something to try would be outputting all the variables (ie currentPlace, leavingFrom, arrivingAt etc) whenever any of them change. You might be able to catch the leavingFrom attribute when you exit the small circle into the larger circle. So you would not have to fully exit the large circle for your piston to fire.
I jailbreak my iPhone and had an issue. The TestFlight App requires a higher version of iOS than I am running, and upgrading to the newer version would cause me to loose my jailbreak. It turns out there is a simple soultion. If you are jailbroken, and would like to use the WebCore Precense Sensor, simply download the iFile app from cydia, and use it to edit the system.plist file. You will need to manually change the iOS version (for example, from 10.1 to 10.3), as well at the Build Version. More detailed instuctions on his process can be found using a google search (something like "iPhone spoof firmware version iFile system.plist), or message me for help.
I asked about that a while back and the answer was that the floor function is for indoor maps (dont remember if it was Apple or google maps) with defined floors.
Ok, so I tried this and I can’t seem to define separate locations.
Here is my setup…
webCoRE mobile app registered on both my House and Cabin hubs. In ST, I have the following webCoRE instances:
House - webCoRE House for pistons other that tiles
webCoRE Tiles - for all tile pistons
Cabin - webCoRE Cabin - for positions other than tiles
webCoRE Tiles - for all tile pistions
I authenticated the webCoRE House and webCoRE Cabin. When I went to, “Settings”, for both of those instances, I saw the icon to setup Presence Sensor. I did that in both instances and called them both, “MyName Presence Sensor,” which added them as a, “Thing” in ST. I then added those, “Things,” to each webCoRE version listed above.
I was hoping that when I logged into each instance (House and Cabin) in the webCoRE instances, I could define separate locations such as Home and/or Cabin. What I am seeing is that locations are being, “shared,” across webCoRE instances.
Am I doing something wrong here?
Just noticed that in TestFlight the webCoRE presence app is expiring in 30 days.
It works perfectly for me and would hate to see it get discontinued.
I’ve no doubt @ady624 will push out a new build on test flight before that happens…
Yeah I will. Will try to look into the motion sensor to provide more info, but I might push the app out of beta to get rid of the expiration time. I am still in Romania taking care of my mom but will get back to my usual schedule soon, meaning I will spend weekends on moving forward.
I believe that I solved my issue from above with the different locations defined on separate installs of webCoRE.
What I am noticing is that the presence app used to be pretty accurate. Since I reinstalled the app and redefined the presence sensors in ST, it is wildly inaccurate now.
i.e. I have to open the webCoRE app on my phone most of the times for the presence sensor to update ST.
I use these presence sensors (installed on 2 iPhones) for light and garage door on arrivals and departures so it is pretty important to me that they work properly.
Any ideas on why all of a sudden they are not being accurate?
I have the app in the phone settings (both devices) to use location, “always.”
I have also tried uninstalling the webCoRE app on both devices, removing the created presence sensors in ST. Then reinstalling and creating the new presence sensor in both my webCoRE instances (one for my house and one for my cabin).
Hi, sorry to jump into this thread, I was trying to get a PM sent to you for the Testflight invitation as per the instructions here - but I probably do not have the permissions! Any chance you @ady624 can PM me and then I will reply with my details.
Thanks a tonne for developing this!
Just spend 30 minutes browsing the forum, your trust level will increase and you can then send PM’s
One other aspect, i used to have a separate webCoRE instance of the presence before and it was much more accurate.
When I went to install the app on my gf’s phone, I deleted the independent instance of webCoRE from STs that was dedicated for presence. I then added the, “new,” presence in ST to my existing webCoRE instance that has all my home pistons running.
Hello, nice to meet you, i’m Marco and i’m new to this forum. I would like to join the beta program for iOS but I cannot send you PM. Can you please help me ?
Uhhh really sorry. Just read I have to browse the forum for 30 minutes. Not a big issue because I read it all day
How can you send a PM to get a testflight invitation.
Hey all, new member here. I’m having trouble understanding the purpose of this. Both my Android phone and my SO’s iPhone are set up as presence sensors and, while I’m still trying to figure out how to make webCoRE do stuff for me, it appears to already work. Why do I need this?
SmartThings has improved their backend code of their sensors based on changes Adrian has been making. But webcore presence has infinitely more possibilities
ST presence has been a problem for years. For some it works great and others it never works. If it is working perfectly for you then no need to use the webCoRE presence sensors unless you want to add more locations and have automations happen when you arrive or leave locations other then your home.
For example, when I leave work I have a piston that sends a text message to my wife letting her know that I have left work. With the ST presence sensor I would not be able to do that.
I see. Since I’m still very green, I don’t yet know if ST is working perfectly (or even ‘good enough’) for me but it doesn’t sound like something I need to urgently install and configure. Thanks!