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

Site updated at 2018-01-28 22:02:31 UTC

Browse source
This commit is contained in:
Travis CI 2018-01-28 22:02:31 +00:00
parent 57a21e9eb0
commit 01b474f87c
268 changed files with 412 additions and 412 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/ecosystem/certificates/lets_encrypt/index.html
View file

@ -237,7 +237,7 @@ In cases where your ISP blocks port 80 you will need to change the port forward
</p>
<p>Now SSH in to the device your Home Assistant is running on.</p>
<p class="note">
If you’re running the ‘standard’ setup on a Raspberry Pi the chances are you just logged in as the ‘pi’ user. If not, you may have logged in as the Home Assistant user. There are commands below that require the Home Assistant user to be on the <code class="highlighter-rouge">sudoers</code> list. If you are not using the ‘standard’ pi setup it is presumed you will know how to get your Home Assistant user on the <code class="highlighter-rouge">sudoers</code> list before continuing. If you are running the ‘standard’ pi setup, from your ‘pi’ user issue the following command (where <code class="highlighter-rouge">hass</code> is the Home Assistant user):
If you’re running the ‘standard’ setup on a Raspberry Pi the chances are you just logged in as the ‘pi’ user. If not, you may have logged in as the Home Assistant user. There are commands below that require the Home Assistant user to be on the <code class="highlighter-rouge">sudoers</code> list. If you are not using the ‘standard’ Pi setup it is presumed you will know how to get your Home Assistant user on the <code class="highlighter-rouge">sudoers</code> list before continuing. If you are running the ‘standard’ Pi setup, from your ‘pi’ user issue the following command (where <code class="highlighter-rouge">hass</code> is the Home Assistant user):
<code class="highlighter-rouge">
$ sudo adduser hass sudo
</code>