Configuration
Go Automate reads its configuration from a single YAML file. It needs your Home Assistant URL and a long-lived access token to connect.
Config file location
Section titled “Config file location”The config file is config.yml inside the Go Automate config directory. The directory is
resolved in this order:
$XDG_CONFIG_HOME/go-automateifXDG_CONFIG_HOMEis set.~/.config/go-automateotherwise.
So on a typical Linux setup the file lives at ~/.config/go-automate/config.yml.
Config format
Section titled “Config format”homeassistant: url: http://homeassistant.local:8123 token: your-long-lived-access-tokenhomeassistant.url— the base URL of your Home Assistant instance. Defaults tohttp://homeassistant.local:8123. Usehttps://for TLS; Go Automate connects overws://orwss://automatically based on the scheme.homeassistant.token— a Home Assistant long-lived access token.
First-run setup
Section titled “First-run setup”If the token is empty when you start Go Automate in an interactive terminal, it walks you through a short setup form and writes the file for you.
-
Run the app in a terminal:
Terminal window go-automate -
Enter your Home Assistant URL and long-lived access token when prompted.
-
Go Automate saves
config.ymland continues.
Creating a long-lived access token
Section titled “Creating a long-lived access token”- In Home Assistant, open your profile (click your username in the sidebar).
- Go to the Security tab and scroll to Long-lived access tokens.
- Select Create token, give it a name such as
go-automate, and copy the value.
The token is shown only once, so paste it straight into your config or the setup form.
Next steps
Section titled “Next steps”- Run the bridge so watchers and status bars stay cheap on the network.
- Start controlling Home Assistant.