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>
ssh pi@your_raspberry_pi_ipecho scan | cec-client -s -d 1ssh pi@your_raspberry_pi_ip
+echo scan | cec-client -s -d 1
+# 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 @@
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