localhost.5007.5007.localhost.This can typically be one of those batteryless wall switches. Currently only one type has been tested: Eltako FT55. Other devices will most likely not work without changing the Home Asisstant code.
+This can typically be one of those batteryless wall switches. Currently only one type has been tested: Eltako FT55. Other devices will most likely not work without changing the Home Assistant code.
To use your EnOcean device, you first have to set up your EnOcean hub and then add the following to your configuration.yaml file:
basic or digest.true means decending rather than ascending)true means descending rather than ascending)Configuration variables:
high (default) or low, depicting whether the binary sensor is considered on when the pin is high or low.The ffmpeg platform allows you to use any video feed as a camera in Home Assistant via FFmpeg. This video source must support multiple simultaenous reads, because for every concurrent Home Assistant user, a connection will be made to the source every 10 seconds. Normally this should not be a problem.
The ffmpeg platform allows you to use any video feed as a camera in Home Assistant via FFmpeg. This video source must support multiple simultaneous reads, because for every concurrent Home Assistant user, a connection will be made to the source every 10 seconds. Normally this should not be a problem.
To enable your FFmpeg feed in your installation, add the following to your configuration.yaml file:
synology platform allows you to watch
True.entity_id for a temperature sensor, target_sensor.state must be temperature.Configuration variables:
The radiotherm climate platform let you control a thermostat from Radio Thermostat.
The underlaying library supports:
+The underlying library supports:
Temperature settings from Home Assistant will be sent to thermostat and then hold at that temperature. Set to False if you set a thermostat schedule on the thermostat itself and just want Home Assistant to send temporary temperature changes.
Multiple thermostats could be assigned by using host: if auto-detetion is not used.
Multiple thermostats could be assigned by using host: if auto-detection is not used.
climate:
platform: radiotherm
diff --git a/components/demo/index.html b/components/demo/index.html
index 92d3f29ec8..da2dfb2cae 100644
--- a/components/demo/index.html
+++ b/components/demo/index.html
@@ -90,7 +90,7 @@
- The demo platform allows you to use components which are providing a demo of their implementation. The demo entities are dummies but show you how the acutal platform looks like. This way you can run own demonstration instance like the online Home Assistant demo or hass --demo-mode but combined with your own real/functional platforms.
+ The demo platform allows you to use components which are providing a demo of their implementation. The demo entities are dummies but show you how the actual platform looks like. This way you can run own demonstration instance like the online Home Assistant demo or hass --demo-mode but combined with your own real/functional platforms.
Available demo platforms:
diff --git a/components/device_tracker.bluetooth_tracker/index.html b/components/device_tracker.bluetooth_tracker/index.html
index e2a9eb1d94..b343b0a8d6 100644
--- a/components/device_tracker.bluetooth_tracker/index.html
+++ b/components/device_tracker.bluetooth_tracker/index.html
@@ -100,7 +100,7 @@
In some cases it can be that your device is not discovered. In that case let your phone scan for BT devices while you restart Home Assistant. Just hit Scan on your phone all the time until Home Assisstant is fully restarted and the device should appear in known_devices.yaml.
In some cases it can be that your device is not discovered. In that case let your phone scan for BT devices while you restart Home Assistant. Just hit Scan on your phone all the time until Home Assistant is fully restarted and the device should appear in known_devices.yaml.
For additional configuration variables check the Device tracker page.
diff --git a/components/device_tracker.owntracks/index.html b/components/device_tracker.owntracks/index.html index 9b30dc5207..067ece4e0b 100644 --- a/components/device_tracker.owntracks/index.html +++ b/components/device_tracker.owntracks/index.html @@ -110,7 +110,7 @@A full sample configuration for the owntracks plaftfrom is shown below:
A full sample configuration for the owntracks platform is shown below:
# Example configuration.yaml entry
device_tracker:
diff --git a/components/device_tracker.tplink/index.html b/components/device_tracker.tplink/index.html
index 3132da68ef..732c34c159 100644
--- a/components/device_tracker.tplink/index.html
+++ b/components/device_tracker.tplink/index.html
@@ -93,7 +93,7 @@
The tplink platform allows you to detect presence by looking at connected devices to a TP-Link device. This includes the ArcherC9 line.
-TP-Link devices typically only allow one login at a time to the admin console. This component will count torwards your one allowed login. Depending on how aggressively you configure device_tracker you may not be able to access the admin console of your TP-Link device without first stopping Home Assistant (and waiting a few minutes for the session to timeout) before you’ll be able to login.
+TP-Link devices typically only allow one login at a time to the admin console. This component will count towards your one allowed login. Depending on how aggressively you configure device_tracker you may not be able to access the admin console of your TP-Link device without first stopping Home Assistant (and waiting a few minutes for the session to timeout) before you’ll be able to login.
# Example configuration.yaml entry
@@ -117,7 +117,7 @@ TP-Link devices typically only allow one login at a time to the admin console.
- Go to the login page of your router. (default: 192.168.0.1)
- - Type in the password you use to login into the passsword field.
+ - Type in the password you use to login into the password field.
- Click somewhere else on the page so that the password field is not selected anymore.
- Open the JavaScript console of your browser (usually by pressing F12 and then clicking on “Console”).
- Type
document.getElementById("login-password").value;.
diff --git a/components/ecobee/index.html b/components/ecobee/index.html
index aef9f8d191..83846226ec 100644
--- a/components/ecobee/index.html
+++ b/components/ecobee/index.html
@@ -136,7 +136,7 @@
Configuration variables:
- - api_key (Required): Your ecobee API key. This is only needed for the inital setup of the component. Once registered it can be removed. If you revoke the key in the ecobee portal you will need to update this again and remove the ecobee.conf file in the
.homeassistant configuration path.
+ - api_key (Required): Your ecobee API key. This is only needed for the initial setup of the component. Once registered it can be removed. If you revoke the key in the ecobee portal you will need to update this again and remove the ecobee.conf file in the
.homeassistant configuration path.
- hold_temp (Optional): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event. Defaults to
False.
diff --git a/components/emoncms_history/index.html b/components/emoncms_history/index.html
index eb3cb8116c..db8a3b6f75 100644
--- a/components/emoncms_history/index.html
+++ b/components/emoncms_history/index.html
@@ -112,7 +112,7 @@
- url (Required): The root URL of your Emoncms installation. (Use https://emoncms.org for the cloud based version)
- inputnode (Required): Input node that will be used inside emoncms. Please make sure you use a dedicated, not used before, node for this component!
- whitelist (Required): List of entity IDs you want to publish.
- - scan_interval (Optional): Defines, in seconds, how reguarly the states of the whitelisted entities are being gathered and send to emoncms. Default is 30 seconds.
+ - scan_interval (Optional): Defines, in seconds, how regularly the states of the whitelisted entities are being gathered and send to emoncms. Default is 30 seconds.
diff --git a/components/emulated_hue/index.html b/components/emulated_hue/index.html
index da32a5e71f..9e7a9e90be 100644
--- a/components/emulated_hue/index.html
+++ b/components/emulated_hue/index.html
@@ -94,7 +94,7 @@
entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo with no set up cost outside of configuration changes.
- It is recommended to assign a static IP address to the computer running Home Assistant. This is because the Amazon Echo discovers devices by IP addresss, and if the IP changes, the Echo won’t be able to control it. This is easiest done from your router, see your router’s manual for details.
+ It is recommended to assign a static IP address to the computer running Home Assistant. This is because the Amazon Echo discovers devices by IP addresses, and if the IP changes, the Echo won’t be able to control it. This is easiest done from your router, see your router’s manual for details.
Configuration
@@ -124,7 +124,7 @@ entities. The driving use case behind this functionality is to allow Home Assist
-
-
expose_by_default (Optional): Whether or not entities should be exposed via the bridge by default instead of explicitly (see the ‘emulated_hue’ customization below). If not specified, this defaults to true. Warning: If you have a lot of devices (more than 49 total across all exposed domains), you should be careful with this opton. Exposing more devices than Alexa supports can result in it not seeing any of them. If you are having trouble getting any devices to show up, try disabling this, and explicitly exposing just a few devices at a time to see if that fixes it.
+ expose_by_default (Optional): Whether or not entities should be exposed via the bridge by default instead of explicitly (see the ‘emulated_hue’ customization below). If not specified, this defaults to true. Warning: If you have a lot of devices (more than 49 total across all exposed domains), you should be careful with this option. Exposing more devices than Alexa supports can result in it not seeing any of them. If you are having trouble getting any devices to show up, try disabling this, and explicitly exposing just a few devices at a time to see if that fixes it.
- exposed_domains (Optional): The domains that are exposed by default if
expose_by_default is set to true. If not specified, this defaults to the following list:
diff --git a/components/ffmpeg/index.html b/components/ffmpeg/index.html
index 0df22022e5..6bf739475f 100644
--- a/components/ffmpeg/index.html
+++ b/components/ffmpeg/index.html
@@ -93,7 +93,7 @@
The FFmpeg component allows other Home Assistant components to process video and audio streams. This component supports all FFmpeg versions since 3.0.0; if you have a older version, please update.
-You need the ffmpeg binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from debian-backports. If you want hardware acceleration support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are avilable on the FFmpeg website.
+You need the ffmpeg binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from debian-backports. If you want hardware acceleration support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the FFmpeg website.
To set it up, add the following information to your configuration.yaml file:
diff --git a/components/hdmi_cec/index.html b/components/hdmi_cec/index.html
index ca2afed685..ae02221d36 100644
--- a/components/hdmi_cec/index.html
+++ b/components/hdmi_cec/index.html
@@ -117,7 +117,7 @@
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 Assistant 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 Assistant 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
diff --git a/components/homematic/index.html b/components/homematic/index.html
index a75f0d63e1..f841a834d5 100644
--- a/components/homematic/index.html
+++ b/components/homematic/index.html
@@ -102,7 +102,7 @@
Simple remote controls
-If you want to see if a specific device you have is supported, head over to the pyhomematic repository and browse through the sourcecode. A dictionary with the device identifiers (e.g. HM-Sec-SC-2) can be found within the relevant modules near the bottom.
+If you want to see if a specific device you have is supported, head over to the pyhomematic repository and browse through the source code. A dictionary with the device identifiers (e.g. HM-Sec-SC-2) can be found within the relevant modules near the bottom.
We automatically detect all devices we currently support and try to generate useful names. If you enable name-resolving, we try to fetch names from Metadata (Homegear), via JSON-RPC or the XML-API you may have installed on your CCU. Since this may fail this is disabled by default.
You can manually override the created entities be using Home Assistants Customizing feature. With it you are able to hide entities you don’t need to see within the UI.
@@ -124,7 +124,7 @@ You can manually override the created entities be using Home Assistants resolvenames (Optional): <metadata, json, xml> Try to fetch device names. Defaults to False if not specified.
username (Optional): When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU.
password (Optional): When fetching names via JSON-RPC, you need to specify the password of the user you have configured above.
- delay (Optional): Delay fetching of current state per deivce on startup. Used to prevent overloading of the CCU. Defaults to 0.5.
+ delay (Optional): Delay fetching of current state per device on startup. Used to prevent overloading of the CCU. Defaults to 0.5.
variables (Optional): True or False if you want use CCU2/Homegear variables. Default False.
diff --git a/components/input_select/index.html b/components/input_select/index.html
index 0114e77143..c63f12838b 100644
--- a/components/input_select/index.html
+++ b/components/input_select/index.html
@@ -90,7 +90,7 @@
- The input_select component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. When a user selectes a new item, a state transition event is generated. This state event can be used in an automation trigger.
+ The input_select component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. When a user selects a new item, a state transition event is generated. This state event can be used in an automation trigger.
To enable this platform, add the following lines to your configuration.yaml:
diff --git a/components/isy994/index.html b/components/isy994/index.html
index cf89b1aed5..55160da0c5 100644
--- a/components/isy994/index.html
+++ b/components/isy994/index.html
@@ -114,7 +114,7 @@ The ISY994 controller is manufactured by cover the THEN clause is evaluated for the open_cover service, the ELSE clause is evaluated for the close_cover service
fan the THEN clause is evaluated for the turn_on service, the ELSE clause is evaluated for the turn_off service
lock the THEN clause is evaluated for the lock service, the ELSE clause is evaluated for the unlock service
- switch the THEN clause is evaluated for the turn_on srevice, the ELSE clause is evaluated for the turn_off service
+ switch the THEN clause is evaluated for the turn_on service, the ELSE clause is evaluated for the turn_off service
diff --git a/components/light.hyperion/index.html b/components/light.hyperion/index.html
index ce858115d9..5864cca44c 100644
--- a/components/light.hyperion/index.html
+++ b/components/light.hyperion/index.html
@@ -92,7 +92,7 @@
This platform allows you to integrate your Hyperion into Home Assistant.
-Hyperion is an opensource Ambilight implementation which runs on many platforms.
+Hyperion is an open source Ambilight implementation which runs on many platforms.
# Example configuration.yaml entry
light:
diff --git a/components/light.yeelight/index.html b/components/light.yeelight/index.html
index bcf44342cf..433afb89ec 100644
--- a/components/light.yeelight/index.html
+++ b/components/light.yeelight/index.html
@@ -116,7 +116,7 @@ Determine your bulb ip (using router, software, ping …)
-Tests are only made with a YLDP03YL model. Because it’s the only hardware developer owns. If you have bugs with another kind of model, you could open an issue on Home Assitant Github
+Tests are only made with a YLDP03YL model. Because it’s the only hardware developer owns. If you have bugs with another kind of model, you could open an issue on Home Assistant Github
diff --git a/components/light.zigbee/index.html b/components/light.zigbee/index.html
index 92c3074427..14add87327 100644
--- a/components/light.zigbee/index.html
+++ b/components/light.zigbee/index.html
@@ -106,7 +106,7 @@
- name (Required): The name you would like to give the light in Home Assistant.
- pin (Required): The number identifying which pin to use.
- - address (Optional): The long 64 bit address of the remote ZigBee device whose digital output pin you wouldd like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.
+ - address (Optional): The long 64 bit address of the remote ZigBee device whose digital output pin you would like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.
- on_state (Optional): Either
high (default) or low, depicting whether the digital output pin is pulled high or low when the light is turned on.
diff --git a/components/light/index.html b/components/light/index.html
index 92e07af509..fad48975f4 100644
--- a/components/light/index.html
+++ b/components/light/index.html
@@ -138,12 +138,12 @@ The light component supports multiple entries in configuration.yaml
xy_coloryes
- A list containing two floats representing the xy color you want the light to be. Two comma seperated floats that represent the color in XY.
+ A list containing two floats representing the xy color you want the light to be. Two comma separated floats that represent the color in XY.
rgb_coloryes
- A list containing three integers representing the rgb color you want the light to be. Three comma seperated integers that represent the color in RGB. You can find a great chart here: Hue Color Chart
+ A list containing three integers representing the rgb color you want the light to be. Three comma separated integers that represent the color in RGB. You can find a great chart here: Hue Color Chart
color_tempSelect System > About > Network.
- The following commands must be run in a Python 2.x environment. They will allow the component to function in an Ubuntu 16.04/Hassbian enviorment.
+ The following commands must be run in a Python 2.x environment. They will allow the component to function in an Ubuntu 16.04/Hassbian environment.
apt-get install swig libssl-dev python-dev libusb-1.0-0pip install flask
- The mpd platform allows you to control a Music Player Daemon from Home Assistant. Unfortunatly you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs.
+ The mpd platform allows you to control a Music Player Daemon from Home Assistant. Unfortunately you will not be able to manipulate the playlist (add or delete songs) or add transitions between the songs.
Even though no playlist manipulation is possible, it is possible to use the play_media service to load an existing saved playlist as part of an automation or scene.
diff --git a/components/media_player.sonos/index.html b/components/media_player.sonos/index.html
index 665bcc5fb5..35a52e83d2 100644
--- a/components/media_player.sonos/index.html
+++ b/components/media_player.sonos/index.html
@@ -153,7 +153,7 @@
Service sonos_restore
-Restore a previosly taken snapshot of one or more speakers. If no entity_id is provided, all speakers are restored.
+Restore a previously taken snapshot of one or more speakers. If no entity_id is provided, all speakers are restored.
diff --git a/components/media_player.universal/index.html b/components/media_player.universal/index.html
index f6eb9dab7f..400c30cea0 100644
--- a/components/media_player.universal/index.html
+++ b/components/media_player.universal/index.html
@@ -138,7 +138,7 @@
It is recommended that the command turn_on, the command turn_off, and the attribute state all be provided together. The state attribute indicates if the Media Player is on or off. If state indicates the media player is off, this status will take precedent over the states of the children. If all the children are idle/off and state is on, the universal media player’s state will be on.
-It is also recomended that the command volume_up, the command volume_down, the command volume_mute, and the attribute is_volume_muted all be provided together. The attribute is_volume_muted should return either True or the on state when the volume is muted. The volume_mute service should toggle the mute setting.
+It is also recommended that the command volume_up, the command volume_down, the command volume_mute, and the attribute is_volume_muted all be provided together. The attribute is_volume_muted should return either True or the on state when the volume is muted. The volume_mute service should toggle the mute setting.
Below is an example configuration.
diff --git a/components/media_player.yamaha/index.html b/components/media_player.yamaha/index.html
index e2c6544bf7..f187fbdf27 100644
--- a/components/media_player.yamaha/index.html
+++ b/components/media_player.yamaha/index.html
@@ -124,7 +124,7 @@
- Not specifying the host variable will result in automatically searching your network for Yamaha Receivers. It will add a media player device for each one.
- For receivers that support more than one zone, Home Assistant will add one media player per zone supported by the player, named “$name Zone 2” and “$name Zone 3”.
- - In some cases, autodiscovery fails due to a known bug in the receiver’s firmware. It is possible to manually specify the reveiver’s IP address or via it’s hostname (if it is discoverably by your DNS) then.
+ - In some cases, autodiscovery 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 discoverably by your DNS) then.
- Please note: If adding the IP address or hostname manually, you must enable network standby on your receiver, or else startup of Home Assistant will hang if you have your receiver switched off.
- Currently, this component supports powering on/off, mute, volume control and source selection. Playback controls, for instance play and stop are available for sources that supports it.
diff --git a/components/mqtt/index.html b/components/mqtt/index.html
index 837ea777ed..c29ca9eaa2 100644
--- a/components/mqtt/index.html
+++ b/components/mqtt/index.html
@@ -329,7 +329,7 @@ Home Assistant will automatically load the correct certificate if you connect to
Testing your setup
-The mosquitto broker package ships commandline tools to send and recieve MQTT messages. As an alternative have a look at hbmqtt_pub and hbmqtt_sub which are provied by HBMQTT. For sending test messages to a broker running on localhost check the example below:
+The mosquitto broker package ships commandline tools to send and receive MQTT messages. As an alternative have a look at hbmqtt_pub and hbmqtt_sub which are provided by HBMQTT. For sending test messages to a broker running on localhost check the example below:
$ mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON"
diff --git a/components/mqtt_eventstream/index.html b/components/mqtt_eventstream/index.html
index 5e4705511e..3ee9e1df06 100644
--- a/components/mqtt_eventstream/index.html
+++ b/components/mqtt_eventstream/index.html
@@ -104,8 +104,8 @@
Configuration variables:
- - publish_topic (Required): Topic for pushlishing local events
- - subscribe_topic (Required): Topic to recieve events from the remote server.
+ - publish_topic (Required): Topic for publishing local events
+ - subscribe_topic (Required): Topic to receive events from the remote server.
diff --git a/components/notify.group/index.html b/components/notify.group/index.html
index 6ed809b435..b5d7623655 100644
--- a/components/notify.group/index.html
+++ b/components/notify.group/index.html
@@ -113,7 +113,7 @@
- services (Required): A list of all the services to be included in the group.
- service (Required): The service part of an entity ID, i.e. if you use
notify.html5 normally, just put html5.
- - data (Optional): A dictonary containing parameters to add to all notify payloads. This can be anything that is valid to use in a payload, such as
data, message, target, title.
+ - data (Optional): A dictionary containing parameters to add to all notify payloads. This can be anything that is valid to use in a payload, such as
data, message, target, title.
diff --git a/components/notify.pushetta/index.html b/components/notify.pushetta/index.html
index 8fdb845efe..fb86a16042 100644
--- a/components/notify.pushetta/index.html
+++ b/components/notify.pushetta/index.html
@@ -111,7 +111,7 @@
- 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.
- api_key (Required): Your API key for Pushetta.
- channel_name (Required): The name of your channel.
- - send_test_msg (Optional): Disable/enable the test message send on Home Asssitant’s startup to test the API key and the existance of the channel. Default to
False.
+ - send_test_msg (Optional): Disable/enable the test message send on Home Assistant’s startup to test the API key and the existence of the channel. Default to
False.
It’s easy to test your Pushetta setup outside of Home Assistant. Assuming you have a channel home-assistant, just fire a request and check the channel page in the dashboard for a new message.
diff --git a/components/notify.rest/index.html b/components/notify.rest/index.html
index e2f17e9e34..cf0d215932 100644
--- a/components/notify.rest/index.html
+++ b/components/notify.rest/index.html
@@ -106,7 +106,7 @@
- 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.
- - resource (Required): The resource or endpoint that will recieve the value.
+ - resource (Required): The resource or endpoint that will receive the value.
- method (Optional): The method of the request. Default is GET.
- message_param_name (Optional): Parameter name for the message. Defaults to
message.
- title_param_name (Optional): Parameter name for the title. Defaults to none.
diff --git a/components/notify.slack/index.html b/components/notify.slack/index.html
index aefbdd3ef4..1a5cab0c55 100644
--- a/components/notify.slack/index.html
+++ b/components/notify.slack/index.html
@@ -98,7 +98,7 @@
Don’t forget to invite the bot to the room where you want to get the notifications.
-To enable the slack notification in your installation, add the following to your configuration.yaml file:
+To enable the Slack notification in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
notify:
@@ -113,10 +113,10 @@
- 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.
- - api_key (Required): The slack API token to use for sending slack messages.
+ - api_key (Required): The Slack API token to use for sending Slack messages.
- default_channel (Required): The default channel to post to if no channel is explicitly specified when sending the notification message.
- - username (Optional): Setting username will allow homeassistant to post to slack using the username specified. By default not setting this will post to slack using the user account or botname that you generated the api_key as.
- - icon (Optional): Use one of the slack emoji’s as an Icon for the supplied username. Slack uses the standard emoji sets used here.
+ - username (Optional): Setting username will allow Home Assistant to post to Slack using the username specified. By default not setting this will post to Slack using the user account or botname that you generated the api_key as.
+ - icon (Optional): Use one of the Slack emoji’s as an Icon for the supplied username. Slack uses the standard emoji sets used here.
To use notifications, please see the getting started with automation page.
diff --git a/components/notify.syslog/index.html b/components/notify.syslog/index.html
index 7fefb1767e..eb794a9667 100644
--- a/components/notify.syslog/index.html
+++ b/components/notify.syslog/index.html
@@ -214,7 +214,7 @@
-For details about facility, option, and priority please consult the wikpedia article and RFC 3164.
+For details about facility, option, and priority please consult the wikipedia article and RFC 3164.
To use notifications, please see the getting started with automation page.
diff --git a/components/openalpr/index.html b/components/openalpr/index.html
index 38a5bc9b26..bab52a4205 100644
--- a/components/openalpr/index.html
+++ b/components/openalpr/index.html
@@ -100,7 +100,7 @@ If you want use a video stream. You need setup the
If you want process all data local you need the command line tool alpr in version > 2.3.1
-If you don’t found binarys for you distribution you can compile from source. A documention how to build a openalpr is found here.
+If you don’t find binaries for your distribution you can compile from source. Documention of how to build openalpr is found here.
On a debian system you can use this cmake command to build only the command line tool (which second part on linux build instruction - ubuntu 14.04+):
cmake -DWITH_TEST=FALSE -DWITH_BINDING_JAVA=FALSE --DWITH_BINDING_PYTHON=FALSE --DWITH_BINDING_GO=FALSE -DWITH_DAEMON=FALSE -DCMAKE_INSTALL_PREFIX:PATH=/usr ..
@@ -140,7 +140,7 @@ If you want use a video stream. You need setup the
- region (Required): Country or region. List of Supported value.
- confidence (Optional): Default 80. The minimum of confidence in percent to process with Home-Assistant.
- entities (Required): A list of device to add in Home-Assistant.
- - name (Optional): This parameter allows you to override the name of your openalpr entitie.
+ - name (Optional): This parameter allows you to override the name of your openalpr entity.
- interval (Optional): Default 2. Time in seconds to poll a picture. If the interval is 0 It don’t poll and it only process data with
openalpr.scan service.
- render (Optional): default is with ffmpeg. How is Home-Assistant to get a picture from. It support
ffmpeg for video streams and image for a still image.
- input (Required): The source from getting pictures. With ffmpeg it could by all supported input. Image only support a url.
diff --git a/components/pilight/index.html b/components/pilight/index.html
index 90bd1d914a..d1435a88e9 100644
--- a/components/pilight/index.html
+++ b/components/pilight/index.html
@@ -135,8 +135,8 @@
Troubleshooting
- - A list of tested RF transceiver hardware is available here. This might be usefull before buying.
- - Sending commands is simple when the protocol is known by pilight, but receiving commands can be rather difficult. It can happend that the code is not correctly recognized due to different timings in the sending hardware or the RF receiver. If this happens follow these steps:
+ - A list of tested RF transceiver hardware is available here. This might be useful before buying.
+ - Sending commands is simple when the protocol is known by pilight, but receiving commands can be rather difficult. It can happen that the code is not correctly recognized due to different timings in the sending hardware or the RF receiver. If this happens follow these steps:
diff --git a/components/recorder/index.html b/components/recorder/index.html
index 0ee79000e2..62228447c7 100644
--- a/components/recorder/index.html
+++ b/components/recorder/index.html
@@ -150,7 +150,7 @@
Installation notes
-Not all Python bindings for the choosen database engine can be installed directly. This section contains additional details which should help you to get it working.
+Not all Python bindings for the chosen database engine can be installed directly. This section contains additional details which should help you to get it working.
MYSQL
diff --git a/components/rfxtrx/index.html b/components/rfxtrx/index.html
index a4e2bb44f5..e132b7a9e9 100644
--- a/components/rfxtrx/index.html
+++ b/components/rfxtrx/index.html
@@ -105,12 +105,12 @@
- device (Required): The path to your device, e.g.
/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0
- debug (Optional): If you want to receive debug output.
- - dummy (Optional): Then you have need a connected drive to test your settings. Can be usefull for debugging and testing.
+ - dummy (Optional): Then you have need a connected drive to test your settings. Can be useful for debugging and testing.
Supported protocols
-Not all protocols as advertised are enabled on inital setup of your transceiver. Enabling all protocols is not recommmended either. Your 433.92 product not showing in the logs? Visit the RFXtrx website to download RFXmgmr and enable the required protocol.
+Not all protocols as advertised are enabled on initial setup of your transceiver. Enabling all protocols is not recommended either. Your 433.92 product not showing in the logs? Visit the RFXtrx website to download RFXmgmr and enable the required protocol.
diff --git a/components/sensor.arwn/index.html b/components/sensor.arwn/index.html
index b77b86019e..2b1cfd7320 100644
--- a/components/sensor.arwn/index.html
+++ b/components/sensor.arwn/index.html
@@ -100,7 +100,7 @@
-Currently all temperature, barometer, and wind sensors will be displayed. Support for rain guage sensors will happen in the future.
+Currently all temperature, barometer, and wind sensors will be displayed. Support for rain gauge sensors will happen in the future.
diff --git a/components/sensor.bbox/index.html b/components/sensor.bbox/index.html
index f907371b2c..562fa64ce4 100644
--- a/components/sensor.bbox/index.html
+++ b/components/sensor.bbox/index.html
@@ -117,7 +117,7 @@ Due to third party limitation, the sensors will only be available if Home Assist
- down_max_bandwidth: Maximum bandwidth available for download.
- up_max_bandwidth: Maximum bandwidth available for upload.
- current_down_bandwidth: Instant measure of the current used bandwidth for download.
- - current_up_bandwidth: Instant measure of the current used bandwidthfor upload.
+ - current_up_bandwidth: Instant measure of the current used bandwidth for upload.
diff --git a/components/sensor.deutsche_bahn/index.html b/components/sensor.deutsche_bahn/index.html
index abbac2c11f..501b426956 100644
--- a/components/sensor.deutsche_bahn/index.html
+++ b/components/sensor.deutsche_bahn/index.html
@@ -90,7 +90,7 @@
- The deutsche_bahn sensor will give you the departure time of the next train for the given connection. In case of a delay, the delay is also shown. Additional details are used to inform about eg. the type of the train, price, and if it is ontime.
+ The deutsche_bahn sensor will give you the departure time of the next train for the given connection. In case of a delay, the delay is also shown. Additional details are used to inform about eg. the type of the train, price, and if it is on time.
To enable this sensor, add the following lines to your configuration.yaml file:
@@ -109,7 +109,7 @@
to (Required): The name of the end/destination station.
-As already mentioned this sensor contains a lot of information to access those a template senosr can come handy.
+This sensor stores a lot of attributes which can be accessed by other sensors eg. a template sensor.
# Example configuration.yaml entry
sensor:
diff --git a/components/sensor.emoncms/index.html b/components/sensor.emoncms/index.html
index e4f9e0b787..c269719543 100644
--- a/components/sensor.emoncms/index.html
+++ b/components/sensor.emoncms/index.html
@@ -191,7 +191,7 @@
-Display feeds from the same Emoncms instance with 2 groups of feeds, diffrent scan_interval and a diffrent unit_of_measurement.
+Display feeds from the same Emoncms instance with 2 groups of feeds, different scan_interval and a different unit_of_measurement.
# Example configuration.yaml entry
sensor:
diff --git a/components/sensor.gpsd/index.html b/components/sensor.gpsd/index.html
index 2e9faf039c..2d94d389d5 100644
--- a/components/sensor.gpsd/index.html
+++ b/components/sensor.gpsd/index.html
@@ -121,7 +121,7 @@ Escape character is '^]'.
To setup a GPSD sensor in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
-senosr:
+sensor:
- platform: gpsd
diff --git a/components/sensor.imap_email_content/index.html b/components/sensor.imap_email_content/index.html
index 3ab7844d63..00c2d21212 100644
--- a/components/sensor.imap_email_content/index.html
+++ b/components/sensor.imap_email_content/index.html
@@ -114,7 +114,7 @@
name (Optional): Name of the IMAP sensor to use in the frontend.
username (Required): Username for the IMAP server.
password (Required): Password for the IMAP server.
- senders (Required): A list of sender email addresses that are allowed to report state via email. Only emails recieved from these addresses will be processed.
+ senders (Required): A list of sender email addresses that are allowed to report state via email. Only emails received from these addresses will be processed.
value_template (Optional): If specified this template will be used to render the state of sensor. If a template is not supplied the raw message body will be used for the sensor value. The following attributes will be supplied to the template:
diff --git a/components/sensor.knx/index.html b/components/sensor.knx/index.html
index c75c7d1c6f..5722a76b24 100644
--- a/components/sensor.knx/index.html
+++ b/components/sensor.knx/index.html
@@ -154,7 +154,7 @@
address (Required): The address of the sensor on the bus.
name (Optional): The name to use in the frontend.
minimum (Optional): Minimum sensor value who gets processed. Defaults to a hardcoded default values.
- maxmimum (Optional): Maxmimum sensor value who gets processed. Defaults to a hardcoded default.
+ maximum (Optional): Maximum sensor value who gets processed. Defaults to a hardcoded default.
diff --git a/components/sensor.min_max/index.html b/components/sensor.min_max/index.html
index fd376b04a3..aabc3989d8 100644
--- a/components/sensor.min_max/index.html
+++ b/components/sensor.min_max/index.html
@@ -90,7 +90,7 @@
- The min_max sensor platform is consuming the state from other sensors and determine the minimum, maximum, and the mean of the collected states. The sensor will always show you the highest/lowest value which was received from your all monitored sensors. If you have spikes in your values, it’s recommanded filter/equalize your values with a statistics sensor first.
+ The min_max sensor platform is consuming the state from other sensors and determine the minimum, maximum, and the mean of the collected states. The sensor will always show you the highest/lowest value which was received from your all monitored sensors. If you have spikes in your values, it’s recommended filter/equalize your values with a statistics sensor first.
It’s an alternative to the template sensor’s value_template: to get the average of multiple sensors.
diff --git a/components/sensor.mqtt_room/index.html b/components/sensor.mqtt_room/index.html
index 64b9bbefa4..b5788e6848 100644
--- a/components/sensor.mqtt_room/index.html
+++ b/components/sensor.mqtt_room/index.html
@@ -111,7 +111,7 @@
device_id (Required): The device id to track for this sensor.
name (Optional): The name of the sensor.
state_topic (Optional): The topic that contains all subtopics for the rooms.
- timeout (Optional): The time in seconds after which a room presence state is considered old. An example: device1 is reported at scanner1 with a distance of 1. No further updates are sent from scanner1. After 5 secoonds scanner2 reports device with a distance of 2. The old location info is discarded in favor of the new scanner2 information as the timeout has passed.
+ timeout (Optional): The time in seconds after which a room presence state is considered old. An example: device1 is reported at scanner1 with a distance of 1. No further updates are sent from scanner1. After 5 seconds scanner2 reports device with a distance of 2. The old location info is discarded in favor of the new scanner2 information as the timeout has passed.
away_timeout (Optional): The time in seconds after which the state should be set to away if there were no updates. 0 disables the check and is the default.
diff --git a/components/sensor.pilight/index.html b/components/sensor.pilight/index.html
index c8e0b7f190..ab9c4d7d74 100644
--- a/components/sensor.pilight/index.html
+++ b/components/sensor.pilight/index.html
@@ -90,7 +90,7 @@
- This pilight sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g. uuid) can be set to distinguish between multile pilight devices. To use a pilight sensor the pilight home assistant hub has to be set up.
+ This pilight sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g. uuid) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight home assistant hub has to be set up.
To use your sensor via pilight, make sure it is supported and add the following to your configuration.yaml file:
diff --git a/components/sensor.rest/index.html b/components/sensor.rest/index.html
index ab1636c252..6cf09de34b 100644
--- a/components/sensor.rest/index.html
+++ b/components/sensor.rest/index.html
@@ -216,7 +216,7 @@ User-Agent: Home Assistant
Use GitHub to get the latest release of Home Assistant
-This sample is very similar to the updater component but the information is recieved from GitHub.
+This sample is very similar to the updater component but the information is received from GitHub.
sensor:
- platform: rest
diff --git a/components/sensor.sabnzbd/index.html b/components/sensor.sabnzbd/index.html
index 6a548ca549..5adc768f2f 100644
--- a/components/sensor.sabnzbd/index.html
+++ b/components/sensor.sabnzbd/index.html
@@ -113,7 +113,7 @@
- host (Required): The host where your SABnzbd instance is running, eg. 192.168.1.32
- - port (Optional): The port to use whith SABnzbd instance. Defaults to
8080.
+ - port (Optional): The port to use with SABnzbd instance. Defaults to
8080.
- api_key (Required): Name that will be used in the frontend for the pin.
- name (Optional): The name to use when displaying this SABnzbd instance.
- ssl (Optional): Use
https instead of http to connect. Defaults to False.
@@ -124,7 +124,7 @@
- queue_size: Size of the queue
- queue_remaining: Remaining elements in the queue
- disk_size: Disk size of the storage location
- - disk_free: Free disk space at the sotrage location
+ - disk_free: Free disk space at the storage location
diff --git a/components/sensor.statistics/index.html b/components/sensor.statistics/index.html
index e080c64d85..0d4ee1c8f0 100644
--- a/components/sensor.statistics/index.html
+++ b/components/sensor.statistics/index.html
@@ -92,7 +92,7 @@
The statistics sensor platform is consuming the state from other sensors. Beside the maximal and the minimal value also the total, the mean, the median, the variance, and the standard deviation are as attributes available. If it’s a binary sensor then only the state changes are counted.
-It can take time till the sensor starts to work because a couple of atrributes need more than one value to do the calculation.
+It can take time till the sensor starts to work because a couple of attributes need more than one value to do the calculation.
To enable the statistics sensor, add the following lines to your configuration.yaml:
diff --git a/components/sensor.ted5000/index.html b/components/sensor.ted5000/index.html
index f91f91cb40..8ca6d667bd 100644
--- a/components/sensor.ted5000/index.html
+++ b/components/sensor.ted5000/index.html
@@ -35,7 +35,7 @@ your configuration.yaml:
name (Optional): Name of the ted gateway. Defaults to ted.
-For each plugged MTU, using an index starting at 1, the platorm creates 2 sensors:
+For each plugged MTU, using an index starting at 1, the platform creates 2 sensors:
sensor.<name>_mtu<MTU id>_power
sensor.<name>_mtu<MTU id>_voltage
diff --git a/components/sensor.template/index.html b/components/sensor.template/index.html
index 1477f34cdb..0ccc3b2651 100644
--- a/components/sensor.template/index.html
+++ b/components/sensor.template/index.html
@@ -199,7 +199,7 @@
Please note the blank line to close the multi-line template.
- Change the unit of measurment
+ Change the unit of measurement
With a template sensor it’s easy to convert given values into others if the unit of measurement don’t fit your needs.
diff --git a/components/sensor.thinkingcleaner/index.html b/components/sensor.thinkingcleaner/index.html
index a54587c8f7..5dce51232c 100644
--- a/components/sensor.thinkingcleaner/index.html
+++ b/components/sensor.thinkingcleaner/index.html
@@ -9,7 +9,7 @@
Thinking Cleaner sensor - Home Assistant
-
+
@@ -19,14 +19,14 @@
-
+
-
+
diff --git a/components/sensor.yweather/index.html b/components/sensor.yweather/index.html
index 37aec94799..c8af759f4d 100644
--- a/components/sensor.yweather/index.html
+++ b/components/sensor.yweather/index.html
@@ -125,7 +125,7 @@ Use of the Yahoo Weather API should not exceed reasonable request volume. Access
monitored_conditions array (Required): Conditions to display in the frontend.
- weather: A human-readable text summary with picture from yahoo.
- - weather_current: A human-readable text summary with picture from yahoo from current conditon.
+ - weather_current: A human-readable text summary with picture from yahoo from current condition.
- temperature: The current temperature.
- temp_min: The minimal temperature of this day.
- temp_max: The maximum temperature of this day.
diff --git a/components/simple_alarm/index.html b/components/simple_alarm/index.html
index 629683bc76..506c9ede95 100644
--- a/components/simple_alarm/index.html
+++ b/components/simple_alarm/index.html
@@ -90,7 +90,7 @@
- The component simple_alarm is capable of detecting intruders. It does so by checking if lights are being turned on while there is no one at home. When this happens it will turn the lights red, flash them for 30 seconds and send a message via the notifiy component. It will also flash a specific light when a known person comes home.
+ The component simple_alarm is capable of detecting intruders. It does so by checking if lights are being turned on while there is no one at home. When this happens it will turn the lights red, flash them for 30 seconds and send a message via the notify component. It will also flash a specific light when a known person comes home.
This component depends on the components device_tracker and light being setup.
diff --git a/components/splunk/index.html b/components/splunk/index.html
index 38d16c7f1f..2f929231ef 100644
--- a/components/splunk/index.html
+++ b/components/splunk/index.html
@@ -90,7 +90,7 @@
- The splunk component makes it possible to log all state changes to an external Splunk database using Splunk’s HTTP Event Collector feature. You can either use this alone, or with the HomeAssistant for Splunk app. Since the HEC feature is new to Splunk, you will need to use at least version 6.3.
+ The splunk component makes it possible to log all state changes to an external Splunk database using Splunk’s HTTP Event Collector feature. You can either use this alone, or with the Home Assistant for Splunk app. Since the HEC feature is new to Splunk, you will need to use at least version 6.3.
To use the splunk component in your installation, add the following to your configuration.yaml file:
diff --git a/components/sun/index.html b/components/sun/index.html
index 26b82e3329..56bb4813e6 100644
--- a/components/sun/index.html
+++ b/components/sun/index.html
@@ -100,7 +100,7 @@
Configuration variables:
- - elevation (Optional): The (physical) elevation of your location, in metres above sea level. If ommitted will be retrieved from Google Maps.
+ - elevation (Optional): The (physical) elevation of your location, in metres above sea level. If omitted will be retrieved from Google Maps.
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index a207895258..b44e46aa69 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -132,7 +132,7 @@
aREST device
-The example below is doing the same as the aREST switch. The commandline tool curl is used to toogle a pin which is controllable through REST.
+The example below is doing the same as the aREST switch. The commandline tool curl is used to toggle a pin which is controllable through REST.
# Example configuration.yaml entry
switch:
diff --git a/components/switch.dlink/index.html b/components/switch.dlink/index.html
index f5f73db871..a1e3971032 100644
--- a/components/switch.dlink/index.html
+++ b/components/switch.dlink/index.html
@@ -116,7 +116,7 @@
- host (Required): The IP address of your D-Link plug, eg. http://192.168.1.32
- name (Optional): The name to use when displaying this switch.
- username (Required): The username for your plug. Defaults to
admin.
- - password (Required): The password for your plug. Default password is the
PIN inlcuded on the configuration card.
+ - password (Required): The password for your plug. Default password is the
PIN included on the configuration card.
- use_legacy_protocol (Optional): Enable limited support for legacy firmware protocols (Tested with v1.24).
diff --git a/components/switch.hikvision/index.html b/components/switch.hikvision/index.html
index 2a67e9c608..7bd0456c89 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -109,7 +109,7 @@ Currently works using default https port only.
- host (Required): The IP address of your Hikvision camera, eg.
192.168.1.32.
- - port (Optional): The port to connec to your Hikvision camera. Defaults to
80.
+ - port (Optional): The port to connect to your Hikvision camera. Defaults to
80.
- name (Optional): This parameter allows you to override the name of your camera.
- username (Optional): The username for accessing your Hikvision camera. Defaults to
admin.
- password (Optional): The password to access your Hikvision camera. Defaults to
12345.
diff --git a/components/switch.knx/index.html b/components/switch.knx/index.html
index 19f5d44823..c8099e12b5 100644
--- a/components/switch.knx/index.html
+++ b/components/switch.knx/index.html
@@ -105,8 +105,8 @@
- name (Optional): A name for this devices used within Home assistant
- address (Required): The KNX group address that is used to turn on/off this actuator channel
- - state_address (Optional): Some KNX devices can change their state internally without any messages on the KXN bus, e.g. if you configure a timer on a channel. The optional
state_address can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this wil overwrite the state of the switch object.
-For switching actuators that are only controlled by a single group address and can’t change their state internally, you don’t have to configrue the state address.
+ - state_address (Optional): Some KNX devices can change their state internally without any messages on the KXN bus, e.g. if you configure a timer on a channel. The optional
state_address can be used to inform Home Assistant about these state changes. If a KNX message is seen on the bus addressed to the given state address, this will overwrite the state of the switch object.
+For switching actuators that are only controlled by a single group address and can’t change their state internally, you don’t have to configure the state address.
diff --git a/components/switch.pilight/index.html b/components/switch.pilight/index.html
index 4e9ea2b196..f5d11fac3c 100644
--- a/components/switch.pilight/index.html
+++ b/components/switch.pilight/index.html
@@ -141,7 +141,7 @@
- ‘on’ (Optional):
1 or 0
-For possible code entries look at the pilight API. All commands allowed by pilight-send can be used. Which means that if for a certain protocol there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the elro_800_switch or mumbi protocol for example, you will have to replace the variable unit with unitcode or there will be errors occuring.
+For possible code entries look at the pilight API. All commands allowed by pilight-send can be used. Which means that if for a certain protocol there are different parameters used, you should be able to replace the variables above by the proper ones required by the specific protocol. When using the elro_800_switch or mumbi protocol for example, you will have to replace the variable unit with unitcode or there will be errors occurring.
Examples
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index 24fc221e66..7a3a8f0fad 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -109,7 +109,7 @@
Configuration variables:
- - sink_name (Required): The name of the Pulseaudio sink that will recieve the audio.
+ - sink_name (Required): The name of the Pulseaudio sink that will receive the audio.
- source_name (Required): The name of the Pulseaudio source that will supply the audio.
- name (Optional): Name of the switch.
- host (Optional): The IP address or host name of the PulseAudio server. If not specified, 127.0.0.1 is used.
diff --git a/components/switch.rfxtrx/index.html b/components/switch.rfxtrx/index.html
index c963ade91a..10f347fb57 100644
--- a/components/switch.rfxtrx/index.html
+++ b/components/switch.rfxtrx/index.html
@@ -132,7 +132,7 @@ Then you should update your configuration to:
Generate codes:
-If you need to generate codes for switches you can use a template (usefull for example COCO switches).
+If you need to generate codes for switches you can use a template (useful for example COCO switches).
- Go to home-assistant-IP:8123/dev-template
@@ -147,7 +147,7 @@ Then you should update your configuration to:
- Use this code to add a new switch in your configuration.yaml
- Launch your homeassistant and go the website.
- Enable learning mode on your switch (i.e. push learn button or plug it in a wall socket)
- - Toggle your new switch in the homeassisant interface
+ - Toggle your new switch in the Home Assistant interface
Examples
diff --git a/components/updater/index.html b/components/updater/index.html
index 0b1f8eabb2..dd98a82dca 100644
--- a/components/updater/index.html
+++ b/components/updater/index.html
@@ -92,7 +92,7 @@
The updater component will check daily for new releases. It will show a badge in the frontend if a new version was found.
-The updater component will also collect basic information about Home Assistant and its environment. The information includes the current Home Assistant version, the timezone, Python version and operating system infomation. No identifiable information (i.e. IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python source code.
+The updater component will also collect basic information about Home Assistant and its environment. The information includes the current Home Assistant version, the timezone, Python version and operating system information. No identifiable information (i.e. IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python source code.
To integrate this into Home Assistant, add the following section to your configuration.yaml file:
diff --git a/components/wink/index.html b/components/wink/index.html
index d8f460dc1a..7fbabe95ed 100644
--- a/components/wink/index.html
+++ b/components/wink/index.html
@@ -121,7 +121,7 @@
-The following can also be provied to allow access to the Wink Relay sensors. This value could change at any time.
+The following can also be provided to allow access to the Wink Relay sensors. This value could change at any time.
wink:
user_agent: Manufacturer/Home-Assistant WinkAndroid/4
@@ -132,10 +132,10 @@
- access_token (Required if the below aren’t present.): The retrieved access token.
- - email (Required if access token isn’t provied): Your Wink login email.
- - password (Required if access token isn’t provied): Your Wink loging password.
- - client_id (Required if access token isn’t provied): Your provided Wink client_id.
- - client_secret (Required if access token isn’t provied): Your provided Wink client_secret.
+ - email (Required if access token isn’t provided): Your Wink login email.
+ - password (Required if access token isn’t provided): Your Wink login password.
+ - client_id (Required if access token isn’t provided): Your provided Wink client_id.
+ - client_secret (Required if access token isn’t provided): Your provided Wink client_secret.
- user_agent (Optional): The user-agent passed in the API calls to Wink.
diff --git a/getting-started/z-wave/index.html b/getting-started/z-wave/index.html
index f51484914a..72f71692b3 100644
--- a/getting-started/z-wave/index.html
+++ b/getting-started/z-wave/index.html
@@ -321,7 +321,7 @@ You can use this for automations.
change_association
- Add or remove an association in th Z-Wave network
+ Add or remove an association in the Z-Wave network
cancel_command
diff --git a/sitemap.xml b/sitemap.xml
index 12a627a98f..f6237c5d5c 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2349,62 +2349,62 @@
https://home-assistant.io/demo/frontend.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/index.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:35+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:36+00:00
https://home-assistant.io/static/mdi-demo.html
-2016-11-23T07:57:22+00:00
+2016-11-23T09:24:36+00:00