I have noticed the same, however new regions are still not populating to the iOS devices, so I think it is just a fluke where it synced the regions, then the notifications are now using those regions properly. Which does kind of tell us that the only issue is the region creation/update, all other communications about the region work perfectly fine afterwards.
Any regions you had in 1.7.48 would properly sync to the iOS, but not on 1.7.49. Next version will properly correct this.
1 Like
yeah I get the non-syncing on 49 part, but the interesting thing is that regions synced to ios in 48, after transitioning to 49 still work, so notifications and presence for iOS devices work in 49 as long as the regions were synced in 48 (and obviously not changed).
Oh, yes that is expected. The issue was incoming regions were stored as strings with "quotes" around the numbers. In the lasted iOS version, when the timestamp went back with the "quotes" around it, it would reject it. Technically, they should have always been stored as 'just numbers' on the HE side to match their API document.
1 Like
Is there anything that the phone apps send that can be used to determine if they are iOS or Android? If so, maybe the response can be sent based on that.
They do, but that wasn't actually the issue. I should have been storing those numbers as numbers instead of strings which get wrapped in quotes. This last iOS OwnTracks version must have removed the conversion from strings -> numbers (since it shouldn't have been needed) and that is why it stopped working.
Changes are almost done. Just need to double check the notifications are fine, and then I can release it.
2 Likes
This may be what has been recently discussed, and I'm just too dense to realize it. But if I have a device that hasn't reported in days and each time it tries to report, I log this on the HE side
what do I need to correct?
Can you check that region on that device? Radius of 0 can cause you issues, and it looks like there is no name assigned to it?
Pushed a new version to address the iOS regions.
Once you upgrade the HE app, open it and click 'Done' on the bottom right to force the app to migrate the stored regions to the proper format.
@s1godfrey started the virtual device that you were asking for. It's in the driver, and I'll get the cloud link portion in the next version.
3 Likes
Home region stays updated, notification regions save properly (though they were unset and I had to reset them). So far so good. New regions pushing over to iOS without issue. Notifications working without issue from what I have tested so far, but I am hopeful.
1 Like
@ipakula is there a way you can add a test button to the google api sections so we can make sure its working. having issues and not sure of an easy way to test. (Geocoding & Maps API)
The lat/long of the failing report is my home. All of my regions defined in the app have names and radii. Just for fun, I've now deleted all regions except +60follow on in the app, restarted the app, but when I force an update I still get the same error.
The status in the app side says error 500 The operation couldn't be completed, but obviously it is reaching HE.
Now I'm not receiving any updates to the HE app from my Android. Waiting to see if the iOS checks in (It's a friends).
app:7112024-04-26 07:55:22.929debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:55:22.889debugOwnTracks: Check members for stale locations.
app:7112024-04-26 07:55:22.880debugOwnTracks: Leaving Lisa device name as 'OT - Lisa'
app:7112024-04-26 07:55:22.878debugOwnTracks: Leaving Jeff device name as 'OT - Jeff'
app:7112024-04-26 07:55:22.876debugOwnTracks: Leaving Cathy device name as 'OT - Cathy'
app:7112024-04-26 07:55:22.875debugOwnTracks: Leaving Brian device name as 'OT - Brian'
app:7112024-04-26 07:55:22.867infoOwnTracks: Updated
app:7112024-04-26 07:55:19.512debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:55:14.762debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:55:06.963debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:55:01.434debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:54:38.147debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:54:33.132debugOwnTracks: updateWaypoints for user Lisa: true
app:7112024-04-26 07:54:33.131debugOwnTracks: updateWaypoints for user Jeff: true
app:7112024-04-26 07:54:33.131debugOwnTracks: updateWaypoints for user Cathy: true
app:7112024-04-26 07:54:33.130debugOwnTracks: updateWaypoints for user Brian: true
app:7112024-04-26 07:54:33.120infoOwnTracks: updated place: [_type:waypoint, desc:Parrish House, lat:42.460469, lon:-87.851551, rad:223, tst:1712181729]
app:7112024-04-26 07:54:22.052debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:49:09.525debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:49:09.521debugOwnTracks: Check members for stale locations.
app:7112024-04-26 07:49:09.512debugOwnTracks: Leaving Lisa device name as 'OT - Lisa'
app:7112024-04-26 07:49:09.510debugOwnTracks: Leaving Jeff device name as 'OT - Jeff'
app:7112024-04-26 07:49:09.508debugOwnTracks: Leaving Cathy device name as 'OT - Cathy'
app:7112024-04-26 07:49:09.506debugOwnTracks: Leaving Brian device name as 'OT - Brian'
app:7112024-04-26 07:49:09.497infoOwnTracks: Updated
app:7112024-04-26 07:49:02.113debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:44:41.814debugOwnTracks: Cathy's position is stale. Requesting a high accuracy location update.
app:7112024-04-26 07:44:41.810debugOwnTracks: Check members for stale locations.
app:7112024-04-26 07:44:41.800debugOwnTracks: Leaving Lisa device name as 'OT - Lisa'
app:7112024-04-26 07:44:41.798debugOwnTracks: Leaving Jeff device name as 'OT - Jeff'
app:7112024-04-26 07:44:41.797debugOwnTracks: Leaving Cathy device name as 'OT - Cathy'
app:7112024-04-26 07:44:41.787debugOwnTracks: Leaving Brian device name as 'OT - Brian'
app:7112024-04-26 07:44:41.766infoOwnTracks: Updated
app:7112024-04-26 07:44:16.282errorjava.nio.file.NoSuchFileException: Lisa.jpg on line 1448 (method insertThumbnailObject)
app:7112024-04-26 07:44:10.835errorjava.nio.file.NoSuchFileException: Lisa.jpg on line 1448 (method insertThumbnailObject)
app:7112024-04-26 07:44:10.697errorjava.nio.file.NoSuchFileException: Lisa.jpg on line 1448 (method insertThumbnailObject)
app:7112024-04-26 06:44:53.133warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 06:44:48.899warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 06:44:48.792infoOwnTracks: Request status for user Jeff
app:7112024-04-26 06:44:48.565warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 06:44:48.500infoOwnTracks: Request status for user Jeff
app:7112024-04-26 06:44:33.761warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 06:44:33.598infoOwnTracks: Request status for user Jeff
app:7112024-04-26 04:30:44.796warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 04:30:44.218warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 04:30:43.634warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 04:30:43.521infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 04:00:44.138warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 04:00:43.549warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 04:00:43.386infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 03:30:45.022warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 03:30:44.276warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 03:30:43.517warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 03:30:43.355infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 03:00:44.423warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 03:00:43.901warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 03:00:43.309warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 03:00:43.158infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 02:30:44.252warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 02:30:43.697warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 02:30:43.205warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 02:30:43.010infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 02:00:44.158warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 02:00:43.621warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 02:00:42.991warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 02:00:42.878infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 01:30:43.864warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 01:30:43.461warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 01:30:42.766warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 01:30:42.662infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 01:00:43.948warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 01:00:43.456warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 01:00:42.863warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 01:00:42.691infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 00:30:45.214warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:30:44.660warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:30:43.904warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:30:43.886infoOwnTracks: Requesting a high accuracy location update for Brian
app:7112024-04-26 00:30:42.539warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:18:59.060warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:18:58.496warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:18:58.445infoOwnTracks: Requesting a high accuracy location update for Jeff
app:7112024-04-26 00:11:06.252warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:09:17.023warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:09:15.881warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:00:44.794warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:00:43.175warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:00:42.577warnOwnTracks: OwnTracks HTTP response: 404, with error: Not Found
app:7112024-04-26 00:00:42.445infoOwnTracks: Requesting a high accuracy location update for Brian
Looks like it really stopped at 6:44 AM This morning:
dev:24422024-04-26 06:44:52.976debugUpdating 'Manual' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 98%, accuracy: 13 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-26 06:44:48.691debugUpdating 'Ping' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 98%, accuracy: 13 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-26 06:44:48.409debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 98%, Velocity: 1.2 mph, accuracy: 33 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-26 06:44:33.469debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 98%, Velocity: 1.2 mph, accuracy: 33 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-26 00:18:58.856debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: true), 0.1 mi from Home, Battery: 80%, accuracy: 52 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-26 00:18:58.346debugUpdating 'Ping' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 80%, accuracy: 52 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 23:58:02.486debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: true), 0.1 mi from Home, Battery: 80%, accuracy: 328 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 23:58:01.658debugUpdating 'Ping' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 80%, accuracy: 328 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 23:27:18.402debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: true), 0.1 mi from Home, Battery: 59%, accuracy: 328 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 23:27:12.823debugUpdating 'Ping' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 59%, accuracy: 328 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 22:57:01.033debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 26%, accuracy: 328 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 22:57:00.512debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: true), 0.1 mi from Home, Battery: 26%, accuracy: 328 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 22:56:59.719debugUpdating 'Ping' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 26%, accuracy: 23 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 22:26:49.531debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 32%, accuracy: 23 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 22:26:45.073debugUpdating 'Location' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: true), 0.1 mi from Home, Battery: 32%, Velocity: 3.1 mph, accuracy: 49 ft, Regions: [Parrish House] , SSID: Parrish
dev:24422024-04-25 22:26:39.686debugUpdating 'Ping' presence for OT - Jeff -- 'present' (Home Wifi: true, High Accuracy: false), 0.1 mi from Home, Battery: 32%, Velocity: 3.1 mph, accuracy: 49 ft, Regions: [Parrish House] , SSID: Parrish
When you deleted them from the hub, did you delete them from that phone that is having the issue?
The error 500 is the hub throwing that error and not sending a response to back to the phone.
Can you turn on the debug logging on the HE app and get me the logs from it? Something isn't set up correctly for all those 404 errors.
Yep not working. This happened after I updated owntracks app from HPM.
EDIT: oh.. needed to force presence update from hubitat..then 5min and no more errors in log.
1 Like
Looks like my phone updated to 2.5.0 and that's where it messed up. Along with Android 15. So, I think Android quarantined the OT app.
New 2.5.0 Beta 2 - Release refs/tags/v2.5.0-beta2 · owntracks/android · GitHub
2 Likes
Those logs were with debugging.
Forced my OT to install 2.4.12 by installing the APK and it started working for my phone again.
I deleted them only on the phone. I have now checked and regions as seen on the HE side all have names and radii, although Home has a 10000 ft radius which I didn't think was possible; I guess related to setting a large geofence?
Still getting the error. I can try deleting regions from the HE side but heading out the door for a plane and it will be late next week before I can do so. Thanks so much for your assistance!
