Remove excessive warnings (#12444)

* Remove excessive warnings

* Address comments
This commit is contained in:
Alok Saboo 2020-03-19 14:10:55 -04:00 committed by GitHub
parent 67cc19694d
commit 7568a7ea95
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 5 additions and 70 deletions

View File

@ -52,12 +52,6 @@ Event `service_executed` is fired by the service handler to indicate the service
| ----------------- | ----------------------------------------------------------------------------------------- |
| `service_call_id` | String with the unique call id of the service call that was executed. Example: `23123-4`. |
<div class='note warning'>
Starting with 0.84, it is no longer possible to listen for event `service_executed`.
</div>
### Event `platform_discovered`
Event `platform_discovered` is fired when a new platform has been discovered by the [`discovery`](/integrations/discovery/) component.

View File

@ -108,10 +108,6 @@ headers:
type: [list, string]
{% endconfiguration %}
<div class='note warning'>
Make sure that the URL exactly matches your endpoint or resource.
</div>
## Examples
In this section you find some real-life examples of how to use this sensor.

View File

@ -49,7 +49,3 @@ The Certificate Expiry entities provide extra attributes to represent the state
| ---- | ----------- |
| `is_valid` | If the certificate is able to be validated: `True` / `False`.
| `error` | A human-readable error description if the certificate is considered invalid, "None" otherwise.
<div class='note warning'>
Make sure that the URL exactly matches your endpoint or resource.
</div>

View File

@ -13,12 +13,6 @@ The `haveibeenpwned` sensor platform creates sensors that check for breached ema
## Configuration
<div class='note warning'>
The HaveIBeenPwned API is no longer a free API. For more information about this change read the HIBP creator's [blogpost regarding the change](https://www.troyhunt.com/authentication-and-the-have-i-been-pwned-api/).
</div>
In order to use this integration you need to purchase an API key. Visit the [API key page](https://haveibeenpwned.com/API/Key) on the HIBP website to purchase one.
## Configuration

View File

@ -13,33 +13,4 @@ ha_domain: met
The `met` platform uses the [Met.no](https://met.no/) web service as a source for meteorological data for your location. The weather forecast is delivered by the Norwegian Meteorological Institute and the NRK.
<div class='note warning'>
Configuration of the Met.no platform via configuration.yaml is deprecated from version 0.95
</div>
## Configuration
To add Met.no to your installation, go to Configuration >> Integrations in the UI and enable the Met.no integration. By default the values will be taken from the Home Assistant configuration.
{% configuration %}
name:
description: Manually specify Name.
required: true
type: string
default: Provided by Home Assistant configuration
latitude:
description: Manually specify latitude.
required: true
type: float
default: Provided by Home Assistant configuration
longitude:
description: Manually specify longitude.
required: true
type: float
default: Provided by Home Assistant configuration
altitude:
description: Manually specify altitude.
required: false
type: integer
default: Provided by Home Assistant configuration
{% endconfiguration %}
To add Met.no to your installation, go to Configuration >> Integrations in the UI and enable the Met.no integration.

View File

@ -8,16 +8,10 @@ ha_iot_class: Cloud Polling
ha_domain: pocketcasts
---
The `pocketcasts` sensor platform lets you monitor how many unplayed episodes you have of your favorite podcasts at [Pocket Casts](https://play.pocketcasts.com/).
The `pocketcasts` sensor platform lets you monitor how many unplayed episodes you have of your favorite podcasts at [Pocket Casts](https://play.pocketcasts.com/). This integration requires a [Pocket Casts + Plus](https://www.pocketcasts.com/plus/) subscription to work!
## Configuration
<div class='note warning'>
This integration requires a [Pocket Casts + Plus](https://www.pocketcasts.com/plus/) subscription to work!
</div>
To enable this sensor, add the following lines to your `configuration.yaml`:
```yaml

View File

@ -119,10 +119,6 @@ force_update:
default: false
{% endconfiguration %}
<div class='note warning'>
Make sure that the URL exactly matches your endpoint or resource.
</div>
<div class='note'>
Use either `resource` or `resource_template`.
@ -414,7 +410,7 @@ sensor:
value_template: '{{ states.sensor.steam_system_data.attributes["time0"] }}'
unit_of_measurement: "minutes"
switch:
switch:
- platform: template
switches:
steam:
@ -441,7 +437,7 @@ switch:
- service: homeassistant.update_entity
data:
entity_id: sensor.steam_system_data
friendly_name: Steam
friendly_name: Steam
rest_command:
set_steam_led:
@ -454,7 +450,7 @@ For reference, the XML content of endpoint shown above example is below:
```xml
<?xml version="1.0" encoding="utf-8"?>
<response>
<scan>0</scan>
<ver>12556</ver>

View File

@ -19,12 +19,6 @@ ha_domain: tellduslive
The `tellduslive` integration let you connect to [Telldus Live](https://live.telldus.com). It's cloud platform that connects to your Tellstick Net or Tellstick ZNet connected gear at home.
<div class='note warning'>
If you are upgrading from 0.58 or older, you need to remove all Telldus configuration from your `configuration.yaml` file before continuing.
</div>
Home Assistant will automatically discover the presence of a Tellstick Net or Tellstick ZNet on your local network if the [discovery]({{site_root}}/integrations/discovery/) integration is enabled. When discovery and the key exchange with Telldus Live have been completed, you will be presented with an option to integrate with the cloud or local API for direct communication with your hardware in your LAN. Local API supports only one device at this stage. Local API is only supported with the Znet Lite products, the older hardware (such as Tellstick Net) does not support local API.
## Configuration