Hello all,
Is anyone using the GPS Logger app on android to use as device tracker? I may be confusing something but it seems to require that the location is on in the settings in order for it to log anything. I was under the impression that with this app, I could get a rough location estimate based on the network towers. So I was hopping not to have to turn on the location all the time on my phone.
Can someone help me with this?
Cheers,
Lucian
Where did you get that impression?
In Android, location sharing is the general term for the different level of precision.
The app itself decides / requires the level it wants, being “coarse” (ie the network tower) or “precise” (the GPS)
I get it now. So basically because android doesn’t have an option to disable just the GPS I have to keep location on in general. I was hopping to avoid exacly that… Eh well such is life 
Thank you for the clarification
Typically a GPS logger will need gps, indeed 
The HA Android companion has more control on how location is sent to HA.
I know it is in the name right? 
I just read somewhere that this app had the opportunity to log some sort of passive location based on the cell towers so I imagined that this mode doesn’t require the GPS itself. Probably it doesn’t and it is just Android that bundled all these modes together in one button toggle.
As I said above, it’s in the hand of the app.
If the app actually supports this, then it won’t use the GPS, but you still need to give it permission to read your location generally.
@koying could you help me out with the setup for gps logger? i thought I did the settings correctly but it doesn’t seem to update my location properly. I could post the relevant settings here if you are ok with it.
I have the problem with the device tracker and the map that the integration correctly saves all 14 decimal places for the device as attributes. But in the map, the digits after the second decimal place are cut off, e.g. 6.12 instead of 6.12345678901234. As a result, the location is displayed completely incorrectly on the map (currently 15km off).
Does anyone have an idea how to fix this? The attributes in the developer console are still correct, the error apparently occurs later.