Here’s logs of this evening sanitized…
Phone has moved around inside house but mostly sitting next to me on the desk.
HA LOGBOOK:
4:43 PM Nate Geocoded Location changed to *** HOME ***
5:12 PM Nate Geocoded Location changed to *** THREE HOUSES AWAY IN PROPERTY THAT HOUSES SIT ON FOUR ACRES ***
5:25 PM Nate Geocoded Location changed to *** HOME ***
6:10 PM Nate Geocoded Location changed to *** SAME AWAY PROPERTY AS BEFORE ***
6:25 PM Nate Geocoded Location changed to *** HOME ***
7:43 PM Nate Geocoded Location changed to *** NEIGHBOR AGAIN ***
APP EVENT LOG SAME TIMEFRAME:
4:43 looks normal, triggered by entering the geofence around “Home”
5:12 A background fetch starts right at log rotation to a new file…
2019-10-25 17:12:11.549 [Verbose] [main] [AppDelegate.swift:227] application(_:performFetchWithCompletionHandler:) > Background fetch activated at Oct 25, 2019 at 17:12:11 Mountain Daylight Time!
new file, removed logger notice about file rotation…
`2019-10-25 17:12:11.551 [Warning] [main] [WebhookSensors.swift:297] getLatestMotionActivity() > Motion permission not enabled
2019-10-25 17:12:11.572 [Verbose] [main] [HAAPI.swift:506] GetAndSendLocation(trigger:) > getAndSendLocation called via BackgroundFetch
2019-10-25 17:12:11.589 [Info] [main] [ClientEventStore.swift:23] ClientEventStore > ClientEvent {
date = 2019-10-25 23:12:11 +0000;
text = Ignoring one shot location with accuracy over threshold.Accuracy: 263.0239512427212m;
typeString = locationUpdate;
jsonData = <(null) — 0 total bytes>;
}
2019-10-25 17:12:11.591 [Verbose] [main] [WatchHelpers.swift:85] BuildWatchRenderTemplatePayload() > complications Results <0x10335d3c0> (
)
2019-10-25 17:12:11.592 [Verbose] [main] [WatchHelpers.swift:91] BuildWatchRenderTemplatePayload() > mostRecentlyReceievedContext.content nil []
2019-10-25 17:12:11.592 [Verbose] [main] [WatchHelpers.swift:127] updateComplications() > No complications have templates, not sending the request!
2019-10-25 17:12:20.026 [Verbose] [main] [OneShotLocationManager.swift:43] locationManager(_:didUpdateLocations:) > LocationManager: Got 1 locations, stopping updates!
2019-10-25 17:12:20.031 [Info] [main] [HAAPI.swift:477] SubmitLocation(updateType:location:zone:) > Location update payload: [“gps_accuracy”: 50.0, “gps”: [REDACTED, REDACTED], “speed”: 0.0, “altitude”: 1865.509952545166, “vertical_accuracy”: 48.0, “battery”: 43]
2019-10-25 17:12:20.190 [Warning] [main] [WebhookSensors.swift:297] getLatestMotionActivity() > Motion permission not enabled
2019-10-25 17:12:20.191 [Warning] [main] [WebhookSensors.swift:217] getLatestPedometerData() > Motion permission not enabled
2019-10-25 17:12:20.192 [Verbose] [main] [WatchHelpers.swift:85] BuildWatchRenderTemplatePayload() > complications Results <0x102625ac0> (
)
2019-10-25 17:12:20.193 [Verbose] [main] [WatchHelpers.swift:91] BuildWatchRenderTemplatePayload() > mostRecentlyReceievedContext.content nil []
2019-10-25 17:12:20.193 [Verbose] [main] [WatchHelpers.swift:127] updateComplications() > No complications have templates, not sending the request!
2019-10-25 17:12:20.915 [Verbose] [main] [HAAPI.swift:493] SubmitLocation(updateType:location:zone:) > Device seen via webhook!
2019-10-25 17:12:20.920 [Info] [main] [ClientEventStore.swift:23] ClientEventStore > ClientEvent {
date = 2019-10-25 23:12:20 +0000;
text = Current location delivery triggered via background fetch;
typeString = locationUpdate;
jsonData = <length = 24, bytes = 0x7b0a2020226770735f616363757261637922203a2035302c — 185 total bytes>;
}
2019-10-25 17:12:20.922 [Verbose] [main] [AppDelegate.swift:753] setupFirebase() > Logging event location_update to analytics`
I’ll just stop there… I see the phone is lying to the app. The REDACTED Lat/Long are the neighbor’s land next door well over 300m away, but the phone reported 50m accuracy. That’s BS, but not the App’s fault.
Not sure how the App can deal with it, other than ask for multiple locations in a row and see if the phone tends to get two out of three right, or what… but if the phone says 50m accuracy and drops the coordinates over 300m from where it actually is, there’s nothing the App can EASILY do about it.
It looks like the App also did the right thing and got an inaccurate location first that even the phone said was inaccurate, and then asked again. Phone said 50m so it sent it to HA.
Would be interesting to track if this happens on only one carrier – mine is Verizon and since the phone is using assisted GPS with tower locations factored in, and they are VERY far apart out here… I wonder if the phones give inaccurate junk locations.
I skimmed the other events and they’re all similar. Phone is lying about accuracy… sigh.
