From a544cf45dd47e15b9427807895743e150e74bf4a Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Wed, 9 Oct 2019 22:28:41 +0200 Subject: [PATCH] Update troubleshooting.markdown (#10674) --- source/_docs/configuration/troubleshooting.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_docs/configuration/troubleshooting.markdown b/source/_docs/configuration/troubleshooting.markdown index 392794099dc..6c0b22d35cd 100644 --- a/source/_docs/configuration/troubleshooting.markdown +++ b/source/_docs/configuration/troubleshooting.markdown @@ -18,11 +18,12 @@ If you have incorrect entries in your configuration files you can use the [`chec #### Problems with the configuration -One of the most common problems with Home Assistant is an invalid `configuration.yaml` file. +One of the most common problems with Home Assistant is an invalid `configuration.yaml` or other configuration file. - You can test your configuration using the command line with: `hass --script check_config`. - On Hass.io you can use the [hassio command](/hassio/commandline/#home-assistant): `hassio homeassistant check`. - On Docker you can use `docker exec home-assistant python -m homeassistant --script check_config --config /config` - where `homeassistant` 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. - You can verify your configuration's yaml structure using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/). - To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).