Disadvantages:
These are devices that will only report their state to their own cloud backend. The cloud backend will allow reading the state but will not notify when a new state has arrived. This requires the home automation to check frequently if the state has been updated.
diff --git a/blog/2017/02/25/config-panel-and-state-restoration/index.html b/blog/2017/02/25/config-panel-and-state-restoration/index.html index 753c906491..3b9f974825 100644 --- a/blog/2017/02/25/config-panel-and-state-restoration/index.html +++ b/blog/2017/02/25/config-panel-and-state-restoration/index.html @@ -118,7 +118,7 @@Thanks to Fabian we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.
Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. Johann has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to input_select and input_boolean components. We will be adding this to more integrations in the future.
Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. Johann has added the foundation for state restoration to Home Assistant. For the initial release support has been added to input_select and input_boolean components. We will be adding this to more integrations in the future.
A couple of releases ago we introduced a new way of doing customize. It became a list that allowed different ways of matching the config to the entity.
We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?
diff --git a/blog/categories/announcements/atom.xml b/blog/categories/announcements/atom.xml index 88b5706db4..a770de1b21 100644 --- a/blog/categories/announcements/atom.xml +++ b/blog/categories/announcements/atom.xml @@ -4,7 +4,7 @@Thanks to Fabian we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.
Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. Johann has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to input_select and input_boolean components. We will be adding this to more integrations in the future.
Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. Johann has added the foundation for state restoration to Home Assistant. For the initial release support has been added to input_select and input_boolean components. We will be adding this to more integrations in the future.
A couple of releases ago we introduced a new way of doing customize. It became a list that allowed different ways of matching the config to the entity.
We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?
diff --git a/components/alarm_control_panel.egardia/index.html b/components/alarm_control_panel.egardia/index.html index fce47de280..71e39628c6 100644 --- a/components/alarm_control_panel.egardia/index.html +++ b/components/alarm_control_panel.egardia/index.html @@ -75,7 +75,7 @@The egardia platform enables the ability to control an Egardia/Woonveilig control panel. These alarm panels are known under different brand names across the world, including Woonveilig in the Netherlands. This was tested on a Gate01 version of the Egardia/Woonveilig platform.
You will need to know the IP of your alarm panel on your local network. Test if you can login to the panel by browsing to the IP address and log in in using your Egardia/Woonveilig account.
+You will need to know the IP of your alarm panel on your local network. Test if you can login to the panel by browsing to the IP address and log in using your Egardia/Woonveilig account.
To enable this, add the following lines to your configuration.yaml:
# Example configuration.yaml entry
alarm_control_panel:
diff --git a/components/alexa/index.html b/components/alexa/index.html
index 116fda77d6..2406fd8b84 100644
--- a/components/alexa/index.html
+++ b/components/alexa/index.html
@@ -92,7 +92,7 @@
- In your router, forward external 443 to your Home Assistant serving port (defaults to 8123)
OR
- - Change your Home Assistant serving port to 443 this is done in the
http section with the the server_port entry in your configuration.yaml file
+ - Change your Home Assistant serving port to 443 this is done in the
http section with the server_port entry in your configuration.yaml file
To get started with Alexa skills:
diff --git a/components/asterisk_mbox/index.html b/components/asterisk_mbox/index.html
index a100ec567b..2863f96b9f 100644
--- a/components/asterisk_mbox/index.html
+++ b/components/asterisk_mbox/index.html
@@ -77,7 +77,7 @@
The Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox. The component includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google’s API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.
To enable the component, a configuration is required in both Home Assistant as well as on the Asterisk server.
First follow the Asterisk PBX configuration guide to setup the necessary server on the Asterisk PBX server (this is needed even if Asterisk and Home Assistant are running on the same server)
-Once that is complete, add the the following entry configuration.yaml file:
+Once that is complete, add the following entry configuration.yaml file:
# Example configuration.yaml entry
asterisk_mbox:
password: ASTERISK_PBX_PASSWORD
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 47da55044d..6aecb927c9 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -87,7 +87,7 @@
- resource (Required): IP address and schema of the device that is exposing an aREST API, e.g. http://192.168.1.10.
- pin (Required): Number of the pin to monitor.
- - name (Optional): Let you overwrite the the name of the device. By default name from the device is used.
+ - name (Optional): Let you overwrite the name of the device. By default name from the device is used.
Accessing the URL http://IP_ADDRESS/digital/PIN_NUMBER should give you the state of the pin inside a JSON response as return_value.
$ curl -X GET http://192.168.0.5/digital/9
diff --git a/components/binary_sensor.command_line/index.html b/components/binary_sensor.command_line/index.html
index 8bef0644ea..3060b6161a 100644
--- a/components/binary_sensor.command_line/index.html
+++ b/components/binary_sensor.command_line/index.html
@@ -85,7 +85,7 @@
Configuration variables:
- command (Required): The action to take to get the value.
- - name (Optional): Let you overwrite the the name of the device. By default name from the device is used.
+ - name (Optional): Let you overwrite the name of the device. By default name from the device is used.
- device_class (Optional): The type/class of the sensor to set the icon in the frontend.
- payload_on (Optional): The payload that represents enabled state. Default is “ON”.
- payload_off (Optional): The payload that represents disabled state. Default is “OFF”.
diff --git a/components/climate.eq3btsmart/index.html b/components/climate.eq3btsmart/index.html
index bfa31c4147..8e1d5762f5 100644
--- a/components/climate.eq3btsmart/index.html
+++ b/components/climate.eq3btsmart/index.html
@@ -79,7 +79,7 @@
As the device doesn’t contain a temperature sensor (read more),
we report target temperature also as current one.
Testing the connectivity
-Before configuring Home Assistant you should check that connectivity with the thermostat is working, which can can be done with the eq3cli tool:
+Before configuring Home Assistant you should check that connectivity with the thermostat is working, which can be done with the eq3cli tool:
eq3cli --mac 00:11:22:33:44:55
[00:1A:22:XX:XX:XX] Target 17.0 (mode: auto dst, away: no)
diff --git a/components/device_tracker.snmp/index.html b/components/device_tracker.snmp/index.html
index b20bc71165..df0228db8d 100644
--- a/components/device_tracker.snmp/index.html
+++ b/components/device_tracker.snmp/index.html
@@ -163,7 +163,7 @@ This device tracker needs SNMP to be enabled on the router. It could be that you
Configuration variables:
- host (Required): The IP address of the router, eg. 192.168.1.1.
- - community (Required): The SNMP community which is set for the device. Most devices have a default community set to to
public with read-only permission (which is sufficient).
+ - community (Required): The SNMP community which is set for the device. Most devices have a default community set to
public with read-only permission (which is sufficient).
- baseoid (Required): The OID prefix where wireless client registrations can be found, usually vendor specific. It’s advised to use the numerical notation. To find this base OID, check vendor documentation or check the MIB file for your device.
- authkey (Inclusive): Authentication key for SNMPv3. Variable privkey must also be set.
- privkey (Inclusive): Privacy key SNMPv3. Variable authkey must also be set.
diff --git a/components/downloader/index.html b/components/downloader/index.html
index 3229e9391c..e2bb12cd56 100644
--- a/components/downloader/index.html
+++ b/components/downloader/index.html
@@ -86,7 +86,7 @@
- download_dir (Required): If the path is not absolute, it’s assumed to be relative to the Home Assistant configuration directory (eg.
.homeassistant/downloads).
Use the service
-Go the the “Developer Tools”, then to “Call Service”, and choose downloader/download_file from the list of available services. Fill the “Service Data” field as shown in the example below and hit “CALL SERVICE”.
+Go to the “Developer Tools”, then to “Call Service”, and choose downloader/download_file from the list of available services. Fill the “Service Data” field as shown in the example below and hit “CALL SERVICE”.
{"url":"http://domain.tld/path/to/file"}
diff --git a/components/joaoapps_join/index.html b/components/joaoapps_join/index.html
index d0fa325b2c..d99415cc03 100644
--- a/components/joaoapps_join/index.html
+++ b/components/joaoapps_join/index.html
@@ -74,7 +74,7 @@
- The Join platform exposes services from Join. In Home Assistant, the Join features are divided up in two locations, the Join component, and the Join notify platform. The notify platform allows us to send messages to Join devices, the the component allows us to access the other special features that Join offers.
+ The Join platform exposes services from Join. In Home Assistant, the Join features are divided up in two locations, the Join component, and the Join notify platform. The notify platform allows us to send messages to Join devices, the component allows us to access the other special features that Join offers.
In the configuration.yaml file you need to provide the api key and device id or name of the target device. You can find your device id and api key here.
To set it up, add the following information to your configuration.yaml file:
notify:
diff --git a/components/lock/index.html b/components/lock/index.html
index 30fe0450d7..217b2c8473 100644
--- a/components/lock/index.html
+++ b/components/lock/index.html
@@ -80,7 +80,7 @@
- Registers services
lock/lock and lock/unlock to control locks.
Use the services
-Go the the Developer Tools, then to Call Service in the frontend, and choose lock/lock or lock/unlock from the list of available services (Available services: on the left). Enter something like the sample below into the Service Data field and hit CALL SERVICE.
+Go to the Developer Tools, then to Call Service in the frontend, and choose lock/lock or lock/unlock from the list of available services (Available services: on the left). Enter something like the sample below into the Service Data field and hit CALL SERVICE.
{"entity_id":"lock.front_door"}
diff --git a/components/media_player.anthemav/index.html b/components/media_player.anthemav/index.html
index ca3ef63bd7..78dd34b53d 100644
--- a/components/media_player.anthemav/index.html
+++ b/components/media_player.anthemav/index.html
@@ -74,7 +74,7 @@
- Both Anthem’s current and last generation of A/V Receivers and and Processors support IP-based, network control. This Home Assistant platform adds proper “local push” support for any of these receivers on your network.
+ Both Anthem’s current and last generation of A/V Receivers and Processors support IP-based, network control. This Home Assistant platform adds proper “local push” support for any of these receivers on your network.
Supported Models
- MRX 520, MRX 720, MRX 1120, and AVM 60
diff --git a/components/media_player.directv/index.html b/components/media_player.directv/index.html
index fa7447986f..44c8363f5b 100644
--- a/components/media_player.directv/index.html
+++ b/components/media_player.directv/index.html
@@ -74,7 +74,7 @@
- Master DirecTV receivers (ie: those that have tuners) will be automatically discovered if you enable the discovery component and the the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.
+ Master DirecTV receivers (ie: those that have tuners) will be automatically discovered if you enable the discovery component and the receiver is powered-on. Slave/RVU client/Genie boxes will also be discovered, but only if they are also online at the time of discovery.
To ensure that your DirecTV boxes are always found and configured, they should be added into your configuration.yaml.
# Example configuration.yaml entry
media_player:
diff --git a/components/plant/index.html b/components/plant/index.html
index cb2c1bc20d..fb2c24d077 100644
--- a/components/plant/index.html
+++ b/components/plant/index.html
@@ -117,7 +117,7 @@
Using plain MQTT sensor to get the data
This is a practical example that uses a multiple of MQTT sensors to supply the readings used by the plant sensor.
Another good source of this data would be the Mi Flora component.
-If the sensor data within the the min/max values the status will be ok, if not the status will be problem. You can use this to trigger a notification, if there is a problem with your plant. Of course you can only monitor attributes of your plant, where the sensor is configured and is providing the data.
+If the sensor data is within the min/max values the status will be ok, if not the status will be problem. You can use this to trigger a notification, if there is a problem with your plant. Of course you can only monitor attributes of your plant, where the sensor is configured and is providing the data.
Data Source
The main sources of the data will usually be a MiFlora sensor or a MQTT sensor receiving the data from a PlantGateway.
If you want to get the date via a PlantGateway, this is a typical configuration for the MQTT sensors:
diff --git a/components/remote/index.html b/components/remote/index.html
index 9906ddd1a8..4347c2b05e 100644
--- a/components/remote/index.html
+++ b/components/remote/index.html
@@ -80,7 +80,7 @@
- Registers services
remote/turn_on, remote/turn_off, remote/toggle, remote/sync, and remote/send_command to control remotes.
Use the services
-Go the the Developer Tools, then to Call Service in the frontend, and choose remote/turn_on, remote/turn_off, or remote/toggle from the list of available services (Available services: on the left). Enter something like the sample below into the Service Data field and hit Call Service.
+Go to the Developer Tools, then to Call Service in the frontend, and choose remote/turn_on, remote/turn_off, or remote/toggle from the list of available services (Available services: on the left). Enter something like the sample below into the Service Data field and hit Call Service.
{"entity_id":"remote.family_room"}
diff --git a/components/sensor.arest/index.html b/components/sensor.arest/index.html
index 2abd69f759..6c951733c8 100644
--- a/components/sensor.arest/index.html
+++ b/components/sensor.arest/index.html
@@ -91,7 +91,7 @@
Configuration variables:
- resource (Required): IP address and schema of the device that is exposing an aREST API, e.g. http://192.168.1.10.
- - name (Optional): Let you overwrite the the name of the device. By default name from the device is used.
+ - name (Optional): Let you overwrite the name of the device. By default name from the device is used.
- monitored_variables array (Optional): List of exposed variables.
- [variable] (Required): Name of the variable to monitor.
diff --git a/components/sensor.citybikes/index.html b/components/sensor.citybikes/index.html
index 59145a7ef3..99491ebd5e 100644
--- a/components/sensor.citybikes/index.html
+++ b/components/sensor.citybikes/index.html
@@ -86,8 +86,8 @@
- name (Optional): The base name of this group of monitored stations. The entity ID of every monitored station in this group will be prefixed with this base name, in addition to the network ID.
- network (Optional): The name of the bike sharing system to poll. Defaults to the system that operates in the monitored location.
- - latitude (Optional): Latitude of the location, around which bike stations are monitored. Defaults to the latitude in your your
configuration.yaml file.
- - longitude (Optional): Longitude of the location, around which bike stations are monitored. Defaults to the longitude in your your
configuration.yaml file.
+ - latitude (Optional): Latitude of the location, around which bike stations are monitored. Defaults to the latitude in your
configuration.yaml file.
+ - longitude (Optional): Longitude of the location, around which bike stations are monitored. Defaults to the longitude in your
configuration.yaml file.
- radius (Optional): The radius (in meters or feet, depending on the Home Assistant configuration) around the monitored location. Only stations closer than this distance will be monitored.
- stations array (Optional): A list of specific stations to monitor. The list should contain station
IDs or UIDs, which can be obtained from the CityBikes API.
diff --git a/components/sensor.dweet/index.html b/components/sensor.dweet/index.html
index f5d84152e6..1aa28146ab 100644
--- a/components/sensor.dweet/index.html
+++ b/components/sensor.dweet/index.html
@@ -87,7 +87,7 @@
- device (Required): Identification of the device (also known as
thing).
- value_template (Required): The variable to extract a value from the content.
- - name (Optional): Let you overwrite the the name of the device in the frontend.
+ - name (Optional): Let you overwrite the name of the device in the frontend.
- unit_of_measurement (Optional): Defines the unit of measurement of the sensor, if any.
Full configuration sample
diff --git a/components/sensor.loop_energy/index.html b/components/sensor.loop_energy/index.html
index d136c6560a..8e3468febb 100644
--- a/components/sensor.loop_energy/index.html
+++ b/components/sensor.loop_energy/index.html
@@ -74,9 +74,9 @@
- Integrate your Loop Energy meter information into Home Assistant. To use this sensor you need the the client serial number and secret keys for your devices.
+ Integrate your Loop Energy meter information into Home Assistant. To use this sensor you need the client serial number and secret keys for your devices.
The library used to get the data isn’t officially supported and the only way to get the keys is to log into loop energy’s website and type a command into your browser console.
-To do this log into Loop Energy. Once you’re logged in you should be able see see your live readings on the web page.
+To do this log into Loop Energy. Once you’re logged in you should be able see your live readings on the web page.
You can then open your browser’s console window, how you do this varies by browser but in Chrome you click on `More Tools / Developer Tools’ and click on the console window. You then type:
Drupal.settings.navetas_realtime.
This should show something like
diff --git a/components/sensor.snmp/index.html b/components/sensor.snmp/index.html
index a698dc900b..8407f7412a 100644
--- a/components/sensor.snmp/index.html
+++ b/components/sensor.snmp/index.html
@@ -88,7 +88,7 @@
- host (Required): The IP address of your host, eg.
192.168.1.32.
- baseoid (Required): The OID where the information is located. It’s advised to use the numerical notation.
- port (Option): The SNMP port of your host. Defaults to
161.
- - community (Optional): The SNMP community which is set for the device. Most devices have a default community set to to
public with read-only permission (which is sufficient).
+ - community (Optional): The SNMP community which is set for the device. Most devices have a default community set to
public with read-only permission (which is sufficient).
- version (Optional) version of SNMP protocol,
1 or 2c. Defaults to 1. Version 2c is needed to read data from 64-bit counters.
- name (Optional): Name of the SNMP sensor.
- unit_of_measurement (Optional): Defines the unit of measurement of the sensor, if any.
diff --git a/components/sensor.uber/index.html b/components/sensor.uber/index.html
index ff151f767b..80370f4119 100644
--- a/components/sensor.uber/index.html
+++ b/components/sensor.uber/index.html
@@ -86,7 +86,7 @@
Configuration variables:
- server_token (Required): A server token obtained from developer.uber.com after creating an app.
- - start_latitude (Optional): The starting latitude for a trip. Defaults to the latitude in your your
configuration.yaml file.
+ - start_latitude (Optional): The starting latitude for a trip. Defaults to the latitude in your
configuration.yaml file.
- start_longitude (Optional): The starting longitude for a trip. Defaults to the longitude in your
configuration.yaml file.
- end_latitude (Optional): The ending latitude for a trip. While
end_latitude is optional, it is strongly recommended to provide an end_latitude/end_longitude when possible as you will get more accurate price and time estimates.
- end_longitude (Optional): The ending longitude for a trip. While
end_longitude is optional, it is strongly recommended to provide an end_latitude/end_longitude when possible as you will get more accurate price and time estimates.
diff --git a/components/switch.arest/index.html b/components/switch.arest/index.html
index 12c20cc828..6add4f7515 100644
--- a/components/switch.arest/index.html
+++ b/components/switch.arest/index.html
@@ -99,7 +99,7 @@
Configuration variables:
- resource (Required): IP address and schema of the device that is exposing an aREST API, eg. http://192.168.1.10 (no-trailing slash)
- - name (Optional): Let you overwrite the the name of the device. By default name from the device is used.
+ - name (Optional): Let you overwrite the name of the device. By default name from the device is used.
- pins array (Optional): An array with all used pins.
- name (Required): The name of the pin to use in the frontend.
diff --git a/components/switch.flux/index.html b/components/switch.flux/index.html
index 42d9da5a98..723a895f02 100644
--- a/components/switch.flux/index.html
+++ b/components/switch.flux/index.html
@@ -75,8 +75,8 @@
The flux switch platform will change the temperature of your lights similar to the way flux works on your computer, using circadian rhythm. They will be bright during the day, and gradually fade to a red/orange at night.
-The component will update your lights based on the the time of day. It will only affect lights that are turned on and listed in the flux configuration.
-During the day (in between start time and sunset time), it will fade the lights from the start_colortemp to the sunset_colortemp. After sunset (between sunset_time and stop_time), the lights will fade from the the sunset_colortemp to the stop_colortemp. If the lights are still on after the stop_time it will continue to change the light to the stop_colortemp until the light is turned off. The fade effect is created by updating the lights every 30 seconds with a 30 second transition time.
+The component will update your lights based on the time of day. It will only affect lights that are turned on and listed in the flux configuration.
+During the day (in between start time and sunset time), it will fade the lights from the start_colortemp to the sunset_colortemp. After sunset (between sunset_time and stop_time), the lights will fade from the sunset_colortemp to the stop_colortemp. If the lights are still on after the stop_time it will continue to change the light to the stop_colortemp until the light is turned off. The fade effect is created by updating the lights every 30 seconds with a 30 second transition time.
If you don’t wish to have flux update on 30 second intervals, you can leave the switch turned off and use automation rules that call the service switch.<name>_update whenever you want the lights updated, where <name> equals the name: property in the switch configuration.
To use the Flux switch in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
diff --git a/components/switch/index.html b/components/switch/index.html
index a97bd6a564..e9bdc51dbf 100644
--- a/components/switch/index.html
+++ b/components/switch/index.html
@@ -80,7 +80,7 @@
- Registers services
switch/turn_on, switch/turn_off, and switch/toggle to control switches.
Use the services
-Go the the Developer Tools, then to Call Service in the frontend, and choose switch/turn_on or switch/turn_off from the list of available services (Available services: on the left). Enter something like the sample below into the Service Data field and hit CALL SERVICE.
+Go the Developer Tools, then to Call Service in the frontend, and choose switch/turn_on or switch/turn_off from the list of available services (Available services: on the left). Enter something like the sample below into the Service Data field and hit CALL SERVICE.
{"entity_id":"livingroom_pin2"}
diff --git a/components/telegram_bot.webhooks/index.html b/components/telegram_bot.webhooks/index.html
index 91877e36e9..b5547a754f 100644
--- a/components/telegram_bot.webhooks/index.html
+++ b/components/telegram_bot.webhooks/index.html
@@ -101,7 +101,7 @@
- proxy_params (Optional): Proxy configuration parameters, as dict, if working behind a proxy (
username, password, etc.)
- url (Optional): Allow to overwrite the
base_url from the http component for different configurations (https://<public_url>:<port>).
-To get your chat_id and api_key follow the instructions here. As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error (“Incoming message is not allowed”), you can easily obtain the the users id by looking in the “from” section of this error message.
+To get your chat_id and api_key follow the instructions here. As well as authorizing the chat, if you have added your bot to a group you will also need to authorize any user that will be interacting with the webhook. When an unauthorized user tries to interact with the webhook Home Assistant will raise an error (“Incoming message is not allowed”), you can easily obtain the users id by looking in the “from” section of this error message.
Full configuration sample:
# Example configuration.yaml entry
http:
diff --git a/developers/development_environment/index.html b/developers/development_environment/index.html
index 4e99626eea..a482430564 100644
--- a/developers/development_environment/index.html
+++ b/developers/development_environment/index.html
@@ -88,7 +88,7 @@
Different distributions have different package installation mechanisms and sometimes packages names as well. For example Centos would use: sudo yum install epel-release && sudo yum install python34 python34-devel mysql-devel
-Additional dependencies exist if you you plan to perform Frontend Development, please read the Frontend section to learn more.
+Additional dependencies exist if you plan to perform Frontend Development, please read the Frontend section to learn more.
Developing on Windows
If you are using Windows as a development platform, make sure that you have the correct Microsoft Visual C++ build tools installed. Check the Windows Compilers section on the Python website for details. Validation using tox will fail if this is not done correctly.
Also, make sure to install or upgrade the setuptools Python package. It contains compatibility improvements and adds automatic use of compilers:
diff --git a/docs/installation/hassbian/common-tasks/index.html b/docs/installation/hassbian/common-tasks/index.html
index 402e4354f0..51d1892d8f 100644
--- a/docs/installation/hassbian/common-tasks/index.html
+++ b/docs/installation/hassbian/common-tasks/index.html
@@ -85,7 +85,7 @@ Linux and Mac OS users execute the following command in a terminal.
Windows users start Putty, enter the IP address of the Raspberry Pi in the Host name field and port 22 in the Port field. Then click Open and a terminal window will open. Enter the credentials. Default user name is pi and password is raspberry.
Optionally, starting with Windows 10 anniversary update, you can use the built-in ‘Bash on Windows’ to use SSH if you have enabled Developer mode and have installed the “Windows Subsystem for Linux (beta)” feature.
Start/Stop/Restart Home Assistant
-Log in as the pi account account and execute the following commands:
+Log in as the pi account and execute the following commands:
$ sudo systemctl stop home-assistant@homeassistant.service
diff --git a/docs/installation/synology/index.html b/docs/installation/synology/index.html
index 102c5f582a..3e8ef46f0e 100644
--- a/docs/installation/synology/index.html
+++ b/docs/installation/synology/index.html
@@ -237,7 +237,7 @@ esac
# chmod 777 /volume1/homeassistant/hass-daemon
-Update your firewall (if it is turned on on the Synology device):
+Update your firewall (if it is turned on the Synology device):
- Go to your Synology control panel
- Go to security
diff --git a/docs/tools/scripts/index.html b/docs/tools/scripts/index.html
index 15fb3e4dba..ac0684937c 100644
--- a/docs/tools/scripts/index.html
+++ b/docs/tools/scripts/index.html
@@ -75,7 +75,7 @@
- The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with with Home Assistant’s script feature.
+ The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with Home Assistant’s script feature.
Configuration check
Test any changes to your configuration.yaml file before launching Home Assistant. This script allows you to test changes without the need to restart Home Assistant.
$ hass --script check_config
diff --git a/sitemap.xml b/sitemap.xml
index 52ae0537fa..2196e2760b 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -3374,7 +3374,7 @@
https://home-assistant.io/components/switch.hook/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/cookbook/automation_for_rainy_days/
@@ -4006,99 +4006,99 @@
https://home-assistant.io/docs/autostart/init.d/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/api/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/configuration/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/example_apps/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/installation/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/operation/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/reboot/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/running/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/tutorial/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/updating/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/appdaemon/windows/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/certificates/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/hadashboard/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/hass-configurator/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/ios/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/nginx/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/notebooks/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/scenegen/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/ecosystem/synology/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/tools/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/tools/dev-tools/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/tools/hass/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/docs/tools/scripts/
-2017-09-26T16:07:55+00:00
+2017-09-26T18:31:09+00:00
https://home-assistant.io/faq/after-upgrading/
@@ -5110,62 +5110,62 @@
https://home-assistant.io/demo/frontend.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/index.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:34+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:35+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:35+00:00
https://home-assistant.io/static/mdi-demo.html
-2017-09-26T16:06:57+00:00
+2017-09-26T18:30:35+00:00