Google Find Hub devices in Traccar
I am not sure you need to make it on the same machine, but from what I have seen, it needs to be the same OS and IP.
I tried to rebuild docker after I added a new authentication file, but it doesn't work.
Microserver Docker Log reports that secret.json is end-to-end encrypted.
find-hub | \[FCMReceiver\] Listening for notifications. This can take a few seconds...
find-hub | `\[SharedKeyRetrieval\] You need to log in again to access end-to-end encrypted keys to decrypt location reports.`
find-hub | > This script will now open Google Chrome on your device.
find-hub | > Make that you allow Python (or PyCharm) to control Chrome (macOS only).
find-hub |
find-hub | \[2025-12-04 17:36:39,338\] ERROR in app: Exception on /devices/`mydeviceID`/position-single \[POST\]
All ideas are appreciated :D
Thank you
Fede
@renaud: ok, I can try later from the same IP, but I haven't ideas how to use the same OS because Docker run under Unraid OS.
I think linux/linux should be OK, but linux/BSD definitely doesn't work. But the public IP seems to also be important.
@renaud:
I generate a new secret.json using Lubuntu tablet in my internal network (the same public IP of the server), then i upload it in Unraid Docker.
It doesn't work.
Hello everybody!!
I read a lot of documentation, and now it's working finally!!!
The authentication error was because after the first authentication, you must recall service and require a device position. With this step, google requires a new authentication. No need to be under the same public IP.
Thank you all for support!
Hello,
is it possible to create a script and autorun it on docker startup (with cronjob)?
Every night my system stops containers, updates it and restarts everything. So in the morning I need to manually send commands to start acquisition from find-hub.
thanks
Hello, I'm using your google-find-hub-sync project and I'm facing a synchronization problem when running it on a Linux VPS.
Scenario:
I performed full authentication on Windows (where Chrome opens for OAuth) and the server works perfectly, sending the positions to Traccar.
I copied the identical folder to the Linux VPS (Ubuntu).
On the VPS, the server starts, the FCMReliver stays in "Listening" mode, and the tags even appear as "Online" in the log.
Problem: Despite being online, the position doesn't update and the console displays the following decryption error: Failed to decrypt E2EE data. This tracker was encrypted with owner key version 9, but the current owner key version is 12.
Even with write permissions enabled on the Auth and KeyBackup folders, the script on Linux seems unable to download or update to Owner Key Version 12, remaining "stuck" on version 9. Since the login was done via Windows, is there any way to export the correct key or force the VPS to request the encryption PIN to generate the new key?
I think you have to login from the same system.
Hi Anton,
Regarding your previous comment about logging in on the same system:
I am trying to run the microservice on a Headless Linux Server (VPS). However, when I try to authenticate, the script attempts to launch Selenium/Chrome to perform the login flow, which obviously fails because there is no GUI (Graphic Interface).
I have two specific questions for you:
Is there any way to perform the login/authentication directly via terminal (CLI) using an App Password or by passing credentials manually, without relying on Selenium?
Was this microservice specifically built to only work on operating systems with a GUI, or is there a "headless" mode for server environments?
I already have the tokens and the Owner Key (v9) from my Windows machine, but when I move them to the Linux VPS, I get the Authentication Failed: wrong_secret error even after adjusting the android_id.
Thanks for the help.
You can't login via terminal. This microservice was built with whatever workaround we can get away with. Google doesn't provide any official way to access this data.
Hello Anton, there is a way to send scheduled saved commands?
I don't think we have scheduling for commands currently.
Somehow I missed this post. I actually just built the same tool but mine is meant to run in docker. I run it on a truenas instance. It also lets you run it entirely headless (though you need to generate the secrets on a headed machine first)
I'm not sure.