webCoRE mobile app - iOS Source Code

kxavier_23 · 2018-03-03 22:36:50 UTC

When I say, “smaller,” I just want to reduce the 200M difference to say 100M or 50M. I don’t want to make them the same size.

This is why.

Ryan780 · 2018-03-03 23:41:47 UTC

I still don’t understand how making the departure zone smalerl will reduce the number of false triggers. The reason you’re getting false arrivals is because it’s first detecting that you left. Right?

Robin · 2018-03-03 23:52:10 UTC

He’s driving past home… scraping the edge of his outer geo-Fence… which triggers arriving followed immediately by departure.

So he wants a smalller outer geofence.

Robin · 2018-03-03 23:57:41 UTC

@kxavier_23

Going back to your original post requesting the app source code.

My understanding is that the mobile app is not much more than a web wrapper with the ability to report location to webCoRE.

I believe the geofence size is set by the dashboard code… not the mobile app.

The dashboard code is in @ady624’s GitHub repo but you’d need to figure out how to run it on your own servers / web address.

Ryan780 · 2018-03-04 00:01:49 UTC

I’m sorry, I’m still not understanding. The outer ring is the departure radius. So, if you’re clipping that but you’re already “not present” that shouldn’t be a problem. I was able to go in and make my arrival zone as small as 50m. You need to get smaller than that?

Robin · 2018-03-04 00:06:12 UTC

@kxavier_23

I think this is the relevant part of the dashboard JS:

if ($scope.designer.inner + 200 >= $scope.designer.outer) {
	        $scope.designer.outer = $scope.designer.inner + 200;
	    }

github.com

ady624/webCoRE/blob/master/dashboard/js/modules/dashboard.module.js

config.controller('dashboard', ['$scope', '$rootScope', 'dataService', '$timeout', '$interval', '$location', '$sce', '$routeParams', 'ngDialog', '$window', function($scope, $rootScope, dataService, $timeout, $interval, $location, $sce, $routeParams, ngDialog, $window) {
	var tmrStatus = null;
	var tmrClock = null;
	var tmrActivity = null;
	$scope.initialized = false;
    $scope.loading = true;
    $scope.data = null;
    $scope.error = '';
	$scope.designer = {};
	$scope.locations = null;
	$scope.instances = null;
	$scope.requestId = 0;
	$scope.dropDownMenu = false;
	$scope.endpoint = '';
	$scope.rawEndpoint = '';
	$scope.categories = [];
	$scope.pausedPistons = [];
	$scope.view = 'piston';
	$scope.isAppHosted = !!window.BridgeCommander;
	$scope.hostDeviceId = '';

This file has been truncated. show original

Robin · 2018-03-04 00:09:59 UTC

When entering the outer ring it triggers ‘arriving at place’.

When entering the inner ring it triggers ‘current place’

So if he wants an action for arriving at place, not current place, the outer ring needs to be smaller to avoid drive by false alarms.

Ryan780 · 2018-03-04 00:12:04 UTC

Then it seems you would want to have the trigger be current place not arriving at place. If you make the outer ring smaller, you are going to get false departures. When my phone automatically turns off GPS, since it can’t run it 24/7, I frequently jump into my neighbors house…so I have to set up geofences accordingly.

And if you’re in such an area that it needs to be that accurate (I’m thinking large city) maybe you want to use a virtual presence center tied to your wifi or something rather than GPS.

Robin · 2018-03-04 00:14:56 UTC

Some people like to use arriving at place so their garage door is open by the time they actually pull onto the drive.

I don’t know the OP’s use case so using current place may work for him… but the fact he has been tweaking the presence DTH tells me he knows those options already.

Ryan780 · 2018-03-04 00:16:50 UTC

Possibly…but I don’t know if I would assume that right off the bat. Plus, how long does a garage door take to open? 10 seconds? make your home location a tiny bit bigger and voila, it will open earlier. I dunno, just seems like there are easier ways to fix the problem he has than tweeking code.

Robin · 2018-03-04 00:25:40 UTC

I was using the Garage Door as an example… might be to open a driveway gate or turn on a driveway light.

Also, for many users, particularly those in a built up area, the inner 50m is too large as well.

Robin · 2018-03-04 00:35:35 UTC

My inner radius for example means I can’t drive past the house without triggering current place… and the outer radius covers several surrounding roads.

kxavier_23 · 2018-03-04 01:27:08 UTC

Yes, this is the same issue I have.

I can get horizontalAccuracy down to 10M. If I can shrink the circles and make them tighter, I believe the false triggers will go away. I truly like the location capabilities, It’s just not manageable with the current restrictions.

Ryan780 · 2018-03-04 01:37:49 UTC

And you think that tweeking the diameter of the outer ring is going to solve any of that? If it does, I’ll be the first to admit I was wrong but I think even if it solves those problems it’s going to cause others.

kxavier_23 · 2018-03-04 01:38:55 UTC

Where is this? I am looking through the code in the smartapps, but can’t find it.

You did find the correct place though

Ryan780 · 2018-03-04 01:40:46 UTC

You’re able to have 10m accuracy all the time? Remember, you don’t just have to look at arriving and leaving…you need to think of staying home as well. If things happen when you leave home, you don’t want them to trigger all the time out of nowhere.

kxavier_23 · 2018-03-04 01:42:26 UTC

I have considered that as well. I would just like to experiment with my geo fence sizes and go from there. I understand it is at my own risk.

Robin · 2018-03-04 08:23:55 UTC

It’s not in any of the smartapps, it’s in the dashboard JS file I linked to above.

kxavier_23 · 2018-03-04 14:50:37 UTC

So where/how would I make the changes locally?

Robin · 2018-03-04 15:01:07 UTC

you would need to host the webcore dashboard (website) locally on a server, using the various JS modules etc. shared on GitHub… I wouldn’t have a clue myself!!!

Then you would still have the problem with the mobile app pointing towards webcore.co instead of your local address.

Gonna need to be addressed by the webCoRE team but from what I understand there has been tonnes of issues with smaller radius’s, loads of questions from disgruntled users and lots of repeating ourselves (telling users to make their radius bigger)… so unlikely the change will happen.