From 0b3677790f4433c5d33e96ee83fd88f3581e1eda Mon Sep 17 00:00:00 2001 From: Travis CI Date: Sat, 19 Nov 2016 10:35:00 +0000 Subject: [PATCH] Site updated at 2016-11-19 10:35:00 UTC --- atom.xml | 2 +- blog/categories/community/atom.xml | 2 +- blog/categories/device-tracking/atom.xml | 2 +- blog/categories/esp8266/atom.xml | 2 +- blog/categories/how-to/atom.xml | 2 +- blog/categories/ibeacons/atom.xml | 2 +- blog/categories/internet-of-things/atom.xml | 2 +- blog/categories/iot-data/atom.xml | 2 +- blog/categories/micropython/atom.xml | 2 +- blog/categories/mqtt/atom.xml | 2 +- blog/categories/organisation/atom.xml | 2 +- blog/categories/owntracks/atom.xml | 2 +- blog/categories/presence-detection/atom.xml | 2 +- .../public-service-announcement/atom.xml | 2 +- blog/categories/release-notes/atom.xml | 2 +- blog/categories/survey/atom.xml | 2 +- blog/categories/talks/atom.xml | 2 +- blog/categories/technology/atom.xml | 2 +- blog/categories/user-stories/atom.xml | 2 +- blog/categories/video/atom.xml | 2 +- blog/categories/website/atom.xml | 2 +- components/hdmi_cec/index.html | 20 ++++++++++--- components/openalpr/index.html | 2 +- components/sensor.command_line/index.html | 10 +++---- components/sensor.synologydsm/index.html | 30 +++++++++---------- sitemap.xml | 30 +++++++++---------- 26 files changed, 73 insertions(+), 61 deletions(-) diff --git a/atom.xml b/atom.xml index 866b6ac361..113ecab421 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 5cb2a8e267..98f2f58bc1 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index 8d3cfeeb44..495ce2f082 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]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index b3a4beb1f4..8d091115b9 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index 176e150d83..481ff2480c 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]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index 566ce0c327..4b009403e7 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index 3e277b2e17..c8912e2b27 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]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index e6b7d69de3..f8ef193bb5 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]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index bc165d5064..26fa0f176c 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index c9af08ef29..025f922fd2 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index 70670553d5..9aa34e4e59 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 9b08aef630..9d0fc87a04 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index 9c45b8ef10..b72e15ca8a 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]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+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 202cd81951..3916a61354 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]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 030e70cdc5..0fd988d9e2 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]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 03a89edf79..e399c38b13 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 8970c29343..0056dae3d7 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index 4e63467b68..1bb7023d4e 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index cc80d3657e..16aba62934 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]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index 261251dde1..07428124b9 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index deaad2694b..94d0b0a28f 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2016-11-19T09:10:07+00:00 + 2016-11-19T10:33:06+00:00 https://home-assistant.io/ diff --git a/components/hdmi_cec/index.html b/components/hdmi_cec/index.html index 57e0a93073..ca2afed685 100644 --- a/components/hdmi_cec/index.html +++ b/components/hdmi_cec/index.html @@ -110,21 +110,33 @@ -

For the default virtual environment of a Raspberry Pi AIO the command would be as follows.

+

For the default virtual environment of a Raspberry Pi All-In-One installation the command would be as follows.

$ ln -s /usr/local/lib/python3.4/dist-packages/cec /srv/hass/hass_venv/lib/python3.4/site-packages

If after symlinking and adding hdmi_cec: to your configuration you are getting the following error in your logs, -* failed to open vchiq instance you will also need to add the user account Home Asssistant runs under, to the video group. To add the Home Assisitant’s user account to the video group, run the following command. $ usermod -a -G video <hass_user_account> +* failed to open vchiq instance you will also need to add the user account Home Asssistant runs under, to the video group. To add the Home Assistant user account to the video group, run the following command. $ usermod -a -G video <hass_user_account>

Testing your installation

    -
  • Login to Raspberry Pi ssh pi@your_raspberry_pi_ip
    • -
  • at the command line type: echo scan | cec-client -s -d 1
    • +
  • Login to Raspberry Pi
    • +
+ +
ssh pi@your_raspberry_pi_ip
+
+
+
    +
  • at the command line type:
    • +
+ +
echo scan | cec-client -s -d 1
+
+
+
  • This will give you the list of devices that are on the bus
diff --git a/components/openalpr/index.html b/components/openalpr/index.html index d56b5dca6f..38a5bc9b26 100644 --- a/components/openalpr/index.html +++ b/components/openalpr/index.html @@ -170,7 +170,7 @@ If you want use a video stream. You need setup the 
# Example configuration.yaml entry
 openalpr:
-  engine: local
+  engine: cloud
   region: eu
   api_key: SK_AAABBBBCCCEEEE
   entities:
diff --git a/components/sensor.command_line/index.html b/components/sensor.command_line/index.html
index c81294d7a0..3eb3bcdb0f 100644
--- a/components/sensor.command_line/index.html
+++ b/components/sensor.command_line/index.html
@@ -122,7 +122,7 @@
-

To use those information, the entry for a command-line sensor in the configuration.yaml file will look like this.

+

To use this information, the entry for a command-line sensor in the configuration.yaml file will look like this.

# Example configuration.yaml entry
 sensor:
@@ -146,9 +146,9 @@
-

Monitoring the failed login attempt on HA

+

Monitoring failed login attempts on Home Assistant

-

If you’d like to know how much failed login attempts are made to HA proceed with the following

+

If you’d like to know how many failed login attempts are made to Home Assistant, add the following to your configuration.yaml file:

# Example configuration.yaml entry
 sensor:
@@ -158,7 +158,7 @@
-

Make sure to configure the logger to monitor the proper component at the proper level.

+

Make sure to configure the logger component to monitor the http component at least the warning level.

# Example working logger settings that works
 logger:
@@ -192,7 +192,7 @@
 
 
 Use an external script

 
-
The example is doing the same as the aREST sensor but with an external Python script. It should give you an idea about interacting with devices which are exposing a RESTful API.

+
The example is doing the same as the aREST sensor but with an external Python script. It should give you an idea about interfacing with devices which are exposing a RESTful API.

 
 
The one-line script to retrieve a value is shown below. Of course would it be possible to use this directly in the configuration.yaml file but need extra care about the quotation marks.

 
diff --git a/components/sensor.synologydsm/index.html b/components/sensor.synologydsm/index.html
index bd21caffd1..b93890d9fa 100644
--- a/components/sensor.synologydsm/index.html
+++ b/components/sensor.synologydsm/index.html
@@ -90,9 +90,9 @@
   

   
 
-  
This synologydsm sensor allows getting various statistics from your Synology NAS. Please note that using this sensor wakes up your synology if in hibernation mode.

+  
This synologydsm sensor allows getting various statistics from your Synology NAS. Please note that using this sensor wakes up your Synology NAS if in hibernation mode.

 
-
To use the SynologyDSM sensor in your installation, add the following to your configuration.yaml file:

+
To use the synologydsm sensor in your installation, add the following to your configuration.yaml file:

 
 
# Example configuration.yml entry
 sensor:
@@ -106,14 +106,14 @@
       - network_up
 

 

-
Note: After booting HASS it can take up to 15 minutes for the sensors to show up. This is due to the fact that sensors are created after HASS has fully been initialised.

+
Note: After booting Home Assistant it can take up to 15 minutes for the sensors to show up. This is due to the fact that sensors are created after Home Assistant has fully been initialized.

 
 
Configuration variables:

 
 
    
   
  • host (Required): The IP address of the Synology NAS to monitor
    • 
-  
  • port (Optional): The port number on which the NAS is reachable. Defaults to 5000.
    • 
-  
  • username (Required): An user to connect to the Synology NAS (a seperate account is adviced, see the Seperate User Configuration section below for details).
    • 
+  
  • port (Optional): The port number on which the Synology NAS is reachable. Defaults to 5000.
    • 
+  
  • username (Required): An user to connect to the Synology NAS (a separate account is advised, see the Separate User Configuration section below for details).
    • 
   
  • password (Required): The password of the user to connect to the Synology NAS.
    • 
   
  • volumes (Optional): Array of volumes to monitor. Defaults to all volumes.
    • 
   
  • disks (Optional): Array of disks to monitor. Defaults to all disks.
    • 
@@ -135,13 +135,13 @@
       
  • memory_total_real: Displays total size of real memory in MB.
    • 
       
  • network_up: Displays total up speed of network interfaces (combines all interfaces).
    • 
       
  • network_down: Displays total down speed of network interfaces (combines all interfaces).
    • 
-      
  • disk_name: Displays the name of the harddisk (creates a new entry for each disk).
    • 
-      
  • disk_device: Displays the path of the harddisk (creates a new entry for each disk).
    • 
-      
  • disk_smart_status: Displays the S.M.A.R.T status of the harddisk (creates a new entry for each disk).
    • 
-      
  • disk_status: Displays the status of the harddisk (creates a new entry for each disk).
    • 
-      
  • disk_exceed_bad_sector_thr: Displays true / false to indicate if the harddisk exceeded the maximum bad sector threshold (creates a new entry for each disk).
    • 
-      
  • disk_below_remain_life_thr: Displays true / false to indicate if the harddisk dropped below the remain life threshold (creates a new entry for each disk).
    • 
-      
  • disk_temp: Displays the temperature of the harddisk (creates a new entry for each disk, uses the unit_system to display in C or F).
    • 
+      
  • disk_name: Displays the name of the hard disk (creates a new entry for each disk).
    • 
+      
  • disk_device: Displays the path of the hard disk (creates a new entry for each disk).
    • 
+      
  • disk_smart_status: Displays the S.M.A.R.T status of the hard disk (creates a new entry for each disk).
    • 
+      
  • disk_status: Displays the status of the hard disk (creates a new entry for each disk).
    • 
+      
  • disk_exceed_bad_sector_thr: Displays true / false to indicate if the hard disk exceeded the maximum bad sector threshold (creates a new entry for each disk).
    • 
+      
  • disk_below_remain_life_thr: Displays true / false to indicate if the hard disk dropped below the remain life threshold (creates a new entry for each disk).
    • 
+      
  • disk_temp: Displays the temperature of the hard disk (creates a new entry for each disk, uses the unit_system to display in C or F).
    • 
       
  • volume_status: Displays the status of the volume (creates a new entry for each volume).
    • 
       
  • volume_device_type: Displays the volume type (RAID, etc) (creates a new entry for each volume).
    • 
       
  • volume_size_total: Displays the total size of the volume in GB’s (creates a new entry for each volume).
    • 
@@ -153,11 +153,11 @@
   
 

 
-
Seperate User Configuration:

+
Separate User Configuration:

 
-
Due to the nature of the Synology DSM Api it is required to grant de user admin rights. This is related to the fact that utilisation information is stored in the core module.

+
Due to the nature of the Synology DSM API it is required to grant the user admin rights. This is related to the fact that utilization information is stored in the core module.

 
-
When creating the user it is possible to deny access to all locations and applications. By doing this the user will not be able to login to the web interface or view any of the files on the NAS. It is still able to read the utilisation and storage information using the API.

+
When creating the user it is possible to deny access to all locations and applications. By doing this the user will not be able to login to the web interface or view any of the files on the Synology NAS. It is still able to read the utilization and storage information using the API.

 
 
 
diff --git a/sitemap.xml b/sitemap.xml
index ac0879a12c..5359c34cd1 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2309,62 +2309,62 @@
 
 
 https://home-assistant.io/demo/frontend.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/index.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-history.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-map.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/googlef4f3693c209fe788.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:25+00:00
 
 
 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:26+00:00
 
 
 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:26+00:00
 
 
 https://home-assistant.io/static/mdi-demo.html
-2016-11-19T09:09:26+00:00
+2016-11-19T10:32:26+00:00