+
+
+
+
diff --git a/components/axis/index.html b/components/axis/index.html
index f6ab5911c6..a50268d130 100644
--- a/components/axis/index.html
+++ b/components/axis/index.html
@@ -172,6 +172,9 @@ Any specific levels for triggers needs to be configured on the device.
diff --git a/components/blink/index.html b/components/blink/index.html
index d098a81880..f7cd985ba6 100644
--- a/components/blink/index.html
+++ b/components/blink/index.html
@@ -160,6 +160,9 @@ There are three services availiabe for the blink platform:
To get your Arlo sensors working within Home Assistant, please follow the instructions for the general Arlo component.
+
This component is not yet able to live stream from your Arlo camera, but it will be able to playback the last video capture.
+
Once you have enabled the Arlo component, add the following to your configuration.yaml file:
+
# Example configuration.yaml entry
+camera:
+ -platform:arlo
+ ffmpeg_arguments:'-pred1-q:v2'
+
+
+
Configuration variables:
+
+
ffmpeg_arguments: (Optional): Extra options to pass to ffmpeg, e.g. image quality or video filter options.
+
+
Note: To be able to playback the last capture, it is required to install the ffmpeg component. Make sure to follow the steps mentioned at FFMPEG documentation.
diff --git a/components/camera.blink/index.html b/components/camera.blink/index.html
index 31a682807f..2bfc3c3644 100644
--- a/components/camera.blink/index.html
+++ b/components/camera.blink/index.html
@@ -105,6 +105,9 @@ To get your Blink cameras working with Home Assistant, follow the instructions f
diff --git a/components/camera.foscam/index.html b/components/camera.foscam/index.html
index b8c0a3471d..fd18f3c845 100644
--- a/components/camera.foscam/index.html
+++ b/components/camera.foscam/index.html
@@ -108,6 +108,9 @@ There seems to be some issues within Foscam with lengthy passwords and passwords
diff --git a/components/camera.local_file/index.html b/components/camera.local_file/index.html
index 1fb9eee8d0..339dd91fb1 100644
--- a/components/camera.local_file/index.html
+++ b/components/camera.local_file/index.html
@@ -108,6 +108,9 @@ The given file_path must be an existing f
diff --git a/components/camera.mjpeg/index.html b/components/camera.mjpeg/index.html
index 213f660e7b..ce93e83d53 100644
--- a/components/camera.mjpeg/index.html
+++ b/components/camera.mjpeg/index.html
@@ -108,6 +108,9 @@ There is a Nest component configured to u
diff --git a/components/camera.synology/index.html b/components/camera.synology/index.html
index 3e3ddcaccb..faf329a862 100644
--- a/components/camera.synology/index.html
+++ b/components/camera.synology/index.html
@@ -122,6 +122,9 @@ Most users will need to set verify_ssl to
diff --git a/components/camera.zoneminder/index.html b/components/camera.zoneminder/index.html
index 40e32819f9..1bddfa5ff9 100644
--- a/components/camera.zoneminder/index.html
+++ b/components/camera.zoneminder/index.html
@@ -112,6 +112,9 @@ You must have the ZoneMinder component con
diff --git a/components/climate.zwave/index.html b/components/climate.zwave/index.html
index 8d69ce4fc1..b3336186ba 100644
--- a/components/climate.zwave/index.html
+++ b/components/climate.zwave/index.html
@@ -87,7 +87,7 @@ If the thermostat support different operating modes, you will get one thermostat
-alias:Turn on Heater at 8pmtrigger:-platform:time
- after:"20:00:00"
+ at:"20:00:00"action:-service:climate.set_operation_modeentity_id:climate.remotec_zxt120_heating_1_id
@@ -104,7 +104,7 @@ If the thermostat support different operating modes, you will get one thermostat
-alias:Turn off Heater at 9pmtrigger:-platform:time
- after:"21:00:00"
+ at:"21:00:00"action:-service:climate.set_operation_modeentity_id:climate.remotec_zxt120_heating_1_id
@@ -149,6 +149,9 @@ If the thermostat support different operating modes, you will get one thermostat
diff --git a/components/climate/index.html b/components/climate/index.html
index 3d463362fd..4143ecab0d 100644
--- a/components/climate/index.html
+++ b/components/climate/index.html
@@ -106,7 +106,7 @@ Not all climate services may be available for your platform. Be sure to check th
automation:trigger:platform:time
- after:"07:15:00"
+ at:"07:15:00"action:-service:climate.set_aux_heatdata:
@@ -143,7 +143,7 @@ reflecting a situation where the climate device is set to save energy. This may
automation:trigger:platform:time
- after:"07:15:00"
+ at:"07:15:00"action:-service:climate.set_away_modedata:
@@ -181,7 +181,7 @@ temporary target temperature. The particular modes available depend on the clima
automation:trigger:platform:time
- after:"07:15:00"
+ at:"07:15:00"action:-service:climate.set_hold_modedata:
@@ -231,7 +231,7 @@ temporary target temperature. The particular modes available depend on the clima
automation:trigger:platform:time
- after:"07:15:00"
+ at:"07:15:00"action:-service:climate.set_temperaturedata:
@@ -267,7 +267,7 @@ temporary target temperature. The particular modes available depend on the clima
automation:trigger:platform:time
- after:"07:15:00"
+ at:"07:15:00"action:-service:climate.set_humiditydata:
@@ -302,7 +302,7 @@ temporary target temperature. The particular modes available depend on the clima
automation:trigger:platform:time
- after:"07:15:00"
+ at:"07:15:00"action:-service:climate.set_fan_modedata:
@@ -337,7 +337,7 @@ temporary target temperature. The particular modes available depend on the clima
automation:trigger:platform:time
- after:"07:15:00"
+ at:"07:15:00"action:-service:climate.set_operation_modedata:
@@ -372,7 +372,7 @@ temporary target temperature. The particular modes available depend on the clima
A picture that you can use to easily identify the person or device. You can also save the image file in a folder “www” in the same location (can be obtained from developer tools) where you have your configuration.yaml file and just use picture: /local/favicon-192x192.png.
+
+
icon
+
mdi:account
+
An icon for this device (use as an alternative to picture).
+
gravatar
None
@@ -161,7 +165,7 @@
track
-
False
+
[uses platform setting]
If yes/on/true then the device will be tracked. Otherwise its location and state will not update
diff --git a/components/emulated_hue/index.html b/components/emulated_hue/index.html
index 56c161c3a0..f4a5b51678 100644
--- a/components/emulated_hue/index.html
+++ b/components/emulated_hue/index.html
@@ -193,6 +193,9 @@ The virtual bridge has the ability to turn entities on or off, or change the bri
diff --git a/components/fan.mqtt/index.html b/components/fan.mqtt/index.html
index a7a0044152..281518fde1 100644
--- a/components/fan.mqtt/index.html
+++ b/components/fan.mqtt/index.html
@@ -202,6 +202,9 @@ Make sure that your topic is an exact match. som
diff --git a/components/fan.wink/index.html b/components/fan.wink/index.html
index b66d79955e..88b4bdbffe 100644
--- a/components/fan.wink/index.html
+++ b/components/fan.wink/index.html
@@ -138,6 +138,9 @@ The above devices are confimed to work, but others may work as well.
diff --git a/components/homematic/index.html b/components/homematic/index.html
index f26206c1dc..20b5c0fabb 100644
--- a/components/homematic/index.html
+++ b/components/homematic/index.html
@@ -282,6 +282,9 @@ Using this service provides you direct access to the setValue-method of the prim
diff --git a/components/ifttt.manything/index.html b/components/ifttt.manything/index.html
index 6b82edf866..92078a7dac 100644
--- a/components/ifttt.manything/index.html
+++ b/components/ifttt.manything/index.html
@@ -151,6 +151,9 @@ For ManyThing support, you need to set up an on<
diff --git a/components/index.html b/components/index.html
index 063b499ea6..f2b0496b06 100644
--- a/components/index.html
+++ b/components/index.html
@@ -72,7 +72,7 @@ Support for these components is provided by the Home Assistant community.
The template platform creates lights that combine components and provides the ability to run scripts or invoke services for each of the on, off, and brightness commands of a light.
+
To enable Template lights in your installation, add the following to your configuration.yaml file:
friendly_name (Optional): Name to use in the Frontend.
+
value_template (Optional): Defines a template to get the state of the light. If not provided the component defaults to optimisitc state determination.
+
turn_on (Required): Defines an action to run when the light is turned on.
+
turn_off (Required): Defines an action to run when the light is turned off.
+
set_level (Optional): Defines an action to run when the light is given a brightness command.
+
level_template (*Optional): Defines a template to get the brightness of the light. If not provided the component defaults to optimisitc brightness determination.
+
entity_id (Optional): Add a list of entity IDs so the switch only reacts to state changes of these entities. This will reduce the number of times the light will try to update it’s state.
+
+
+
+
Considerations
+
If you are using the state of a platform that takes extra time to load, the template light may get an ‘unknown’ state during startup. This results in error messages in your log file until that platform has completed loading. If you use is_state() function in your template, you can avoid this situation. For example, you would replace ‘{{ states.switch.source.state }}’ with this equivalent that returns true/false and never gives an unknown result:
+‘{{ is_state(‘switch.source’, ‘on’) }}’
+
Examples
+
In this section you will find some real life examples of how to use this light.
+
Theater Volume Control
+
This example shows a light that is actually a home theater’s volume. This component gives you the flexibility to provide whatever you’d like to send as the payload to the consumer including any scale conversions you may need to make; the media_player component needs a floating point percentage value 0.0-1.0
diff --git a/components/light.wink/index.html b/components/light.wink/index.html
index da4656ca0a..28d1ef9ce6 100644
--- a/components/light.wink/index.html
+++ b/components/light.wink/index.html
@@ -228,6 +228,9 @@ The above devices are confimed to work, but others may work as well.
diff --git a/components/light.yeelight/index.html b/components/light.yeelight/index.html
index 345bddf0ff..20cd3c3c59 100644
--- a/components/light.yeelight/index.html
+++ b/components/light.yeelight/index.html
@@ -219,6 +219,9 @@ This component is tested to work with models YLDP01YL, YLDP02YL and YLDP03YL. If
diff --git a/components/light.yeelightsunflower/index.html b/components/light.yeelightsunflower/index.html
index edbf8aab01..782bf25811 100644
--- a/components/light.yeelightsunflower/index.html
+++ b/components/light.yeelightsunflower/index.html
@@ -204,6 +204,9 @@ The Yeelight Sunflower hub supports SSDP discovery, but that has not been built
diff --git a/components/lutron/index.html b/components/lutron/index.html
index e8d3be9630..79d12be220 100644
--- a/components/lutron/index.html
+++ b/components/lutron/index.html
@@ -118,6 +118,9 @@ It is recommended to assign a static IP address to your Main Repeater. This ensu
diff --git a/components/lutron_caseta/index.html b/components/lutron_caseta/index.html
index bd24503761..502ce1b2db 100644
--- a/components/lutron_caseta/index.html
+++ b/components/lutron_caseta/index.html
@@ -125,6 +125,9 @@ It is recommended to assign a static IP address to your Lutron SmartBridge. This
diff --git a/components/mysensors/index.html b/components/mysensors/index.html
index 71f906eea0..77b157d162 100644
--- a/components/mysensors/index.html
+++ b/components/mysensors/index.html
@@ -270,6 +270,9 @@ The MQTT gateway requires MySensors version 2.0 and only the MQTT client gateway
diff --git a/components/neato/index.html b/components/neato/index.html
index 2ceb49ab74..215f20813c 100644
--- a/components/neato/index.html
+++ b/components/neato/index.html
@@ -120,6 +120,9 @@ The Home Assistant Neato platform has only be tested with a Botvac Connected. Th
diff --git a/components/netatmo/index.html b/components/netatmo/index.html
index db5bf28aa4..b93e9ebfe6 100644
--- a/components/netatmo/index.html
+++ b/components/netatmo/index.html
@@ -142,6 +142,9 @@ The Home Assistant Netatmo platform has only be tested with the classic indoor,
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
+
sender (Required): E-mail address of the sender.
+
recipient (Required): E-mail address of the recipient of the notification. This can be a recipient address or a list of addresses for multiple recipients.
server (Optional): SMTP server which is used to end the notifications. Defaults to localhost.
port (Optional): The port that the SMTP server is using. Defaults to 25.
timeout (Optional): The timeout in seconds that the SMTP server is using. Defaults to 5.
-
sender (Optional): E-mail address of the sender.
username (Optional): Username for the SMTP account.
password (Optional): Password for the SMTP server that belongs to the given username. If the password contains a colon it need to be wrapped in apostrophes.
-
recipient (Required): E-mail address of the recipient of the notification. This can be a recipient address or a list of addresses for multiple recipients.
starttls (Optional): Enables STARTTLS, eg. True or False. Defaults to False.
sender_name (Optional): Sets a custom ‘sender name’ in the emails headers (From: Custom name example@mail.com).
debug (Optional): Enables Debug, eg. True or False. Defaults to False.
To enable Telegram notifications in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry for the Telegram Bottelegram_bot:
- platform:polling
- api_key:ABCDEFGHJKLMNOPQRSTUVXYZ
- allowed_chat_ids:
- -CHAT_ID_1
- -CHAT_ID_2
- -CHAT_ID_3
+ -platform:polling
+ api_key:ABCDEFGHJKLMNOPQRSTUVXYZ
+ allowed_chat_ids:
+ -CHAT_ID_1
+ -CHAT_ID_2
+ -CHAT_ID_3# Example configuration.yaml entry for the notifiernotify:
@@ -118,11 +118,11 @@
service:notify.NOTIFIER_NAMEdata:title:'*Sendamessage*'
- message:'That's an example that _sends_ a *formatted* message with a custom keyboard.'
+ message:'That's an example that _sends_ a *formatted* message with a custom inline keyboard.'data:
- keyboard:
- -'/command1,/command2'
- -'/command3,/command4'
+ inline_keyboard:
+ -'Task1:/command1,Task2:/command2'
+ -'Task3:/command3,Task4:/command4'
Configuration variables:
@@ -154,8 +154,9 @@
url or file (Required): For local or remote path to an image.
caption (Optional): The title of the image.
-
username (Optional): Username for a URL which require HTTP basic authentication.
-
password (Optional): Username for a URL which require HTTP basic authentication.
+
username (Optional): Username for a URL which require HTTP authentication.
+
password (Optional): Username for a URL which require HTTP authentication.
+
authentication (Optional): Set to ‘digest’ to use HTTP digest authentication, defaults to ‘basic’.
keyboard (Optional): List of rows of commands, comma-separated, to make a custom keyboard.
inline_keyboard (Optional): List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with asociated callback data.
@@ -165,19 +166,23 @@
service:notify.NOTIFIER_NAMEdata:title:Send a document
- message:That's an example that sends a document.
+ message:That's an example that sends a document and a custom keyboard.data:document:file:/tmp/whatever.odfcaption:Document Title xy
+ keyboard:
+ -'/command1,/command2'
+ -'/command3,/command4'
Configuration variables:
url or file (Required): For local or remote path to a document.
caption (Optional): The title of the document.
-
username (Optional): Username for a URL which require HTTP basic authentication.
-
password (Optional): Username for a URL which require HTTP basic authentication.
+
username (Optional): Username for a URL which require HTTP authentication.
+
password (Optional): Username for a URL which require HTTP authentication.
+
authentication (Optional): Set to ‘digest’ to use HTTP digest authentication, defaults to ‘basic’.
keyboard (Optional): List of rows of commands, comma-separated, to make a custom keyboard.
inline_keyboard (Optional): List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with asociated callback data.
@@ -197,7 +202,6 @@
Configuration variables:
-
location (Required): For local or remote path to an image.
latitude (Required): The latitude to send.
longitude (Required): The longitude to send.
keyboard (Optional): List of rows of commands, comma-separated, to make a custom keyboard.
diff --git a/components/nuimo_controller/index.html b/components/nuimo_controller/index.html
index ec6ce92b65..812a871bf4 100644
--- a/components/nuimo_controller/index.html
+++ b/components/nuimo_controller/index.html
@@ -144,6 +144,9 @@ Then invoke home-assistant with hass --skip-pip<
Turn Off: Turn off all devices that were switched on from the start of the current activity.
+
Turn Off: Turn off all devices that were switched on from the start of the current activity.s
Turn On: Start an activity, will start the default activity from configuration.yaml if no activity is specified. The specified activity can either be the activity name or the activity ID from the configuration file written to your Home Assistant configuration directory. The service will respond faster if the activity ID is passed instead of the name.
-
Send Command: Send a command to one device, device ID and available commands are written to the configuration file at startup.
+
Send Command: Send a single command or a set of commands to one device, device ID and available commands are written to the configuration file at startup. You can optionally specify the number of times you wish to repeat the command(s) and delay you want between repeated command(s).
Sync: Synchronizes the Harmony device with the Harmony web service if any changes are made from the web portal or app.
Examples
diff --git a/components/rflink/index.html b/components/rflink/index.html
index 3aa9f314f9..42219ae7d3 100644
--- a/components/rflink/index.html
+++ b/components/rflink/index.html
@@ -205,6 +205,9 @@ When re-flashing the Arduino MEGA, disconnect the ESP8266 to avoid programming d
diff --git a/components/sensor.bbox/index.html b/components/sensor.bbox/index.html
index 3289740977..4d0a3549bc 100644
--- a/components/sensor.bbox/index.html
+++ b/components/sensor.bbox/index.html
@@ -130,6 +130,9 @@ Due to third party limitation, the sensors will only be available if Home Assist
diff --git a/components/sensor.blink/index.html b/components/sensor.blink/index.html
index 3963955f7a..f9d67eae03 100644
--- a/components/sensor.blink/index.html
+++ b/components/sensor.blink/index.html
@@ -113,6 +113,9 @@ To get your Blink sensors working with Home Assistant, follow the instructions f
diff --git a/components/sensor.broadlink/index.html b/components/sensor.broadlink/index.html
index baeda85e02..efffe5e17e 100644
--- a/components/sensor.broadlink/index.html
+++ b/components/sensor.broadlink/index.html
@@ -166,6 +166,9 @@ The pycrypto library needs to be available on your platform. On a typical window
diff --git a/components/sensor.haveibeenpwned/index.html b/components/sensor.haveibeenpwned/index.html
index bba9f2f0a6..e63c6a47f0 100644
--- a/components/sensor.haveibeenpwned/index.html
+++ b/components/sensor.haveibeenpwned/index.html
@@ -123,6 +123,9 @@ account has been breached as well as the added date of the breach data. This dat
+ The /dev-template page of your home-assistant UI can help you check if the values for start, end or duration are correct.
If you want to check if your period is right, just click on your component, the from and to attributes will show the start and end of the period, nicely formatted.
The hp_ilo platform allows you to do an API call to the HP ILO (Integrated Lights-Out) sensor of your server, and use this data in (template) sensors.
-
The component will output the ILO information in the sensor attributes so they can be accessed like that.
-
If the ILO only returns a single value (e.g. a temperature or state), it will be put in the state field.
+
The hp_ilo platform allows you to do an API call to the HP ILO (Integrated Lights-Out) sensor of your server, and use this data in Home Assistant sensors.
+
If the ILO or specified jsonpath query returns only a single value (e.g. a temperature or state), it will be put in the state field. If a data structure is returned, it will be placed in the ilo_data attribute.
Some more details about what can be retrieved from these sensors is available in the python-hpilo documentation.
port (Optional): The port on which the ILO can be reached, defaults to port 443.
username (Required): The username used to connect to the ILO.
password (Required): The password used to connect to the ILO.
-
monitored_variables array (Optional): Information to be collected from the ILO, defaults to server_name.
+
monitored_variables array (Optional): Sensors created from the ILO data. Defaults to an empty list (no sensors are created).
-
server_name: Get the name of the server this iLO is managing.
-
server_fqdn: Get the fqdn of the server this iLO is managing.
-
server_host_data: Get SMBIOS records that describe the host.
-
server_oa_info: Get information about the Onboard Administrator of the enclosing chassis.
-
server_power_status: Whether the server is powered on or not.
-
server_power_readings: Get current, min, max and average power readings.
-
server_power_on_time: How many minutes ago has the server been powered on.
-
server_asset_tag: Gets the server asset tag.
-
server_uid_status: Get the status of the UID light.
-
server_health: Get server health information.
-
network_settings: Get the iLO network settings.
+
name (Required): The sensor name.
+
sensor_type (Required): The sensor type, has to be one of the specified valid sensor types.
+
unit_of_measurement (Optional): The sensors’ unit of measurement.
+
value_template (Optional): When a Jinja2 template is specified here, the created sensor will output the template result. The ILO response can be referenced with the ilo_data variable.
+
Valid sensor_types:
+
+
server_name: Get the name of the server this iLO is managing.
+
server_fqdn: Get the fqdn of the server this iLO is managing.
+
server_host_data: Get SMBIOS records that describe the host.
+
server_oa_info: Get information about the Onboard Administrator of the enclosing chassis.
+
server_power_status: Whether the server is powered on or not.
+
server_power_readings: Get current, min, max and average power readings.
+
server_power_on_time: How many minutes ago has the server been powered on.
+
server_asset_tag: Gets the server asset tag.
+
server_uid_status: Get the status of the UID light.
+
server_health: Get server health information.
+
network_settings: Get the iLO network settings.
+
+
Example
+
In order to get two sensors reporting CPU fan speed and Ambient Inlet Temperature, as well as a dump of server_health on a HP Microserver Gen8, you could use the following in your configuration.yaml file
On this hardware you need to remove the below listed variables from monitored_variables: to avoid errors.
+
HP Microserver Gen8
+
On this hardware you should avoid using the following sensor_types as monitored_variables: to prevent errors.
server_oa_info
server_power_readings
diff --git a/components/sensor.http/index.html b/components/sensor.http/index.html
index 31e9b76a01..f9598ddfe2 100644
--- a/components/sensor.http/index.html
+++ b/components/sensor.http/index.html
@@ -142,6 +142,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
diff --git a/components/sensor.moldindicator/index.html b/components/sensor.moldindicator/index.html
index 635351efdd..56d2b44653 100644
--- a/components/sensor.moldindicator/index.html
+++ b/components/sensor.moldindicator/index.html
@@ -124,6 +124,9 @@ With the three measured temperatures (in Celsius or Fahrenheit), the calibration
diff --git a/components/sensor.neato/index.html b/components/sensor.neato/index.html
index 99c02d463a..d21a6c4cb3 100644
--- a/components/sensor.neato/index.html
+++ b/components/sensor.neato/index.html
@@ -113,6 +113,9 @@ The status sensor will contain attributes on the robots last clean session.
diff --git a/components/sensor.nest/index.html b/components/sensor.nest/index.html
index 6b740d0490..428a22e2e4 100644
--- a/components/sensor.nest/index.html
+++ b/components/sensor.nest/index.html
@@ -151,6 +151,9 @@ You must have the Nest component configured to u
diff --git a/components/sensor.octoprint/index.html b/components/sensor.octoprint/index.html
index d6adb80f1b..bd61335491 100644
--- a/components/sensor.octoprint/index.html
+++ b/components/sensor.octoprint/index.html
@@ -132,6 +132,9 @@ You must have the OctoPrint component confi
diff --git a/components/sensor.pushbullet/index.html b/components/sensor.pushbullet/index.html
index fa5072a430..022ac2b3cc 100644
--- a/components/sensor.pushbullet/index.html
+++ b/components/sensor.pushbullet/index.html
@@ -138,6 +138,9 @@ This sensor platform provide sensors that show the properties of the latest rece
diff --git a/components/sensor.rfxtrx/index.html b/components/sensor.rfxtrx/index.html
index 245f0e3e39..8f20a5788d 100644
--- a/components/sensor.rfxtrx/index.html
+++ b/components/sensor.rfxtrx/index.html
@@ -181,6 +181,9 @@ Then you should update your configuration to (_temperature is not needed):
diff --git a/components/sensor.sensehat/index.html b/components/sensor.sensehat/index.html
index 44389e23c9..a6cb17440b 100644
--- a/components/sensor.sensehat/index.html
+++ b/components/sensor.sensehat/index.html
@@ -230,6 +230,9 @@ These issues have been discussed in the repository issue (#5093)[https://github.
diff --git a/components/sensor.synologydsm/index.html b/components/sensor.synologydsm/index.html
index e5d40d75a3..96ea60f32f 100644
--- a/components/sensor.synologydsm/index.html
+++ b/components/sensor.synologydsm/index.html
@@ -165,6 +165,9 @@ This sensor will wake up your Synology NAS if it’s in hibernation mode.
diff --git a/components/sensor.temper/index.html b/components/sensor.temper/index.html
index 6e84856361..1d76be90c8 100644
--- a/components/sensor.temper/index.html
+++ b/components/sensor.temper/index.html
@@ -112,6 +112,9 @@ The calculation follows the formula scale * sens
diff --git a/components/sensor.template/index.html b/components/sensor.template/index.html
index 5fb81491af..d1cddf3436 100644
--- a/components/sensor.template/index.html
+++ b/components/sensor.template/index.html
@@ -202,6 +202,9 @@ Please note the blank line to close the multi-line template.
diff --git a/components/sensor.ups/index.html b/components/sensor.ups/index.html
index 9fb98f2838..8f4b2575f7 100644
--- a/components/sensor.ups/index.html
+++ b/components/sensor.ups/index.html
@@ -130,6 +130,9 @@ The UPS sensor logs into the UPS My Choice website to scrape package data. It do
The usps platform allows one to track deliveries by the US Postal Service (USPS).
-In addition to having a USPS account, you will need to complete the “Opt-In” process by clicking “Get Started Now” on this page. Currently, you also will need to have a package listed in the “Package Dashboard” in order for the component to complete set-up.
+
The usps platform allows one to track deliveries and inbound mail from the US Postal Service (USPS).
+In addition to having a USPS account, you will need to complete the “Opt-In” process by clicking “Get Started Now” on this page. You must also “Opt-In” to Informed Delivery to see inbound mail.
To enable this sensor, add the following lines to your configuration.yaml:
# Example configuration.yaml entrysensor:
@@ -76,27 +76,12 @@ In addition to having a USPS account, you will need to complete the “Opt-In”
password:YOUR_PASSWORD
+
You will see two new sensors, one for packages and one for mail.
Configuration options for the USPS Sensor:
username (Required): The username to access the MyUSPS service.
password (Required): The password for the given username.
-
name (Optional): Name the sensor (default: your mailing address).
-
update_inverval (Optional): Minimum time interval between updates. Default is 1 hour. Supported formats:
-
-
update_interval: 'HH:MM:SS'
-
update_interval: 'HH:MM'
-
Time period dictionary, e.g.:
-
update_interval:
- # At least one of these must be specified:
- days: 0
- hours: 0
- minutes: 3
- seconds: 30
- milliseconds: 0
-
-
-
-
+
name (Optional): Prefix for sensor names (defaults to “USPS”)
The USPS sensor logs into the MyUSPS website to scrape package data. It does not use an API.
@@ -131,6 +116,9 @@ The USPS sensor logs into the MyUSPS website to scrape package data. It does not
diff --git a/components/sensor.wink/index.html b/components/sensor.wink/index.html
index a66210cbd6..106257cca7 100644
--- a/components/sensor.wink/index.html
+++ b/components/sensor.wink/index.html
@@ -143,6 +143,9 @@ The above devices are confimed to work, but others may work as well.
diff --git a/components/sensor.zoneminder/index.html b/components/sensor.zoneminder/index.html
index 892d5bebec..8b65d6617b 100644
--- a/components/sensor.zoneminder/index.html
+++ b/components/sensor.zoneminder/index.html
@@ -125,6 +125,9 @@ You must have the ZoneMinder component con
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index aedf251892..cbbd522267 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -300,6 +300,9 @@ This switch will shutdown your host immediately, there will be no confirmation.
diff --git a/components/switch.fritzdect/index.html b/components/switch.fritzdect/index.html
index b6be3efa30..f55afedf8d 100644
--- a/components/switch.fritzdect/index.html
+++ b/components/switch.fritzdect/index.html
@@ -223,6 +223,9 @@ If this component throws an error when starting home-assistant you should check
diff --git a/components/switch.hikvision/index.html b/components/switch.hikvision/index.html
index f270dfcc5c..4c8d80d840 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -220,6 +220,9 @@ Currently works using default https port only.
diff --git a/components/switch.mqtt/index.html b/components/switch.mqtt/index.html
index 0abcba3db2..924fbca651 100644
--- a/components/switch.mqtt/index.html
+++ b/components/switch.mqtt/index.html
@@ -281,6 +281,9 @@ Make sure that your topic match exact. some-topi
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index c6674ffe89..eb184e68d2 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -219,6 +219,9 @@ This component relies on raw TCP commands to PulseAudio. In order for PulseAudio
diff --git a/components/switch.rest/index.html b/components/switch.rest/index.html
index 5fbe223929..9b8b86b2e4 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -241,6 +241,9 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/switch.rfxtrx/index.html b/components/switch.rfxtrx/index.html
index d10d3ae7f8..36345bb73b 100644
--- a/components/switch.rfxtrx/index.html
+++ b/components/switch.rfxtrx/index.html
@@ -335,6 +335,9 @@ Then you should update your configuration to:
diff --git a/components/switch.rpi_rf/index.html b/components/switch.rpi_rf/index.html
index 88cfc37334..ab8d307295 100644
--- a/components/switch.rpi_rf/index.html
+++ b/components/switch.rpi_rf/index.html
@@ -233,6 +233,9 @@ For more info see the PyPi module description:
if the message is sent from a press from an inline button, for example, a callback query is received, and Home Assistant will fire a telegram_callback event with:
diff --git a/components/tradfri/index.html b/components/tradfri/index.html
index 76b0930164..5f6b1215c7 100644
--- a/components/tradfri/index.html
+++ b/components/tradfri/index.html
@@ -144,6 +144,9 @@ If you see an “Unable to connect” message, restart the gateway and try again
diff --git a/components/twilio/index.html b/components/twilio/index.html
index eb10aa881c..d2ad76ef30 100644
--- a/components/twilio/index.html
+++ b/components/twilio/index.html
@@ -107,6 +107,9 @@ Calls are limited to 10 minutes and will play a short trial message before your
diff --git a/components/wink/index.html b/components/wink/index.html
index a805e368fd..bc4953926e 100644
--- a/components/wink/index.html
+++ b/components/wink/index.html
@@ -172,6 +172,9 @@ The Wink hub can only be accessed via the cloud. This means it requires an activ
diff --git a/components/zha/index.html b/components/zha/index.html
index e5a4f2092e..419c46597f 100644
--- a/components/zha/index.html
+++ b/components/zha/index.html
@@ -135,6 +135,9 @@ and the path to the serial device for the radio and path to the database which w
Triggers when the state of tracked entities change. If only entity_id given will match all state changes.
+
Triggers when the state of tracked entities change. If only entity_id given will match all state changes, even if only state attributes change.
automation:trigger:platform:stateentity_id:device_tracker.paulus, device_tracker.anne_therese# Optionalfrom:'not_home'
+ # Optionalto:'home'
- # Alias for 'to'
- state:'home'
-
# If given, will trigger when state has been the to state for X time.for:hours:1
@@ -138,6 +136,9 @@
Use quotes around your values for from and to to avoid the YAML parser interpreting values as booleans.
+
+ Using state as an alias for to is deprecated.
+
Sun trigger
Trigger when the sun is setting or rising. An optional time offset can be given to have it trigger for example 45 minutes before sunset, when dusk is setting in.
automation:
@@ -159,7 +160,7 @@ With template triggers you can also evaluate attribute changes by using is_state
Time trigger
-
Time can be triggered in many ways. The most common is to specify after and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. You can prefix the value with a / to match whenever the value is divisible by that number. You cannot use after together with hour, minute or second.
+
Time can be triggered in many ways. The most common is to specify at and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. You can prefix the value with a / to match whenever the value is divisible by that number. You cannot use at together with hour, minute or second.
automation:trigger:platform:time
@@ -170,9 +171,9 @@ With template triggers you can also evaluate attribute changes by using is_state
automation 2:trigger:platform:time
- # When 'after' is used, you cannot also match on hour, minute, seconds.
+ # When 'at' is used, you cannot also match on hour, minute, seconds.# Military time format.
- after:'15:32:00'
+ at:'15:32:00'automation 3:trigger:
diff --git a/docs/tools/scripts/index.html b/docs/tools/scripts/index.html
index 81aac21730..23fdfea863 100644
--- a/docs/tools/scripts/index.html
+++ b/docs/tools/scripts/index.html
@@ -83,8 +83,14 @@
$ hass --script keyring
+
Benchmark
+
For testing the performance of Home Assistant the Benchmark scipt runs until you exit using Control+C.
+
Firing and handling of a million events.
+
$ hass --script benchmark async_million_events
+
+
Old scripts
-
Usally those scripts were only use when a massive update happend and was announced in the release notes.
+
Usally those scripts were only used when a massive update happend and was announced in the release notes.
db_migrator: Migrate an existing SQLite database to the new schema.
influxdb_migrator: Convert an old InfluxDB to the new format.
diff --git a/docs/z-wave/index.html b/docs/z-wave/index.html
index c725972e2a..6f5e068a5e 100644
--- a/docs/z-wave/index.html
+++ b/docs/z-wave/index.html
@@ -263,6 +263,10 @@ Depending on what’s plugged into your USB ports, the name found above may chan
replace_failed_node
Replace a failed device with another. If the node is not in the controller’s failed nodes list, or the node responds, this command will fail.
+
+
reset_node_meters
+
Reset a node’s meter values. Only works if the node supports this.
+
set_config_parameter
Let’s the user set a config parameter to a node.
@@ -291,14 +295,14 @@ Depending on what’s plugged into your USB ports, the name found above may chan
-alias:soft reset at 2:30amtrigger:platform:time
- after:'2:30:00'
+ at:'2:30:00'action:service:zwave.soft_reset-alias:heal at 2:31amtrigger:platform:time
- after:'2:31:00'
+ at:'2:31:00'action:service:zwave.heal_network
diff --git a/images/screenshots/hp_ilo_sensors.png b/images/screenshots/hp_ilo_sensors.png
new file mode 100644
index 0000000000..0c7c4a96ad
Binary files /dev/null and b/images/screenshots/hp_ilo_sensors.png differ
diff --git a/images/supported_brands/arlo.png b/images/supported_brands/arlo.png
new file mode 100644
index 0000000000..1dbcc4ffe8
Binary files /dev/null and b/images/supported_brands/arlo.png differ
diff --git a/images/supported_brands/rachio.png b/images/supported_brands/rachio.png
new file mode 100644
index 0000000000..340105ff82
Binary files /dev/null and b/images/supported_brands/rachio.png differ
diff --git a/sitemap.xml b/sitemap.xml
index 7dec430c2b..ccb51ec7a5 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1786,6 +1786,9 @@
https://home-assistant.io/components/sensor.lastfm/
+https://home-assistant.io/components/light.template/
+
+https://home-assistant.io/components/recorder/
@@ -1810,6 +1813,9 @@
https://home-assistant.io/components/light.osramlightify/
+https://home-assistant.io/components/camera.arlo/
+
+https://home-assistant.io/components/switch.flux/
@@ -2935,6 +2941,18 @@
https://home-assistant.io/components/cover.lutron_caseta/
+https://home-assistant.io/components/fan.zwave/
+
+
+https://home-assistant.io/components/switch.rachio/
+
+
+https://home-assistant.io/components/arlo/
+
+
+https://home-assistant.io/components/sensor.arlo/
+
+https://home-assistant.io/components/sensor.ted5000/
@@ -3473,62 +3491,62 @@
https://home-assistant.io/demo/frontend.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/index.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-history.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/demo/panels/ha-panel-map.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/googlef4f3693c209fe788.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00https://home-assistant.io/static/mdi-demo.html
-2017-06-03T19:44:17+00:00
+2017-06-04T03:14:51+00:00
+ 
@@ -81,17 +80,8 @@
+