So it looks like I've been getting exceptions in my logs, too, but not the same ones that you guys are getting:
- Code: Select all
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
As for the 'latest_location' exception, it looks like I just screwed it up (or Automatic changed their API response?). I dunno. That field doesn't even exist int he API response for vehicle. It looks like I was trying to figure out how I can get location data via the API instead of the SocketIO connection.
The plugin is only supposed to poll for API info when automaticLocationApproved hasn't been set yet. I will look into this, but it's possible that my config page isn't properly saving the value of the checkbox or something. I'll try to fix that this weekend.
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}