mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-10 02:46:53 +00:00
AIO installer is deprecated (#4080)
* AIO installer is deprecated * Remove AiO
This commit is contained in:
c727
Fabian Affolter
parent
14c7ca6dff
commit
2c0837926b
@ -8,124 +8,6 @@ footer: true
|
||||
redirect_from: /getting-started/installation-raspberry-pi-all-in-one/
|
||||
---
|
||||
|
||||
The [Raspberry Pi All-In-One Installer](https://github.com/home-assistant/fabric-home-assistant) deploys a complete Home Assistant server including support for MQTT with websockets, Z-Wave, and the OpenZWave Control Panel.
|
||||
|
||||
<p class='note'>
|
||||
Please remember to ensure you're using an [appropriate power supply](https://www.raspberrypi.org/help/faqs/#powerReqs) with your Pi. Mobile chargers may not be suitable, since some are designed to only provide the full power with that manufacturer's handsets.
|
||||
</p>
|
||||
|
||||
The only requirement is that you have a Raspberry Pi with a fresh installation of [Raspbian](https://www.raspberrypi.org/downloads/raspbian/) Jessie (Stretch is not supported at this time) connected to your network.
|
||||
|
||||
<p class='note'>
|
||||
Note that as of 2016-11-30 SSH is disabled by default in the official Raspbian images. Adding an empty file called `ssh` to `/boot/` on the FAT32 partition will enable it. More information is on the Raspberry Pi Foundation [Blog](https://www.raspberrypi.org/blog/page/2/?fish#a-security-update-for-raspbian-pixel).
|
||||
</p>
|
||||
|
||||
Irrespective of whether you use SSH to connect to the Pi from another computer or not, you need SSH to install Home Assistant. So go ahead and enable SSH.
|
||||
|
||||
* Login to Raspberry Pi. For example with `ssh pi@your_raspberry_pi_ip`
|
||||
* Run the following command:
|
||||
|
||||
<p class='note warning'>
|
||||
This command is a one-liner and not run as sudo.
|
||||
The All-In-One Installer is deprecated, you will have problems updating Home Assistant in 2018. Please move to another [installation method](https://home-assistant.io/getting-started/).
|
||||
</p>
|
||||
|
||||
```bash
|
||||
$ curl -O https://raw.githubusercontent.com/home-assistant/fabric-home-assistant/master/hass_rpi_installer.sh && sudo chown pi:pi hass_rpi_installer.sh && bash hass_rpi_installer.sh
|
||||
```
|
||||
|
||||
Installation will take approx. 1-2 hours depending on the Raspberry Pi model the installer is being run against. The installer will identitfy what Raspberry Pi hardware revision you are using and adjust commands accordingly. A complete log of the install is located at: `/home/pi/fabric-home-assistant/installation_report.txt` The installer has been updated to simply log any errors encountered, but resume installing. Please consult the "installation report" if your install encountered issues.
|
||||
|
||||
[BRUH automation](http://www.bruhautomation.com) has created [a tutorial video](https://www.youtube.com/watch?v=VGl3KTrYo6s) explaining how to install Raspbian on your Raspberry Pi and install Home Assistant using the All-In-One Installer.
|
||||
|
||||
Once rebooted, your Raspberry Pi will be up and running with Home Assistant. You can access it at [http://your_raspberry_pi_ip:8123](http://your_raspberry_pi_ip:8123).
|
||||
|
||||
The Home Assistant configuration is located at `/home/homeassistant/.homeassistant` (or `/home/hass/.homeassistant` if installed prior to December 2016). The [virtualenv](https://virtualenv.pypa.io/en/latest/) with the Home Assistant installation is located at `/srv/homeassistant/homeassistant_venv`. As part of the secure installation, a new user (**homeassistant**) is added to your Raspberry Pi to run Home Assistant. This is a system account and does not have login or other abilities by design. When editing your `configuration.yaml` files, you will need to run the commands with `sudo` or by switching user.
|
||||
|
||||
<p class='note note'>
|
||||
*Windows users*: Setting up WinSCP to allow this seemlessly is at the end of this page.
|
||||
</p>
|
||||
|
||||
By default, installation makes use of a Python Virtualenv. If you wish to not follow this recommendation, you may add the flag `-n` to the end of the install command specified above.
|
||||
|
||||
The All-In-One Installer script will do the following automatically:
|
||||
|
||||
* Create all needed directories
|
||||
* Create needed service accounts
|
||||
* Install OS and Python dependencies
|
||||
* Setup a python virtualenv to run Home Assistant and components inside.
|
||||
* Run as `homeassistant` service account
|
||||
* Install Home Assistant in a virtualenv
|
||||
* Install Mosquitto with websocket support running on ports 1883 and 9001
|
||||
* Build and Install Python-openzwave in the Home Assistant virtualenv
|
||||
* Build OpenZWave Control Panel in `/srv/homeassistant/src/open-zwave-control-panel`
|
||||
* Add Home Assistant to systemd services to start at boot
|
||||
|
||||
### {% linkable_title Upgrading %}
|
||||
|
||||
To upgrade the All-In-One setup manually:
|
||||
|
||||
* Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip`
|
||||
* Change to homeassistant user `sudo su -s /bin/bash homeassistant`
|
||||
* Change to virtual environment `source /srv/homeassistant/homeassistant_venv/bin/activate`
|
||||
* Update Home Assistant `pip3 install --upgrade homeassistant`
|
||||
* Type `exit` to logout the hass user and return to the `pi` user.
|
||||
|
||||
<div class='note note'>
|
||||
**If you deployed Home Assistant via the AiO installer prior to December 2016**
|
||||
* Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip`
|
||||
* Change to homeassistant user `sudo su -s /bin/bash hass`
|
||||
* Change to virtual environment `source /srv/hass/hass_venv/bin/activate`
|
||||
* Update Home Assistant `pip3 install --upgrade homeassistant`
|
||||
* Type `exit` to logout the hass user and return to the `pi` user.
|
||||
</div>
|
||||
|
||||
After upgrading, you can restart Home Assistant a few different ways:
|
||||
|
||||
* Restarting the Raspberry Pi `sudo reboot`
|
||||
* Restarting the Home-Assistant Service `sudo systemctl restart home-assistant.service`
|
||||
|
||||
### {% linkable_title To change the MQTT default password %}
|
||||
|
||||
* Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip`
|
||||
* Change password `sudo mosquitto_passwd /etc/mosquitto/pwfile pi`
|
||||
* Restart mosquitto `sudo systemctl restart mosquitto.service`
|
||||
* Be sure to update your `configuration.yaml` to reflect the new password.
|
||||
|
||||
### {% linkable_title Using the OZWCP web application %}
|
||||
|
||||
To launch the OpenZWave Control Panel (OZWCP) web application:
|
||||
|
||||
* Make sure Home Assistant is not running! So stop that first
|
||||
* Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip`
|
||||
* Change to the OZWCP directory `cd /srv/homeassistant/src/open-zwave-control-panel/`
|
||||
* Launch the control panel `sudo ./ozwcp -p 8888`
|
||||
* Open a web browser to `http://your_pi_ip:8888`
|
||||
* Specify your Z-Wave controller, for example `/dev/ttyACM0` and hit initialize
|
||||
|
||||
<p class='note warning'>
|
||||
If OZWCP is running really slow verify that your not running Home Assistant or have another page running OZWCP open or strange errors might occur.
|
||||
</p>
|
||||
|
||||
<div class='note note'>
|
||||
**If you deployed Home Assistant via the AiO installer prior to December 2016**
|
||||
* Make sure Home Assistant is not running! So stop that first
|
||||
* Login to Raspberry Pi `ssh pi@your_raspberry_pi_ip`
|
||||
* Change to the OZWCP directory `cd /srv/hass/src/open-zwave-control-panel/`
|
||||
* Launch the control panel `sudo ./ozwcp -p 8888`
|
||||
* Open a web browser to `http://your_pi_ip:8888`
|
||||
* Specify your Z-Wave controller, for example `/dev/ttyACM0` and hit initialize
|
||||
</div>
|
||||
|
||||
<p class='note warning'>
|
||||
Don't check the USB box regardless of using a USB based device.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Using the GPIOs %}
|
||||
|
||||
The (**homeassistant**) user is added to the GPIO group as part of the install now.
|
||||
|
||||
### {% linkable_title WinSCP %}
|
||||
|
||||
If you are Windows users who is using [WinSCP](https://winscp.net/), please note that after running the installer, you will need to modify settings allowing you to "switch users" to edit your configuration files.
|
||||
|
||||
First create a new session on WinSCP using Protocol **SCP** pointing to your Pi IP address and port 22 and then modify the needed setting by click on **Advanced...** -> **Environment** -> **SCP/Shell** -> **Shell** and selecting `sudo su -`.
|
||||
|
||||
@ -11,7 +11,7 @@ redirect_from: /getting-started/updating/
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/common-tasks/#update-home-assistant), [Raspberry Pi All-In-One Installer](/docs/installation/raspberry-pi-all-in-one/#upgrading), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant).
|
||||
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/common-tasks/#update-home-assistant), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv/#upgrading-home-assistant).
|
||||
</p>
|
||||
|
||||
View what's new in the latest version and potential impacts on your system [here](https://github.com/home-assistant/home-assistant/releases).
|
||||
@ -25,7 +25,7 @@ $ pip3 install --upgrade homeassistant
|
||||
After updating, you must restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take considerable amount of time (i.e. minutes) depending on your device. This is because all requirements are updated as well.
|
||||
|
||||
<p class='note'>
|
||||
To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/installation/), [Raspberry Pi All-In-One Installer](/docs/installation/raspberry-pi-all-in-one/), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv).
|
||||
To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [Hass.io](/hassio/), [HASSbian](/docs/hassbian/installation/), [Vagrant](/docs/installation/vagrant/), or [Virtualenv](/docs/installation/virtualenv).
|
||||
</p>
|
||||
|
||||
[BRUH automation](http://www.bruhautomation.com) has created [a tutorial video](https://www.youtube.com/watch?v=tuG2rs1Cl2Y) explaining how to upgrade Home Assistant.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user