I think mine did too but I flashed my phone and haven’t yet reconnected with my Automatic 1 so I’m not sure if this is an issue or not until I get things back to normal again. I am getting errors trying to initialize the automatic component, but again - not sure if this is related to my disconnections at the moment.
Well, connected up with Automatic but doesn’t seem to have solved my issue. Also showing 25 instead of 1/25 like @Coolie1101.
Also noticing the URL is http://localhost and the OAUTH is http://localhost/redirect.
Were those the original values? Are they correct? I can’t remember as I set it up so long ago.
EDIT: Went back to way up this thread and those are the correct URLs so everything over at Automatic is the way it always was.
Has anyone opened an issue yet?
OK there is an open issue for this that jamieshaw put in. Please add your findings to this issue so that devs can see the impact. Otherwise it’s just two random users as far as anyone knows (I put in my findings).
I have a single Automatic PRO adapter which was WORKING fine as one of my device_trackers at v0.49. First NOTICED it was broke after upgrading to 0.50.2
HASS Config:
device_tracker:
- platform: owntracks
- platform: automatic
client_id: !secret automatic_client_id
secret: !secret automatic_secret
username: !secret automatic_username
password: !secret automatic_password
HASS Log:
ERROR (MainThread) [homeassistant.components.device_tracker.automatic] err_invalid_client
ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform automatic
The Automatic Developer site shows Maximum Connections 25 just like @Coolie1101 and @rpitera. Last time I checked on March 4, 2017 it showed 1/25
From the Automatic Labs Dev Site:
App Mode: Development
Maximum Users: 25
Client Type: Confidential/Web
URL: http://localhost
OAuth Redirect URL: http://localhost/redirect
Available Scopes:
scope:public Access to public information about user.
scope:user:profile Access to user’s profile.
scope:location Access to historical location.
scope:current_location Access heartbeat location updates in realtime during a drive.
scope:vehicle:profile Access to vehicle information.
scope:vehicle:events Access to vehicle events details.
scope:trip Access to trips that are visible to a user.
scope:behavior Access to user’s driving behavior summary stats.
Guys, please add your comments to the issue in HA I referenced above so the devs are aware of the extent.
Thanks.
1 Like
Was looking on the API page and it says that OAuth2 is required. I think we are just using OAuth.
Nope mine shows 25 too. But I see someone is working on fix
It should show 1/25 when HASS is connected.
I thought that I had done something wrong, my Automatic has been showing “Away” for quite some time now. Glad to see that someone is working on a fix.
No fix for this yet ? any updates findings ?
Will be fixed in HA .52 release update.
1 Like
Great news thanks !!!
I am very excited for this.
Justed wanted to say thanks to @jamieshaw for updating this component. I had no problem with OAuth2 and all is well within HA.
Developer Web Site Observations:
Maximum User = 25 even after HA is connected (not 1/25 as it was in the past)
The Simulate a Websocket Event function fails for me as well, but this does not appear to affect the function of Home Assistant (Websocket is required for Heartbeat functionality and that is working just fine in HA)
Anybody having issues entering the OAuth redirect url in the Automatic Dev panel? I keep entering the url and hitting save but the URL wont stick.
Alternatively, updating the url field saves just fine.
I did not have an issue. Per Automatic’s documentation: “…all API requests must be made over HTTPS”
Could that be your issue?
Ref:
Same issue here.
Are you saying the OAuth Redirect URL shoud be https:// instead of http:// acording to the documentatin here?
All I know is I used my HTTPS address and had no issue.
I suggest you enter HTTPS at the site as a test to see if the web interface allows you to save the URL. if it does, we’d know for sure …