I recently added the integration (it’s great!). I hope my notes help:
1. Create developer account (one time only)
Visit developer.automatic.com and create a new app
Name: HASSIO
URL: https://my_domain.duckdns.org
OAuth Redirect URL: https://my_domain.duckdns.org/api/automatic/callback (must be externally accessible)
Once the app is created, go back and manually change the event delivery to websocket.
Optional for live tracking:
After creating the app we have to manually request (and receive approval) to add scope:current_location. Click “Request Changes to Scopes”, and request this new scope. (takes ~1 day for approval). It’s advised to wait for this scope update before proceeding as [I think] we have to re-authenticate everything when scopes change.
2. Configure HASSIO
Within configuration.yaml add,
device_tracker:
- platform: automatic
client_id: !secret automatic_clientid
secret: !secret automatic_secret
current_location: true (false if we didn’t request the above, optional scope:current_location)
Restart HASSIO.
In the HASSIO Notification (bell) we’ll see “Click button to configure Automatic”, proceed to sign in.
Note:
Once authenticated an /config/.automatic directory will be created with a session-XXXX.json file.
Also, vehicle(s) will be added to /config/known_devices.yaml.
3. Testing
Vehicle(s) should automatically appear in the map tab, and/or add them as badges to the lovelace UI.
From developer.automatic.com you can simulate events (under event delivery), select “ignition off” and the first vehicle in your automatic file should jump around on your lovelace maps tap.
Optionally: If we requested scope:current_location then we can also send location updated events.
The configuration script for this intergration attempts to redirect to /states after authenticating to Automatic. I’ve submitted a PR this morning to change that to /lovelace.