Update troubleshooting.markdown (#14509)

Slightly outdated reference to HA
This commit is contained in:
Dubh Ad 2020-09-16 21:00:03 +01:00 committed by GitHub
parent 44e32e9b01
commit 18ff3bea69
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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.