I’ll put my plugin in debug and capture some logs to show you what I get. I’ll also see if I can craft up some tests to see if your tokens are working.
Sent from my iPhone using Tapatalk
Automatic OBD-II Debug getting location
Automatic OBD-II Debug getLocation C_400027b0f9a87963
Automatic OBD-II Location unknown, geocode failed: list index out of range
Automatic OBD-II Debug getLocation: unknown location
Automatic OBD-II Location unknown, geocode failed: list index out of range
rapamatic wrote:Just to clarify on my post above, which had a long string of the debug code, it looks like the errors are occuring around this part:
- Code: Select all
Automatic OBD-II Debug getting location
Automatic OBD-II Debug getLocation C_400027b0f9a87963
Automatic OBD-II Location unknown, geocode failed: list index out of range
Automatic OBD-II Debug getLocation: unknown location
And when I turn of debugging, I still get that one error message, about every second, in my log:
- Code: Select all
Automatic OBD-II Location unknown, geocode failed: list index out of range
Mar 1, 2018, 5:12:15 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Automatic OBD-II 2013 Audi S4 Premium Plus:ignition:on @ 2018-03-01 17:12:16
Trigger Car Started
Automatic OBD-II 2013 Audi S4 Premium Plus:notification:hard_accel @ 2018-03-01 17:12:19
Automatic OBD-II 2013 Audi S4 Premium Plus:notification:hard_accel @ 2018-03-01 17:12:20
Mar 1, 2018, 5:17:29 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Mar 1, 2018, 5:20:57 PM
Automatic OBD-II 2013 Audi S4 Premium Plus:notification:speeding @ 2018-03-01 17:20:57
Mar 1, 2018, 5:21:56 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Mar 1, 2018, 5:22:20 PM
Automatic OBD-II 2013 Audi S4 Premium Plus:notification:hard_accel @ 2018-03-01 17:22:20
Mar 1, 2018, 5:27:44 PM
Automatic OBD-II 2013 Audi S4 Premium Plus:notification:hard_accel @ 2018-03-01 17:27:44
Mar 1, 2018, 5:29:44 PM
Automatic OBD-II 2013 Audi S4 Premium Plus:notification:hard_accel @ 2018-03-01 17:29:44
Mar 1, 2018, 5:32:08 PM
Trigger Car Approaching Home
Automatic OBD-II 2013 Audi S4 Premium Plus En Route; At Shoen Road, 14 mins / 5.7 miles from home, ETA 06:45 PM
Mar 1, 2018, 5:36:47 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Automatic OBD-II 2018 Honda Odyssey EX-L:ignition:on @ 2018-03-01 17:36:48
Trigger Van Started
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Mar 1, 2018, 5:40:44 PM
Automatic OBD-II 2013 Audi S4 Premium Plus:ignition:off @ 2018-03-01 17:40:44
Trigger Car Parked
Mar 1, 2018, 5:41:51 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Automatic OBD-II 2013 Audi S4 Premium Plus:trip:finished @ 2018-03-01 17:41:52
Mar 1, 2018, 5:42:38 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Mar 1, 2018, 5:45:55 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Automatic OBD-II 2013 Audi S4 Premium Plus:ignition:on @ 2018-03-01 17:45:56
Trigger Car Started
Mar 1, 2018, 5:46:41 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Mar 1, 2018, 5:49:56 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Mar 1, 2018, 5:50:25 PM
Automatic OBD-II 2018 Honda Odyssey EX-L:notification:speeding @ 2018-03-01 17:50:25
Mar 1, 2018, 5:50:57 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Mar 1, 2018, 5:51:25 PM
Automatic OBD-II FYI - Exception caught getting vehicle info: 'latest_location'
Mar 1, 2018, 5:51:46 PM
Automatic OBD-II 2013 Audi S4 Premium Plus:notification:hard_accel @ 2018-03-01 17:51:46
Trigger Car Approaching Home
Automatic OBD-II 2013 Audi S4 Premium Plus En Route; At Moore Road, 4 mins / 1.7 miles from home, ETA 06:55 PM
Mar 1, 2018, 5:53:01 PM
Trigger Van Approaching Home
Automatic OBD-II 2018 Honda Odyssey EX-L En Route; At Pennsylvania Turnpike, 16 mins / 11.8 miles from home, ETA 07:06 PM
dgarozzo wrote:
As for rapamatic's problem with the geocode failed, I think that's a problem with your access to the Google API.
Can you try this URL (with your own googleMapsApiKey) and make sure you get a response?
https://maps.googleapis.com/maps/api/ge ... 66349&key={googleMapsApiKey}
rapamatic wrote:dgarozzo wrote:
As for rapamatic's problem with the geocode failed, I think that's a problem with your access to the Google API.
Can you try this URL (with your own googleMapsApiKey) and make sure you get a response?
https://maps.googleapis.com/maps/api/ge ... 66349&key={googleMapsApiKey}
Ok, that helped me solve the issue - the problem is that I had only turned on Geolocation (which I think is using cell towers and wifi signals to triangulate location - do we need this?) and Distance Matrix. I think you may need to update the instructions on the first page of this post to say that we also need to enable the geocoding API. Turning that on seems to have fixed my issues.
dgarozzo wrote:I don’t know how I got lucky and got one api key for both services. If you can’t figure out how to combine access into one key, I’ll have to update the plugin to be able to accept separate keys.
rapamatic wrote:dgarozzo wrote:I don’t know how I got lucky and got one api key for both services. If you can’t figure out how to combine access into one key, I’ll have to update the plugin to be able to accept separate keys.
As long as the two services are turned on for your project, it shouldn't matter which API key is used, and you really only need one enabled.
Go here: https://console.developers.google.com/apis/library and make sure that geocoding and distance matrix are enabled for your project. Then you can use any of the API keys (see them here: https://console.developers.google.com/apis/credentials) for your project to access any of those APIs...
DVDDave wrote:Ah, maybe when I obtained the Geocoding key, it enabled that api and the URL worked and fixed the errors. I just went back and checked the test URL with the other keys and they work without error. I guess the trick is that the Geocoding key needs to be enabled no matter which key is entered into the plugin configuration. dgarozzo probably had enabled it earlier. No need for multiple keys in the configuration.
rapamatic wrote:DVDDave wrote:Ah, maybe when I obtained the Geocoding key, it enabled that api and the URL worked and fixed the errors. I just went back and checked the test URL with the other keys and they work without error. I guess the trick is that the Geocoding key needs to be enabled no matter which key is entered into the plugin configuration. dgarozzo probably had enabled it earlier. No need for multiple keys in the configuration.
You can also go here: https://console.developers.google.com/apis/dashboard and see which APIs your project is using - looking at this, it doesn't look like it is using the geolocation API at all, at least for me I see: 895 requests on distance matrix, 41 on geocoding, and 0 on geolocation over the past 30 days.
dgarozzo wrote:I will double check my directions on the required Google API access. Very sorry about that!
Users browsing this forum: No registered users and 3 guests