Skip to content

Commit

Permalink
Update troubleshooting.markdown (home-assistant#14509)
Browse files Browse the repository at this point in the history
Slightly outdated reference to HA
  • Loading branch information
DubhAd authored Sep 16, 2020
1 parent 44e32e9 commit 18ff3be
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion source/_docs/configuration/troubleshooting.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ If you have incorrect entries in your configuration files you can use the config

One of the most common problems with Home Assistant is an invalid `configuration.yaml` or other configuration file.

- With Home Assistant you can use the [`ha` command](/hassio/commandline/#home-assistant): `ha core check`.
- With Home Assistant OS and Supervised you can use the [`ha` command](/hassio/commandline/#home-assistant): `ha core check`.
- You can test your configuration with Home Assistant Core using the command line with: `hass --script check_config`. If you need to provide the path for your configuration you can do this using the `-c` argument like this: `hass --script check_config -c /path/to/your/config/dir`.
- On Docker you can use `docker exec home-assistant python -m homeassistant --script check_config --config /config` - where `home-assistant` is the name of the container.
- The configuration files, including `configuration.yaml` must be UTF-8 encoded. If you see error like `'utf-8' codec can't decode byte`, edit the offending configuration and re-save it as UTF-8.
Expand Down

0 comments on commit 18ff3be

Please sign in to comment.