diff --git a/atom.xml b/atom.xml index 7927643531..d1007a4f2f 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/2018/01/21/clarification-emulated-hue/index.html b/blog/2018/01/21/clarification-emulated-hue/index.html index af01d72464..3b96738c8f 100644 --- a/blog/2018/01/21/clarification-emulated-hue/index.html +++ b/blog/2018/01/21/clarification-emulated-hue/index.html @@ -78,9 +78,7 @@ diff --git a/blog/categories/announcement/atom.xml b/blog/categories/announcement/atom.xml deleted file mode 100644 index 3e8b7f9dd1..0000000000 --- a/blog/categories/announcement/atom.xml +++ /dev/null @@ -1,46 +0,0 @@ - - - - <![CDATA[Category: Announcement | Home Assistant]]> - - - 2018-01-23T07:07:28+00:00 - https://home-assistant.io/ - - - - - Octopress - - - - <![CDATA[Clarification about Emulated Hue]]> - - 2018-01-21T01:00:00+00:00 - https://home-assistant.io/blog/2018/01/21/clarification-emulated-hue - Alexa type is deprecated and will be removed in a future version - -That config option should never have been called `type: alexa` but instead have been called `mode: legacy`. If you think about it, why would emulating something even have different modes it emulates based on the consumer? That means that one of the two emulation modes is incorrect. - -The old implementation was not 100% correct. It was correct enough to work with Alexa (the original target) but not with Google Home. When fixing Emulated Hue we added `type: alexa` to re-enable the old implementation so that people did not have to go through the trouble to re-add their Alexa devices. The option was deprecated to indicate that we would remove the incorrect emulation in the future. However, we forgot about actually following through with that. - -The mistake we made was calling the correct mode `google_home` although it had nothing to do with Google Home. It confused people and they kept adding `type: alexa` to their configuration, triggering the deprecation warning. - -The warning will be updated starting Home Assistant 0.62 and will also include a link to this blog post. - -More info: - -- To read about what was incorrect in the first version of Emulated Hue, take a look at the PR fixing it: [Re-org emulated_hue and fix google home][pr1]. -- Read the [documentation on how to configure Emulated Hue][eh-conf] - -[pr1]: https://github.com/home-assistant/home-assistant/pull/4708 -[pr2]: https://github.com/home-assistant/home-assistant/pull/5549 -[eh-conf]: https://home-assistant.io/components/emulated_hue/#configuration -]]> - - - diff --git a/blog/categories/announcement/index.html b/blog/categories/announcement/index.html deleted file mode 100644 index 0607ee8f11..0000000000 --- a/blog/categories/announcement/index.html +++ /dev/null @@ -1,218 +0,0 @@ - - - - - - - - - Category: Announcement - Home Assistant - - - - - - - - - - - - - - - - - - - - - - -
-
-
-
- - - Home Assistant - -
-
- - -
-
-
-
-
-
-
- -
- -
-
- - - - - - - - diff --git a/blog/categories/announcements/atom.xml b/blog/categories/announcements/atom.xml index 872a0b279b..f86e24f99c 100644 --- a/blog/categories/announcements/atom.xml +++ b/blog/categories/announcements/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Announcements | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 859d770e05..c8f611da71 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index 19172808dc..1c2a8e772d 100644 --- a/blog/categories/device-tracking/atom.xml +++ b/blog/categories/device-tracking/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Device-Tracking | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 97890164df..b86ccfc90e 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index a3699af9d7..2b103740e3 100644 --- a/blog/categories/how-to/atom.xml +++ b/blog/categories/how-to/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: How-To | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index 1978d4bf0c..0da845ef0e 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index d2d62ba571..e5181d3c16 100644 --- a/blog/categories/internet-of-things/atom.xml +++ b/blog/categories/internet-of-things/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Internet-of-Things | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index e94c39f508..741fc12ad2 100644 --- a/blog/categories/iot-data/atom.xml +++ b/blog/categories/iot-data/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: IoT-Data | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/media/atom.xml b/blog/categories/media/atom.xml index 8db26cc743..e4c95cd618 100644 --- a/blog/categories/media/atom.xml +++ b/blog/categories/media/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Media | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/merchandise/atom.xml b/blog/categories/merchandise/atom.xml index 0976ead128..31425d17c2 100644 --- a/blog/categories/merchandise/atom.xml +++ b/blog/categories/merchandise/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Merchandise | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 3fb85d0898..8ef3aacaad 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 1d2f4f6198..e48490b9ba 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index eb68384368..ff186b32c7 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 955c8e436c..174c50e1e5 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index f5ae96fc7a..d4cee1af7f 100644 --- a/blog/categories/presence-detection/atom.xml +++ b/blog/categories/presence-detection/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Presence-Detection | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml index 5fc89f3ffe..75ffa3291d 100644 --- a/blog/categories/public-service-announcement/atom.xml +++ b/blog/categories/public-service-announcement/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Public-Service-Announcement | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ @@ -13,6 +13,36 @@ Octopress + + <![CDATA[Clarification about Emulated Hue]]> + + 2018-01-21T01:00:00+00:00 + https://home-assistant.io/blog/2018/01/21/clarification-emulated-hue + Alexa type is deprecated and will be removed in a future version + +That config option should never have been called `type: alexa` but instead have been called `mode: legacy`. If you think about it, why would emulating something even have different modes it emulates based on the consumer? That means that one of the two emulation modes is incorrect. + +The old implementation was not 100% correct. It was correct enough to work with Alexa (the original target) but not with Google Home. When fixing Emulated Hue we added `type: alexa` to re-enable the old implementation so that people did not have to go through the trouble to re-add their Alexa devices. The option was deprecated to indicate that we would remove the incorrect emulation in the future. However, we forgot about actually following through with that. + +The mistake we made was calling the correct mode `google_home` although it had nothing to do with Google Home. It confused people and they kept adding `type: alexa` to their configuration, triggering the deprecation warning. + +The warning will be updated starting Home Assistant 0.62 and will also include a link to this blog post. + +More info: + +- To read about what was incorrect in the first version of Emulated Hue, take a look at the PR fixing it: [Re-org emulated_hue and fix google home][pr1]. +- Read the [documentation on how to configure Emulated Hue][eh-conf] + +[pr1]: https://github.com/home-assistant/home-assistant/pull/4708 +[pr2]: https://github.com/home-assistant/home-assistant/pull/5549 +[eh-conf]: https://home-assistant.io/components/emulated_hue/#configuration +]]> + + <![CDATA[[Update: fixed] A frank and serious warning about X]]> diff --git a/blog/categories/public-service-announcement/index.html b/blog/categories/public-service-announcement/index.html index f32b2e24a5..49aba288bd 100644 --- a/blog/categories/public-service-announcement/index.html +++ b/blog/categories/public-service-announcement/index.html @@ -76,6 +76,28 @@
+

2018

+

2017

diff --git a/blog/categories/public/atom.xml b/blog/categories/public/atom.xml deleted file mode 100644 index 9e479e4a9d..0000000000 --- a/blog/categories/public/atom.xml +++ /dev/null @@ -1,46 +0,0 @@ - - - - <![CDATA[Category: Public | Home Assistant]]> - - - 2018-01-23T07:07:28+00:00 - https://home-assistant.io/ - - - - - Octopress - - - - <![CDATA[Clarification about Emulated Hue]]> - - 2018-01-21T01:00:00+00:00 - https://home-assistant.io/blog/2018/01/21/clarification-emulated-hue - Alexa type is deprecated and will be removed in a future version - -That config option should never have been called `type: alexa` but instead have been called `mode: legacy`. If you think about it, why would emulating something even have different modes it emulates based on the consumer? That means that one of the two emulation modes is incorrect. - -The old implementation was not 100% correct. It was correct enough to work with Alexa (the original target) but not with Google Home. When fixing Emulated Hue we added `type: alexa` to re-enable the old implementation so that people did not have to go through the trouble to re-add their Alexa devices. The option was deprecated to indicate that we would remove the incorrect emulation in the future. However, we forgot about actually following through with that. - -The mistake we made was calling the correct mode `google_home` although it had nothing to do with Google Home. It confused people and they kept adding `type: alexa` to their configuration, triggering the deprecation warning. - -The warning will be updated starting Home Assistant 0.62 and will also include a link to this blog post. - -More info: - -- To read about what was incorrect in the first version of Emulated Hue, take a look at the PR fixing it: [Re-org emulated_hue and fix google home][pr1]. -- Read the [documentation on how to configure Emulated Hue][eh-conf] - -[pr1]: https://github.com/home-assistant/home-assistant/pull/4708 -[pr2]: https://github.com/home-assistant/home-assistant/pull/5549 -[eh-conf]: https://home-assistant.io/components/emulated_hue/#configuration -]]> - - - diff --git a/blog/categories/public/index.html b/blog/categories/public/index.html deleted file mode 100644 index 6d5c95b4c5..0000000000 --- a/blog/categories/public/index.html +++ /dev/null @@ -1,218 +0,0 @@ - - - - - - - - - Category: Public - Home Assistant - - - - - - - - - - - - - - - - - - - - - - -
-
-
-
- - - Home Assistant - -
-
- - -
-
-
-
-
-
-
- -
- -
-
- - - - - - - - diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index b1c718703e..a3f7638989 100644 --- a/blog/categories/release-notes/atom.xml +++ b/blog/categories/release-notes/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Release-Notes | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/service/atom.xml b/blog/categories/service/atom.xml deleted file mode 100644 index 76df219a11..0000000000 --- a/blog/categories/service/atom.xml +++ /dev/null @@ -1,46 +0,0 @@ - - - - <![CDATA[Category: Service | Home Assistant]]> - - - 2018-01-23T07:07:28+00:00 - https://home-assistant.io/ - - - - - Octopress - - - - <![CDATA[Clarification about Emulated Hue]]> - - 2018-01-21T01:00:00+00:00 - https://home-assistant.io/blog/2018/01/21/clarification-emulated-hue - Alexa type is deprecated and will be removed in a future version - -That config option should never have been called `type: alexa` but instead have been called `mode: legacy`. If you think about it, why would emulating something even have different modes it emulates based on the consumer? That means that one of the two emulation modes is incorrect. - -The old implementation was not 100% correct. It was correct enough to work with Alexa (the original target) but not with Google Home. When fixing Emulated Hue we added `type: alexa` to re-enable the old implementation so that people did not have to go through the trouble to re-add their Alexa devices. The option was deprecated to indicate that we would remove the incorrect emulation in the future. However, we forgot about actually following through with that. - -The mistake we made was calling the correct mode `google_home` although it had nothing to do with Google Home. It confused people and they kept adding `type: alexa` to their configuration, triggering the deprecation warning. - -The warning will be updated starting Home Assistant 0.62 and will also include a link to this blog post. - -More info: - -- To read about what was incorrect in the first version of Emulated Hue, take a look at the PR fixing it: [Re-org emulated_hue and fix google home][pr1]. -- Read the [documentation on how to configure Emulated Hue][eh-conf] - -[pr1]: https://github.com/home-assistant/home-assistant/pull/4708 -[pr2]: https://github.com/home-assistant/home-assistant/pull/5549 -[eh-conf]: https://home-assistant.io/components/emulated_hue/#configuration -]]> - - - diff --git a/blog/categories/service/index.html b/blog/categories/service/index.html deleted file mode 100644 index 8feacd76cb..0000000000 --- a/blog/categories/service/index.html +++ /dev/null @@ -1,218 +0,0 @@ - - - - - - - - - Category: Service - Home Assistant - - - - - - - - - - - - - - - - - - - - - - -
-
-
-
- - - Home Assistant - -
-
- - -
-
-
-
-
-
-
- -
- -
-
- - - - - - - - diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 3599477ff0..7848474264 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 5f5efc57f4..d0bb2b7c43 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index c75749418f..5327d0e77f 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index b47751870c..40449205bc 100644 --- a/blog/categories/user-stories/atom.xml +++ b/blog/categories/user-stories/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: User-Stories | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index aa7e098457..67b8bc0a07 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 3c8da616f6..70f46708b9 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2018-01-23T07:07:28+00:00 + 2018-01-24T07:42:29+00:00 https://home-assistant.io/ diff --git a/blog/index.html b/blog/index.html index 407e236993..5338b056d6 100644 --- a/blog/index.html +++ b/blog/index.html @@ -79,9 +79,7 @@
    -
  • Public
    • -
  • Service
    • -
  • Announcement
    • +
  • Public-Service-Announcement

Categories

Service parameters:

    -
  • adsvar: Name of the variable on the ADS device. To access global variables on TwinCAT2 use a prepending dot .myvariable, for TwinCAT3 use -GBL.myvariable.
    • +
  • adsvar: Name of the variable on the ADS device. To access global variables on TwinCAT2 use a prepending dot .myvariable, for TwinCAT3 use GBL.myvariable.
  • adstype: Specify the type of the variable. Use one of the following: int, byte, uint, bool
  • value: The value that will be written in the variable.
diff --git a/components/alarm_control_panel.concord232/index.html b/components/alarm_control_panel.concord232/index.html index cd1d0dcc35..0e5d3fd34e 100644 --- a/components/alarm_control_panel.concord232/index.html +++ b/components/alarm_control_panel.concord232/index.html @@ -75,7 +75,7 @@

The concord232 platform provides integration with GE, Interlogix (and other brands) alarm panels that support the RS-232 Automation Control Panel interface module (or have it built in). Supported panels include Concord 4.

-

To use this platform, you will need to have the external concord232 client and server installed. The server must be running on the device which is connected to the automation module’s serial port. The client must be installed on the machine running Home Assistant. These may often be the same machine, but do not have to be. For additional details in setting up and testing the client and server, see https://github.com/JasonCarter80/concord232.

+

To use this platform, you will need to have the external concord232 client and server installed. The server must be running on the device which is connected to the automation module’s serial port. The client must be installed on the machine running Home Assistant. These may often be the same machine, but do not have to be. For additional details in setting up and testing the client and server, see https://github.com/JasonCarter80/concord232

To enable this platform in home assistant, add the following lines to your configuration.yaml:

# Example configuration.yaml entry
 alarm_control_panel:
diff --git a/components/alarm_control_panel.egardia/index.html b/components/alarm_control_panel.egardia/index.html
index 756d1cff16..40fd74b46c 100644
--- a/components/alarm_control_panel.egardia/index.html
+++ b/components/alarm_control_panel.egardia/index.html
@@ -104,20 +104,20 @@ You can change this, however, using the following procedure. This is a more adva
   
  • Once logged in, go to System Settings, Report and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. You can leave the port number set to 52010 or change it to anything you like. Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia’s / Woonveilig services. Maybe, that is just what you want. Make sure to save your settings by selecting ‘OK’.
    • 
   
  • On your Home Assistant machine run $ sudo python3 egardiaserver.py. Refer to the python-egardia repository for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. You will need the codes to include in your configuration.yaml. Make sure to change the status of your alarm to all states (disarm, arm, home) by all means possible (all users, remotes, web login, app) as well as trigger the alarm in all ways possible to get 100% coverage. Before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).
    • 
   
  • Once you have the codes, update your configuration.yaml:
-    
    # Example configuration.yaml entry
-alarm_control_panel:
+    
     # Example configuration.yaml entry
+ alarm_control_panel:
   - platform: egardia
     host: YOUR_HOST
     username: YOUR_USERNAME
     password: YOUR_PASSWORD
- report_server_enabled: True
- report_server_port: PORT_OF_EGARDIASERVER (optional, defaults to 52010)
- report_server_codes:
-   arm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
-   disarm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
-   home: XXXXXXXXXXXXXXXX
-   triggered: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
-   ignore: XXXXXXXXXXXXXXXX
+     report_server_enabled: True
+     report_server_port: PORT_OF_EGARDIASERVER (optional, defaults to 52010)
+     report_server_codes:
+       arm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
+       disarm: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
+       home: XXXXXXXXXXXXXXXX
+       triggered: XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXX
+       ignore: XXXXXXXXXXXXXXXX
 
    
     
    
   
    • 
diff --git a/components/binary_sensor.ping/index.html b/components/binary_sensor.ping/index.html
index 0c118f2969..c12de89909 100644
--- a/components/binary_sensor.ping/index.html
+++ b/components/binary_sensor.ping/index.html
@@ -95,6 +95,15 @@
   
  • round trip time min
    • 
   
  • round trip time max
    • 
 
+
    The default polling interval is 5 minutes. As many components based on the entity class, it is possible to overwrite this scan interval by specifying a scan_interval configuration key (value in seconds). In the example below we setup the ping binary sensor to poll the devices every 30 seconds.
    
+
    # Example configuration.yaml entry to ping host 192.168.0.1 with 2 packets every 30 seconds.
+binary_sensor:
+  - platform: ping
+    host: 192.168.0.1
+    count: 2
+    scan_interval: 30
+
    
+
    
 
    
 When run on Windows systems, the round trip time attributes are rounded to the nearest millisecond and the mdev value is unavailable.
 
    
diff --git a/developers/rest_api/index.html b/developers/rest_api/index.html
index e8378e32f6..207f4ab354 100644
--- a/developers/rest_api/index.html
+++ b/developers/rest_api/index.html
@@ -87,7 +87,7 @@
     http://IP_ADDRESS:8123/ENDPOINT
    -

    Another option is to use Python and the Requests module.

    +

    Another option is to use Python and the Requests module. =

    from requests import get
 
 url = 'http://localhost:8123/ENDPOINT'
@@ -124,8 +124,8 @@ You can append ?api_password=YOUR_PASSWORD
 
     GET /api/config
    
 
    Returns the current configuration as JSON.
    
-
    {  
-   "components":[  
+
    {
+   "components":[
       "sensor.cpuspeed",
       "frontend",
       "config.core",
@@ -157,7 +157,7 @@ You can append ?api_password=YOUR_PASSWORD"volume":"L"
    },
    "version":"0.56.2",
-   "whitelist_external_dirs":[  
+   "whitelist_external_dirs":[
       "/home/ha/.homeassistant/www",
       "/home/ha/.homeassistant/"
    ]
diff --git a/docs/installation/virtualenv/index.html b/docs/installation/virtualenv/index.html
index d20f39b312..4453dbfc89 100644
--- a/docs/installation/virtualenv/index.html
+++ b/docs/installation/virtualenv/index.html
@@ -92,6 +92,11 @@
   
   
  • Activate the virtual environment:
     
    $ source bin/activate
+
    
+    
    
+  
    • 
+  
  • Install wheel:
+    
    $ python3 -m pip install wheel
 
    
     
    
   
    • 
diff --git a/hassio/index.html b/hassio/index.html
index 8780acfa72..cb08dbaf02 100644
--- a/hassio/index.html
+++ b/hassio/index.html
@@ -8,7 +8,7 @@
     
     Hass.io - Home Assistant
     
-    
+    
     
     
     
@@ -16,12 +16,12 @@
     
     
     
-    
+    
     
     
     
     
-    
+    
     
     
     
@@ -92,7 +92,7 @@
   
 
    
 
     Upgrading
    
-
    Hass.io users can update Home Assistant via the ‘Hass.io’ page in the UI. However please note that Home Assistant updates take time to roll into the Hass.io builds. Therefore there is often a slight delay between the availability of a Home Assistant update and an update being available in Hass.io, be patient. When a Hass.io update is available it will be shown as available on the ‘Hass.io’ page in your UI.
    
+
    Hass.io users can update Home Assistant via the ‘Hass.io’ page in the UI. However please note that Home Assistant updates take time to roll into the Hass.io builds. Therefore there is often a slight delay between the availability of a Home Assistant update and an update being available in Hass.io, be patient. When a Hass.io update is available, it will be shown as available on the ‘Hass.io’ page in your UI.
    
 
    
 
 Hass.io dashboard with upgrade notification (under the hamburger menu -> Hass.io)
diff --git a/hassio/installation/index.html b/hassio/installation/index.html
index 3c1f7a1653..21cc040f34 100644
--- a/hassio/installation/index.html
+++ b/hassio/installation/index.html
@@ -90,7 +90,7 @@
   
  • Insert SD card to Raspberry Pi and turn it on. On first boot, it downloads the latest version of Home Assistant which takes ~20 minutes (slower/faster depending on the platform).
    • 
 
 
    
-Please remember to ensure you’re using an appropriate power supply with your Pi. Mobile chargers may not be suitable, since some are designed to only provide the full power with that manufacturer’s handsets.
+Please remember to ensure you’re using an appropriate power supply with your Pi. Mobile chargers may not be suitable since some are designed to only provide the full power with that manufacturer’s handsets.
 
    
 
    
 
      
@@ -106,7 +106,7 @@ If you copy over your existing Home Assistant configuration, make sure to enable
 
    
 
    
 
    
-When you use this installation method, some add-ons will not be available and the documentation might not work for your installation.
+When you use this installation method, some add-ons will not be available, and the documentation might not work for your installation.
 
    
 
    A detailed guide about running Hass.io as a virtual machine is available in the blog.
    diff --git a/hassio/installing_third_party_addons/index.html b/hassio/installing_third_party_addons/index.html index dd4009f765..41d44dacdf 100644 --- a/hassio/installing_third_party_addons/index.html +++ b/hassio/installing_third_party_addons/index.html @@ -80,7 +80,7 @@

    -Home Assistant cannot guarantee the quality or security of third party add-ons. Use at your own risk. +Home Assistant cannot guarantee the quality or security of third-party add-ons. Use at your own risk.

    diff --git a/hassio/run_local/index.html b/hassio/run_local/index.html index 2aab39b80a..2ff228ad86 100644 --- a/hassio/run_local/index.html +++ b/hassio/run_local/index.html @@ -8,7 +8,7 @@ Run local scripts - Home Assistant - + @@ -16,12 +16,12 @@ - + - + diff --git a/hassio/zwave/index.html b/hassio/zwave/index.html index acb50df886..be561c3626 100644 --- a/hassio/zwave/index.html +++ b/hassio/zwave/index.html @@ -90,10 +90,10 @@ usb_path: /dev/ttyAMA0 -

    HUSBZB-1:

    +

    HUSBZB-1

    zwave:
   usb_path: /dev/ttyUSB0
-  
+
 zha:
   usb_path: /dev/ttyUSB1
   database_path: /config/zigbee.db
diff --git a/help/index.html b/help/index.html
index 4764204459..9df94ba55a 100644
--- a/help/index.html
+++ b/help/index.html
@@ -137,7 +137,7 @@
   
  • Home Assistant – Open Source Python Home Automation Platform - January 2015
    • 
 
 
     Roadmap
    
-
    There is no explicit roadmap available but the public tracker can give you some insight into what is going on.
    
+
    There is no explicit roadmap available, but the public tracker can give you some insight into what is going on.
    diff --git a/sitemap.xml b/sitemap.xml index 14cc851b53..c64a743e1a 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -3910,7 +3910,7 @@ https://home-assistant.io/components/switch.hook/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/cookbook/automation_for_rainy_days/ @@ -4594,99 +4594,99 @@ https://home-assistant.io/docs/autostart/init.d/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/api/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/configuration/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/example_apps/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/installation/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/operation/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/reboot/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/running/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/tutorial/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/updating/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/appdaemon/windows/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/certificates/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/hadashboard/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/hass-configurator/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/ios/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/nginx/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/notebooks/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/scenegen/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/ecosystem/synology/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/tools/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/tools/dev-tools/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/tools/hass/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/docs/tools/scripts/ -2018-01-23T07:07:28+00:00 +2018-01-24T07:42:29+00:00 https://home-assistant.io/faq/after-upgrading/ @@ -5781,15 +5781,6 @@ https://home-assistant.io/blog/categories/announcements/ -https://home-assistant.io/blog/categories/public/ - - -https://home-assistant.io/blog/categories/service/ - - -https://home-assistant.io/blog/categories/announcement/ - - https://home-assistant.io/blog/posts/2/ @@ -5839,62 +5830,62 @@ https://home-assistant.io/demo/frontend.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/index.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00 https://home-assistant.io/static/mdi-demo.html -2018-01-23T07:06:49+00:00 +2018-01-24T07:41:45+00:00