jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Convert to proper GFM

Browse source
This commit is contained in:
Paulus Schoutsen 2015-10-27 23:51:12 -07:00
parent 75bb815796
commit a522f15dd1
14 changed files with 303 additions and 399 deletions
Download patch file Download diff file Expand all files Collapse all files

71
source/getting-started/troubleshooting.markdown
View file

@ -12,60 +12,61 @@ footer: true
It can happen that you run into trouble while installing Home Assistant. This page is here to help
you figure out the most common problems.
**pip3: command not found**<br>
This utility should have been installed as part of the Python 3.4 installation. Check if Python 3.4
is installed by running `python3 --version`. If it is not installed,
[download it here](https://www.python.org/getit/).
**pip3: command not found**
This utility should have been installed as part of the Python 3.4 installation. Check if Python 3.4 is installed by running `python3 --version`. If it is not installed, [download it here](https://www.python.org/getit/).
If you are able to successfully run `python3 --version` but not `pip3`, run the following command instead
to install Home Assistant: `python3 -m pip install homeassistant`.
If you are able to successfully run `python3 --version` but not `pip3`, run the following command instead to install Home Assistant:
**No module named pip**<br>
[Pip](https://pip.pypa.io/en/stable/) should come bundled with the latest Python 3 but is ommitted
by some distributions. If you are unable to run `python3 -m pip --version` you can install `pip` by
[downloading the installer](https://bootstrap.pypa.io/get-pip.py) and run it with Python 3:
`python3 get-pip.py`.
```bash
$ python3 -m pip install homeassistant
```
**distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both**<br>
This is a known issue if you're on a Mac using Homebrew to install Python. Please follow
[these instructions](https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Homebrew-and-Python.md#note-on-pip-install---user)
to resolve it.
**No module named pip**
[Pip](https://pip.pypa.io/en/stable/) should come bundled with the latest Python 3 but is ommitted by some distributions. If you are unable to run `python3 -m pip --version` you can install `pip` by [downloading the installer](https://bootstrap.pypa.io/get-pip.py) and run it with Python 3:
**CentOS and Python 3**<br>
To run Python 3.x on [CentOS](https://www.centos.org/) or RHEL, [Software Collections](https://www.softwarecollections.org/en/scls/rhscl/rh-python34/) needs to be activated.</p>
```bash
$ python3 get-pip.py
```
**Run the development version**<br>
If you want to stay on top of the development of Home Assistant then you can upgrade to the dev branch using
`pip3 install --upgrade git+git://github.com/balloob/home-assistant.git@dev`. Keep in mind, that stable releases
of Home Assistant are published often.
**distutils.errors.DistutilsOptionError: must supply either home or prefix/exec-prefix -- not both**
This is a known issue if you're on a Mac using Homebrew to install Python. Please follow [these instructions](https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Homebrew-and-Python.md#note-on-pip-install---user) to resolve it.
**No access to the frontend**<br>
In newer Linux distributions (at least Fedora 22/CentOS 7) the access to a host is very limited.
This means that you can't access the Home Assistant Frontend that is running on a host outside of the
host machine. Windows and OSX machines may also have issues with this.
**CentOS and Python 3**
To run Python 3.x on [CentOS](https://www.centos.org/) or RHEL, [Software Collections](https://www.softwarecollections.org/en/scls/rhscl/rh-python34/) needs to be activated.
To fix this you will need to open your machine's firewall for TCP traffic over port 8123. The method
for doing this will vary depending on your operating system and the firewall you have installed.
Below are some suggestions to try. Google is your friend here.
**No access to the frontend**
In newer Linux distributions (at least Fedora 22/CentOS 7) the access to a host is very limited. This means that you can't access the Home Assistant Frontend that is running on a host outside of the host machine. Windows and OSX machines may also have issues with this.
[Windows instructions](http://windows.microsoft.com/en-us/windows/open-port-windows-firewall#1TC=windows-7)<br>
To fix this you will need to open your machine's firewall for TCP traffic over port 8123. The method for doing this will vary depending on your operating system and the firewall you have installed. Below are some suggestions to try. Google is your friend here.
[Windows instructions](http://windows.microsoft.com/en-us/windows/open-port-windows-firewall#1TC=windows-7)
[Mac OSX instructions](https://support.apple.com/en-us/HT201642)
For firewalld systems (Fedora, RHEL, etc.):
```bash
sudo firewall-cmd --permanent --add-port=8123/tcp
sudo firewall-cmd --reload
$ sudo firewall-cmd --permanent --add-port=8123/tcp
$ sudo firewall-cmd --reload
```
For UFW systems (Ubuntu, Debian, Raspbian, etc.):
```bash
sudo ufw allow 8123/tcp
$ sudo ufw allow 8123/tcp
```
For iptables systems (usually the default):
```bash
iptables -I INPUT -p tcp --dport 8123 -j ACCEPT
iptables-save > /etc/network/iptables.rules # your rules may be saved elsewhere
$ iptables -I INPUT -p tcp --dport 8123 -j ACCEPT
$ iptables-save > /etc/network/iptables.rules # your rules may be saved elsewhere
```
###[&laquo; Back to Getting Started](/getting-started/index/)
**Run the development version**
If you want to stay on top of the development of Home Assistant then you can upgrade to the dev branch. This can result in an unstable system, loss of data etc etc.
```bash
$ pip3 install --upgrade git+git://github.com/balloob/home-assistant.git@dev
```
### [&laquo; Back to Getting Started](/getting-started/index/)