diff --git a/atom.xml b/atom.xml index afc9248d6b..bf6fcb9f49 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ @@ -1477,7 +1477,7 @@ For Custom UI users: your custom UI will need to be updated before it can work w

Setting up Tor

-

Our documentation provides an detailed guide about seting up a Tor’s Hidden Service. The setup is straight-forward:

+

Our documentation provides a detailed guide about setting up a Tor’s Hidden Service. The setup is straight-forward:

  1. Install Tor. On a Debian-based system: $ sudo apt-get install tor. On Fedora: $ sudo dnf install tor
    2. @@ -1750,7 +1750,7 @@ INFO: ----------------------------------------------------------- -

    This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add an configuration variable to mqtt_ttn sensor which allows you to select the device.

    +

    This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add a configuration variable to mqtt_ttn sensor which allows you to select the device.

    ]]> @@ -2686,7 +2686,7 @@ Demo is running... -> CTRL + C to shutdown

    Breaking Changes

Using both types of iBeacons at the same time

-

Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I’ve been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.

+

Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I’ve been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.

diff --git a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html index 3788904f8a..0aed748e0c 100644 --- a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html +++ b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html @@ -87,7 +87,7 @@

When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!

-

Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can add it’s own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!

+

Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can add its own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!

We have also seen an exciting trend of people starting to visualize their Internet of Things data using Jupyter Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the blog post by @kireyeu shows an advanced usecase while our Notebooks in the Home Assistant Notebooks repository cover the basics.

This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!

The brand-new iFrame panel component allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.

diff --git a/blog/2016/08/16/we-have-apps-now/index.html b/blog/2016/08/16/we-have-apps-now/index.html index 731269d807..48f97338d7 100644 --- a/blog/2016/08/16/we-have-apps-now/index.html +++ b/blog/2016/08/16/we-have-apps-now/index.html @@ -98,13 +98,13 @@
  • Is it open and expandable?
  • Does it run locally without any reliance on the cloud?
    • -

    In my opinion, Home Assistant accomplishes the majority of these very well with a combination of Automations, Scripts and Templates, and it’s Restful API.

    +

    In my opinion, Home Assistant accomplishes the majority of these very well with a combination of Automations, Scripts and Templates, and its Restful API.

    So why AppDaemon? AppDaemon is not meant to replace Home Assistant Automations and Scripts, rather complement them. For a lot of things, automations work well and can be very succinct. However, there is a class of more complex automations for which they become harder to use, and appdeamon then comes into its own. It brings quite a few things to the table:

    If you need help…

    …don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

    diff --git a/blog/2017/02/03/babyphone/index.html b/blog/2017/02/03/babyphone/index.html index ca7013e1c2..80895c83d7 100644 --- a/blog/2017/02/03/babyphone/index.html +++ b/blog/2017/02/03/babyphone/index.html @@ -94,14 +94,14 @@

    We change the platform name for binary sensor in 0.38 from ffmpeg to ffmpeg_noise. Also all service going to component and was rename from binary_sensor.ffmpeg_xy to ffmpeg.xy.

    -

    On Raspbian Jessie, you can setup FFmpeg and install a icecast2 server using:

    +

    On Raspbian Jessie, you can setup FFmpeg and install an icecast2 server using:

    $ sudo echo "deb http://ftp.debian.org/debian jessie-backports main" >> /etc/apt/sources.list
 $ sudo apt-get update
 $ sudo apt-get -t jessie-backports install ffmpeg
 $ sudo apt-get install icecast2
    -

    We setup a icecast mount point for our babyphone and update /etc/icecast2/icecast.xml:

    +

    We setup an icecast mount point for our babyphone and update /etc/icecast2/icecast.xml:

    <mount>
     <mount-name>/babyphone.mp3</mount-name>
     <stream-name>Babyphone</stream-name>
@@ -152,7 +152,7 @@ We change the platform name for binary sensor in 0.38 from entity_id: binary_sensor.ffmpeg_noise
    -

    Trigger a alarm

    +

    Trigger an alarm

    Now we can make a lot stuff. Here is a simple example of an automation what should be possible with Sonos speakers.

    automation:
  - alias: 'Babyphone alarm on'
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 89272f3b4f..ff8e8e8846 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
@@ -124,8 +124,8 @@
 
    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?
    
 
    So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
    
 
    Update: the online tool can be found here.
    
-
    Customize has been reverted to it’s original config
    
-
    The old customize is back. The options to match by domain or using glob have been moved to it’s own options. It will now look like this:
    
+
    Customize has been reverted to its original config
    
+
    The old customize is back. The options to match by domain or using glob have been moved to its own options. It will now look like this:
    
 
    homeassistant:
   customize:
     light.kitchen:
diff --git a/blog/2017/10/07/release-55/index.html b/blog/2017/10/07/release-55/index.html
index 938a61dc6d..506e066be2 100644
--- a/blog/2017/10/07/release-55/index.html
+++ b/blog/2017/10/07/release-55/index.html
@@ -128,7 +128,7 @@
 
 
     Breaking Changes
    
 
      
-  
    • history_graph component: If your component used history.get_significant_states function then you need to adjust the string entitity_id parameter has been changed to a list of strings entity_ids parameter. (@andrey-git - #9472) (history_graph docs) (breaking change)
      • 
+  
    • history_graph component: If your component used history.get_significant_states function then you need to adjust the string entity_id parameter has been changed to a list of strings entity_ids parameter. (@andrey-git - #9472) (history_graph docs) (breaking change)
      • 
   
    • UPNP component: The external_port configuration option was removed. (@balloob - #9560) (upnp docs) (breaking change)
      • 
   
    • New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by  “_” and no longer “ “. (@w1ll1am23 - #9303) (wink docs) (binary_sensor.wink docs) (lock.wink docs) (breaking change)
      • 
   
    • TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. (@djchen - #9607) (switch.tplink docs) (breaking change)
      • 
diff --git a/blog/2017/11/10/ttn-with-mqtt/index.html b/blog/2017/11/10/ttn-with-mqtt/index.html
index 5430345a87..a431e34a88 100644
--- a/blog/2017/11/10/ttn-with-mqtt/index.html
+++ b/blog/2017/11/10/ttn-with-mqtt/index.html
@@ -251,7 +251,7 @@
     state_topic: "home/ttn/garden_temp"
 
    
 
    
-
    This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add an configuration variable to mqtt_ttn sensor which allows you to select the device.
    
+
    This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add a configuration variable to mqtt_ttn sensor which allows you to select the device.
    
 
 
    
 
    
diff --git a/blog/2017/11/12/tor/index.html b/blog/2017/11/12/tor/index.html
index 09a6b00e34..c9d39c62cb 100644
--- a/blog/2017/11/12/tor/index.html
+++ b/blog/2017/11/12/tor/index.html
@@ -97,7 +97,7 @@
 
    The most amazing part? It is super easy to set up!
    
 
 
     Setting up Tor
    
-
    Our documentation provides an detailed guide about seting up a Tor’s Hidden Service. The setup is straight-forward:
    
+
    Our documentation provides a detailed guide about setting up a Tor’s Hidden Service. The setup is straight-forward:
    
 
      
   
    1. Install Tor. On a Debian-based system: $ sudo apt-get install tor. On Fedora: $ sudo dnf install tor
      2. 
   
    2. 
diff --git a/blog/archives/index.html b/blog/archives/index.html
index e174945fbb..22435307d4 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -443,7 +443,7 @@
    -

    MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported

    +

    MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported

    diff --git a/blog/categories/announcements/atom.xml b/blog/categories/announcements/atom.xml index dc4202c8e5..631e603b8c 100644 --- a/blog/categories/announcements/atom.xml +++ b/blog/categories/announcements/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Announcements | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 53d3df3254..d6a09631a1 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index 1df673d335..3970eff207 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-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ @@ -129,7 +129,7 @@ script: ### Using both types of iBeacons at the same time -Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home. +Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.

    diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 24cd2d8af7..9bb59a61c9 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index 07adaf00c1..053127a2a4 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-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ @@ -181,7 +181,7 @@ The most amazing part? It is super easy to set up! ## Setting up Tor -Our [documentation](/docs/ecosystem/tor/) provides an detailed guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward: +Our [documentation](/docs/ecosystem/tor/) provides a detailed guide about setting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward: 1. Install Tor. On a Debian-based system: `$ sudo apt-get install tor`. On Fedora: `$ sudo dnf install tor` 2. Modify Tor's main configuration file `/etc/tor/torrc` to include the following lines: @@ -446,7 +446,7 @@ sensor: state_topic: "home/ttn/garden_temp" ``` -This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add an configuration variable to `mqtt_ttn` sensor which allows you to select the device. +This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add a configuration variable to `mqtt_ttn` sensor which allows you to select the device. ]]> diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index e7e3b17003..0197269649 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ @@ -129,7 +129,7 @@ script: ### Using both types of iBeacons at the same time -Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home. +Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.

    diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index 0da0817cf2..d85aac7cef 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-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index 99c2c5ae1f..3a7f8b7ed6 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-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/media/atom.xml b/blog/categories/media/atom.xml index ce59965f7b..489802a2b2 100644 --- a/blog/categories/media/atom.xml +++ b/blog/categories/media/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Media | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/merchandise/atom.xml b/blog/categories/merchandise/atom.xml index d78021b429..77ad7b7403 100644 --- a/blog/categories/merchandise/atom.xml +++ b/blog/categories/merchandise/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Merchandise | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 52a97fc57d..bc52399345 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index befcc22171..4113307785 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ @@ -307,7 +307,7 @@ Here is the final sequence of events: There are a lot of stops along the way for these events, but each piece is a simple translation layer to shuttle the events between systems. ### Future Improvements -- **Raspberry pi**: There is a lot of interest in getting this running on the Raspberry Pi. It only requires binaries compiled for ARM, so we plan to get ARM-compatible versions of the containers going at some point. +- **Raspberry Pi**: There is a lot of interest in getting this running on the Raspberry Pi. It only requires binaries compiled for ARM, so we plan to get ARM-compatible versions of the containers going at some point. - **Authentication for MQTT**: At the moment, the MQTT bridge doesn't understand how to authenticate to MQTT, so only unauthenticated MQTT is supported. This is mitigated to some degree if you use our Docker Compose config, because MQTT's port is not actually shared publicly. - **Authentication for MQTT Bridge**: Right now the bridge expects that anyone subscribing is the SmartThings hub. This could use proper authentication. diff --git a/blog/categories/organization/atom.xml b/blog/categories/organization/atom.xml index dc9cb7e018..dfef116a60 100644 --- a/blog/categories/organization/atom.xml +++ b/blog/categories/organization/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organization | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 81b45cf3c2..67abc351ef 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ @@ -129,7 +129,7 @@ script: ### Using both types of iBeacons at the same time -Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home. +Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.

    diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index b8e3e33580..a30d983de6 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-28T17:56:25+00:00 + 2018-01-28T21:52:35+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 1670cd9d0e..4ed96c12ee 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-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 0fd08234b4..582a5008bc 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-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html index 601f938c39..d924053611 100644 --- a/blog/categories/release-notes/index.html +++ b/blog/categories/release-notes/index.html @@ -1412,7 +1412,7 @@

    -

    MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported

    +

    MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported

    diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index a71ee96aab..ceb0743bf9 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index ebc1d0fd02..ee73d6af61 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index 105c999b00..cdc9d932b2 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index e91e13c3d3..03c13dfc5a 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-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index d48af2080a..1355162b7b 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index ba8e164443..3f23c57f48 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2018-01-28T17:56:25+00:00 + 2018-01-28T21:52:35+00:00 https://home-assistant.io/ diff --git a/blog/posts/10/index.html b/blog/posts/10/index.html index 404eeaa9a1..98a4a9369d 100644 --- a/blog/posts/10/index.html +++ b/blog/posts/10/index.html @@ -297,7 +297,7 @@ Heatmap

    When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!

    -

    Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can add it’s own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!

    +

    Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can add its own page to the frontend. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!

    We have also seen an exciting trend of people starting to visualize their Internet of Things data using Jupyter Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the blog post by @kireyeu shows an advanced usecase while our Notebooks in the Home Assistant Notebooks repository cover the basics.

    This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!

    The brand-new iFrame panel component allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.

    diff --git a/blog/posts/12/index.html b/blog/posts/12/index.html index b385c8be72..59c42d938b 100644 --- a/blog/posts/12/index.html +++ b/blog/posts/12/index.html @@ -312,7 +312,7 @@

    It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs.

    -

    Since the last release we have moved all Home Assistant source code etc into it’s own organization on GitHub. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.

    +

    Since the last release we have moved all Home Assistant source code etc into its own organization on GitHub. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.

      @@ -444,7 +444,7 @@
    -

    Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we’ve been hard at work to introduce config validation! Especially huge thanks to @jaharkes for his hard work on this. Config validation is still in it’s early stages. More common platforms and components have been added but we didn’t do everything yet.

    +

    Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we’ve been hard at work to introduce config validation! Especially huge thanks to @jaharkes for his hard work on this. Config validation is still in its early stages. More common platforms and components have been added but we didn’t do everything yet.

    When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We’re looking into options to make it more clear - it is a work in progress.

    Another big thing is the addition of GTFS support. You probably don’t know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.

    diff --git a/blog/posts/16/index.html b/blog/posts/16/index.html index 7099799dd8..645d381397 100644 --- a/blog/posts/16/index.html +++ b/blog/posts/16/index.html @@ -148,7 +148,7 @@

    - MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported + MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported

    @@ -166,7 +166,7 @@
    -

    It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.

    +

    It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documenting all the various components.

    MQTT Support The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.

    # Example configuration.yaml entry
diff --git a/blog/posts/7/index.html b/blog/posts/7/index.html
index dab59640f0..ff4c80e9cc 100644
--- a/blog/posts/7/index.html
+++ b/blog/posts/7/index.html
@@ -357,8 +357,8 @@ Screenshot of all the different functionality the IP webcam integration offers.
 
    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?
    
 
    So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
    
 
    Update: the online tool can be found here.
    
-
    Customize has been reverted to it’s original config
    
-
    The old customize is back. The options to match by domain or using glob have been moved to it’s own options. It will now look like this:
    
+
    Customize has been reverted to its original config
    
+
    The old customize is back. The options to match by domain or using glob have been moved to its own options. It will now look like this:
    
 
    homeassistant:
   customize:
     light.kitchen:
diff --git a/blog/posts/8/index.html b/blog/posts/8/index.html
index 9562dbdd4a..55b1561873 100644
--- a/blog/posts/8/index.html
+++ b/blog/posts/8/index.html
@@ -243,7 +243,7 @@
   
  • Due to massive improvements of the Wink integration, the names of your binary sensors will change and new devices can show up.
    • 
   
  • The MySensors component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.
    • 
   
  • The Sonos service sonos_group_players was removed. Use now sonos_join for this function.
    • 
-  
  • TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. HASH_LANG_PLATFORM.xxx -> HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with - on exiting platforms.
    • 
+  
  • TTS cache have change for the last time. Files use now also an option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. HASH_LANG_PLATFORM.xxx -> HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with - on exiting platforms.
    • 
 
 
     If you need help…
    
 
    …don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
    
diff --git a/blog/posts/9/index.html b/blog/posts/9/index.html
index a20e84bf46..e070b64040 100644
--- a/blog/posts/9/index.html
+++ b/blog/posts/9/index.html
@@ -545,7 +545,7 @@
 
    
   
 
    
-
    As the results are processed on-the-fly you still need to use the data from your database for a in-depth analysis of your stored information. Check the latest notebook for doing statistics with your Home Assistant database.
    
+
    As the results are processed on-the-fly you still need to use the data from your database for an in-depth analysis of your stored information. Check the latest notebook for doing statistics with your Home Assistant database.
    
 
     REST! We don’t…
    
 
    There was a lot of work done on our implementation which are working with RESTful APIs. @w1ll1am23 extended the aREST platforms to display if an aREST unit is available or not. The aREST implementations are now covered by the configuration check as well. Please check the Breaking changes section for more details.
    
 
    The REST sensor supports now HTTP authentication (basic and digest) and custom headers. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.
    
diff --git a/components/alarmdecoder/index.html b/components/alarmdecoder/index.html
index a8a68a68b5..1d92df3460 100644
--- a/components/alarmdecoder/index.html
+++ b/components/alarmdecoder/index.html
@@ -79,7 +79,7 @@
 
    There is currently support for the following device types within Home Assistant:
    
 
 
    This is a fully event-based component. Any event sent by the AlarmDecoder device will be immediately reflected within Home Assistant.
    
diff --git a/components/arduino/index.html b/components/arduino/index.html
index 2e205144c5..44489bccdd 100644
--- a/components/arduino/index.html
+++ b/components/arduino/index.html
@@ -165,7 +165,7 @@ A word of caution: The Arduino boards are not storing states. This means that wi
             PiFace Digital I/O
         
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/bbb_gpio/index.html b/components/bbb_gpio/index.html
index 12fe07f335..5cf8ba4109 100644
--- a/components/bbb_gpio/index.html
+++ b/components/bbb_gpio/index.html
@@ -135,7 +135,7 @@
             PiFace Digital I/O
         
    • 
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/binary_sensor.abode/index.html b/components/binary_sensor.abode/index.html
index 7b16f94177..118dc189ee 100644
--- a/components/binary_sensor.abode/index.html
+++ b/components/binary_sensor.abode/index.html
@@ -260,7 +260,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.ads/index.html b/components/binary_sensor.ads/index.html
index 5761460780..4847ebfe02 100644
--- a/components/binary_sensor.ads/index.html
+++ b/components/binary_sensor.ads/index.html
@@ -270,7 +270,7 @@ file:
    
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.alarmdecoder/index.html b/components/binary_sensor.alarmdecoder/index.html
index e5ef9681a3..b51e641bf7 100644
--- a/components/binary_sensor.alarmdecoder/index.html
+++ b/components/binary_sensor.alarmdecoder/index.html
@@ -244,7 +244,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.android_ip_webcam/index.html b/components/binary_sensor.android_ip_webcam/index.html
index e5fc9f2cc7..9a952b701b 100644
--- a/components/binary_sensor.android_ip_webcam/index.html
+++ b/components/binary_sensor.android_ip_webcam/index.html
@@ -256,7 +256,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index c4864ea273..d71737019a 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    The arest binary sensor platform allows you to get all data from your devices (like Arduinos with a ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the aREST RESTful framework.
    
+  
    The arest binary sensor platform allows you to get all data from your devices (like Arduinos with an ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the aREST RESTful framework.
    
 
    To use your aREST binary sensor in your installation, add the following to your configuration.yaml file:
    
 
    # Example configuration.yaml entry
 binary_sensor:
@@ -270,7 +270,7 @@ This sensor is not suitable for fast state changes because there is a high possi
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.aurora/index.html b/components/binary_sensor.aurora/index.html
index b20530007e..7a12986340 100644
--- a/components/binary_sensor.aurora/index.html
+++ b/components/binary_sensor.aurora/index.html
@@ -243,7 +243,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.axis/index.html b/components/binary_sensor.axis/index.html
index c8b2ecf35e..37c97f0158 100644
--- a/components/binary_sensor.axis/index.html
+++ b/components/binary_sensor.axis/index.html
@@ -249,7 +249,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.bayesian/index.html b/components/binary_sensor.bayesian/index.html
index 29726674e9..ad5685d493 100644
--- a/components/binary_sensor.bayesian/index.html
+++ b/components/binary_sensor.bayesian/index.html
@@ -298,7 +298,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.bbb_gpio/index.html b/components/binary_sensor.bbb_gpio/index.html
index a271ea05d8..98f6633171 100644
--- a/components/binary_sensor.bbb_gpio/index.html
+++ b/components/binary_sensor.bbb_gpio/index.html
@@ -266,7 +266,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.blink/index.html b/components/binary_sensor.blink/index.html
index 0a45eb379a..d34259d5a1 100644
--- a/components/binary_sensor.blink/index.html
+++ b/components/binary_sensor.blink/index.html
@@ -241,7 +241,7 @@ To get your Blink binary sensors working with Home Assistant, follow the instruc
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.bloomsky/index.html b/components/binary_sensor.bloomsky/index.html
index 54f76f330e..844c839ad6 100644
--- a/components/binary_sensor.bloomsky/index.html
+++ b/components/binary_sensor.bloomsky/index.html
@@ -261,7 +261,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.command_line/index.html b/components/binary_sensor.command_line/index.html
index 2dd42d94bb..62486c264e 100644
--- a/components/binary_sensor.command_line/index.html
+++ b/components/binary_sensor.command_line/index.html
@@ -298,7 +298,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.concord232/index.html b/components/binary_sensor.concord232/index.html
index 7aa4f1b83f..321f9c14b1 100644
--- a/components/binary_sensor.concord232/index.html
+++ b/components/binary_sensor.concord232/index.html
@@ -244,7 +244,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.deconz/index.html b/components/binary_sensor.deconz/index.html
index 5233ddef5e..b170fdfbcf 100644
--- a/components/binary_sensor.deconz/index.html
+++ b/components/binary_sensor.deconz/index.html
@@ -267,7 +267,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.ecobee/index.html b/components/binary_sensor.ecobee/index.html
index 8761d84b66..d951ec1623 100644
--- a/components/binary_sensor.ecobee/index.html
+++ b/components/binary_sensor.ecobee/index.html
@@ -248,7 +248,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.eight_sleep/index.html b/components/binary_sensor.eight_sleep/index.html
index 8727ff8e27..e80fccb02a 100644
--- a/components/binary_sensor.eight_sleep/index.html
+++ b/components/binary_sensor.eight_sleep/index.html
@@ -240,7 +240,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.enocean/index.html b/components/binary_sensor.enocean/index.html
index 1cd110418c..54da94765f 100644
--- a/components/binary_sensor.enocean/index.html
+++ b/components/binary_sensor.enocean/index.html
@@ -281,7 +281,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.envisalink/index.html b/components/binary_sensor.envisalink/index.html
index 6b6407a8a4..6e79166c56 100644
--- a/components/binary_sensor.envisalink/index.html
+++ b/components/binary_sensor.envisalink/index.html
@@ -244,7 +244,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.ffmpeg_motion/index.html b/components/binary_sensor.ffmpeg_motion/index.html
index 8460366951..dbabc91cda 100644
--- a/components/binary_sensor.ffmpeg_motion/index.html
+++ b/components/binary_sensor.ffmpeg_motion/index.html
@@ -260,7 +260,7 @@ If the ffmpeg process is broken, the sens
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.ffmpeg_noise/index.html b/components/binary_sensor.ffmpeg_noise/index.html
index 426adcbd6a..e26a99518f 100644
--- a/components/binary_sensor.ffmpeg_noise/index.html
+++ b/components/binary_sensor.ffmpeg_noise/index.html
@@ -251,7 +251,7 @@ If the ffmpeg process is broken, the sens
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.flic/index.html b/components/binary_sensor.flic/index.html
index 1a2a3b3a27..3ea9244be0 100644
--- a/components/binary_sensor.flic/index.html
+++ b/components/binary_sensor.flic/index.html
@@ -272,7 +272,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.gc100/index.html b/components/binary_sensor.gc100/index.html
index 649a41a08a..c7d62f27e8 100644
--- a/components/binary_sensor.gc100/index.html
+++ b/components/binary_sensor.gc100/index.html
@@ -8,7 +8,7 @@
     
     gc100 Binary Sensor - Home Assistant
     
-    
+    
     
     
     
@@ -16,12 +16,12 @@
     
     
     
-    
+    
     
     
     
     
-    
+    
     
     
     
@@ -250,7 +250,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.hikvision/index.html b/components/binary_sensor.hikvision/index.html
index 4001a4d8e1..ed7fcfe13e 100644
--- a/components/binary_sensor.hikvision/index.html
+++ b/components/binary_sensor.hikvision/index.html
@@ -321,7 +321,7 @@ binary_sensor.home_line_crossing_2
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.hive/index.html b/components/binary_sensor.hive/index.html
index 6fa6ff2342..b231f7e7dc 100644
--- a/components/binary_sensor.hive/index.html
+++ b/components/binary_sensor.hive/index.html
@@ -256,7 +256,7 @@ Full configuration details can be found on the main 
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.homematic/index.html b/components/binary_sensor.homematic/index.html
index 60c168c0c0..4f5e125cf9 100644
--- a/components/binary_sensor.homematic/index.html
+++ b/components/binary_sensor.homematic/index.html
@@ -252,7 +252,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.http/index.html b/components/binary_sensor.http/index.html
index 3cb65f60ee..ec819d65ed 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -288,7 +288,7 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.ihc/index.html b/components/binary_sensor.ihc/index.html
index 7333a03509..a0037ea622 100644
--- a/components/binary_sensor.ihc/index.html
+++ b/components/binary_sensor.ihc/index.html
@@ -299,7 +299,7 @@ For more information about IHC resource ids see show_on_map Nest component configured to u
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.netatmo/index.html b/components/binary_sensor.netatmo/index.html
index 1fc9a00e8f..e818350c9a 100644
--- a/components/binary_sensor.netatmo/index.html
+++ b/components/binary_sensor.netatmo/index.html
@@ -290,7 +290,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.nx584/index.html b/components/binary_sensor.nx584/index.html
index 65dfb286b1..20dcb393a2 100644
--- a/components/binary_sensor.nx584/index.html
+++ b/components/binary_sensor.nx584/index.html
@@ -266,7 +266,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.octoprint/index.html b/components/binary_sensor.octoprint/index.html
index 14841b9c3d..d313befea5 100644
--- a/components/binary_sensor.octoprint/index.html
+++ b/components/binary_sensor.octoprint/index.html
@@ -260,7 +260,7 @@ You must have the OctoPrint component confi
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.pilight/index.html b/components/binary_sensor.pilight/index.html
index cc67969a16..eb8b82c63b 100644
--- a/components/binary_sensor.pilight/index.html
+++ b/components/binary_sensor.pilight/index.html
@@ -272,7 +272,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.ping/index.html b/components/binary_sensor.ping/index.html
index a704fa086f..46fba4fd94 100644
--- a/components/binary_sensor.ping/index.html
+++ b/components/binary_sensor.ping/index.html
@@ -265,7 +265,7 @@ When run on Windows systems, the round trip time attributes are rounded to the n
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.raincloud/index.html b/components/binary_sensor.raincloud/index.html
index 8c225c83ec..6983d20ca3 100644
--- a/components/binary_sensor.raincloud/index.html
+++ b/components/binary_sensor.raincloud/index.html
@@ -257,7 +257,7 @@
             RFXtrx Binary Sensor
         
    • 
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/binary_sensor.raspihats/index.html b/components/binary_sensor.raspihats/index.html
index a8bce81003..7cc447efad 100644
--- a/components/binary_sensor.raspihats/index.html
+++ b/components/binary_sensor.raspihats/index.html
@@ -8,7 +8,7 @@
     
     Raspihats Binary Sensor - Home Assistant
     
-    
+    
     
     
     
@@ -16,12 +16,12 @@
     
     
     
-    
+    
     
     
     
     
-    
+    
     
     
     
@@ -143,7 +143,7 @@
 70: -- -- -- -- -- -- -- 77
 
    • 
 
    
-
    For more details about the raspihats add-on boards for Raspberry PI, visit raspihats.com.
    
+
    For more details about the raspihats add-on boards for Raspberry Pi, visit raspihats.com.

    Local image with Hass.io

    -

    You can show an static image with this platform. Just place the image here: /config/www/your_image.png

    +

    You can show a static image with this platform. Just place the image here: /config/www/your_image.png

    camera:
   - platform: generic
     name: Some Image
diff --git a/components/climate.mqtt/index.html b/components/climate.mqtt/index.html
index 77759688ae..b832f6386f 100644
--- a/components/climate.mqtt/index.html
+++ b/components/climate.mqtt/index.html
@@ -252,7 +252,7 @@
     mode_state_template: "{{ value_json }}"
    -

    This will parse the incoming "auto" as JSON, resulting in auto. Obvisouly, in this case you could also just set value_template: "{{ value_json }}".

    +

    This will parse the incoming "auto" as JSON, resulting in auto. Obviously, in this case you could also just set value_template: "{{ value_json }}".

    Example

    A full configuration example looks like the one below.

    # Full example configuration.yaml entry
diff --git a/components/climate.oem/index.html b/components/climate.oem/index.html
index 4d1da70c07..59cdc6eb4e 100644
--- a/components/climate.oem/index.html
+++ b/components/climate.oem/index.html
@@ -75,7 +75,7 @@
   
   
    
   
    This platform supports the ESP82666 based “WiFi MQTT Relay / Thermostat” sold by OpenEnergyMonitor. The underlying library only supports this single relay variant of the original device.
    
-
    This platform controls the setpoint of the thermostat in it’s “manual” mode, therefore there is a configuration option the away setpoint.
    
+
    This platform controls the setpoint of the thermostat in its “manual” mode, therefore there is a configuration option the away setpoint.
    
 
    To set it up, add the following information to your configuration.yaml file:
    
 
    # Example configuration.yaml entry
 climate oem:
diff --git a/components/cover.mqtt/index.html b/components/cover.mqtt/index.html
index b4117792a2..1a7241b58e 100644
--- a/components/cover.mqtt/index.html
+++ b/components/cover.mqtt/index.html
@@ -190,7 +190,7 @@
     
     
     tilt_closed_value
    
     
    
-      
    (integer)(Optional)The value that will be sent on an close_cover_tilt command.
    
+      
    (integer)(Optional)The value that will be sent on a close_cover_tilt command.
    
       
    Default value: 0
    
     
    
     
     tilt_opened_value
    
diff --git a/components/cover.rflink/index.html b/components/cover.rflink/index.html
index b67d080d4c..f1a837b025 100644
--- a/components/cover.rflink/index.html
+++ b/components/cover.rflink/index.html
@@ -135,7 +135,7 @@ RTS Record: 15 Address: FFFFFF RC: FFFF
 
      
   
    • name (Optional): Name for the device, defaults to Rflink ID.
      • 
   
    • aliases (Optional): Alternative Rflink ID’s this device is known by.
      • 
-  
    • fire_event (Optional): Fire an button_pressed event if this device is turned on or off (default: False).
      • 
+  
    • fire_event (Optional): Fire a button_pressed event if this device is turned on or off (default: False).
      • 
   
    • signal_repetitions (Optional): Repeat every Rflink command this number of times (default: 1).
      • 
   
    • fire_event_ (Optional): Set default fire_event for RFLink switch devices (see below).
      • 
   
    • signal_repetitions (Optional): Set default signal_repetitions for RFLink switch devices (see below).
      • 
diff --git a/components/cover.rpi_gpio/index.html b/components/cover.rpi_gpio/index.html
index b5f0ddadd9..8a59243e44 100644
--- a/components/cover.rpi_gpio/index.html
+++ b/components/cover.rpi_gpio/index.html
@@ -149,13 +149,13 @@
           
      Related components
      
           
     
    
diff --git a/components/device_tracker.icloud/index.html b/components/device_tracker.icloud/index.html
index ef0e013cc0..f7fa2820f4 100644
--- a/components/device_tracker.icloud/index.html
+++ b/components/device_tracker.icloud/index.html
@@ -104,7 +104,7 @@ You may receive an email from Apple stating that someone has logged into your ac
 
      
   
    • icloud_update: This service can be used to ask for an update of a certain iDevice. The account_name and device_name are optional.
      • 
   
    • icloud_lost_iphone: This service will play the Lost iPhone sound on a certain iDevice. The account_name and device_name are optional.
      • 
-  
    • icloud_set_interval: This service will change the dynamic interval of an iDevice. The account_name and device_name are optional. If interval is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If interval isn’t used in the service_data, the interval for that iDevice will revert back to it’s default dynamic interval based on it’s current zone, it’s distance towards home and it’s battery level.
      • 
+  
    • icloud_set_interval: This service will change the dynamic interval of an iDevice. The account_name and device_name are optional. If interval is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If interval isn’t used in the service_data, the interval for that iDevice will revert back to its default dynamic interval based on its current zone, its distance towards home and its battery level.
      • 
   
    • icloud_reset_account: This service can be used to reset an iCloud account. This is helpful when not all devices are being found by the component or if you have added a new iDevice to your account. The account_name is optional.
      • 
 
    
 
diff --git a/components/device_tracker.owntracks/index.html b/components/device_tracker.owntracks/index.html
index c9cd0b1207..b9af04156a 100644
--- a/components/device_tracker.owntracks/index.html
+++ b/components/device_tracker.owntracks/index.html
@@ -136,7 +136,7 @@ The Android app for OwnTracks is no longer developed or supported, Zanzito is a
 
     Using Owntracks iBeacons to track devices
    
 
    iBeacons don’t need to be stationary. You could put one on your key ring, or in your car.
    
 
    When your phone sees a mobile iBeacon that it knows about, it will tell HA the location of that iBeacon. If your phone moves while you are connected to the iBeacon, HA will update the location of the iBeacon. But when your phone loses the connection, HA will stop updating the iBeacon location.
    
-
    To use mobile iBeacons with HA, you just set up a region that doesn’t match your Zone names. If HA sees an entry event for a iBeacon region that doesn’t match a Zone name (say keys) - it will start tracking it, calling the device device_tracker.beacon_keys).
    
+
    To use mobile iBeacons with HA, you just set up a region that doesn’t match your Zone names. If HA sees an entry event for an iBeacon region that doesn’t match a Zone name (say keys) - it will start tracking it, calling the device device_tracker.beacon_keys).
    
 
    This allows you to write zone automations for devices that can’t track themselves (for example alert me if I leave the house and my keys are still at home). Another example would be open the gates if my car arrives home.
    
 
     Using mobile and fixed iBeacons together
    
 
    You can use iBeacons of both types together, so if you have a Zone drive with an iBeacon region called -drive and you arrive home with a mobile iBeacon called -car, then device_tracker.beacon_car will be set to a state of drive.
    
diff --git a/components/device_tracker.tado/index.html b/components/device_tracker.tado/index.html
index c98174dd73..6b082b4625 100644
--- a/components/device_tracker.tado/index.html
+++ b/components/device_tracker.tado/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    The tado device tracker is using the Tado Smart Thermostat and it’s support for person presence detection based on smartphone location by geofencing.
    
+  
    The tado device tracker is using the Tado Smart Thermostat and its support for person presence detection based on smartphone location by geofencing.
    
 
    This tracker uses the Tado API to determine if a mobile device is at home. It tracks all devices in your home that Tado knows about.
    
 
    To use the Tado platform in your installation, add the following to your configuration.yaml file:
    
 
    # Example configuration.yaml entry for Tado
diff --git a/components/envisalink/index.html b/components/envisalink/index.html
index f793bf814a..4293722dc6 100644
--- a/components/envisalink/index.html
+++ b/components/envisalink/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    The envisalink component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and it’s sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4.
    
+  
    The envisalink component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4.
    
 
    Please visit the eyezon website for further information about the evl3 and evl4 boards.
    
 
    There is currently support for the following device types within Home Assistant:
    
 
      
diff --git a/components/hue/index.html b/components/hue/index.html
index 632ee3d31e..15288637cb 100644
--- a/components/hue/index.html
+++ b/components/hue/index.html
@@ -134,7 +134,7 @@
 
      
 
      More information can be found on the Philips Hue API documentation website.
      
 
       Using Hue Scenes in Home Assistant
      
-
      The Hue platform has it’s own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you’ve never used, almost all very poorly named.
      
+
      The Hue platform has its own concept of scenes for setting the colors of a group of lights at once. Hue Scenes are very cheap, get created by all kinds of apps (as it is the only way to have 2 or more lights change at the same time), and are rarely deleted. A typical Hue hub might have hundreds of scenes stored in them, many that you’ve never used, almost all very poorly named.
      
 
      To avoid user interface overload we don’t expose scenes directly. Instead there is a hue.hue_activate_scene service which can be used by automation or script components.
 This will have all the bulbs transitioned at once, instead of one at a time using standard scenes in Home Assistant.
      
 
      For instance:
      
diff --git a/components/image_processing.microsoft_face_detect/index.html b/components/image_processing.microsoft_face_detect/index.html
index 99c2379957..ace0888b97 100644
--- a/components/image_processing.microsoft_face_detect/index.html
+++ b/components/image_processing.microsoft_face_detect/index.html
@@ -74,7 +74,7 @@
     
   
   
      
-  
      The microsoft_face_detect image processing platform allows you to use the Microsoft Face Identify API through Home Assistant. This platform enables you do detect face on camera and fire a event with attributes.
      
+  
      The microsoft_face_detect image processing platform allows you to use the Microsoft Face Identify API through Home Assistant. This platform enables you do detect face on camera and fire an event with attributes.
      
 
      Please refer to the component configuration on how to setup the API key.
      
 
      For using the result inside an automation rule, take a look at the component page.
      
 
       Configuration Home Assistant
      
diff --git a/components/image_processing.microsoft_face_identify/index.html b/components/image_processing.microsoft_face_identify/index.html
index 585d23822b..1ece672a0e 100644
--- a/components/image_processing.microsoft_face_identify/index.html
+++ b/components/image_processing.microsoft_face_identify/index.html
@@ -74,7 +74,7 @@
     
   
   
      
-  
      The microsoft_face_identify image processing platform lets you use Microsoft Face identify API through Home Assistant. This platform allow you do identify persons on camera and fire a event with identify persons.
      
+  
      The microsoft_face_identify image processing platform lets you use Microsoft Face identify API through Home Assistant. This platform allow you do identify persons on camera and fire an event with attributes.
      
 
      Please refer to the component configuration on how to setup the API key.
      
 
      For using the result inside an automation rule, take a look at the component page.
      
 
       Configuration Home Assistant
      
diff --git a/components/index.html b/components/index.html
index 06cca2d01a..ea4dc1ec4f 100644
--- a/components/index.html
+++ b/components/index.html
@@ -777,11 +777,11 @@ var allComponents = [
 {url:"/components/switch.rainmachine/", title:"RainMachine Switch", cat:"switch", featured: false, v: "0.51", logo: "rainmachine.png"},
 {url:"/components/binary_sensor.random/", title:"Random Binary Sensor", cat:"sensor", featured: false, v: "0.57", logo: "home-assistant.png"},
 {url:"/components/sensor.random/", title:"Random Sensor", cat:"sensor", featured: false, v: "0.32", logo: "home-assistant.png"},
-{url:"/components/rpi_gpio/", title:"Raspberry PI GPIO", cat:"diy", featured: false, v: "0.7", logo: "raspberry-pi.png"},
-{url:"/components/binary_sensor.rpi_gpio/", title:"Raspberry PI GPIO Binary Sensor", cat:"binary-sensor", featured: false, v: "0.7", logo: "raspberry-pi.png"},
-{url:"/components/switch.rpi_gpio/", title:"Raspberry PI GPIO Switch", cat:"switch", featured: false, v: "0.7", logo: "raspberry-pi.png"},
 {url:"/components/camera.rpi_camera/", title:"Raspberry Pi Camera", cat:"camera", featured: false, v: "0.17", logo: "raspberry-pi.png"},
 {url:"/components/cover.rpi_gpio/", title:"Raspberry Pi Cover", cat:"cover", featured: false, v: "0.23", logo: "raspberry-pi.png"},
+{url:"/components/rpi_gpio/", title:"Raspberry Pi GPIO", cat:"diy", featured: false, v: "0.7", logo: "raspberry-pi.png"},
+{url:"/components/binary_sensor.rpi_gpio/", title:"Raspberry Pi GPIO Binary Sensor", cat:"binary-sensor", featured: false, v: "0.7", logo: "raspberry-pi.png"},
+{url:"/components/switch.rpi_gpio/", title:"Raspberry Pi GPIO Switch", cat:"switch", featured: false, v: "0.7", logo: "raspberry-pi.png"},
 {url:"/components/switch.rpi_rf/", title:"Raspberry Pi RF Switch", cat:"switch", featured: false, v: "0.19", logo: "raspberry-pi.png"},
 {url:"/components/raspihats/", title:"Raspihats", cat:"diy", featured: false, v: "0.45", logo: "raspihats.png"},
 {url:"/components/binary_sensor.raspihats/", title:"Raspihats Binary Sensor", cat:"binary-sensor", featured: false, v: "0.44", logo: "raspihats.png"},
@@ -1872,11 +1872,11 @@ allComponents.pop(); // remove placeholder element at the end
       
    • RainMachine Switch
      • 
       
    • Random Binary Sensor
      • 
       
    • Random Sensor
      • 
-      
    • Raspberry PI GPIO
      • 
-      
    • Raspberry PI GPIO Binary Sensor
      • 
-      
    • Raspberry PI GPIO Switch
      • 
       
    • Raspberry Pi Camera
      • 
       
    • Raspberry Pi Cover
      • 
+      
    • Raspberry Pi GPIO
      • 
+      
    • Raspberry Pi GPIO Binary Sensor
      • 
+      
    • Raspberry Pi GPIO Switch
      • 
       
    • Raspberry Pi RF Switch
      • 
       
    • Raspihats
      • 
       
    • Raspihats Binary Sensor
      • 
diff --git a/components/light.ihc/index.html b/components/light.ihc/index.html
index bf250945ca..a7efa40e3e 100644
--- a/components/light.ihc/index.html
+++ b/components/light.ihc/index.html
@@ -124,7 +124,7 @@
   
 
    
 
    In the example above 12345 is ihc resource id and “tablelight” is the name. 
-The IHC resource id can be a light level for dimmers or an boolean output of a relay. 
+The IHC resource id can be a light level for dimmers or a boolean output of a relay. 
 For more information about IHC resource ids see Manual Setup
    diff --git a/components/light.rflink/index.html b/components/light.rflink/index.html index 864554916c..460d0db47a 100644 --- a/components/light.rflink/index.html +++ b/components/light.rflink/index.html @@ -107,7 +107,7 @@
  • name (Optional): Name for the device, defaults to Rflink ID.
  • type (Optional): Override automatically detected type of the light device, can be: switchable, dimmable, hybrid or toggle. See ‘Light Types’ below. (default: Switchable)
  • aliases (Optional): Alternative Rflink ID’s this device is known by.
    • -
  • fire_event (Optional): Fire an button_pressed event if this device is turned on or off (default: False).
    • +
  • fire_event (Optional): Fire a button_pressed event if this device is turned on or off (default: False).
  • signal_repetitions (Optional): Repeat every Rflink command this number of times (default: 1).
  • fire_event_ (Optional): Set default fire_event for RFLink switch devices (see below).
  • signal_repetitions (Optional): Set default signal_repetitions for RFLink switch devices (see below).
    • @@ -137,7 +137,7 @@

    Light types

    Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated on command as they turn into a pulsating state until on is pressed again (for example KlikAanKlikUit). The RFLink component support three types of lights to make things work in every situation:

      -
    • Hybrid: This type sends a dim followed by an a on command; and off commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple on signals will cause dimmers to go into disco mode.
      • +
    • Hybrid: This type sends a dim followed by an an on command; and off commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple on signals will cause dimmers to go into disco mode.
    • Switchable: Device type that sends only on and off commands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above).
    • Dimmable: Sends only dim and off commands. This does not work on on/off type devices as they don’t understand the dim command. For dimmers this does not cause issues with signal repetitions.
    • Toggle: Device type that sends only on commands to turn on or off the device. Some switches like for example Livolo light switches use the same ‘on’ command to switch on and switch off the lights. If the light is on and ‘on’ gets sent, the light will turn off and if the light is off and ‘on’ gets sent, the light will turn on. If the device has an unknown state, it will assume it is off by default.
      • diff --git a/components/logbook/index.html b/components/logbook/index.html index adcf76aa0a..c8002d6c64 100644 --- a/components/logbook/index.html +++ b/components/logbook/index.html @@ -132,7 +132,7 @@

    Exclude Events

    -

    Entities customized as hidden are excluded from the logbook by default, but sometimes you want to show the entity in the UI and not in the logbook. For instance you use the sensor.dateto show the current date in the UI, but you do not want an logbook entry for that sensor every day. +

    Entities customized as hidden are excluded from the logbook by default, but sometimes you want to show the entity in the UI and not in the logbook. For instance you use the sensor.dateto show the current date in the UI, but you do not want a logbook entry for that sensor every day. To exclude these entities just add them to the exclude > entities list in the configuration of the logbook.

    To exclude all events from a whole domain add it to the exclude > domain list. For instance you use the sun domain only to trigger automations on the `azimuth attribute, then you possible are not interested in the logbook entries for sun rise and sun set.

    Custom Entries

    diff --git a/components/mailbox/index.html b/components/mailbox/index.html index 6c10824aad..473aa6acd5 100644 --- a/components/mailbox/index.html +++ b/components/mailbox/index.html @@ -74,7 +74,7 @@
    -

    Mailboxes provide an list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend.

    +

    Mailboxes provide a list of messages with short information about each. Mailbox messages appear on a separate panel in the frontend.

    Home Assistant currently supports only the Asterisk Voicemail mailbox.

    Each mailbox also provides an entity to indicate the number of messages available on the main page.

    diff --git a/components/media_player.cast/index.html b/components/media_player.cast/index.html index a362682e26..c1bc0a01b2 100644 --- a/components/media_player.cast/index.html +++ b/components/media_player.cast/index.html @@ -74,7 +74,7 @@
    -

    Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable the discovery component. There is a issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.

    +

    Google Cast devices like Android TVs and Chromecasts will be automatically discovered if you enable the discovery component. There is an issue where Chromecasts can only be discovered if your device is connected to the same subnet as your Chromecast.

    The Chromecast platform can also be forced to load by adding the following lines to your configuration.yaml:

    # Example configuration.yaml entry
 media_player:
diff --git a/components/media_player.gstreamer/index.html b/components/media_player.gstreamer/index.html
index 99fae96416..a27ac64bab 100644
--- a/components/media_player.gstreamer/index.html
+++ b/components/media_player.gstreamer/index.html
@@ -106,13 +106,13 @@
 
    ln -s /path/to/your/installation/of/gi /path/to/your/venv/lib/python3.4/site-packages
 
    
 
    
-
    On a Raspberry PI, you may need to add the Home Assistant user to the audio group:
    
+
    On a Raspberry Pi, you may need to add the Home Assistant user to the audio group:
    
 
    sudo usermod -a -G audio <ha_user>
 
    
 
    
 
     Example Usage
    
 
     Using with TTS
    
-
    To play TTS on your local computer (for example, if you have speakers attached to your Raspberry PI:
    
+
    To play TTS on your local computer (for example, if you have speakers attached to your Raspberry Pi:
    
 
    media_player:
   - platform: gstreamer
 
diff --git a/components/media_player.yamaha/index.html b/components/media_player.yamaha/index.html
index 955afa6260..f296ce3654 100644
--- a/components/media_player.yamaha/index.html
+++ b/components/media_player.yamaha/index.html
@@ -112,7 +112,7 @@ on your receiver, or else startup of Home Assistant will hang if you
 have your receiver switched off.
   
  • In some cases, auto-discovery fails due to a known bug in the
 receiver’s firmware. It is possible to manually specify the
-receiver’s IP address or via it’s hostname (if it is discoverable by
+receiver’s IP address or via its hostname (if it is discoverable by
 your DNS) then.
    • 
 
 
     Supported operations
    
diff --git a/components/mycroft/index.html b/components/mycroft/index.html
index 5efb1e94d2..182f97017c 100644
--- a/components/mycroft/index.html
+++ b/components/mycroft/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    Mycroft is a open source voice assistant that allows you to send notifications and more to Mycroft from Home Assistant.
    
+  
    Mycroft is an open source voice assistant that allows you to send notifications and more to Mycroft from Home Assistant.
    
 
    # Example configuration.yaml entry
 mycroft:
   host: 0.0.0.0
diff --git a/components/notify.clickatell/index.html b/components/notify.clickatell/index.html
index 15d98684d8..8a88305210 100644
--- a/components/notify.clickatell/index.html
+++ b/components/notify.clickatell/index.html
@@ -76,7 +76,7 @@
   
    
   
    The clickatell platform uses Clickatell to deliver SMS notifications from Home Assistant.
    
 
    Get your Clickatell API Credentials
    
-
    Go to your Clickatell SMS Platform Portal section and create a new SMS integration. There are three screens of information required to creater an integration. Please ensure the following:
    
+
    Go to your Clickatell SMS Platform Portal section and create a new SMS integration. There are three screens of information required to create an integration. Please ensure the following:
    
 
      
   
    1. Give the new Integration an identification name.
      2. 
   
    2. Ensure it is set for ‘production’ use.
      3. 
diff --git a/components/notify.html5/index.html b/components/notify.html5/index.html
index 5ddb6b1d2a..55d9d1ca9e 100644
--- a/components/notify.html5/index.html
+++ b/components/notify.html5/index.html
@@ -286,7 +286,7 @@
 
    
 
    
 
     Making notifications work with NGINX proxy
    
-
    If you use NGINX as an proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It’s because of authentication token that cannot be passed through the proxy.
    
+
    If you use NGINX as a proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It’s because of authentication token that cannot be passed through the proxy.
    
 
    To solve the issue put additional location into your nginx site’s configuration:
    
 
    location /api/notify.html5/callback {
     if ($http_authorization = "") { return 403; }
diff --git a/components/notify.pushsafer/index.html b/components/notify.pushsafer/index.html
index 29574fd8d0..f2e87d73b8 100644
--- a/components/notify.pushsafer/index.html
+++ b/components/notify.pushsafer/index.html
@@ -75,7 +75,7 @@
   
   
    
   
    The Pushsafer service is a platform for the notify component. This allows you to send messages to the user using Pushsafer.
    
-
    In order to get an private or alias key you need to go to the Pushsafer website and register.
    
+
    In order to get a private or alias key you need to go to the Pushsafer website and register.
    
 
    To use Pushsafer notifications, add the following to your configuration.yaml file:
    
 
    # Example configuration.yaml entry
 notify:
diff --git a/components/raspihats/index.html b/components/raspihats/index.html
index 344f706699..3a68ac392f 100644
--- a/components/raspihats/index.html
+++ b/components/raspihats/index.html
@@ -8,7 +8,7 @@
     
     Raspihats - Home Assistant
     
-    
+    
     
     
     
@@ -16,12 +16,12 @@
     
     
     
-    
+    
     
     
     
     
-    
+    
     
     
     
@@ -135,7 +135,7 @@
             PiFace Digital I/O
         
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/rflink/index.html b/components/rflink/index.html
index 88dc399205..28504126a0 100644
--- a/components/rflink/index.html
+++ b/components/rflink/index.html
@@ -166,7 +166,7 @@ Wildcards only work at the end of the ID, not in the middle or front!
 
    If you find a device is recognized differently, with different protocols or the ON OFF is swapped or detected as two ON commands, it can  be overcome with the RFLink ‘RF Signal Learning’ mechanism from RFLink Rev 46 (11 March 2017). Link to further detail.
    
 
     Technical Overview
    
 
      
-  
    • Therflink Python module is a asyncio transport/protocol which is setup to fire a callback for every (valid/supported) packet received by the RFLink gateway.
      • 
+  
    • Therflink Python module is an asyncio transport/protocol which is setup to fire a callback for every (valid/supported) packet received by the RFLink gateway.
      • 
   
    • This component uses this callback to distribute ‘rflink packet events’ over Home Assistant’s event bus which can be subscribed to by entities/platform implementations.
      • 
   
    • The platform implementation takes care of creating new devices (if enabled) for unseen incoming packet ID’s.
      • 
   
    • Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entity logic is maintained in this main component.
      • 
diff --git a/components/rpi_gpio/index.html b/components/rpi_gpio/index.html
index 38fdca2b8d..e0c183d398 100644
--- a/components/rpi_gpio/index.html
+++ b/components/rpi_gpio/index.html
@@ -6,22 +6,22 @@
   
     
     
-    Raspberry PI GPIO - Home Assistant
+    Raspberry Pi GPIO - Home Assistant
     
-    
+    
     
     
     
-    
+    
     
     
     
-    
+    
     
     
     
-    
-    
+    
+    
     
     
     
@@ -70,7 +70,7 @@
           
      
   
      
     
      
-      Raspberry PI GPIO
+      Raspberry Pi GPIO
     
      
   
      
   
      
@@ -93,15 +93,15 @@
           
      
           
      Related components
      
           
     
      
     
      
@@ -138,7 +138,7 @@
             PiFace Digital I/O
         
         
    • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
      • 
         
    • 
             Raspihats
diff --git a/components/rpi_pfio/index.html b/components/rpi_pfio/index.html
index 27b139239c..1a6c11f43a 100644
--- a/components/rpi_pfio/index.html
+++ b/components/rpi_pfio/index.html
@@ -136,7 +136,7 @@
             PiFace Digital I/O
         
      • 
         
    • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
      • 
         
    • 
             Raspihats
diff --git a/components/satel_integra/index.html b/components/satel_integra/index.html
index e0c539afd9..513e2e4604 100644
--- a/components/satel_integra/index.html
+++ b/components/satel_integra/index.html
@@ -112,7 +112,7 @@
   
    • port (Optional): The port on which the ETHM module listens for clients using integration protocol. Default: 7094
      • 
   
    • partition (Optional): The partition to operate on. Integra can support multiple partitions, this platform only supports one. Default: 1
      • 
   
    • arm_home_mode (Optional): The mode in which arm Satel Integra when ‘arm home’ is used. Possible options are 1,2 or 3, default being 1. For more information on what are the differences between them, please refer to Satel Integra manual.
      • 
-  
    • zones (Optional): This module does not discover currently which zones are actually in use, so it will only monitor the ones defined in the config. For each zone, a proper ID must be given as well as it’s name (does not need to match the one specified in Satel Integra alarm). For more information on the available zone types, take a look at the Binary Sensor docs. Note: If no zones are specified, Home Assistant will not load any binary_sensor components.
      • 
+  
    • zones (Optional): This module does not discover currently which zones are actually in use, so it will only monitor the ones defined in the config. For each zone, a proper ID must be given as well as its name (does not need to match the one specified in Satel Integra alarm). For more information on the available zone types, take a look at the Binary Sensor docs. Note: If no zones are specified, Home Assistant will not load any binary_sensor components.
      • 
 
    
 
    List of all zone IDs can be taken from DloadX program.
    
 
    Having configured the zones, you can use them for automation, such as to react on the movement in your bedroom.
diff --git a/components/sensor.arduino/index.html b/components/sensor.arduino/index.html
index 6bb22b2594..98b9db6257 100644
--- a/components/sensor.arduino/index.html
+++ b/components/sensor.arduino/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    The arduino sensor platform allows you to get an numerical values from an analog input pin of an Arduino board. Usually the value is between 0 and 1024.
    
+  
    The arduino sensor platform allows you to get numerical values from an analog input pin of an Arduino board. Usually the value is between 0 and 1024.
    
 
    To enable an Arduino sensor with Home Assistant, add the following section to your configuration.yaml file:
    
 
    # Example configuration.yaml entry
 sensor:
@@ -177,7 +177,7 @@
             PiFace Digital I/O
         
    • 
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/sensor.buienradar/index.html b/components/sensor.buienradar/index.html
index bc6aba828c..a222063a82 100644
--- a/components/sensor.buienradar/index.html
+++ b/components/sensor.buienradar/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    The buienradar platform uses buienradar.nl as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a web service that provides detailed weather information for users in The Netherlands. The relevant weather station used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weather stations can be found here.
    
+  
    The buienradar platform uses buienradar.nl as a source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a web service that provides detailed weather information for users in The Netherlands. The relevant weather station used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weather stations can be found here.
    
 
    The selected weather station will provide all weather data, with the exception of the forecasted precipitation. The forecasted precipitation data will be retrieved from buienradar using your actual gps-location (and not the location of the nearest weather station).
    
 
    To integrate buienradar with Home Assistant, add the following section to your configuration.yaml file:
    
 
    # Example configuration.yaml entry
diff --git a/components/sensor.dht/index.html b/components/sensor.dht/index.html
index 10256a5802..1f31f93661 100644
--- a/components/sensor.dht/index.html
+++ b/components/sensor.dht/index.html
@@ -162,7 +162,7 @@
             PiFace Digital I/O
         
    • 
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/sensor.dsmr/index.html b/components/sensor.dsmr/index.html
index 5f1bcb55c9..194039fb8a 100644
--- a/components/sensor.dsmr/index.html
+++ b/components/sensor.dsmr/index.html
@@ -180,7 +180,7 @@
 
     Technical overview
    
 
    DSMR is a standard to which Dutch smartmeters must comply. It specifies that the smartmeter must send out a ‘telegram’ every 10 seconds over a serial port.
    
 
    The contents of this telegram differ between version but they generally consist of lines with ‘obis’ (Object Identification System, a numerical ID for a value) followed with the value and unit.
    
-
    This module sets up a asynchronous reading loop using the dsmr_parser module which waits for a complete telegram, parser it and puts it on an async queue as a dictionary of obis/object mapping. The numeric value and unit of each value can be read from the objects attributes. Because the obis are know for each DSMR version the Entities for this component are create during bootstrap.
    
+
    This module sets up an asynchronous reading loop using the dsmr_parser module which waits for a complete telegram, parser it and puts it on an async queue as a dictionary of obis/object mapping. The numeric value and unit of each value can be read from the objects attributes. Because the obis are know for each DSMR version the Entities for this component are create during bootstrap.
    
 
    Another loop (DSMR class) is setup which reads the telegram queue, stores/caches the latest telegram and notifies the Entities that the telegram has been updated.
    
 
         
    • 
diff --git a/components/sensor.ecobee/index.html b/components/sensor.ecobee/index.html
index 41212d1a84..89455ebc76 100644
--- a/components/sensor.ecobee/index.html
+++ b/components/sensor.ecobee/index.html
@@ -244,7 +244,7 @@
             RFXtrx Binary Sensor
         
         
  • 
-            Raspberry PI GPIO Binary Sensor
+            Raspberry Pi GPIO Binary Sensor
         
    • 
         
  • 
             Raspihats Binary Sensor
diff --git a/components/sensor.eddystone_temperature/index.html b/components/sensor.eddystone_temperature/index.html
index 18b51c116c..5a797ebab2 100644
--- a/components/sensor.eddystone_temperature/index.html
+++ b/components/sensor.eddystone_temperature/index.html
@@ -168,7 +168,7 @@ All beacons that support the Eddystone protocol, have a temperature sensor and c
             PiFace Digital I/O
         
    • 
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/sensor.miflora/index.html b/components/sensor.miflora/index.html
index b317cd8e2b..f87b2be699 100644
--- a/components/sensor.miflora/index.html
+++ b/components/sensor.miflora/index.html
@@ -81,7 +81,7 @@
   
  • On Hass.io: Miflora will work out of the box.
    • 
   
  • On other Linux systems:
     
      
-      
    • Prefered solution: Install the bluepy library (via pip). When using a virtual environment, make sure to use install the library in the right one.
+      
    • Preferred solution: Install the bluepy library (via pip). When using a virtual environment, make sure to use install the library in the right one.
     - Fallback solution: Install gatttool via your package manager. Depending on the distribution, the package name might be: bluez, bluetooth, bluez-deprecated
      • 
     
    
   
    • 
@@ -204,7 +204,7 @@ Reducing polling intervals will have a negative effect on the battery life.
    
             PiFace Digital I/O
         
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/sensor.modem_callerid/index.html b/components/sensor.modem_callerid/index.html
index c25ebc2ae6..f98a44cd68 100644
--- a/components/sensor.modem_callerid/index.html
+++ b/components/sensor.modem_callerid/index.html
@@ -91,7 +91,7 @@
 
    If Home Assistant (hass) runs with another user (e.g. homeassistant on Hassbian) give access to the stick with:
    
 
    $ sudo usermod -a -G dialout homeassistant
    
 
    Depending on what’s plugged into your USB ports, the name found above may change. You can lock in a name, such as /dev/modem, by following these instructions.
    
-
    When the sensor detects a new call, it’s state changes to ‘ring’ for each ring and ‘callerid’ when caller id information is received. It returns to ‘idle’ once ringing stops. The state event includes an attribute payload that includes the time of the call, name and number.
    
+
    When the sensor detects a new call, its state changes to ‘ring’ for each ring and ‘callerid’ when caller id information is received. It returns to ‘idle’ once ringing stops. The state event includes an attribute payload that includes the time of the call, name and number.
    
 
    Some example automations:
    
 
    automation:
   - alias: Notify CallerID
diff --git a/components/sensor.onewire/index.html b/components/sensor.onewire/index.html
index 03e498e634..8e9cbb74d9 100644
--- a/components/sensor.onewire/index.html
+++ b/components/sensor.onewire/index.html
@@ -172,7 +172,7 @@ Remember to replace <sensor_name> w
             PiFace Digital I/O
         
    • 
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/sensor.openweathermap/index.html b/components/sensor.openweathermap/index.html
index abe4415189..a949a5d109 100644
--- a/components/sensor.openweathermap/index.html
+++ b/components/sensor.openweathermap/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    The openweathermap platform uses OpenWeatherMap as an source for current meteorological data for your location. The forecast will show you the condition in 3 h.
    
+  
    The openweathermap platform uses OpenWeatherMap as a source for current meteorological data for your location. The forecast will show you the condition in 3 h.
    
 
    You need an API key which is free but requires a registration.
    
 
    To add OpenWeatherMap to your installation, add the following to your configuration.yaml file:
    
 
    # Example configuration.yaml entry
diff --git a/components/sensor.serial_pm/index.html b/components/sensor.serial_pm/index.html
index c04a982ec0..1fcaf1b9b7 100644
--- a/components/sensor.serial_pm/index.html
+++ b/components/sensor.serial_pm/index.html
@@ -153,7 +153,7 @@
             PiFace Digital I/O
         
    • 
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/sensor.skybeacon/index.html b/components/sensor.skybeacon/index.html
index 8805e4704d..eb520b83ff 100644
--- a/components/sensor.skybeacon/index.html
+++ b/components/sensor.skybeacon/index.html
@@ -146,7 +146,7 @@
             PiFace Digital I/O
         
    • 
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/sensor.supervisord/index.html b/components/sensor.supervisord/index.html
index 56fae85c58..46f8220de4 100644
--- a/components/sensor.supervisord/index.html
+++ b/components/sensor.supervisord/index.html
@@ -80,7 +80,7 @@
 port=127.0.0.1:9001
 
    • 
 
    
-
    After a restart of supervisord you should be able to access the web interface. If needed then this could be added as a iFrame panel.
    
+
    After a restart of supervisord you should be able to access the web interface. If needed then this could be added as an iFrame panel.
    
 
    
   
 
    
diff --git a/components/sensor.vera/index.html b/components/sensor.vera/index.html
index bdc403bb28..9e971495ab 100644
--- a/components/sensor.vera/index.html
+++ b/components/sensor.vera/index.html
@@ -76,7 +76,7 @@
   
    
   
    The vera platform allows you to get data from your Vera sensors from within Home Assistant.
    
 
    They will be automatically discovered if the vera component is loaded.
    
-
    Please note that some vera sensors (such as motion and flood  sensors) are armable which means that vera will send alerts (email messages to txts) when they are armed an change state.
    
+
    Please note that some vera sensors (such as motion and flood  sensors) are armable which means that vera will send alerts (email messages to txts) when they are armed and change state.
    
 
    Home Assistant will display the state of these sensors regardless of the armed state.
    
 
    To allow you to change the armed state - Home Assistant will create a switch as well as a sensor for each Armable sensor. You can hide these switches using customization if you wish.
    
 
diff --git a/components/sensor.worxlandroid/index.html b/components/sensor.worxlandroid/index.html
index 0447e21aae..c8d4837438 100644
--- a/components/sensor.worxlandroid/index.html
+++ b/components/sensor.worxlandroid/index.html
@@ -142,7 +142,7 @@
             PiFace Digital I/O
         
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/sensor.yr/index.html b/components/sensor.yr/index.html
index 568fc9645b..13af12c163 100644
--- a/components/sensor.yr/index.html
+++ b/components/sensor.yr/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    The yr platform uses YR.no as an source for current meteorological data for your location. The
+  
    The yr platform uses YR.no as a source for current meteorological data for your location. The
 weather forecast is delivered by the Norwegian Meteorological Institute and the NRK.
    
 
    To add YR to your installation, add the following to your configuration.yaml file:
    
 
    # Example configuration.yaml entry
diff --git a/components/sensor.yweather/index.html b/components/sensor.yweather/index.html
index 3c1f489f51..174a4fcd9a 100644
--- a/components/sensor.yweather/index.html
+++ b/components/sensor.yweather/index.html
@@ -74,7 +74,7 @@
     
   
   
    
-  
    The yweather platform uses Yahoo Weather as an source for current meteorological data. The forecast will show you the condition for 5 days, 0 is the current day. You can use only weather, temp_min, and temp_max with forecast. It’s important to note that a yweather sensor will only show ONE days forecast at a time so to show multiple days forecasts, you will need to use the ‘name:’ option and give each sensor a unique name.
    
+  
    The yweather platform uses Yahoo Weather as a source for current meteorological data. The forecast will show you the condition for 5 days, 0 is the current day. You can use only weather, temp_min, and temp_max with forecast. It’s important to note that a yweather sensor will only show ONE days forecast at a time so to show multiple days forecasts, you will need to use the ‘name:’ option and give each sensor a unique name.
    
 
    
 Use of the Yahoo Weather API should not exceed reasonable request volume. Access is limited to 2000 signed calls per day.
 
    
diff --git a/components/switch.abode/index.html b/components/switch.abode/index.html
index 4fbbf759b4..86be4c25bd 100644
--- a/components/switch.abode/index.html
+++ b/components/switch.abode/index.html
@@ -269,7 +269,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.acer_projector/index.html b/components/switch.acer_projector/index.html
index a9af9bef22..67984e70ab 100644
--- a/components/switch.acer_projector/index.html
+++ b/components/switch.acer_projector/index.html
@@ -251,7 +251,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.ads/index.html b/components/switch.ads/index.html
index a30d856fb5..80389b60a1 100644
--- a/components/switch.ads/index.html
+++ b/components/switch.ads/index.html
@@ -275,7 +275,7 @@ file:
    
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.android_ip_webcam/index.html b/components/switch.android_ip_webcam/index.html
index ef79edd737..2876293591 100644
--- a/components/switch.android_ip_webcam/index.html
+++ b/components/switch.android_ip_webcam/index.html
@@ -255,7 +255,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.anel_pwrctrl/index.html b/components/switch.anel_pwrctrl/index.html
index ffc8ee1a5a..0e568af78a 100644
--- a/components/switch.anel_pwrctrl/index.html
+++ b/components/switch.anel_pwrctrl/index.html
@@ -261,7 +261,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.arduino/index.html b/components/switch.arduino/index.html
index ecc9e4dee9..92cd69b5c4 100644
--- a/components/switch.arduino/index.html
+++ b/components/switch.arduino/index.html
@@ -193,7 +193,7 @@
             PiFace Digital I/O
         
    • 
         
  • 
-            Raspberry PI GPIO
+            Raspberry Pi GPIO
         
    • 
         
  • 
             Raspihats
diff --git a/components/switch.arest/index.html b/components/switch.arest/index.html
index 47c07d4868..2ceeefd864 100644
--- a/components/switch.arest/index.html
+++ b/components/switch.arest/index.html
@@ -291,7 +291,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.bbb_gpio/index.html b/components/switch.bbb_gpio/index.html
index 8bc4d25748..f4d2c7524f 100644
--- a/components/switch.bbb_gpio/index.html
+++ b/components/switch.bbb_gpio/index.html
@@ -274,7 +274,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.broadlink/index.html b/components/switch.broadlink/index.html
index e912916aa3..5767659e52 100644
--- a/components/switch.broadlink/index.html
+++ b/components/switch.broadlink/index.html
@@ -428,7 +428,7 @@ Use this
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index 0181e5a466..e3baf24181 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -340,7 +340,7 @@ This switch will shutdown your host immediately, there will be no confirmation.
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.digital_ocean/index.html b/components/switch.digital_ocean/index.html
index 0d5d11760f..d9b65b6133 100644
--- a/components/switch.digital_ocean/index.html
+++ b/components/switch.digital_ocean/index.html
@@ -266,7 +266,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.digitalloggers/index.html b/components/switch.digitalloggers/index.html
index 40b4431c80..f3a46bef6b 100644
--- a/components/switch.digitalloggers/index.html
+++ b/components/switch.digitalloggers/index.html
@@ -259,7 +259,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.dlink/index.html b/components/switch.dlink/index.html
index 6b6a9a9713..98549eb2fa 100644
--- a/components/switch.dlink/index.html
+++ b/components/switch.dlink/index.html
@@ -259,7 +259,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.doorbird/index.html b/components/switch.doorbird/index.html
index 435a7bfea0..ab76c3a5a4 100644
--- a/components/switch.doorbird/index.html
+++ b/components/switch.doorbird/index.html
@@ -264,7 +264,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.edimax/index.html b/components/switch.edimax/index.html
index 04afce13a6..6a9b03d442 100644
--- a/components/switch.edimax/index.html
+++ b/components/switch.edimax/index.html
@@ -248,7 +248,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.enocean/index.html b/components/switch.enocean/index.html
index 3e8933f5bd..d4a5c2ca1a 100644
--- a/components/switch.enocean/index.html
+++ b/components/switch.enocean/index.html
@@ -266,7 +266,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.fritzdect/index.html b/components/switch.fritzdect/index.html
index a411ed0bcb..f8d7363735 100644
--- a/components/switch.fritzdect/index.html
+++ b/components/switch.fritzdect/index.html
@@ -263,7 +263,7 @@ If this component throws an error when starting home-assistant you should check
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.gc100/index.html b/components/switch.gc100/index.html
index a891e7e95b..1536499825 100644
--- a/components/switch.gc100/index.html
+++ b/components/switch.gc100/index.html
@@ -8,7 +8,7 @@
     
     gc100 Switch - Home Assistant
     
-    
+    
     
     
     
@@ -16,12 +16,12 @@
     
     
     
-    
+    
     
     
     
     
-    
+    
     
     
     
@@ -260,7 +260,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.hikvisioncam/index.html b/components/switch.hikvisioncam/index.html
index 3a68112cbf..bbb364a08c 100644
--- a/components/switch.hikvisioncam/index.html
+++ b/components/switch.hikvisioncam/index.html
@@ -252,7 +252,7 @@ Currently works using default https port only.
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.hive/index.html b/components/switch.hive/index.html
index 0d3a73016b..16f1402c42 100644
--- a/components/switch.hive/index.html
+++ b/components/switch.hive/index.html
@@ -264,7 +264,7 @@ Full configuration details can be found on the main 
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.homematic/index.html b/components/switch.homematic/index.html
index 1ade6dc543..a67a9467fb 100644
--- a/components/switch.homematic/index.html
+++ b/components/switch.homematic/index.html
@@ -261,7 +261,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.hook/index.html b/components/switch.hook/index.html
index abfd4b2b51..e1c128ae62 100644
--- a/components/switch.hook/index.html
+++ b/components/switch.hook/index.html
@@ -263,7 +263,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.ihc/index.html b/components/switch.ihc/index.html
index 0c3459c800..2948a205f1 100644
--- a/components/switch.ihc/index.html
+++ b/components/switch.ihc/index.html
@@ -295,7 +295,7 @@ For more information about IHC resource ids see some-
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.mysensors/index.html b/components/switch.mysensors/index.html
index f2a9005918..0c2712dd3c 100644
--- a/components/switch.mysensors/index.html
+++ b/components/switch.mysensors/index.html
@@ -510,7 +510,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.mystrom/index.html b/components/switch.mystrom/index.html
index 92d1196e2a..13902aa41d 100644
--- a/components/switch.mystrom/index.html
+++ b/components/switch.mystrom/index.html
@@ -293,7 +293,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.neato/index.html b/components/switch.neato/index.html
index c1d7b7d691..ae6659902e 100644
--- a/components/switch.neato/index.html
+++ b/components/switch.neato/index.html
@@ -249,7 +249,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.netio/index.html b/components/switch.netio/index.html
index 35285bc5ea..bb969ebf53 100644
--- a/components/switch.netio/index.html
+++ b/components/switch.netio/index.html
@@ -284,7 +284,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.orvibo/index.html b/components/switch.orvibo/index.html
index ef01bae6bb..f2e6e88eac 100644
--- a/components/switch.orvibo/index.html
+++ b/components/switch.orvibo/index.html
@@ -259,7 +259,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.pilight/index.html b/components/switch.pilight/index.html
index 04b46bfbf3..cff8422860 100644
--- a/components/switch.pilight/index.html
+++ b/components/switch.pilight/index.html
@@ -327,7 +327,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index 03b61fcabf..c0d6d9c788 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -259,7 +259,7 @@ This component relies on raw TCP commands to PulseAudio. In order for PulseAudio
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.qwikswitch/index.html b/components/switch.qwikswitch/index.html
index 3fb10b0416..1fa2510258 100644
--- a/components/switch.qwikswitch/index.html
+++ b/components/switch.qwikswitch/index.html
@@ -250,7 +250,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.rachio/index.html b/components/switch.rachio/index.html
index 81f35d1f38..4f8a6936d4 100644
--- a/components/switch.rachio/index.html
+++ b/components/switch.rachio/index.html
@@ -296,7 +296,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.raincloud/index.html b/components/switch.raincloud/index.html
index 15fc2c6acf..9f006210f9 100644
--- a/components/switch.raincloud/index.html
+++ b/components/switch.raincloud/index.html
@@ -267,7 +267,7 @@
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.rainmachine/index.html b/components/switch.rainmachine/index.html
index c8a2d1c920..8d52594c33 100644
--- a/components/switch.rainmachine/index.html
+++ b/components/switch.rainmachine/index.html
@@ -296,7 +296,7 @@ can fix the issue.
    
             RainMachine Switch
         
    • 
         
  • 
-            Raspberry PI GPIO Switch
+            Raspberry Pi GPIO Switch
         
    • 
         
  • 
             Raspberry Pi RF Switch
diff --git a/components/switch.raspihats/index.html b/components/switch.raspihats/index.html
index 6d235b6390..fe236ec9ff 100644
--- a/components/switch.raspihats/index.html
+++ b/components/switch.raspihats/index.html
@@ -8,7 +8,7 @@
     
     Raspihats Switch - Home Assistant
     
-    
+    
     
     
     
@@ -16,12 +16,12 @@
     
     
     
-    
+    
     
     
     
     
-    
+    
     
     
     
@@ -143,7 +143,7 @@
 70: -- -- -- -- -- -- -- 77
 
    • 
 
    
-
    For more details about the Raspihats add-on boards for Raspberry PI, visit raspihats.com.
    
+
    For more details about the Raspihats add-on boards for Raspberry Pi, visit raspihats.com.