mxdcodes

It works but I wouldn’t call it the cleanest solution, more a workaround. As far as I know only apps targeting SDK 37 are affected, older apps still get the permission implicitly. So the proper way would be to just grant “Nearby devices” to the apps that need it e.g. Immich or Jellyfin and if an app doesn’t ask for it that’s actually a bug and worth reporting, because it should request the permission as soon as the server resolves to a local IP. I also find the “Nearby Devices” title a bit misleading for apps that only need it to reach your own server, but on the other side it gives a somehow proper hint what the permission actually allows.

Tunnel is fine security wise. Keep the reverse proxy anyway and let the tunnel point at it. Routing, logs, etc. stay in one place this way.

Zero Trust with Google etc. is the way for family. Tailscale or Wireguard means installing a VPN client and making sure it keeps running, that’s too much for most people who just want to click a link.

Image There is a toggle next to it which enables it.

Sorry, should have mentioned it when i refer to it. In “Settings > Tracking & Sync > Advanced Settings” See also colota.app/docs/configuration/gps-settings

In case you have a profile that should activate at >10km/h it will kick in when the last 5 points average speed is above >10 km/h. The notifcation banner and dashboard will show when a profile is active. If your interval for that profile is 5s, a new point will be requested every 5 seconds. With a movement threshold of 10m in that profile, all points that have not atleast a distance of 10m to the last location will be skipped.

So to get smoother tracks you can decrease the movement threshold. Personally I use a movement threshold of 2m with a tracking interval of 6seconds which works very well for me.

Logging points every 10m is without a time interval is not possible, because the app needs a location to determine you moved 10m. A workaround would be to decrease the interval to something like 3 sec and set the movement threshold to 10m. Then the app will request every 3 seconds a new location and checks if it is atleast 10m apart from the last point. If it is it will recorded and otherwise it will be discarded. That will use a lot more battery though.

You can read more about the tracking profiles in the docs: colota.app/docs/guides/tracking-profiles

For places where you stay frequently (home, work, etc.) geofences work better. The stationary profile is good for situations where you are temporary for a longer time at a place (restaurant, friends, etc.)

Out of the box Colota records every fix it gets by the device. So in case you haven’t already I would suggest to enable the accuracy filter and set it e.g. to 25m. This way all points with accuracy worse than 25m get filtered out. Also the movement threshold helps with the stationary drift

Colota dev here 👋 What do you want the profiles to do?

Profiles are an optional thing to finetune your tracking settings based on certain conditions, e.g. speed above or below x km/h, phone charging, Android Auto connected or being stationary. So you could raise the interval while charging, since that usually means you are not moving. To start with you could also make a pause zone at home and at work and turn on the WiFi pause. GPS stops completely while you are there and the app will consume much less battery. Tracking resumes when the WiFi drops.

I would add one at a time and see if it behaves like you want. When you create like 10 different tracking profiles with different priorities they can interfere with each other, so less is often more.