Geolocation Error with Google

Cheers,

Wondering if this is known in Traccar 5.3. I get "WARN: Geolocation network error - HTTP 404 Not Found". What could this be ?

2022-08-11 13:59:37  INFO: [Ta1cbdee9] connected
2022-08-11 13:59:41  INFO: [Ta1cbdee9: xexun2 < 185.40.61.71] faaf001400078622050551584160002eeba601002b1e62f4ef22180057820204ccce1e68b8f7d7b8c75d0ca05ba730d32d89a0d9a6e8df709eb27ca600000000faaf
2022-08-11 13:59:41  INFO: [Ta1cbdee9: xexun2 > 185.40.61.71] faaf0014000786220505515841600001fffe01faaf
2022-08-11 13:59:41  WARN: Geolocation network error - HTTP 404 Not Found - NotFoundException (...)
2022-08-11 13:59:41  WARN: Failed to store position - Data truncation: Incorrect datetime value: '1970-01-01 00:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:473 < DatabaseStorage:89 < DefaultDataHandler:45 < ...)
2022-08-11 13:59:41  INFO: [Ta1cbdee9] id: 862205055158416, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0

My traccar.xlm has this:

<entry key='geolocation.enable'>true</entry>
<entry key='geolocation.type'>google</entry>
<entry key='geolocation.key'>mykey...</entry>

It looks like Google API is returning the "not found" error.

The Google API URL is not in default.xml. Is it hardcoded somewhere ?

Yes, it is.

I see this is expected behavior if the post body is not included.
https://issuetracker.google.com/issues/236675599?pli=1
Does it mean that geolocation is not implemented in Xexun2 protocol ?

Geolocation implementation does not depend on a protocol. And I'm pretty sure the body is included.

Hi,

I'm getting the same error:

2023-10-26 XX:XX:XX  WARN: Geolocation network error - HTTP 404 Not Found - NotFoundException (...)

My configuration is

<entry key='geolocation.enable'>true</entry>
<entry key='geolocation.processInvalidPositions'>true</entry>
<entry key='geolocation.reuse'>true</entry>
<entry key='geolocation.type'>google</entry>
<entry key='geolocation.key'>xyz</entry>

I'm sure that the key is correct. I even renewed the key and tried it with the new one again.

What am I doing wrongly? How can I fix this error? On the Google platform I don't find anything that helps me.

Well, the error is coming from the provider.

Thank you, Anton.

Does anyone know how I can check on the Google platform what the problem is?
Indeed, I can see there an error rate of 100%.

I suspect the data might be invalid for some reason, so you should check the values in the database.

Yes, that seems to be the problem. The Megastek protocol needs an update...

Feel free to send a pull request or create a ticket with all the details.