So, what’s the status on this? Not working with Pro? I have two Pro’s, tried cycling through stuff as noted - no dice. That said, I did at one time see two devices pop up and show “fuel status”, then the next Hass restart, they disappeared.
2017-05-21 16:54:33 ERROR (MainThread) [homeassistant.components.device_tracker automatic]
2017-05-21 16:54:33 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform automaticYes it continues to work just fine with my Automatic PRO. I’ve had success on both my now obsolete 64bit Windows 7 installation and my current HASSbian installation.
Stops working after Upgrade to 0.45.1
Show’s Invalid Config.
Is that a PRO or a standard? I have a standard and running 0.45.1 and I’m detecting properly and showing my correct data.
It’s the Pro version.
Worked fine until upgrade.
I’m running 0.45.1 with a PRO adapter without issue.
Were you using it prior to 0.45.1?
Yes, it’s been working since March 4th, and I always keep my HASS installation updated to the latest version.
Same here, no problem at all
Currently I’m getting these errors in the HA log:
ERROR (MainThread) [homeassistant.components.device_tracker.automatic]
ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform automatic
I have the automatic PRO model and I’m running HA 0.48.1 on a RPI 3. I didn’t have this setup on a prior version before. I followed the instructions on Automatic component page.
From what I can tell it doesn’t look like HA is able to authenticate with the Automatic API service, I was able to connect using a custom python script on my local environment so I know my client id and secret and credentials are working. Suggestions?
I was able to get this working after upgrading HA to version 0.49.0.
How did you get it working? I have two Automatic PROS that were working fine up until 0.48.1. They still do not work on 0.49.
Same issue here, on latest 0.49, never worked for me, except the very first time I tried, then it errored out the next restart of Hass and has never worked since. Tried revoking authentications and resetting secrets, but no luck. Two automatic PROS as well.
Seems like it’s not working for people with multiple PROs?
If I try specifying either vehicle in my account (to force just one vehicle), this happens:
2017-07-17 22:46:40 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 179, in _step
result = coro.send(None)
File "/usr/src/app/homeassistant/components/device_tracker/automatic.py", line 209, in load_vehicle
yield from self.async_see(**kwargs)
TypeError: async_see() argument after ** must be a mapping, not NoneType
2017-07-17 22:46:40 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 179, in _step
result = coro.send(None)
File "/usr/src/app/homeassistant/components/device_tracker/automatic.py", line 209, in load_vehicle
yield from self.async_see(**kwargs)
TypeError: async_see() argument after ** must be a mapping, not NoneTypeOkay, I guess it’s not working for me anymore either. It looked like it was initially once I upgraded HA the first time, but it’s now throwing errors:
ERROR (MainThread) [homeassistant.components.device_tracker.automatic]
ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform automatic
I’ll brush up on my python skills and see if i can help debug the issue more. In the meantime it looks like there is a mqtt-automatic-bridge that could be leveraged if you have a MQTT server installed and configured with HA. (https://www.npmjs.com/package/mqtt-automatic-bridge)
I’m seeing the following error today, but the tracker is still updating and showing the correct current location on 0.49.0.
2017-07-25 05:33:39 ERROR (MainThread) [homeassistant.components.device_tracker.automatic] Websocket error detected. Connection closed.
2017-07-25 05:33:45 ERROR (MainThread) [homeassistant.components.device_tracker.automatic] Error opening websocket connection:
Hi
I’m having the following problem after updating to 0.50.2
Using 4 Automatic PRO gives me the followin error :
2017-08-02 11:26:15 ERROR (MainThread) [homeassistant.components.device_tracker.automatic] err_invalid_client
2017-08-02 11:26:15 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform automatic
2017-08-02 11:26:15 ERROR (MainThread) [homeassistant.components.device_tracker.automatic] err_invalid_client
2017-08-02 11:26:15 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform automaticSame here with 2 Pro’s on 0.50.2
2017-08-02 13:53:42 ERROR (MainThread) [homeassistant.components.device_tracker.automatic] err_invalid_client
2017-08-02 13:53:42 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform automaticI am getting the same error too, it was working perfectly on 0.47.1 and when i upgraded ha to 0.50.2 it stop working
2017-08-02 15:37:51 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform automaticSince there are enough users to verify it’s not an isolated incident, it would be a good idea to open and issue, link it here and let those effected users add their observations and data to it.
That way a dev can get involved once they are aware of the extent.