You did. 
Oddly, I reinstalled and all was well.
I think it was something google-parent linked.
1 Like
Has anyone seen issues with using OwnTracks with the latest Beta release(s)?
I run OT on a C8 (non-pro) that I updated to the latest Beta release. When one (or worse, both) our iPhones go out, there seems to be a memory issue that hangs the C8. Not sure if this has to do with OT or the Beta release itself, or some strange interaction.
I've been on the 2.4.4 beta releases (and other beta releases before them) and haven't seen any issues so far.
2 Likes
I tend to be the fool that always blindly updates, and not seeing anything either.
Have you tried restarting? It seems that that helps flush any weird database stuff.
I've rebooted a few times...
Here is a graph that shows what happened when the wife left work this afternoon...
When we were traveling this past week, it hung the C8 to the point that it wouldn't respond, and had to be power cycled. We both had 1000+ events that needed to be downloaded. After reboot, it hung again while downloading the location points.
Running the latest iOS version on both our phones. Looks like it is recovering better under Beta 2.4.4.122
Here are my app stats:
EDIT:
Here are the other stats at the top...
40 apps,
hub uptime is 9h 44m 52s
Local apps: 2h 3m 39s / 9h 44m 19s total (21.2%)
Sorry... fully missed your response. Are those phones set to "move mode". That would have them spam the hub with locations at a frequent interval.
Here is the last 4-days for our hub. People (4) haven't been as busy leaving since it's been cold, but still had to go to work, etc (36x less traffic than your image):
Just switched from native Hubitat geofencing to OwnTracks and wish I made the change YEARS ago. Many thanks for this great app and driver!
4 Likes
Yes, that was the case. This hadn't been an issue previously (as much as it is a lot, it never overwhelmed before). I will have to remember to change this to "significant" in the future.
1 Like
Hello,
I'm attempting to log when I arrive and depart from work. I have configured a Region named Work and have discovered the transitionDirection attribute:
Should I trigger on the location attribute changing or a different attribute/event?
Thanks!
If you have configured regions for work, then these 3 attributes is what makes the most sense to trigger on. They only update on a transition in or out of region:
1 Like
Quick question.
Where do we measure the "Distance from Home".
At the moment I'm at home (presence is present, everything's like it should be) but my distance from home is 0.1km. Not a big deal but makes me wonder where is my home if I'm not there 
You must have locations that are bouncing 100m+ but the wifi is holding you "at home".
If your house has wheels, then you are safe since you can drag it wherever you need to go! otherwise.. hmmmm.... 
There are no wheels under the house.
Now that I look more closely, I have placed the pin in a place that is not on top of the house but maybe 0.1km from the house. That explains it.
Maybe there is a way to hide that information when presence is present.
1 Like
I was conflicted on doing that. If you made your "home region" say 1000m, I thought it would be useful to see how far you were from the actual pin.
1 Like
You are right..or actually could there be distance from home when you are not at home, and distance from home when you are at home. Like I said this is really not an issue but as I report person distance from home on my infoscreen it always gets my attention as I am home but still some distance away from home.
1 Like
Just pushed a new version:
- Fixed config map not displaying region data. (Apparently I broken that a while ago!)
- Reduced Google map data to browser. (Addresses history not showing)
- Clicking on member in the drawer properly opens their info page. (Missed that feature)
- Code cleanup and lint
The cleanup addressed the linter concerns which shouldn't change anything, but since I touched stuff, if you see things that don't work right, please let me know.
