Reverse Geocode error

[claude]

Google reverse geocode is working fine here without an API key. What do you get if you put this url into a browser ?

https://maps.googleapis.com/maps/api...08,-1.11649607

I'm getting this, without an API key:

{
"error_message" : "You have exceeded your daily request quota for this API. We recommend registering for a key at the Google Developers Console: https://console.developers.google.com/apis/credentials?project=_",
"results" : [],
"status" : "OVER_QUERY_LIMIT"
}

[sooty]

I'm getting this, without an API key:

{
"error_message" : "You have exceeded your daily request quota for this API. We recommend registering for a key at the Google Developers Console: https://console.developers.google.com/apis/credentials?project=_",
"results" : [],
"status" : "OVER_QUERY_LIMIT"
}

There doesn't seem to be any pattern to when it does and doesn't work. Given the fact that an API key is not being used, it could be that the Google servers are too busy to serve the request or that they are somehow counting access by IP address or something. I really don't know.

The current plug-in beta "being tested now" has the ability to use other services for these lookups and a retry mechanism which should help to eliminate / reduce these issues.

Paul..

[claude]

There doesn't seem to be any pattern to when it does and doesn't work. Given the fact that an API key is not being used, it could be that the Google servers are too busy to serve the request or that they are somehow counting access by IP address or something. I really don't know...

I don't believe it is related to counting access by IP address. I tried repeatedly hitting 'reload page' on the URL you mentioned and, at moments, every 2nd call failed, then, at other times, the response was consistently positive.

So I believe your approach would succeed where you said "I could possibly put something in so if a lookup fails it will wait a couple of seconds and try again"

[sirmeili]

Just a note. I tried LocationIQ and it keeps reporting addresses on my street and my mom's street that aren't even there. My mom's street stops at 318 and it reports her address as 368. Mine it reports as 241 and I live at 209 (it could think i'm next door at 211, which is common, but still off).

I'm switching back to Google, but I was getting the issue described here where the reverse geolocation is failing. Unfortunately I can't test without driving around because the lat/long don't change and it makes testing hard. Hence I've added a feature request here to forcing an API run in the settings for "testing": https://forums.homeseer.com/showthread.php?t=192441

[sirmeili]

Paul (@sooty),

Can you tell me the url format of the reverse geocode with the api key? I still get this error and I can't figure out why. I want to try the url directly to try and debug it.