FAQ


This is a community curated list of frequently asked questions (FAQ) about the installation, setup, and usage of Home Assistant. If you want to get details about a term, please check the glossary.

Common

Python 2

Python 2.x에 대한 지원은 없을것입니다. Python 2는 2020년에 EOL되며, 2015년부터 은퇴가 예정된 릴리즈를 지원하는 것은 의미가 없습니다.

Releases

The current release cycle is three weeks. This allows for two weeks of development time and 1 week of beta testing and fixing. Releases usually occur on a Wednesday. There is no fixed time of day when the release will happen because that depends on the person who is finishing the release, it could therefore be Tuesday or Thursday depending on your timezone when its available for you. If there was no announcement made in the previous release notes or on another communication channel then the release will happen.

Beta’s are normally released on the 2nd Wednesday after the last major release. Please subscribe to the Beta Channel on the Home Assistant Discord server for help running beta versions. When a beta release is in progress, the release notes for it can be found under Beta Release Notes.

The release schedule is published in the upcoming events calender on the Home Assistant Developers website.

Configuration

My integration does not show up

When an integration does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the home-assistant.log file and see if there are any errors related to your integration you are trying to set up.

If you have incorrect entries in your configuration files you can use the check_config script to assist in identifying them: hass --script check_config.

Why are you using YAML for the configuration file?

And not JSON or XML for the configuration file? Because YAML can be written by hand, you don’t have to care about commas or tag and it’s a superset of JSON.

Documentation

Documentation tools

Why are you not using tools X for the documentation? Because the current solution works for us and we see no additional value in using a separate publishing platform.

Missing Documentation

Home Assistant is a FAST moving open source project. This means occasionally the official documentation will not be 100% current or complete. Since this is an open source volunteer project, we would encourage anyone who finds gaps in the documentation to click the edit this page on Github link in the top right and submit any corrections/enhancements they may find useful.

In the absence of information, many users find it beneficial to look at other people’s configurations to find examples of what they want to accomplish in their own configurations. The easiest way to find these configurations is through this Github search.

Installation

Home Assistant vs. Hass.io

Home Assistant is a Python program, in simple words. It can be run on various operating systems and provide the ability to track, control and automate your devices. When people talking about Home Assistant they usually refer to a standalone installation method.

Hass.io is a combination of Home Assistant and tools which allows one to run it easily on a Raspberry Pi and other platforms without setting up an operating system first. Hass.io is an all-in one-solution and has a management user interface that can be used from the Home Assistant frontend. This interface is not present in a standalone setup of Home Assistant.

Be aware that add-ons are only available in Hass.io, due to the way Hass.io is installed.

No module named pip

Pip should come bundled with the latest Python 3 but is omitted by some distributions. If you are unable to run python3 -m pip --version you can install pip by downloading the installer and running it with Python 3:

$ python3 get-pip.py

distutils.errors.DistutilsOptionError

The problem which leads to distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both is a known issue if you’re on a Mac using Homebrew to install Python. Please follow these instructions to resolve it.

libyaml is not found or a compiler error

On a Debian system, install the Python 3 YAML library by sudo apt-get install python3-yaml.

pip3: command not found

This utility should have been installed as part of the Python 3 installation. Check if Python 3 is installed by running python3 --version. If it is not installed, download it here.

If you are able to successfully run python3 --version but not pip3, install Home Assistant by running the following command instead:

$ python3 -m pip install homeassistant

On a Debian system, you can also install python3 by sudo apt-get install python3 and pip3 by sudo apt-get install python3-pip.

If you run into errors during installation, check that you’ve installed all the necessary prerequisite packages, which include python3-dev, libffi-dev, and libssl-dev. On a Debian-based system, you can install these via apt-get:

$ sudo apt-get install python3-dev libffi-dev libssl-dev

Usage

Connection error

It can happen that you get a traceback that notify you about connection issues while running Home Assistant. Eg.

ConnectionRefusedError: [Errno 111] Connection refused

The chance is very high that this is not a bug but an issue with the service/daemon itself. Check your network (DNS, DHCP, uplink, etc.) first and make sure that Home Assistant and the service are poperly configured. Keep in mind that webservices can be down.

Dependencies

The dependencies which are used by Home Assistant are stored in the folder deps of the configuration folder directory. After an upgrade the dependences will be upgraded as well.

Problems with dependencies

Almost all integrations have external dependencies to communicate with your devices and services. Sometimes Home Assistant is unable to install the necessary dependencies. If this is the case, it should show up in home-assistant.log.

The first step is trying to restart Home Assistant and see if the problem persists. If it does, look at the log to see what the error is. If you can’t figure it out, please report it so we can investigate what is going on.

문자 ’ ’를 찾았으며, 이 문자로는 어떠한 토큰을 시작할 수 없습니다.

이 에러는 당신이 스페이스 2칸 대신 탭을 사용했음을 의미합니다. 탭 대신 스페이스를 사용하십시오.

업그레이드한 뒤로, 로그인이 안됩니다

새로운 버전으로 업그레이드하고, 당신의 브라우저는 “데이터 로딩” 로그인 화면에서 멈출수 있습니다. 윈도우/탭을 닫고 브라우저 설정에 들어가 해당 URL의 쿠키를 제거하십시오. 그러면 다시 로그인할 수 있고, 잘 작동할 겁니다.

안드로이드 Chrome:

Chrome -> 설정 -> 사이트 설정 -> 저장소 -> 당신의 홈 어시스턴트 URL 검색 -> “삭제 및 재설정”

프론트엔드가 이상하게 행동합니다.

윈도우나 탭을 닫고 캐시를 삭제하십시오. 프론트엔드는 적극적으로 캐싱하고, 캐시를 지우면 다음에 접속할때 다시 로드됩니다.