OK it seems this is because the original device holds the encryption keys for the tracker tags.
@sven
What I don't know yet is how to change the interval or stop the entire process I started with curl... :D Does anyone know?
You can re-send the cURL command with a new period. You can also use Traccar 6.8 with the built in support for commands, and there are three commands:
I don't yet know the format for the cURL for immediate reporting, or stop reporting. It will be in the python code.
OK for single reporting it is:
curl -X POST -H "Authorization: Bearer API_KEY" "http://localhost:5500/devices/DEVICE_ID/position-single"
And for stopping:
curl -X POST -H "Authorization: Bearer API_KEY" "http://localhost:5500/devices/DEVICE_ID/position-stop"
The "Periodic Reporting" command in Traccar 6.8.1 seems to be not sending the trailing "interval=XXX".
Extract from Wireshark:
POST /devices/68806064-0000-218f-b4c8-34c7e920e6d3/position-periodic HTTP/1.1
Accept: application/json
Authorization: Bearer FOOBLAH
User-Agent: Jersey/3.1.10 (HttpUrlConnection 21.0.7)
Host: 192.168.0.72:5500
Connection: keep-alive
When using cURL, this is the request format:
POST /devices/68806064-0000-218f-b4c8-34c7e920e6d3/position-periodic?interval=300 HTTP/1.1
Host: 192.168.0.72:5500
User-Agent: curl/8.5.0
Accept: */*
Authorization: Bearer FOOBLAH
Apologies, I should have added the error shown in the microservice:
192.168.0.83 - - [04/Aug/2025 12:03:38] "POST /devices/68806064-0000-218f-b4c8-34c7e920e6d3/position-periodic HTTP/1.1" 400 -
Adding some of my own experiences here, my test account (new google account) only had two devices, a Pixel 7 and a tracker. I kept receiving the "Your encryption data is locked on your device" message in Chrome until I first selected the Pixel 7 device. When I finally did that, the chrome browser refreshed with the info on that device, and after this point I could then get the location data for the tracker.