From 22131a31effe9b8e3c9797a653d425f84f6a0ac5 Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Tue, 27 Sep 2016 15:35:01 -0400 Subject: [PATCH] Added information for GPIO access for HA components. (#993) * Added information for GPIO access for HA components. --- .../installation-raspberry-pi-all-in-one.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/getting-started/installation-raspberry-pi-all-in-one.markdown b/source/getting-started/installation-raspberry-pi-all-in-one.markdown index 95af1a189c0..69540647bc6 100644 --- a/source/getting-started/installation-raspberry-pi-all-in-one.markdown +++ b/source/getting-started/installation-raspberry-pi-all-in-one.markdown @@ -84,6 +84,10 @@ To launch the OZWCP web application: Don't check the USB box regardless of using a USB based device.

+### {% linkable_title Using the GPIOs %} + +Please note that if you are using any components for Home Assistant that would use the GPIOs on the RPI, you will need to grant the default AiO user `hass` access to the GPIOs. Run the following command `sudo adduser hass gpio` while in a terminal session on your Pi. This is a one time configuration change to allow All In One Installer based Home Assistant access to the GPIOs. + ### {% 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. The needed change within WinSCP is: **Environment** -> **SCP/Shell** -> **Shell** and set it to `sudo su -`.