It does appear to be the RAT issue in the previous post. I was able to reproduce a 404 with the built-in Google Maps device locator integration.
As a workaround, you can use the technique in this Github. It's fully compatible with the device firmware for the official Google Maps device location integration, but instead of using the built-in integration, you create a custom webhook. The page shows how in the Creating a Webbhook section.
Using that technique I was able to successfully geolocate. Make sure you disable your Google Maps integration so you don't have both running at the same time.