Added known issue to MJPEG cameras, moved customize polling interval to its own category, minor fixes

This commit is contained in:
Lindsay Ward 2016-03-28 16:28:23 +10:00
parent 6138fff8ea
commit 2d085f9518
4 changed files with 10 additions and 6 deletions

View File

@ -31,3 +31,7 @@ Configuration variables:
- **name** *Optional*: This parameter allows you to override the name of your camera. - **name** *Optional*: This parameter allows you to override the name of your camera.
- **username** *Optional*: The username for accessing your camera. - **username** *Optional*: The username for accessing your camera.
- **password** *Optional*: The password for accessing your camera. - **password** *Optional*: The password for accessing your camera.
<p class='note'>
There is a <a href="https://github.com/shazow/urllib3/issues/800" target="_blank">known issue in urllib3</a> that you will get error messages in your logs like <code>[StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ''</code> but the component still works fine. You can ignore the messages.
</p>

View File

@ -28,6 +28,6 @@ When this component is active and you are using a supported browser voice comman
<img src="/images/screenshots/voice-commands.png" /> <img src="/images/screenshots/voice-commands.png" />
</p> </p>
<p class='note note'> <p class='note'>
Apple iPhones do not support this feature in any browser. Apple iPhones do not support this feature in any browser.
</p> </p>

View File

@ -45,7 +45,7 @@ Configuration variables:
- **resource** (*Required*): The resource or endpoint that contains the value. - **resource** (*Required*): The resource or endpoint that contains the value.
- **method** (*Optional*): The method of the request. Default is GET. - **method** (*Optional*): The method of the request. Default is GET.
- **value_template** (*Optional*): Defines a [template](/topics/templating/) to extract the value. - **value_template** (*Optional*): Defines a [template](/topics/templating/) to extract the value.
- **payload** (*Optional*): The payload to send with a POST request. Usualy formed as a dictionary. - **payload** (*Optional*): The payload to send with a POST request. Depends on the service, but usually formed as JSON.
- **name** (*Optional*): Name of the REST sensor. - **name** (*Optional*): Name of the REST sensor.
- **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any. - **unit_of_measurement** (*Optional*): Defines the unit of measurement of the sensor, if any.
@ -66,7 +66,7 @@ In this section you find some real life examples of how to use this sensor.
### {% linkable_title External IP address %} ### {% linkable_title External IP address %}
Always want to know your external IP address. [JSON Test](http://www.jsontest.com) will provide you this information at their http://ip.jsontest.com/ endpoint. You can find your external IP address using the service [JSON Test](http://www.jsontest.com) at their http://ip.jsontest.com/ endpoint.
To display the IP address, the entry for a sensor in the `configuration.yaml` file will look like this. To display the IP address, the entry for a sensor in the `configuration.yaml` file will look like this.
@ -93,7 +93,7 @@ Add something similar to the entry below to your `configuration.yaml` file:
### {% linkable_title Value for other Home Assistant instance %} ### {% linkable_title Value for other Home Assistant instance %}
The Home Assistant [API](/developers/rest_api/) is exposing the data from your attached sensors. If you are running multiple Home Assistant instances which are not [connected](/developers/architecture/#multiple-connected-instances) you can still get information from them. The Home Assistant [API](/developers/rest_api/) exposes the data from your attached sensors. If you are running multiple Home Assistant instances which are not [connected](/developers/architecture/#multiple-connected-instances) you can still get information from them.
```yaml ```yaml

View File

@ -7,8 +7,8 @@ sidebar: true
comments: false comments: false
sharing: true sharing: true
footer: true footer: true
ha_category: Example configuration.yaml ha_category: Customize Defaults
--- -------------------------------
Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` config key. In the example below we setup the Philips Hue lights but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds. Platforms that require polling will be polled in an interval specified by the main component. For example a light will check every 30 seconds for a changed state. It is possible to overwrite this scan interval for any platform that is being polled by specifying a `scan_interval` config key. In the example below we setup the Philips Hue lights but tell Home Assistant to poll the devices every 10 seconds instead of the default 30 seconds.