It worked on another device, thank you.
The average person won't deploy Traccar, so IMO it's not a reasonable response or a position to hold.
Also, for apps development, especially those accessible from the network, Docker has been the standard since years now.
This whole "docker as 2nd/3rd priority" stance is really difficult to understand and IMO hurting the project's popularity.
Find Hub is a personal thing. Each end user would need to have a service deployed against their own Google account. So it's absolutely not the same thing as deploying Traccar server.
Congratulations!
One question: from which server version can I use Traccar Relay? Which Traccar server version is required? Is this APK already backward compatible?
It's not in the official release yet. You need to use the preview.
"Find Hub is a personal thing. Each end user would need to have a service deployed against their own Google account. So it's absolutely not the same thing as deploying Traccar server."
I don't see any way how that answer corresponds to the issue.
There are orders of magnitude more users of Traccar than people hosting Traccar. A single Traccar server can easily have hundreds or even thousands of users.
Thank you Anton,
I'm very interested in this, unfortunately right now I will not be able to try it out or test it: I also rely on a docker installation (and cannot afford to try and install traccar server differently on my production RPi)
I will wait until it makes it way to the official release.
Thanks again
Davide
Hey, thanks for the app.
Unfortunately I faced an issue - I'm able to login to my google account, the app properly communicating with the traccar server, and I succesfully registered the devices on the server, however devices location is being reported as lat: 0.00000, lon: 0.00000.
Any hints?
2026-05-02 10:10:24 INFO: [T56738908: osmand < 10.213.16.145] POST / HTTP/1.1\r\nContent-Type: application/x-www-form-urlencoded\r\nContent-Length: 202\r\nHost: 10.213.16.121:5055\r\nConnection: Keep-Alive\r\nAccept-Encoding: gzip\r\nUser-Agent: okhttp/5.3.0\r\n\r\nid=ffffffff-0000-ffff-ffff-ffffffffffff¬ificationToken=ffffffffffff%3ffffffffffffffff-fffffffffffffffff
2026-05-02 10:10:24 INFO: [T56738908: osmand > 10.213.16.145] HTTP/1.1 200 OK\r\ncontent-length: 0\r\n\r\n
2026-05-02 10:10:27 INFO: [T56738908] id: ffffffff-0000-ffff-ffff-ffffffffffff, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
This is not a location message. It just registered notification token.
Seems like an issue between the Traccar Relay app and Find Hub, then? I get no other notifications on the server side, except for INFO: [T3a682515] disconnected after ~ 5 minutes since launching the app.
I turned on notification permissions for the app, set battery optimization to unrestricted, left the android out of sleep mode. No changes despite tracker device status updates in Find Hub app properly.
Tested on both Pixel 7 Pro and Waydroid VM - same behavior.
Any hints for further debugging?
Did you request a location from Traccar side?
Of course not, this was the issue. Now it works fine, thank you.
I've however tried to request reporting initially, but due to some other misconfiguration nothing happened, so I have just assumed requests do not work for relay. Sorry.
May I ask why the Traccar Relay requires requests from the server side, while Traccar Client can report proper position automatically?
You can request periodic locations. But it is by design that we don't send frequent updates. I'm afraid that Google will ban this usage if it's abused. So the idea is that you request it either as needed or some low frequency, like once every few hours.
For technical people Docker is probably better, but for an average person the app is definitely an easier experience.