+`interface` options are for resinos based installation. On other system you can set it to `""`, for listen on every interface.
+
+
```json
{
"defaults": ["8.8.8.8", "8.8.4.4"],
diff --git a/source/_addons/lets_encrypt.markdown b/source/_addons/lets_encrypt.markdown
index 2b7d51b470d..022911183fa 100644
--- a/source/_addons/lets_encrypt.markdown
+++ b/source/_addons/lets_encrypt.markdown
@@ -17,6 +17,7 @@ This add-on need port 80/443 to verify the certificate request, please stop all
```json
{
+ "challenge": "https",
"email": "example@example.com",
"domains": ["example.com", "mqtt.example.com", "hass.example.com"]
}
@@ -24,6 +25,7 @@ This add-on need port 80/443 to verify the certificate request, please stop all
Configuration variables:
+- **challenge** (*Optional*): Default it use 443 ('https') you can change it to 'http' for use port 80.
- **email** (*Required*): Your email address for registration on Let's Encrypt.
- **domains** (*Required*): A list of domains to create/renew the certificate.
diff --git a/source/_addons/mariadb.markdown b/source/_addons/mariadb.markdown
new file mode 100644
index 00000000000..548d4d0c145
--- /dev/null
+++ b/source/_addons/mariadb.markdown
@@ -0,0 +1,55 @@
+---
+layout: page
+title: "MariaDB"
+description: "MariaDB Server is one of the most popular database servers in the world."
+date: 2017-04-30 13:28
+sidebar: true
+comments: false
+sharing: true
+footer: true
+---
+
+Set up a [mariadb](https://mariadb.org/) SQL server. It support multible database, users and permission. If you want only connect from inside use `172.17.0.1` as host address.
+
+```json
+{
+ "databases": ["homeassistant"],
+ "logins": [
+ {
+ "username": "hass",
+ "host": "172.17.0.1",
+ "password": "securePassword"
+ }
+ ],
+ "rights": [
+ {
+ "username": "hass",
+ "host": "172.17.0.1",
+ "database": "homeassistant",
+ "grant": "ALL PRIVILEGES ON"
+ }
+ ]
+}
+```
+
+Configuration variables:
+
+- **databases** (*Require*): Listen of databases.
+- **logins** (*Require*): Listen of logindata they will create or update.
+ - **username** (*Require*): Username for login.
+ - **host** (*Require*): Host for login, if you need a login with multibe hosts, use '%'.
+ - **password** (*Require*): Password for login.
+- **rights** (*Require*): Listen of rights to be handle.
+ - **username** (*Require*): Username for grant rights.
+ - **host** (*Require*): Host is a part of username like above.
+ - **database** (*Require*): Database name to grant this user rights to.
+ - **grant** (*Require*): SQL grant part for access too.
+
+## {% linkable_title Home Assistant configuration %}
+
+Use the following configuration in Home Assistant to use the database above:
+
+```yaml
+recorder:
+ db_url: mysql://hass:securePassword@127.0.0.1/homeassistant
+```
diff --git a/source/_addons/samba.markdown b/source/_addons/samba.markdown
index baba4d50372..bfca0c16c01 100644
--- a/source/_addons/samba.markdown
+++ b/source/_addons/samba.markdown
@@ -13,6 +13,7 @@ This allows you to set up a [Samba](https://samba.org/) server to access hass.io
```json
{
+ "name": "hassio",
"workgroup": "WORKGROUP",
"guest": true,
"map_config": true,
@@ -25,6 +26,7 @@ This allows you to set up a [Samba](https://samba.org/) server to access hass.io
Configuration variables:
+- **name** (*Optional*): default `hassio`. Set netbios name of hassio device.
- **workgroup** (*Optional*): default `WORKGROUP`. Set network workgroup.
- **guest** (*Optional*): Allow login without a username or password. Defaults to `true`.
- **map_config** (*Optional*): Expose Home Assistant configuration folder. Defaults to `true`.
diff --git a/source/_addons/ssh.markdown b/source/_addons/ssh.markdown
index 2361e378ab4..710521d675b 100644
--- a/source/_addons/ssh.markdown
+++ b/source/_addons/ssh.markdown
@@ -35,3 +35,12 @@ If you're coming from Rasbian or similar, use `root` rather than `pi` when conne
Permission denied (publickey,keyboard-interactive)
```
+
+
+If you install this addon you can use `sshfs` as well to access files from a remote system where you have git and your favourite editing tools installed.
+
+```bash
+$ mkdir ~/ha_config
+$ sshfs -o allow_other,defer_permissions root@h[your_hassio_ip]:/config ~/ha_config
+```
+
diff --git a/source/_components/axis.markdown b/source/_components/axis.markdown
index bdf70c5a40c..bf4736548d3 100644
--- a/source/_components/axis.markdown
+++ b/source/_components/axis.markdown
@@ -23,7 +23,7 @@ Home Assistant will automatically discover their presence on your network.
$ sudo apt-get install python3-gi gir1.2-gstreamer-1.0
```
-Depending on how you run Home Assistant you might be needed to symlink the `gi` module into your environment.
+Depending on how you run Home Assistant, you may need to symlink the `gi` module into your environment.
Hassbian:
diff --git a/source/_components/binary_sensor.command_line.markdown b/source/_components/binary_sensor.command_line.markdown
index 3a612d04b3a..05a482a5fb1 100644
--- a/source/_components/binary_sensor.command_line.markdown
+++ b/source/_components/binary_sensor.command_line.markdown
@@ -33,6 +33,7 @@ Configuration variables:
- **payload_on** (*Optional*): The payload that represents enabled state. Default is "ON".
- **payload_off** (*Optional*): The payload that represents disabled state. Default is "OFF".
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
+- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds).
## {% linkable_title Examples %}
diff --git a/source/_components/blink.markdown b/source/_components/blink.markdown
index 21cd6b4447b..217dcce7438 100644
--- a/source/_components/blink.markdown
+++ b/source/_components/blink.markdown
@@ -36,9 +36,9 @@ Once loaded, your front end will have the following components:
* A camera image for each camera in your system.
* A binary_sensor per camera that indicates whether motion detection is enabled.
* A binary_sensor for the system that indicates if the system is armed or disarmed.
-* A sesnor per camera that reports temperature.
+* A sensor per camera that reports temperature.
* A sensor per camera that reports battery level.
-* A sensor per camera that reports unread notification (ie. detected motion events).
+* A sensor per camera that reports unread notification (i.e., detected motion events).
Since the cameras are battery operated, the images are only updated in Home Assistant when the user manually forces a new photo. This image can be updated with the `snap_picture` service to force Home Assistant to request an update from Blink's servers. As a note, all of the camera-specific sensors are only polled when a new image is requested from the camera. This means that relying on any of these sensors to provide timely and accurate data is not recommended.
@@ -59,7 +59,7 @@ For `arm_system`, the value sent can be either `True` or `False` and will arm an
}
```
-Arm camera follows a similar structure, but each indidivual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if you have a camera named "Living Room" and you want to turn off motion detection on that camera, you would call the `arm_camera` service with the following payload:
+Arm camera follows a similar structure, but each individual camera can have motion detection enabled or disabled. Because of this, you also need to supply a name. For example, if you have a camera named "Living Room" and you want to turn off motion detection on that camera, you would call the `arm_camera` service with the following payload:
```json
{
diff --git a/source/_components/climate.maxcube.markdown b/source/_components/climate.maxcube.markdown
index ac6e5299ba9..0b918cf1033 100644
--- a/source/_components/climate.maxcube.markdown
+++ b/source/_components/climate.maxcube.markdown
@@ -1,6 +1,6 @@
---
layout: page
-title: "eQ-3 MAX! Cube binary sensors"
+title: "eQ-3 MAX! Cube thermostat"
description: "Instructions on how to integrate eQ-3 MAX! components with Home Assistant via eQ-3 MAX! Cube."
date: 2017-02-04 22:00
sidebar: true
diff --git a/source/_components/device_tracker.snmp.markdown b/source/_components/device_tracker.snmp.markdown
index d8559db08c0..65630b80fc0 100644
--- a/source/_components/device_tracker.snmp.markdown
+++ b/source/_components/device_tracker.snmp.markdown
@@ -16,20 +16,23 @@ ha_release: 0.7.5
A lot WiFi access points and WiFi routers support the Simple Network Management Protocol (SNMP). This is a standardized method for monitoring/manageing network connected devices. SNMP uses a tree-like hierarchy where each node is an object. Many of these objects contain (live) lists of insances and metrics, like network interfaces, disks, and wifi registrations.
-This device tracker needs SNMP to be enabled on the router.
+This device tracker needs SNMP to be enabled on the router. It could be that you need to install the SNMP support manually.
OID examples:
-- Mikrotik: `1.3.6.1.4.1.14988.1.1.1.2.1.1` (confirmed, unknown RouterOS version/model)
-- Mikrotik: `1.3.6.1.2.1.4.22.1.2` (confirmed, RouterOS 6.x on RB2011)
-- Aruba: `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.2` (untested)
-- BiPAC 7800DXL: `1.3.6.1.2.1.17.7.1.2.2.1.1` (confirmed on firmware 2.32e)
-- OpenWrt: `1.3.6.1.2.1.4.22.1.2` (tested on Chaos Calmer 15.05 firmware, need to install snmpd package)
-- pfSense: `1.3.6.1.2.1.4.22.1.2` (tested on 2.2.4-RELEASE, need to enable SNMP service)
-- TPLink: `1.3.6.1.2.1.3.1.1.2.19.1` (Archer VR2600v, need to enable SNMP service)
-- EdgeRouter `1.3.6.1.2.1.4.22.1.2` (EdgeRouter Lite v1.9.0, need to enable SNMP service)
-- Ruckus: `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` (Ruckus ZoneDirector, tested on 9.13.3)
+| Brand | Device/Firmware | OID |
+|---|---|---|---|
+| Mikrotik | unknown RouterOS version/model | `1.3.6.1.4.1.14988.1.1.1.2.1.1` |
+| Mikrotik | RouterOS 6.x on RB2011 | `1.3.6.1.2.1.4.22.1.2` |
+| Aruba | (untested) | `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.2` |
+| pfSense | 2.2.4 | `1.3.6.1.2.1.4.22.1.2` |
+| BiPAC | 7800DXL Firmware 2.32e | `1.3.6.1.2.1.17.7.1.2.2.1.1` |
+| OpenWrt | Chaos Calmer 15.05 | `1.3.6.1.2.1.4.22.1.2` |
+| TP-Link | Archer VR2600v | `1.3.6.1.2.1.3.1.1.2.19.1` |
+| TP-Link | Archer VR600 | `1.3.6.1.2.1.3.1.1.2` |
+| EdgeRouter | Lite v1.9.0 | `1.3.6.1.2.1.4.22.1.2` |
+| Ruckus | ZoneDirector 9.13.3 | `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` |
To use the SNMP version 1 platform in your installation, add the following to your `configuration.yaml` file:
diff --git a/source/_components/input_select.markdown b/source/_components/input_select.markdown
index 45dbc19c0d8..d41555c13ab 100644
--- a/source/_components/input_select.markdown
+++ b/source/_components/input_select.markdown
@@ -43,6 +43,10 @@ Configuration variables:
Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`.
+
+Because YAML defines [booleans](http://yaml.org/type/bool.html) as equivalent, any variations of 'On', 'Yes', 'Y', 'Off', 'No', or 'N' (regardless of case) used as option names will be replaced by True and False unless they are defined in quotation marks.
+
+
### {% linkable_title Services %}
This components provide three services to modify the state of the `input_select`:
diff --git a/source/_components/sensor.buienradar.markdown b/source/_components/sensor.buienradar.markdown
index 351e7ce3e13..750a0ae7901 100644
--- a/source/_components/sensor.buienradar.markdown
+++ b/source/_components/sensor.buienradar.markdown
@@ -33,8 +33,9 @@ sensor:
Configuration variables:
-- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
-- **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
+- **name** (*Optional*): You can specify a name of the component, but do not have to. If you specify a name, the sensors will get an entity name of 'sensor.[name]`[monitored_condition]`, for example: `sensor.lopik_temperature`; if no name is specified the sensors will be called `sensor.br_[monitored_condition]`, for example `sensor.br_temperature`.
+- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl.
+- **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl.
- **timeframe** (*Optional*): Minutes to look ahead for precipitation (5..120) [default: 60].
- **monitored_conditions** array (*Required*): One or more conditions to display in the frontend.
- **stationname**: The name of the selected meteo-station.
diff --git a/source/_components/sensor.command_line.markdown b/source/_components/sensor.command_line.markdown
index c0a39d4093e..ba1bee321aa 100644
--- a/source/_components/sensor.command_line.markdown
+++ b/source/_components/sensor.command_line.markdown
@@ -31,7 +31,7 @@ Configuration variables:
- **name** (*Optional*): Name of the command sensor.
- **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any.
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
-- **scan_interval** (*Optional*): Defines number of seconds for polling interval.
+- **scan_interval** (*Optional*): Defines number of seconds for polling interval (defaults to 60 seconds).
## {% linkable_title Examples %}
@@ -104,7 +104,7 @@ sensor:
### {% linkable_title Read value out of a remote text file %}
-If you own a devices which are storing values in text files which are accessible over HTTP then you can use the same approach as shown in the previous section. Instead of looking at the JSON response we directly grab the sensor's value.
+If you own a devices which are storing values in text files which are accessible over HTTP then you can use the same approach as shown in the previous section. Instead of looking at the JSON response we directly grab the sensor's value.
```yaml
sensor:
diff --git a/source/_components/sensor.netatmo.markdown b/source/_components/sensor.netatmo.markdown
index 398a341a607..e92471bdb15 100644
--- a/source/_components/sensor.netatmo.markdown
+++ b/source/_components/sensor.netatmo.markdown
@@ -52,10 +52,10 @@ Configuration variables:
- **rain**: Estimated rainfall for today in mm.
- **sum_rain_1**: Rainfall in the last hour in mm.
- **sum_rain_24**: Rainfall in mm from 00:00am - 23:59pm.
- - **WindAngle**: Wind angle
- - **WindStrength**: Wind strength
- - **GustAngle**: Wind gust angle
- - **GustStrength**: Wind gust strength
+ - **windangle**: Wind angle
+ - **windstrength**: Wind strength
+ - **gustangle**: Wind gust angle
+ - **guststrength**: Wind gust strength
- **min_temp**: Min temperature for today
- **max_temp**: Max temperature for today
- **rf_status**: Current radio status per module. (90=low, 60=highest)
@@ -69,4 +69,3 @@ You can find your modules name in your [online NetAtmo account](https://my.netat
-
diff --git a/source/_components/weather.buienradar.markdown b/source/_components/weather.buienradar.markdown
index 4c1994705b1..07da95af18c 100644
--- a/source/_components/weather.buienradar.markdown
+++ b/source/_components/weather.buienradar.markdown
@@ -26,8 +26,9 @@ weather:
Configuration variables:
-- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
-- **longitude**(*Optional*): Longitude to use for selection of data source location. Longitude & latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
+- **name** (*Optional*): You can specify a name of the component, but do not have to. If you specify a name, the weather component will get an entity name of 'weather.[name]'; if no name is specified, it will try to set its name to 'weather.BR_[stationname]'. However at the moment in time the entity is created, no data has been retrieved yet, so the entity will get named 'weather.BR_unknown_station'. Later the station name will be known and get updated, but the entity name remains.
+- **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
+- **longitude**(*Optional*): Longitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.
- **forecast** (*Optional*): 'True' to add a temperature forecast, 'False' to suppress it.
diff --git a/source/_cookbook/fail2ban.markdown b/source/_cookbook/fail2ban.markdown
index c9c0ff3550b..8eed73efb0c 100644
--- a/source/_cookbook/fail2ban.markdown
+++ b/source/_cookbook/fail2ban.markdown
@@ -1,7 +1,7 @@
---
layout: page
-title: "fail2ban for HASS"
-description: "Setting up fail2ban to read HASS log files to improve security."
+title: "fail2ban"
+description: "Setting up fail2ban to read Home Assistant's log files to improve security."
date: 2017-05-24 10:05
sidebar: true
comments: false
@@ -14,6 +14,15 @@ This is a quick guide on how to setup fail2ban for Home Assistant. This was orig
First install `fail2ban`. On Debian/Ubuntu this would be `apt-get install fail2ban`. On other distros you can google it.
+Then make sure logging is enabled in your `configuration.yaml` file for your Home Assistant instance:
+
+```yaml
+logger:
+ default: critical
+ logs:
+ homeassistant.components.http: warning
+```
+
Next we will be creating these three files :
- `/etc/fail2ban/fail2ban.local`
diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
index e1d2e464c41..d952e497495 100644
--- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown
+++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown
@@ -495,7 +495,7 @@ $ crontab -e
* Scroll to the bottom of the file and paste in the following line
```text
-30 2 * * 1 /usr/bin/letsencrypt renew >> /var/log/le-renew.log
+30 2 * * 1 ~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01
```
* Save the file and exit
diff --git a/source/_docs/ecosystem/hadashboard/hapush.markdown b/source/_docs/ecosystem/hadashboard/hapush.markdown
index 6445a12ae3e..558c3c1cc03 100755
--- a/source/_docs/ecosystem/hadashboard/hapush.markdown
+++ b/source/_docs/ecosystem/hadashboard/hapush.markdown
@@ -43,7 +43,7 @@ $ sudo pip3 install --upgrade requests
## {% linkable_title Configuring hapush (all installation methods) %}
-When you have all the prereqs in place, copy the hapush.cfg.example file to hapush.cfg then edit it to reflect your environment:
+When you have all the prereqs in place, copy the `hapush.cfg.example` file to `hapush.cfg` then edit it to reflect your environment:
```
ha_url = "http://192.168.1.10:8123"
@@ -61,13 +61,13 @@ logfile = "/etc/hapush/hapush.log"
## {% linkable_title Running hapush %}
-For a manual installation you can then run hapush from the command line as follows:
+For a manual installation you can then run `hapush` from the command-line as follows:
```bash
$ ./hapush.py hapush.cfg
```
-For docker installs, hapush will be started automatically when you run the startup command.
+For Docker installs, hapush will be started automatically when you run the startup command.
If all is well, you should start to see `hapush` responding to events as they occur. For a docker installation you should see these messages in `hapush/hapush.log`.
diff --git a/source/_docs/ecosystem/hadashboard/installation.markdown b/source/_docs/ecosystem/hadashboard/installation.markdown
index 4d1fe7ff258..a9c024bf8aa 100755
--- a/source/_docs/ecosystem/hadashboard/installation.markdown
+++ b/source/_docs/ecosystem/hadashboard/installation.markdown
@@ -10,13 +10,14 @@ footer: true
redirect_from: /ecosystem/hadashboard/installation/
---
-Installation can be performed using Docker (Contributed by [marijngiesen](https://github.com/marijngiesen)) or manually if Docker doesn't work for you. We also have a Raspberry PI version of Docker contributed by [snizzleorg](https://community.home-assistant.io/users/snizzleorg/activity)
+Installation can be performed using Docker (Contributed by [marijngiesen](https://github.com/marijngiesen)) or manually if Docker doesn't work for you. We also have a Raspberry Pi version of Docker contributed by [snizzleorg](https://community.home-assistant.io/users/snizzleorg/activity).
## {% linkable_title Using Docker (Non Raspian) %}
Assuming you already have Docker installed, installation is fairly easy.
### {% linkable_title Clone the Repository %}
+
Clone the **hadashboard** repository to the current local directory on your machine.
``` bash
@@ -41,7 +42,7 @@ When the build completes, you can run the dashboard with the following command f
$ docker run --name="hadashboard" -d -v /dashboards:/app/dashboards -v /lib/ha_conf.rb:/app/lib/ha_conf.rb -v /hapush:/app/hapush --net=host hadashboard
```
-If you are running docker on windows you should not use the `--net` command and explicitly specify the port, aslo for security reason `--net=host` should not be used so the following can also be used in unix. This will also set the process to start when the docker process starts so you do not have to worry about reboots. To map the volumes make sure you have ticked the shred drives in the settings. In this example I am using `c:\hadashboard` as the location where the git clone was done and mapping to port 3030 on the host.
+If you are running docker on windows you should not use the `--net` command and explicitly specify the port, also for security reason `--net=host` should not be used so the following can also be used in unix. This will also set the process to start when the docker process starts so you do not have to worry about reboots. To map the volumes make sure you have ticked the shred drives in the settings. In this example I am using `c:\hadashboard` as the location where the git clone was done and mapping to port 3030 on the host.
```powershell
docker run --restart=always --name="hadashboard" -p 3030:3030 -d -v C:/hadashboard/dashboards:/app/dashboards -v C:/hadashboard/lib/ha_conf.rb:/app/lib/ha_conf.rb -v C:/hadashboard/hapush:/app/hapush hadashboard
@@ -57,15 +58,13 @@ By default, the docker instance should pick up your timezone but if you want to
### {% linkable_title Docker on Raspberry Pi %}
-Raspberry pi needs to use a different docker build file so the build command is slightly different:
+Raspberry Pi needs to use a different Docker build file so the build command is slightly different:
```bash
$ sudo docker build -f Docker-raspi/Dockerfile -t hadashboard .
```
-Apart from that the other steps are identical.
-
-*Note - this is pretty slow even on a PI3, be prepared for it to take an hour or two to build all of the extensions and install everything*
+Apart from that the other steps are identical. Running Docker is pretty slow even on a PI3, be prepared for it to take an hour or two to build all of the extensions and install everything.
## {% linkable_title Manual Installation %}
@@ -82,17 +81,23 @@ Change your working directory to the repository root. Moving forward, we will be
$ cd hadashboard
```
-### {% linkable_title 2. Install Dashing and prereqs %}
+### {% linkable_title 2. Install Dashing and prerequirments %}
-Essentially, you want to make sure that you have Ruby installed on your local machine. Then, install the Dashing gem:
+Essentially, you want to make sure that you have Ruby installed on your local machine.
-``` bash
+For Debian based distribution do:
+
+```bash
+$ sudo apt-get install rubygems
+```
+
+Then, install the Dashing gem:
+
+```bash
$ gem install dashing
```
-From your repository root, make sure that all dependencies are available.
-
-Note: on some systems you may also need to install bundler:
+From your repository root, make sure that all dependencies are available. On some systems you may also need to install `bundler`:
```bash
$ gem install bundler
@@ -104,9 +109,7 @@ When installed run it:
$ bundle
```
-Bundle will now install all the ruby prereqs for running dashing.
-
-Note: Prereqs will vary across different machines. So far users have reported requirements for some additional installs to allow the bundle to complete succesfully:
+Bundle will now install all the ruby prerequirements for running dashing. Prerequirements will vary across different machines. So far users have reported requirements for some additional installs to allow the bundle to complete succesfully:
- ruby-dev - `sudo apt-get install ruby-dev`
- node-js - `sudo apt-get install nodejs`
@@ -115,18 +118,18 @@ Note: Prereqs will vary across different machines. So far users have reported re
You will need to research what works on your particular architecture and also bear in mind that version numbers may change over time.
-Note: This is currently running on various versions of Ruby and there are no strong dependencies however your mileage may vary.
+This is currently running on various versions of Ruby and there are no strong dependencies however your mileage may vary.
## {% linkable_title Updating configuration (Manual and Docker) %}
-Next, in the `./lib` directory, copy the ha_conf.rb.example file to ha_conf.rb and edit its settings to reflect your installation, pointing to the machine Home Assistant is running on and adding your api_key.
+Next, in the `./lib` directory, copy the `ha_conf.rb.example` file to `ha_conf.rb` and edit its settings to reflect your installation, pointing to the machine Home Assistant is running on and adding your API key.
```ruby
$ha_url = "http://192.168.1.10:8123"
$ha_apikey = "your key"
```
-- `$ha_url` is a reference to your home assistant installation and must include the correct port number and scheme (`http://` or `https://` as appropriate)
+- `$ha_url` is a reference to your Home Assistant installation and must include the correct port number and scheme (`http://` or `https://` as appropriate)
- `$ha_apikey` should be set to your key if you have one, otherwise it can remain blank.
The file also contains example newsfeeds for the News widget:
diff --git a/source/_docs/ecosystem/hadashboard/reboot.markdown b/source/_docs/ecosystem/hadashboard/reboot.markdown
index 3f912b0268f..ca00dc08fe5 100755
--- a/source/_docs/ecosystem/hadashboard/reboot.markdown
+++ b/source/_docs/ecosystem/hadashboard/reboot.markdown
@@ -10,8 +10,8 @@ footer: true
redirect_from: /ecosystem/hadashboard/reboot/
---
-To run Dashing and `hapush` at reboot, I have provided sample init scripts in the `./init` directory. These have been tested on a Raspberry Pi - your mileage may vary on other systems.
+To run Dashing and `hapush` at reboot, checkout out the sample init scripts in the `./init` directory. These have been tested on a Raspberry Pi - your mileage may vary on other systems.
-Instructions for automatically starting a docker install can be found [here](https://docs.docker.com/engine/admin/host_integration/).
+Instructions for automatically starting a Docker installation can be found [here](https://docs.docker.com/engine/admin/host_integration/).
-For docker you may also want to use docker-compose - there is a sample compose file in the `./init` directory.
+For Docker you may also want to use `docker-compose` - there is a sample compose file in the `./init` directory.
diff --git a/source/_docs/ecosystem/hadashboard/updating.markdown b/source/_docs/ecosystem/hadashboard/updating.markdown
index 6854a554151..2c2196e5de7 100755
--- a/source/_docs/ecosystem/hadashboard/updating.markdown
+++ b/source/_docs/ecosystem/hadashboard/updating.markdown
@@ -16,10 +16,10 @@ To update the dashboard after new code has been released, just run the following
$ git pull origin
```
-For some releases you may also need to rerun the bundle command:
+For some releases you may also need to rerun the `bundle` command:
``` bash
$ bundle
```
-For docker users, you will also need to rerun the docker build process.
+For Docker users, you will also need to rerun the Docker build process.
diff --git a/source/_includes/custom/header.html b/source/_includes/custom/header.html
index 15f04816fdc..d0b387b1c1c 100644
--- a/source/_includes/custom/header.html
+++ b/source/_includes/custom/header.html
@@ -9,4 +9,12 @@
+
+
