Automatic ODB II Issue

Hey there,

I’m assuming that its because I have a Raspberry Pi 2 without bluetooth, that it fails but I am getting the following error when I try to set up Automatic with Home Assistant. Here is the error message I receive:

16-09-11 12:56:06 homeassistant.components.device_tracker: Error setting up platform automatic
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/__init__.py", line 146, in setup_platform
    if not platform.setup_scanner(hass, p_config, tracker.see):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/automatic.py", line 56, in setup_scanner
    AutomaticDeviceScanner(config, see)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/automatic.py", line 84, in __init__
    self.scan_devices()
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/automatic.py", line 88, in scan_devices
    self._update_info()
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/__init__.py", line 296, in wrapper
    result = method(*args, **kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/automatic.py", line 161, in _update_info
    self.see(**kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/__init__.py", line 243, in see
    device.update_ha_state()
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 157, in update_ha_state
    attr = self.state_attributes or {}
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/device_tracker/__init__.py", line 341, in state_attributes
    for key, value in self.attributes:
ValueError: too many values to unpack (expected 2)

If it is because of the lack of Bluetooth, can I plug in a Bluetooth usb adapter or should I be asking for the newest Raspberry Pi for my birthday?

I haven’t upgraded yet but Automatic support is using the API; it doesn’t connect directly to the adapter so BT isn’t necessary to connect. Did you set up the app on the Automatic Dev site?

From what I can tell, I have the proper information filled. All you need from the developer page is the id and secret. I’m pretty sure its filled properly.

1 Like

Still on the fence about this update but if I take the plunge I’ll set it up and let you know. @Teagan42’s Automatic support is something I’ve been waiting for as I had a feature request in for it the first month I started, but I’m waiting to find out if some of the stuff reported as broken (Wink Siren/Light not showing up anymore, Group/Entity orders being screwed up) are isolated or wide spread.

I’m also curious if there is any special configuration required with the developer portal. I set up a developer account and obtained the login info. I’m super excited to try this out.

Just updated, same issue same error message. Time to get @Teagan42 involved. LOL

Edit: I updated the name of the thread as this isn’t so much an issue with configuring it as it is with an issue with the program. We’re using the configuration as it was documented.

Sounds good. Thanks for your help

If she doesn’t check in by tomorrow evening, I’ll see if I can contact her. I don’t want to annoy her too much but she does know I was looking forward to this. Automatic support was actually my first feature request!

I noticed there was an update to Home Assistant. Once it installed, my car showed up in my dashboard.

Cheers

1 Like

Upgrading now! Thanks; hadn’t checked my HASS yet.

Be aware that there may be a bug in polling; I’m looking into this with Teagan and will let you know what we find but if you don’t see any updates to your status in the card, don’t panic. LOL

I noticed that too. Today I took a trip in the car just to see it update… sadly it didn’t.

1 Like

Thanks, I’ll pass that on to her.

0.28.2 Has the polling fix.

2 Likes

Things look good so far. The issue seems to be fixed. I’ll test it more over the weekend. Thank you!

Same here, @Teagan42 - I’ll DM you tomorrow when I get to the client site and see if it updated the trip.

I’ve been getting the following. But am using the Automatic PRO. I didn’t think that would cause any problems since the Developer API seems to be the same. But @Teagan42 do you know if people have this working with Automatic Pro? If so, maybe this is something unique to me. BTW - just did a clean install of hass using AIO script, and this error persisted…

homeassistant.components.device_tracker.automatic: 404 Client Error: NOT FOUND for url:     
https://accounts.automatic.com/oauth/access_token/

I don’t see any entities (device tracker or otherwise) associated with my Automatic Pro and could use some help. I have a developer account setup at https://developer.automatic.com/ and have all the permissions I need checked, but still nojoy. Any advise would be greatly appreciated …

All I did was put the following into my device_tracker section:

- platform: automatic
    client_id: !secret automatic_client_id
    secret: !secret automatic_secret
    username: !secret automatic_user
    password: !secret automatic_PW

I have an original Automatic though, not the Pro. Not sure if this makes a difference.

Thanks for the quick reply …
I did that as well … but no luck. Do you know how HA authenticates? For my Plex and nest accounts HA created a plex.conf and nest.conf file which contain a (JSON?) token. I do not see an automatic.conf file - do you have one?