Google Find Hub devices in Traccar
Hi Anton,
I've successfully managed to authenticate and run your project on a Linux VPS. Since I needed to generate the secrets.json, I set up a VNC interface to handle the Google login flow. Everything works perfectly after that, and I can sync the tags (including v12 E2EE keys).
However, I'm facing a major issue: the session is being dropped by Google in less than 24 hours. The microservice starts failing with a KeyError: 'Auth' because the aas_token seems to expire or get invalidated, requiring a full manual login via the UI again.
Do you know if there is a way to make the session more persistent or if Google has recently changed how they handle these emulated Android tokens? Any advice on how to avoid re-authenticating every day would be greatly appreciated.
It sounds like Google is invalidating the session. Maybe it detects suspicious behavior or something.
i've been running scripts to do this for 6months and never been invalidated. Maybe your requests were too frequent?
I have the code running and a bluetooth tag updating in traccar. However it apears as if there is no destinction between when traccar was updated from the microservice, and when the position data from google was updated.
Is this correctly understood, that in traccar, you cant see when the position was actually updated by google?
I can see this detail in the find hub app, in android, so i would assume this is exposed by google also?
Its hard to utilize the data, if you dont know how stale it is.
What do you mean by no distinction? The fix time should be the actual location time. And server time should server receiving time. Same as we do for all other devices.
what i do is have the coordinate not update traccar if it's identical to a previous one.
Enable filtering. Again, that's not something specific to the Find Hub.
You can also run the official one in Docker.