diff --git a/source/_docs/configuration/events.markdown b/source/_docs/configuration/events.markdown
index 14ce423dab9..5c8e641808a 100644
--- a/source/_docs/configuration/events.markdown
+++ b/source/_docs/configuration/events.markdown
@@ -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`. |
-
-
- Starting with 0.84, it is no longer possible to listen for event `service_executed`.
-
-
-
### Event `platform_discovered`
Event `platform_discovered` is fired when a new platform has been discovered by the [`discovery`](/integrations/discovery/) component.
diff --git a/source/_integrations/binary_sensor.rest.markdown b/source/_integrations/binary_sensor.rest.markdown
index eaa3d8f2e5c..f3a433442b4 100644
--- a/source/_integrations/binary_sensor.rest.markdown
+++ b/source/_integrations/binary_sensor.rest.markdown
@@ -108,10 +108,6 @@ headers:
type: [list, string]
{% endconfiguration %}
-
-Make sure that the URL exactly matches your endpoint or resource.
-
-
## Examples
In this section you find some real-life examples of how to use this sensor.
diff --git a/source/_integrations/cert_expiry.markdown b/source/_integrations/cert_expiry.markdown
index 92141d2ff65..3f378dcf03d 100644
--- a/source/_integrations/cert_expiry.markdown
+++ b/source/_integrations/cert_expiry.markdown
@@ -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.
-
-
-Make sure that the URL exactly matches your endpoint or resource.
-
diff --git a/source/_integrations/haveibeenpwned.markdown b/source/_integrations/haveibeenpwned.markdown
index 2acd832aa6f..f931c6c3365 100644
--- a/source/_integrations/haveibeenpwned.markdown
+++ b/source/_integrations/haveibeenpwned.markdown
@@ -13,12 +13,6 @@ The `haveibeenpwned` sensor platform creates sensors that check for breached ema
## Configuration
-
-
- 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/).
-
-
-
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
diff --git a/source/_integrations/met.markdown b/source/_integrations/met.markdown
index 433bd0450bb..6a1340ccc3d 100644
--- a/source/_integrations/met.markdown
+++ b/source/_integrations/met.markdown
@@ -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.
-
- Configuration of the Met.no platform via configuration.yaml is deprecated from version 0.95
-
-
-## 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.
diff --git a/source/_integrations/pocketcasts.markdown b/source/_integrations/pocketcasts.markdown
index 6b19fa321da..97d4690314e 100644
--- a/source/_integrations/pocketcasts.markdown
+++ b/source/_integrations/pocketcasts.markdown
@@ -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
-
-
- This integration requires a [Pocket Casts + Plus](https://www.pocketcasts.com/plus/) subscription to work!
-
-
-
To enable this sensor, add the following lines to your `configuration.yaml`:
```yaml
diff --git a/source/_integrations/rest.markdown b/source/_integrations/rest.markdown
index 7aa7b332deb..c5e130b79a8 100644
--- a/source/_integrations/rest.markdown
+++ b/source/_integrations/rest.markdown
@@ -119,10 +119,6 @@ force_update:
default: false
{% endconfiguration %}
-
-Make sure that the URL exactly matches your endpoint or resource.
-
-
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
-
+
0
12556
diff --git a/source/_integrations/tellduslive.markdown b/source/_integrations/tellduslive.markdown
index cbb188f5469..fc99d063d2a 100644
--- a/source/_integrations/tellduslive.markdown
+++ b/source/_integrations/tellduslive.markdown
@@ -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.
-
-
-If you are upgrading from 0.58 or older, you need to remove all Telldus configuration from your `configuration.yaml` file before continuing.
-
-
-
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