-
-Loop Energy has said that on November 13, 2020, they will [switch off the servers which this integration uses](https://email.loop.homes/action-required-how-to-claim-your-free-loop-upgrade-1). This integration will stop working then.
-
-
-
-Integrate your [Loop Energy](https://www.your-loop.com/) meter information into Home Assistant. To use this sensor you need the client serial number and secret keys for your devices.
-
-The library used to get the data isn't officially supported and the only way to get the keys is to log into loop energy's website and type a command into your browser console.
-
-To do this log into [Loop Energy](https://www.your-loop.com/). Once you're logged in you should be able see your live readings on the web page.
-
-You can then open your browser's console window, how you do this varies by browser but in Chrome you click on `More Tools / Developer Tools' and click on the console window. You then type:
-
-`Drupal.settings.navetas_realtime.`
-
-This should show something like
-
-```yaml
-client_ip: "127.0.0.1"
-gas_secret: "GAS_SECRET"
-gas_serial: "GAS_SERIAL"
-host: "www.your-loop.com"
-...
-secret: "ELECTRICAL_SECRET"
-serial: "ELECTRICAL_SERIAL"
-```
-
-The serial and secret tokens are the ones you need. If you just have an electricity monitor then you won't see the gas keys.
-
-Now you have the keys, add the following lines to your `configuration.yaml`, replacing the `*_SERIAL` and `*_SECRET` keys with the ones you found in the console:
-
-```yaml
-# Example configuration.yaml entry
-sensor:
- - platform: loopenergy
- electricity:
- electricity_serial: "ELECTRICAL_SERIAL"
- electricity_secret: "ELECTRICAL_SECRET"
- gas:
- gas_serial: "GAS_SERIAL"
- gas_secret: "GAS_SECRET"
-```
-
-{% configuration %}
-electricity_serial:
- description: Serial number of your electricity sensor.
- required: true
- type: string
-electricity_secret:
- description: Secret key for your electricity sensor.
- required: true
- type: string
-gas_serial:
- description: Serial number for your gas sensor.
- required: true
- type: string
-gas_secret:
- description: Secret key for your gas sensor.
- required: true
- type: string
-gas_type:
- description: Type of meter `imperial` or `metric`.
- required: false
- default: metric
- type: string
-gas_calorific:
- description: Calorific value of your gas supply (usually on your gas bill).
- required: false
- default: 39.11
- type: float
-{% endconfiguration %}
-
-The electricity readings are updated every 10 seconds and the gas readings every 15 minutes.
-
-The gas readings are experimental and not all gas meters are properly supported. So if the data you see doesn't agree with the readings you see via loop energy please report an issue.
diff --git a/source/_redirects b/source/_redirects
index 2ca0cb706f9..9481809266f 100644
--- a/source/_redirects
+++ b/source/_redirects
@@ -755,8 +755,6 @@
/components/sensor.logi_circle /integrations/logi_circle#sensor
/components/sensor.london_air /integrations/london_air
/components/sensor.london_underground /integrations/london_underground
-/components/sensor.loop_energy /integrations/loopenergy
-/components/sensor.loopenergy /integrations/loopenergy
/components/sensor.luftdaten /integrations/luftdaten#sensor
/components/sensor.magicseaweed /integrations/magicseaweed
/components/sensor.meteo_france /integrations/meteo_france
@@ -1505,7 +1503,6 @@
/components/logi_circle /integrations/logi_circle
/components/london_air /integrations/london_air
/components/london_underground /integrations/london_underground
-/components/loopenergy /integrations/loopenergy
/components/luci /integrations/luci
/components/luftdaten /integrations/luftdaten
/components/lupusec /integrations/lupusec
@@ -2352,3 +2349,7 @@
/integrations/mychevy /more-info/removed-integration 301
/components/binary_sensor.mychevy /more-info/removed-integration 301
/components/sensor.mychevy /more-info/removed-integration 301
+/integrations/loopenergy /more-info/removed-integration 301
+/components/loopenergy /more-info/removed-integration 301
+/components/sensor.loop_energy /more-info/removed-integration 301
+/components/sensor.loopenergy /more-info/removed-integration 301
\ No newline at end of file
From 7e95b7945761c844b2cc4a267c2e9475e059814c Mon Sep 17 00:00:00 2001
From: Alberto Geniola
diff --git a/source/_integrations/bmw_connected_drive.markdown b/source/_integrations/bmw_connected_drive.markdown
index 83d7b4ad419..eeab1531106 100644
--- a/source/_integrations/bmw_connected_drive.markdown
+++ b/source/_integrations/bmw_connected_drive.markdown
@@ -44,14 +44,14 @@ This integration provides the following platforms:
## Configuration
-The preferred way to enable the `bmw_connected_drive` integration is via **Configuration** > **Integrations**. After connecting to your account, you can set the following settings in the integration's options:
+The preferred way to enable the `bmw_connected_drive` integration is via **Configuration** > **Devices & Services**. After connecting to your account, you can set the following settings in the integration's options:
| Setting | Description |
|---------|-------------|
| Read-only | No execution of services to the vehicle. Still possible to send messages and POIs via `notify` and to request a status update via `bmw_connected_drive.update_state`.
| Use Home Assistant location for car location polls | Older cars (non i3/i8 build before 7/2014) require the phone to be close to the car to get location updates. Enable this option to use the location of your Home Assistant instance for these queries, so updates are available when your car is in the surrounding of your home. |
-The following settings in your `configuration.yaml` file are considered legacy. They will be imported into **Configuration** > **Integrations** and you can set the options from above. Changes to `configuration.yaml` after the first import will be ignored.
+The following settings in your `configuration.yaml` file are considered legacy. They will be imported into **Configuration** > **Devices & Services** and you can set the options from above. Changes to `configuration.yaml` after the first import will be ignored.
### Legacy configuration
diff --git a/source/_integrations/control4.markdown b/source/_integrations/control4.markdown
index a919eb2ebb4..54d08b7f0d3 100644
--- a/source/_integrations/control4.markdown
+++ b/source/_integrations/control4.markdown
@@ -23,7 +23,7 @@ Before setting up, you should assign a static IP address/DHCP reservation on you
## Options
-The Control4 integration offers additional options in **Configuration** -> **Integrations** -> **Control4** -> **Options**:
+The Control4 integration offers additional options in **Configuration** -> **Devices & Services** -> **Control4** -> **Options**:
{% configuration %}
Seconds between updates:
diff --git a/source/_integrations/dexcom.markdown b/source/_integrations/dexcom.markdown
index f9b52bb8dc8..09f67da9752 100644
--- a/source/_integrations/dexcom.markdown
+++ b/source/_integrations/dexcom.markdown
@@ -31,7 +31,7 @@ There are two Dexcom Share servers, `US` for United States customers, and `OUS`
### Unit of measurement
-The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, got to **Configuration** >> **Integrations** in the UI, and click `OPTIONS`.
+The integrations allows both `mg/dL` and `mmol/l` units of measurement for blood glucose values. To change your preferred unit of measurement, got to **Configuration** >> **Devices & Services** in the UI, and click `OPTIONS`.
## Sensor
diff --git a/source/_integrations/dlna_dmr.markdown b/source/_integrations/dlna_dmr.markdown
index 2a3fc1721e8..ab6db01576d 100644
--- a/source/_integrations/dlna_dmr.markdown
+++ b/source/_integrations/dlna_dmr.markdown
@@ -23,7 +23,7 @@ Please note that some devices, such as Samsung TVs, are rather picky about the s
## Options
-Options for DLNA DMR devices can be set going to **Configuration** -> **Integrations** -> **DLNA Digital Media Renderer** -> **Configuration**.
+Options for DLNA DMR devices can be set going to **Configuration** -> **Devices & Services** -> **DLNA Digital Media Renderer** -> **Configuration**.
{% configuration_basic %}
Event listener port:
diff --git a/source/_integrations/dsmr.markdown b/source/_integrations/dsmr.markdown
index 0a8d32bd63a..2c306988856 100644
--- a/source/_integrations/dsmr.markdown
+++ b/source/_integrations/dsmr.markdown
@@ -36,7 +36,7 @@ A sensor platform for Belgian, Dutch, Luxembourg and Swedish Smart Meters which
### Options
-To configure options for DSMR integration go to **Configuration** >> **Integrations** and press **Options** on the DSMR card.
+To configure options for DSMR integration go to **Configuration** >> **Devices & Services** and press **Options** on the DSMR card.
#### Time between updates
diff --git a/source/_integrations/eafm.md b/source/_integrations/eafm.md
index 46dedd7499c..552f283f5ef 100644
--- a/source/_integrations/eafm.md
+++ b/source/_integrations/eafm.md
@@ -21,7 +21,7 @@ The UK Environment Agency Flood Monitoring only provides data for England - Nort
## Configuration
-Home Assistant offers the flood monitoring integration through **Configuration** -> **Integrations** -> **Environment Agency Flood Gauges**.
+Home Assistant offers the flood monitoring integration through **Configuration** -> **Devices & Services** -> **Environment Agency Flood Gauges**.
You will be prompted to select a monitoring station. You can find the name of nearby monitoring stations on the Flood information service [website](https://flood-warning-information.service.gov.uk/river-and-sea-levels).
diff --git a/source/_integrations/ecobee.markdown b/source/_integrations/ecobee.markdown
index f65f11165c8..6e8345ab093 100644
--- a/source/_integrations/ecobee.markdown
+++ b/source/_integrations/ecobee.markdown
@@ -50,14 +50,14 @@ Your new application will now appear on the left. Upon clicking on the applicati
## Configuration
-1. In the **Configuration** > **Integrations** menu, click **+** and then select "ecobee" from the pop-up menu.
+1. In the **Configuration** > **Devices & Services** menu, click **+** and then select "ecobee" from the pop-up menu.
2. In the pop-up box, enter the API key you obtained from ecobee's [developer portal](https://ecobee.com/developers).
3. In the next pop-up box, you will be presented with a unique four-character PIN code which you will need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by logging in, selecting **My Apps** from the hamburger menu, clicking **Add Application** on the left, entering the PIN code from Home Assistant, clicking **Validate** and then **Add Application** in the bottom right.
4. After authorizing the app with ecobee, return to Home Assistant and click **Submit**. If the authorization was successful, a configuration entry will be created and your thermostats and sensors will be available in Home Assistant.
## Manual Configuration
-If you prefer to set up the integration in [`configuration.yaml`](/docs/configuration/), add your API key (and optional parameters) as follows (however, you must still complete authorization via the **Integrations** menu):
+If you prefer to set up the integration in [`configuration.yaml`](/docs/configuration/), add your API key (and optional parameters) as follows (however, you must still complete authorization via the **Integrations** panel):
```yaml
# Example configuration.yaml entry
@@ -67,7 +67,7 @@ ecobee:
{% configuration %}
api_key:
- description: Your ecobee API key. This is only needed for the initial setup of the integration. Once registered it can be removed. If you revoke the key in the ecobee portal, you will need to remove the existing `ecobee` configuration in the **Integrations** menu, update this, and then configure the integration again.
+ description: Your ecobee API key. This is only needed for the initial setup of the integration. Once registered it can be removed. If you revoke the key in the ecobee portal, you will need to remove the existing `ecobee` configuration in the **Integrations** panel, update this, and then configure the integration again.
required: false
type: string
{% endconfiguration %}
@@ -77,7 +77,7 @@ api_key:
-You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Configuration** > **Integrations** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
+You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Configuration** > **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
## Notifications
diff --git a/source/_integrations/flume.markdown b/source/_integrations/flume.markdown
index 8c82bd82711..69b39943575 100644
--- a/source/_integrations/flume.markdown
+++ b/source/_integrations/flume.markdown
@@ -25,7 +25,7 @@ You can find your Client ID and Client Secret under "API Access" on the [setting
The Flume API access is available to Flume Insight users only, which may require a paid subscription.
-To add `Flume` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
+To add `Flume` to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
## Configuration for Binary Sensor
diff --git a/source/_integrations/freebox.markdown b/source/_integrations/freebox.markdown
index 7f6c806f84a..2b751485aaa 100644
--- a/source/_integrations/freebox.markdown
+++ b/source/_integrations/freebox.markdown
@@ -36,7 +36,7 @@ Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more
### Via the frontend
-Menu: **Configuration** -> **Integrations**. Search for "Freebox", add your host and port, click submit.
+Menu: **Configuration** -> **Devices & Services**. Search for "Freebox", add your host and port, click submit.
If you add the integration for the first time, follow the instructions in the [Initial setup](#initial-setup) section.
diff --git a/source/_integrations/harmony.markdown b/source/_integrations/harmony.markdown
index 5f403dbc461..c61e59d8c73 100644
--- a/source/_integrations/harmony.markdown
+++ b/source/_integrations/harmony.markdown
@@ -32,7 +32,7 @@ Supported units:
{% include integrations/config_flow.md %}
-Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Integrations** >> **Your Logitech Harmony Hub**
+Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Devices & Services** >> **Your Logitech Harmony Hub**
### Configuration file
diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown
index 94229cdc5f7..c91e197cf18 100644
--- a/source/_integrations/homekit.markdown
+++ b/source/_integrations/homekit.markdown
@@ -306,7 +306,7 @@ The HomeKit Accessory Protocol Specification only allows a maximum of 150 unique
### Multiple HomeKit instances
-If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Integrations**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
+If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
It is recommended to only edit a HomeKit instance in the UI that was created in the UI, and likewise, only edit a HomeKit instance in YAML that was created in YAML.
@@ -479,15 +479,15 @@ The following home hubs have been reported to have trouble with a large number o
### Resetting when created via YAML
- 1. Delete the `HomeKit` integration in the **{% my integrations %}** screen.
+ 1. Delete the `HomeKit` integration in the **{% my integrations %}** panel.
2. **Restart** Home Assistant.
3. The configuration will be automatically reimported from YAML.
4. [Pair the bridge or accessory](#setup).
-### Resetting when created via the **Integrations** screen
+### Resetting when created via the **Integrations** panel
- 1. Delete the `HomeKit` integration in the **Integrations** screen.
- 2. Recreate the `HomeKit` integration in the **Integrations** screen.
+ 1. Delete the `HomeKit` integration in the **Integrations** panel.
+ 2. Recreate the `HomeKit` integration in the **Integrations** panel.
3. [Pair the bridge or accessory](#setup).
### Errors during pairing
@@ -600,7 +600,7 @@ Ensure that the [`ffmpeg`](/integrations/ffmpeg) integration is configured corre
#### Camera streaming is unstable or slow
-If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Configuration** >> **Integrations** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
+If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Configuration** >> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
#### Multiple camera streams
diff --git a/source/_integrations/huawei_lte.markdown b/source/_integrations/huawei_lte.markdown
index eba6ea7c1f7..883cd9f91cc 100644
--- a/source/_integrations/huawei_lte.markdown
+++ b/source/_integrations/huawei_lte.markdown
@@ -68,7 +68,7 @@ entities varies by device model and firmware version.
### Configuration via the frontend
-Menu: **Configuration** -> **Integrations**.
+Menu: **Configuration** -> **Devices & Services**.
Click on the `+` sign to add an integration and click on **Huawei
LTE**, and follow the configuration flow. After finishing, the Huawei
diff --git a/source/_integrations/keenetic_ndms2.markdown b/source/_integrations/keenetic_ndms2.markdown
index 70e64e5453f..7ab8027803d 100644
--- a/source/_integrations/keenetic_ndms2.markdown
+++ b/source/_integrations/keenetic_ndms2.markdown
@@ -20,4 +20,4 @@ Router running NDMS firmware versions 2.05 and up. It uses telnet connection so
## Configuration
-To add Keenetic router to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**.
+To add Keenetic router to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**.
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 6c7385da613..8f8dc4df672 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -48,7 +48,7 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
### Web Interface
-Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Configuration** -> **Integrations** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
+Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Configuration** -> **Devices & Services** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
Selecting one of these discovered panels will guide you through connecting and configuring the panel. If your panel was discovered via SSDP, you shouldn't need any information to complete configuration - simply confirm that the information displayed is correct. If the UI prompts you for IP/Port, you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
@@ -56,15 +56,15 @@ Selecting one of these discovered panels will guide you through connecting and c
If you have an existing `configuration.yaml` completing the UI configuration will do a one time import of the settings contained in `configuration.yaml`. Once the import creates a **Configured** integration the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the `konnected` section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the settings provided in the Home Assistant web interface.
-If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the UI configuration for that device.
+If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Devices & Services** -> **Configured** and repeat the UI configuration for that device.
-Once configuration is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior.
+Once configuration is completed you'll see a Konnected.io entry in **Configuration** -> **Devices & Services** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior.
#### Using Settings UI to Configure Zone Behavior
-The settings for each panel can be accessed by selecting the entry in **Configuration** -> **Integrations** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied.
+The settings for each panel can be accessed by selecting the entry in **Configuration** -> **Devices & Services** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied.
The settings UI starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that, you'll be prompted, for each zone that is not disabled, to configure details of the zones' behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
**Note some zones do not support all behaviors. The UI will reflect specific options available to each zone.**
diff --git a/source/_integrations/meteo_france.markdown b/source/_integrations/meteo_france.markdown
index 086caf9645e..f2d2e518469 100644
--- a/source/_integrations/meteo_france.markdown
+++ b/source/_integrations/meteo_france.markdown
@@ -33,7 +33,7 @@ It displays the current weather along with a 5 days forecast and create sensors,
To be used with the weather Lovelace card to access current condition, today and next four days forecast.
-The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Configuration** -> **Integrations**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`.
+The weather platform can be configured in the frontend to decide if the forecast is given daily (default) or hourly. To change the setting go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** box and click on **Options**. You can update the `Forecast mode` by choosing between `daily` or `hourly`.
## Sensor platforms
@@ -58,7 +58,7 @@ All the following sensors will be created :
Warning: The probability entities data are not always provided by the API. They are added only if available.
-To enable an entity disabled by default, go in **Configuration** -> **Integrations**, click on the city name in **Météo-France** and then the **X entities** link. You will have the list of the enabled entities. Here click the filter button and select **Show disable entities**. The disabled entities will be visible in the list, select the one you want to enable and click the **Enable Selected** button.
+To enable an entity disabled by default, go in **Configuration** -> **Devices & Services**, click on the city name in **Météo-France** and then the **X entities** link. You will have the list of the enabled entities. Here click the filter button and select **Show disable entities**. The disabled entities will be visible in the list, select the one you want to enable and click the **Enable Selected** button.
### About `next_rain` condition sensor
diff --git a/source/_integrations/mysensors.markdown b/source/_integrations/mysensors.markdown
index 593bc3a79ff..e5f8c4b2381 100644
--- a/source/_integrations/mysensors.markdown
+++ b/source/_integrations/mysensors.markdown
@@ -25,7 +25,7 @@ The [MySensors](https://www.mysensors.org) project combines devices like Arduino
## Configuration
-To integrate your Serial, Ethernet (LAN) or MQTT MySensors Gateway, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integration select **MySensors**.
+To integrate your Serial, Ethernet (LAN) or MQTT MySensors Gateway, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integration select **MySensors**.
Configuration depends on the type of Gateway you use:
diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown
index b07da902d42..5d3af5b4d35 100644
--- a/source/_integrations/nest.markdown
+++ b/source/_integrations/nest.markdown
@@ -297,7 +297,7 @@ In this section you will authorize Home Assistant to access your account by gene
- Restart the Thermostat device. See [How to restart or reset a Nest thermostat](https://support.google.com/googlenest/answer/9247296) for more details.
- In the official Nest app or on https://home.nest.com: Move the Thermostat to a different or fake/temporary room.
-- Reload the integration in Home Assistant: Navigate to **Configuration** then **Integrations**, click `...` next to *Nest* and choose **Reload**.
+- Reload the integration in Home Assistant: Navigate to **Configuration** then **Devices & Services**, click `...` next to *Nest* and choose **Reload**.
{% enddetails %}
diff --git a/source/_integrations/netatmo.markdown b/source/_integrations/netatmo.markdown
index 70d4cea4e2f..598cc26c383 100644
--- a/source/_integrations/netatmo.markdown
+++ b/source/_integrations/netatmo.markdown
@@ -235,7 +235,7 @@ client_secret:
**After the client_id and client_secret is added to your `configuration.yaml` you must enable Netatmo through the integrations page.**
-Menu: **Configuration** -> **Integrations**.
+Menu: **Configuration** -> **Devices & Services**.
Click on the `+` sign to add an integration and click on **Netatmo**.
After completing the configuration flow, the Netatmo integration will be available.
diff --git a/source/_integrations/plex.markdown b/source/_integrations/plex.markdown
index 82867e5dd89..c3e1f15c164 100644
--- a/source/_integrations/plex.markdown
+++ b/source/_integrations/plex.markdown
@@ -338,5 +338,5 @@ play_plex_on_tv:
## Notes
-- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Configuration** > **Integrations**.
+- The Plex integration supports multiple Plex servers. Additional connections can be configured under **Configuration** > **Devices & Services**.
- Movies must be located under the 'Movies' section in a Plex library to properly view the 'playing' state.
diff --git a/source/_integrations/rfxtrx.markdown b/source/_integrations/rfxtrx.markdown
index f23df8486f7..7691eebf043 100644
--- a/source/_integrations/rfxtrx.markdown
+++ b/source/_integrations/rfxtrx.markdown
@@ -62,7 +62,7 @@ You can host your device on another computer by setting up ser2net and example c
## Settings options
-To configure options for RFXtrx integration go to **Configuration** >> **Integrations** and press **Options** on the RFXtrx card.
+To configure options for RFXtrx integration go to **Configuration** >> **Devices & Services** and press **Options** on the RFXtrx card.
-You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Configuration** > **Integrations** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
+You must [restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. After restarting, navigate to the **Configuration** > **Devices & Services** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the app according to the above **Automatic Configuration**, starting at step 2.
## Notifications
diff --git a/source/_integrations/flume.markdown b/source/_integrations/flume.markdown
index 8c82bd82711..69b39943575 100644
--- a/source/_integrations/flume.markdown
+++ b/source/_integrations/flume.markdown
@@ -25,7 +25,7 @@ You can find your Client ID and Client Secret under "API Access" on the [setting
The Flume API access is available to Flume Insight users only, which may require a paid subscription.
-To add `Flume` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
+To add `Flume` to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
## Configuration for Binary Sensor
diff --git a/source/_integrations/freebox.markdown b/source/_integrations/freebox.markdown
index 7f6c806f84a..2b751485aaa 100644
--- a/source/_integrations/freebox.markdown
+++ b/source/_integrations/freebox.markdown
@@ -36,7 +36,7 @@ Please consult the [API documentation](https://dev.freebox.fr/sdk/os/) for more
### Via the frontend
-Menu: **Configuration** -> **Integrations**. Search for "Freebox", add your host and port, click submit.
+Menu: **Configuration** -> **Devices & Services**. Search for "Freebox", add your host and port, click submit.
If you add the integration for the first time, follow the instructions in the [Initial setup](#initial-setup) section.
diff --git a/source/_integrations/harmony.markdown b/source/_integrations/harmony.markdown
index 5f403dbc461..c61e59d8c73 100644
--- a/source/_integrations/harmony.markdown
+++ b/source/_integrations/harmony.markdown
@@ -32,7 +32,7 @@ Supported units:
{% include integrations/config_flow.md %}
-Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Integrations** >> **Your Logitech Harmony Hub**
+Once the Logitech Harmony Hub has been configured, the default activity and duration in seconds between sending commands to a device can be adjusted in the settings via **Configuration** >> **Devices & Services** >> **Your Logitech Harmony Hub**
### Configuration file
diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown
index 94229cdc5f7..c91e197cf18 100644
--- a/source/_integrations/homekit.markdown
+++ b/source/_integrations/homekit.markdown
@@ -306,7 +306,7 @@ The HomeKit Accessory Protocol Specification only allows a maximum of 150 unique
### Multiple HomeKit instances
-If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Integrations**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
+If you create a HomeKit integration via the UI (i.e., **Configuration** >> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
It is recommended to only edit a HomeKit instance in the UI that was created in the UI, and likewise, only edit a HomeKit instance in YAML that was created in YAML.
@@ -479,15 +479,15 @@ The following home hubs have been reported to have trouble with a large number o
### Resetting when created via YAML
- 1. Delete the `HomeKit` integration in the **{% my integrations %}** screen.
+ 1. Delete the `HomeKit` integration in the **{% my integrations %}** panel.
2. **Restart** Home Assistant.
3. The configuration will be automatically reimported from YAML.
4. [Pair the bridge or accessory](#setup).
-### Resetting when created via the **Integrations** screen
+### Resetting when created via the **Integrations** panel
- 1. Delete the `HomeKit` integration in the **Integrations** screen.
- 2. Recreate the `HomeKit` integration in the **Integrations** screen.
+ 1. Delete the `HomeKit` integration in the **Integrations** panel.
+ 2. Recreate the `HomeKit` integration in the **Integrations** panel.
3. [Pair the bridge or accessory](#setup).
### Errors during pairing
@@ -600,7 +600,7 @@ Ensure that the [`ffmpeg`](/integrations/ffmpeg) integration is configured corre
#### Camera streaming is unstable or slow
-If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Configuration** >> **Integrations** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
+If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Configuration** >> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
#### Multiple camera streams
diff --git a/source/_integrations/huawei_lte.markdown b/source/_integrations/huawei_lte.markdown
index eba6ea7c1f7..883cd9f91cc 100644
--- a/source/_integrations/huawei_lte.markdown
+++ b/source/_integrations/huawei_lte.markdown
@@ -68,7 +68,7 @@ entities varies by device model and firmware version.
### Configuration via the frontend
-Menu: **Configuration** -> **Integrations**.
+Menu: **Configuration** -> **Devices & Services**.
Click on the `+` sign to add an integration and click on **Huawei
LTE**, and follow the configuration flow. After finishing, the Huawei
diff --git a/source/_integrations/keenetic_ndms2.markdown b/source/_integrations/keenetic_ndms2.markdown
index 70e64e5453f..7ab8027803d 100644
--- a/source/_integrations/keenetic_ndms2.markdown
+++ b/source/_integrations/keenetic_ndms2.markdown
@@ -20,4 +20,4 @@ Router running NDMS firmware versions 2.05 and up. It uses telnet connection so
## Configuration
-To add Keenetic router to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**.
+To add Keenetic router to your installation, go to **Configuration** >> **Devices & Services** in the UI, click the button with `+` sign and from the list of integrations select **Keenetic NDMS2 Router**.
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 6c7385da613..8f8dc4df672 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -48,7 +48,7 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
### Web Interface
-Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Configuration** -> **Integrations** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
+Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Configuration** -> **Devices & Services** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
Selecting one of these discovered panels will guide you through connecting and configuring the panel. If your panel was discovered via SSDP, you shouldn't need any information to complete configuration - simply confirm that the information displayed is correct. If the UI prompts you for IP/Port, you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
@@ -56,15 +56,15 @@ Selecting one of these discovered panels will guide you through connecting and c
If you have an existing `configuration.yaml` completing the UI configuration will do a one time import of the settings contained in `configuration.yaml`. Once the import creates a **Configured** integration the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the `konnected` section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the settings provided in the Home Assistant web interface.
-If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the UI configuration for that device.
+If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Devices & Services** -> **Configured** and repeat the UI configuration for that device.
diff --git a/source/_integrations/ruckus_unleashed.markdown b/source/_integrations/ruckus_unleashed.markdown
index 4471131124c..59fc1e633b5 100644
--- a/source/_integrations/ruckus_unleashed.markdown
+++ b/source/_integrations/ruckus_unleashed.markdown
@@ -21,7 +21,7 @@ There is currently support for the following device types within Home Assistant:
## Configuration
-To add a Ruckus Unleashed device to your installation, go to **Configuration** -> **Integrations**, click the `+` button, then select **Ruckus** from the list of integrations.
+To add a Ruckus Unleashed device to your installation, go to **Configuration** -> **Devices & Services**, click the `+` button, then select **Ruckus** from the list of integrations.
It is required to configure the IP address of your **master access point**. See the section Access Points on the management web interface. And perhaps consider to set a preferred master (Admin & Services>System>System Info>Preferred master).
diff --git a/source/_integrations/screenlogic.markdown b/source/_integrations/screenlogic.markdown
index f94235da592..95f0de35c09 100644
--- a/source/_integrations/screenlogic.markdown
+++ b/source/_integrations/screenlogic.markdown
@@ -28,7 +28,7 @@ The Pentair ScreenLogic integration allows you to integrate your Pentair Intelli
## Options
-ScreenLogic options are set via **Configuration** -> **Integrations** -> **Pentair ScreenLogic** -> **Options**.
+ScreenLogic options are set via **Configuration** -> **Devices & Services** -> **Pentair ScreenLogic** -> **Options**.
* Seconds between scans - How many seconds between each polling of the ScreenLogic gateway.
diff --git a/source/_integrations/sentry.markdown b/source/_integrations/sentry.markdown
index a70830676ce..28e2d6a0830 100644
--- a/source/_integrations/sentry.markdown
+++ b/source/_integrations/sentry.markdown
@@ -45,6 +45,6 @@ The Sentry integration provides settings to:
- Ability to send out events originating from third-party Python packages.
- Enable performance tracing and tune the tracing sample rate used.
-To change the settings go in **Configuration** -> **Integrations**, find the already installed **Sentry** box and click on **Options**.
+To change the settings go in **Configuration** -> **Devices & Services**, find the already installed **Sentry** box and click on **Options**.
After changing Sentry settings, you'll need to restart Home Assistant in order to make them effective.
diff --git a/source/_integrations/somfy_mylink.markdown b/source/_integrations/somfy_mylink.markdown
index 61020e115f7..0b86d60ba8b 100644
--- a/source/_integrations/somfy_mylink.markdown
+++ b/source/_integrations/somfy_mylink.markdown
@@ -17,4 +17,4 @@ The `Somfy MyLink` integration is used as an interface to a compatible Somfy MyL
{% include integrations/config_flow.md %}
-If any of your devices are reversed, they can be adjusted in **Configuration** >> **Integrations** >> **Somfy MyLink** >> `Options`.
+If any of your devices are reversed, they can be adjusted in **Configuration** >> **Devices & Services** >> **Somfy MyLink** >> `Options`.
diff --git a/source/_integrations/subaru.markdown b/source/_integrations/subaru.markdown
index d7ca78bbc09..c9f396a143f 100644
--- a/source/_integrations/subaru.markdown
+++ b/source/_integrations/subaru.markdown
@@ -54,7 +54,7 @@ If your account includes multiple vehicles, the same PIN will be used for all ve
Subaru integration options are set via:
-**Configuration** -> **Integrations** -> **Subaru** -> **Options**.
+**Configuration** -> **Devices & Services** -> **Subaru** -> **Options**.
The only option is:
diff --git a/source/_integrations/xiaomi_aqara.markdown b/source/_integrations/xiaomi_aqara.markdown
index 7f3455c4599..df311d749b3 100644
--- a/source/_integrations/xiaomi_aqara.markdown
+++ b/source/_integrations/xiaomi_aqara.markdown
@@ -65,7 +65,7 @@ Please note, there are two versions of the hub: v1 and v2. v1 can be used with H
Follow the setup process using your phone and Mi-Home app. From here you will be able to retrieve the key (password) from within the app following [this tutorial](https://www.domoticz.com/wiki/Xiaomi_Gateway_(Aqara)#Adding_the_Xiaomi_Gateway_to_Domoticz).
-To enable {{ page.title }} in your installation, go to **Configuration** in the sidebar, then click **Integrations**. Xiaomi Aqara gateways should be discovered automatically and should show up in the overview. Hit configure and go through the steps to specify the optional settings. If your aqara gateway does not show up automatically, click the + icon in the lower right. Then search for "xiaomi_aqara" and enter the setup. Multiple gateways can be configured by simply repeating the setup multiple times.
+To enable {{ page.title }} in your installation, go to **Configuration** in the sidebar, then click **Devices & Services**. Xiaomi Aqara gateways should be discovered automatically and should show up in the overview. Hit configure and go through the steps to specify the optional settings. If your aqara gateway does not show up automatically, click the + icon in the lower right. Then search for "xiaomi_aqara" and enter the setup. Multiple gateways can be configured by simply repeating the setup multiple times.
{% configuration %}
interface:
diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown
index 18aced7b7c2..464c99219e9 100644
--- a/source/_integrations/zha.markdown
+++ b/source/_integrations/zha.markdown
@@ -338,7 +338,7 @@ This service disables a lock code on a Zigbee lock.
To add a new device:
-1. Go to the **Integrations** page, find the **Zigbee Home Automation** integration that was added by the configuration steps above, and select **Configure**.
+1. Go to the **Integrations** panel, find the **Zigbee Home Automation** integration that was added by the configuration steps above, and select **Configure**.
1. Click on the plus button at the bottom right corner to start a scan for new devices.
1. Reset your Zigbee devices according to the device instructions provided by the manufacturer (e.g., turn on/off lights up to 10 times, switches usually have a reset button/pin). It might take a few seconds for the devices to appear. You can click on **Show logs** for more verbose output.
1. Once the device is found, it will appear on that page and will be automatically added to your devices. You can optionally change its name and add it to an area (you can change this later). You can search again to add another device, or you can go back to the list of added devices.
@@ -405,7 +405,7 @@ When reporting issues, please provide the following information in addition to i
1. Debug logs for the issue, see [debug logging](#debug-logging)
2. Model of Zigbee radio being used
3. If issue is related to a specific Zigbee device, provide device Zigbee signature. Signature is available at
-**Configuration** -> **Integrations** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> **Zigbee Device Signature**
+**Configuration** -> **Devices & Services** -> **Zigbee Home Automation** (click **Configure**) -> **Devices** (pick your device) -> **Zigbee Device Signature**
### Debug logging
diff --git a/source/_integrations/zwave.markdown b/source/_integrations/zwave.markdown
index 41ddbf00efe..c26e041c371 100644
--- a/source/_integrations/zwave.markdown
+++ b/source/_integrations/zwave.markdown
@@ -674,7 +674,7 @@ You can use the **Remove Failed Node** button to remove a failed device (e.g., b
## Control panel
-The Z-Wave control panel is available via **Configuration** → **Integrations** → **Z-Wave** → **Configure**.
+The Z-Wave control panel is available via **Configuration** → **Devices & Services** → **Z-Wave** → **Configure**.
- **No Z-Wave integration?** Follow the [set up instructions](/integrations/zwave/#detailed-installation-instructions) to enable it.
- **Missing the *Configuration* button?** See the [configuration documentation](/integrations/config/) for instructions on enabling it.
diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown
index 8146f02e63b..5d7f788e8af 100644
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@@ -724,7 +724,7 @@ to pick up those new names, either reload the integration or restart Home Assist
When trying to determine why something isn't working as you expect, or when reporting an issue with the integration, it is helpful to know what Z-Wave JS sees as the current state of your Z-Wave network. To get a dump of your current network state, follow the menu:
-**Configuration** -> **Integrations** -> **Z-Wave JS** -> **Configure** -> **Download a dump of your network to help diagnose issues**
+**Configuration** -> **Devices & Services** -> **Z-Wave JS** -> **Configure** -> **Download a dump of your network to help diagnose issues**
### Interference issues
From 2bb896b758880c4ef92dcb443ae54f02ca47d53f Mon Sep 17 00:00:00 2001
From: Franck Nijhof
-
-If you set `show_on_map` to `true` then the location attributes are named `latitude` and `longitude`. The default name of the location attributes is `lat` and `long` to avoid showing them on the map.
-
-
-
-Not all sensors provide all conditions. Also, it's possible that the sensor values are not available all the time. To check what a sensor is publishing use `curl`:
-
-```bash
-curl https://data.sensor.community/airrohr/v1/sensor/[sensorid]/
-```
-
-## Full example
-
-This example would use the sensor with the ID 155, show it on the `map` and would monitor `temperature` and `humidity`.
-
-```yaml
-# Example configuration.yaml entry
-luftdaten:
- sensor_id: 155
- show_on_map: true
- sensors:
- monitored_conditions:
- - temperature
- - humidity
-```
-
-## Sensor
-
-The `luftdaten` sensor platform will query the open data API of [luftdaten.info](https://luftdaten.info/) to monitor air quality and other weather data from a specific (self build) sensor station.
-
-You must have the `luftdaten` integration (from above) configured to use this platform. After configuring that component, sensors will automatically appear.
From 6902060349d3ffd20d59b081d08abd1af4a6a6dc Mon Sep 17 00:00:00 2001
From: "J. Nick Koston"
+Not filtering domains or entities will send every event to Azure Event Hub, thus taking up a lot of space and bandwidth.
+
+
+
+Event Hubs have a retention time of at most 7 days, if you do not capture or use the events they are deleted automatically from the Event Hub, the default retention is 1 day.
+
+
+### Filter Configuration
+
+By default, no entity will be excluded. To limit which entities are being exposed to `Azure Event Hub`, you can use the `filter` parameter.
```yaml
-# Example configuration.yaml entry
+# Example filter to include specified domains and exclude specified entities
azure_event_hub:
- event_hub_namespace: NAMESPACE_NAME
- event_hub_instance_name: EVENT_HUB_INSTANCE_NAME
- event_hub_sas_policy: SAS_POLICY_NAME
- event_hub_sas_key: SAS_KEY
filter:
include_domains:
- - homeassistant
- - light
- - media_player
+ - alarm_control_panel
+ - light
+ include_entity_globs:
+ - binary_sensor.*_occupancy
+ exclude_entities:
+ - light.kitchen_light
```
+Filters are applied as follows:
+
+1. No includes or excludes - pass all entities
+2. Includes, no excludes - only include specified entities
+3. Excludes, no includes - only exclude specified entities
+4. Both includes and excludes:
+ - Include domain and/or glob patterns specified
+ - If domain is included, and entity not excluded or match exclude glob pattern, pass
+ - If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
+ - If domain is not included, glob pattern does not match, and entity not included, fail
+ - Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
+ - If domain is excluded and entity not included, fail
+ - If entity matches exclude glob pattern and entity not included, fail
+ - If entity does not match any exclude criteria (domain, glob pattern or listed), pass
+ - Neither include or exclude specifies domains or glob patterns
+ - If entity is included, pass (as #2 above)
+ - If entity include and exclude, the entity exclude is ignored
+
{% configuration %}
-event_hub_namespace:
- description: The name of your Event Hub namespace.
- required: exclusive
- type: string
-event_hub_instance_name:
- description: The name of your Event Hub instance.
- required: true
- type: string
-event_hub_sas_policy:
- description: The name of your Shared Access Policy.
- required: exclusive
- type: string
-event_hub_sas_key:
- description: The key for the Shared Access Policy.
- required: exclusive
- type: string
-event_hub_connection_string:
- description: The connection string to your event hub.
- required: exclusive
- type: string
-send_interval:
- description: The interval in seconds should events be sent to the Event Hub.
- required: false
- type: integer
- default: 5
-max_delay:
- description: The time in seconds after which a message is to be discarded.
- required: false
- type: integer
- default: 30
filter:
- description: Filter domains and entities for Event Hub. ([Configure Filter](#configure-filter))
- required: true
+ description: Filter domains and entities for Event Hub.
+ required: false
type: map
default: Includes all entities from all domains
keys:
@@ -107,66 +107,6 @@ filter:
type: list
{% endconfiguration %}
-
-Not filtering domains or entities will send every event to Azure Event Hub, thus taking up a lot of space.
-
-
-
-Event Hubs have a retention time of at most 7 days, if you do not capture or use the events they are deleted automatically from the Event Hub, the default retention is 1 day.
-
-
-### Configure Filter
-
-By default, no entity will be excluded. To limit which entities are being exposed to `Azure Event Hub`, you can use the `filter` parameter.
-
-```yaml
-# Example filter to include specified domains and exclude specified entities
-azure_event_hub:
- event_hub_namespace: NAMESPACE_NAME
- event_hub_instance_name: EVENT_HUB_INSTANCE_NAME
- event_hub_sas_policy: SAS_POLICY_NAME
- event_hub_sas_key: SAS_KEY
- filter:
- include_domains:
- - alarm_control_panel
- - light
- include_entity_globs:
- - binary_sensor.*_occupancy
- exclude_entities:
- - light.kitchen_light
-```
-
-Filters are applied as follows:
-
-1. No includes or excludes - pass all entities
-2. Includes, no excludes - only include specified entities
-3. Excludes, no includes - only exclude specified entities
-4. Both includes and excludes:
- - Include domain and/or glob patterns specified
- - If domain is included, and entity not excluded or match exclude glob pattern, pass
- - If entity matches include glob pattern, and entity does not match any exclude criteria (domain, glob pattern or listed), pass
- - If domain is not included, glob pattern does not match, and entity not included, fail
- - Exclude domain and/or glob patterns specified and include does not list domains or glob patterns
- - If domain is excluded and entity not included, fail
- - If entity matches exclude glob pattern and entity not included, fail
- - If entity does not match any exclude criteria (domain, glob pattern or listed), pass
- - Neither include or exclude specifies domains or glob patterns
- - If entity is included, pass (as #2 above)
- - If entity include and exclude, the entity exclude is ignored
-
-### Advanced configuration
-
-This is what the configuration will look like when using a connection string directly, instead of the four parameters. It also shows how to set the send_interval and max_delay to something other than the default. This means once every minute the integration will connect to your hub and send messages, but the messages have to be less than 65 seconds old at the time of sending for them to be counted (send_interval + max_delay).
-
-```yaml
-# Connection string config with non-defaults for send_interval and max_delay
-azure_event_hub:
- event_hub_connection_string: CONNECTION_STRING
- event_hub_instance_name: EVENT_HUB_INSTANCE_NAME
- send_interval: 60
- max_delay: 5
-```
-
## Using the data in Azure
There are a number of ways to stream the data that comes into the Event Hub into storages in Azure, the easiest way is to use the built-in Capture function and this allows you to capture the data in Azure Blob Storage or Azure Data Lake store, [details here](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-capture-overview).
From 32659e2561478907fd704be24053ce36e599fc67 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Hjelseth=20H=C3=B8yer?=
- Please note: Besides the implemented platforms, the `lcn` integration offers a variety of [service calls](#services).
- These service calls cover functionalities of the LCN system, which cannot be represented by the platform implementations.
+ The implemented platforms do not cover the whole functionality of the LCN system.
+ Therefore the `lcn` integration offers a variety of [events](#events), [device triggers](#device-triggers) and [service calls](#services).
They are ideal to be used in automation scripts or for the `template` platforms.
@@ -483,8 +483,10 @@ The `lcn` sensor platform allows the monitoring of the following [LCN](https://w
The sensor can be used in automation scripts or in conjunction with `template` platforms.
+
Ensure that the LCN module is configured properly to provide the requested value.
Otherwise, the module might show unexpected behavior or return error messages.
+
### Switch
@@ -494,12 +496,207 @@ The `lcn` switch platform allows the control of the following [LCN](https://www.
- Output ports
- Relays
+## Additional Features
+
+### Transponder and fingerprint sensor
+
+To use LCN transponders or fingerprint sensors ensure that the corresponding module's I-port property
+is enabled in the LCN-PRO software and properly configured.
+LCN transponders and fingerprints are identified by a six value hexadecimal code (e.g. *123abc*).
+If a code is received a corresponding event ([transponder event](#event-lcn_transponder), [fingerprint event](#event-lcn_fingerprint))
+is fired and can be used to trigger an automation.
+Alternatively, you can use the corresponding [device triggers](#device-triggers).
+
+Example:
+
+This example shows how the `event_data` can be extracted and used in a condition using Home Assistant's templating engine.
+Trigger on a transponder event and ensure that the received code is in the given list:
+
+{% raw %}
+
+```yaml
+automation:
+ trigger:
+ - platform: event
+ event_type: lcn_transponder
+ condition: "{{ trigger.event.data.code in ['aabbcc', 'ddeeff', '112233'] }}"
+ action:
+ ...
+```
+
+{% endraw %}
+
+Further examples can be found in the [event section](#events).
+
+### Remote control
+
+To use LCN remote controls (e.g., LCN-RT or LCN-RT16) ensure that the corresponding module's I-port property
+is enabled in the LCN-PRO software and its behavior is properly configured as "IR access control".
+With this configuration each remote control is identified by a six value hexadecimal code (e.g. *123abc*).
+If a command from a remote control is received a corresponding event ([transponder event](#event-lcn_transponder))
+is fired and can be used to trigger an automation. Along with the transmitted code, the pressed key and the key action
+are transmitted.
+Alternatively, you can use the corresponding [device triggers](#device-triggers).
+
+Examples can be found in the [event section](#events).
+
+### LCN commands addressed to PCHK host (Home Assistant)
+
+A LCN module can not only be programmed to send commands to other modules/groups but also to the PCHK host configured
+in the LCN integration. These commands are directly passed to Home Assistant and can be evaluated. Only the *send keys*
+(former) command is supported.
+
+Within LCN-PRO program the *send keys* command (only "A-C former command" is supported) to a key. For the target address
+manually enter the PCHK host id (default: 4). Select the keys and key actions as desired.
+
+When a *send keys* command is received, the LCN integration will fire a [send keys event](#event-lcn_send_keys) for each
+key configured. These events can be used to trigger an automation.
+Alternatively, you can use the corresponding [device triggers](#device-triggers).
+
+Examples can be found in the [event section](#events).
+
+
+
+ Only commands sent from physical buttons of a module are evaluated. The "Test command" button in the LCN-PRO software
+ is not evaluated and therefore cannot be used for testing purposes.
+
+
+
+## Events
+
+There are several functionalities of the LCN system which are not exposed as regular entities by the integration, but as events.
+Examples are button presses from remote controls (transmitters), transponder findings, fingerprint sensors and so called *send keys* events.
+
+
+
+ If you find it difficult to deal with events in scripted automations, you can also use [device triggers](#device-triggers)
+ which offer automation design via the UI.
+
+
+
+All events have some common attributes in their `event_data` which identify the sending LCN hardware module (e.g., the module the transponder is connected to):
+
+| Event payload | Description | Values |
+| ------------- | ----------- | ------ |
+| `device_id` | Internal device id of LCN module | string |
+| `segment_id` | Module's segment id | 5..128 |
+| `module_id` | Module id | 5..254 |
+
+In addition, every event has its own special attributes which are described below.
+All special attributes are optional and can be used as supplementary filters.
+
+### Event: `lcn_transmitter`
+
+The `lcn_transmitter` event is fired if a LCN remote control command is received.
+
+| Special payload | Description | Values |
+| --------------- | ----------- | ------ |
+| `code` | Transmitter code | string (6 hex values) |
+| `level` | Key level | 0..4 |
+| `key` | Key | 0..4 |
+| `action` | Key action | `hit`, `make`, `break` |
+
+Example:
+
+The trigger will fire if any key on the remote control with code *123abc* is `hit` as long as the
+receiver hardware is connected to module 7 in segment 0.
+
+```yaml
+automation:
+ trigger:
+ - platform: event
+ event_type: lcn_transmitter
+ event_data:
+ segment_id: 0
+ module_id: 7
+ code: 123abc
+ action: hit
+```
+
+### Event: `lcn_transponder`
+
+The `lcn_transponder` event is fired if a LCN transponder command is received.
+
+| Special payload | Description | Values |
+| --------------- | ----------- | ------ |
+| `code` | Transponder code | string (6 hex values) |
+
+Example:
+
+The trigger will fire if the transponder with code *123abc* was detected at
+any hardware module.
+
+```yaml
+automation:
+ trigger:
+ - platform: event
+ event_type: lcn_transponder
+ event_data:
+ code: 123abc
+```
+
+### Event: `lcn_fingerprint`
+
+The `lcn_fingerprint` event is fired if a LCN fingerprint command is received.
+
+| Special payload | Description | Values |
+| --------------- | ----------- | ------ |
+| `code` | Fingerprint code | string (6 hex values) |
+
+Example:
+
+The trigger will fire if the fingerprint with code *123abc* was detected at
+any hardware module.
+
+```yaml
+automation:
+ trigger:
+ - platform: event
+ event_type: lcn_fingerprint
+ event_data:
+ code: 123abc
+```
+
+### Event: `lcn_send_keys`
+
+The `lcn_send_keys` event is fired if the PCHK host receives a *send keys* command.
+
+| Special payload | Description | Values |
+| --------------- | ----------- | ------ |
+| `key` | LCN Key | a1..c8 |
+| `action` | Key action | `hit`, `make`, `break` |
+
+Example:
+
+The trigger will fire if the PCHK host receives a command that issues a `hit` of
+key `a1`.
+
+```yaml
+automation:
+ trigger:
+ - platform: event
+ event_type: lcn_send_keys
+ event_data:
+ key: a1
+ action: hit
+```
+
+## Device triggers
+
+To simplify using events in automations the LCN integration exposes them as device triggers.
+Those device triggers can be selected from the automation editor within Home Assistant.
+
+After creating a new automation select *Device* as trigger type and search for the module which is
+supposed to cause the event in the device list. You may select the trigger type and configure its
+attributes. If an attribute is optional it is considered as a supplementary filter for the trigger.
+For an explanation of the attributes refer to the corresponding [events](#events).
+
## Services
In order to directly interact with the LCN system, and invoke commands which are not covered by the implemented platforms, the following service calls can be used.
Refer to the [Services Calls](/docs/scripts/service-calls) page for examples on how to use them.
-### Service `output_abs`
+### Service: `output_abs`
Set absolute brightness of output port in percent.
@@ -521,7 +718,7 @@ data:
transition: 0
```
-### Service `output_rel`
+### Service: `output_rel`
Set relative brightness of output port in percent.
@@ -542,7 +739,7 @@ data:
brightness: 30
```
-### Service `output_toggle`
+### Service: `output_toggle`
Toggle output port.
@@ -562,7 +759,7 @@ data:
transition: 0
```
-### Service `relays`
+### Service: `relays`
Set the relays status. The relays states are defined as a string with eight characters.
Each character represents the state change of a relay (1=on, 0=off, t=toggle, -=nochange).
@@ -583,7 +780,7 @@ data:
state: t---001-
```
-### Service `led`
+### Service: `led`
Set the LED status.
@@ -602,7 +799,7 @@ data:
state: blink
```
-### Service `var_abs`
+### Service: `var_abs`
Set the absolute value of a variable or setpoint.
If `value` is not defined, it is assumed to be 0.
@@ -631,7 +828,7 @@ data:
Otherwise the module might show unexpected behaviors or return error messages.
-### Service `var_rel`
+### Service: `var_rel`
Set the relative value of a variable or setpoint.
If `value` is not defined, it is assumed to be 0.
@@ -660,7 +857,7 @@ data:
Otherwise the module might show unexpected behavior or return error messages.
-### Service `var_reset`
+### Service: `var_reset`
Reset value of variable or setpoint.
@@ -683,7 +880,7 @@ data:
Otherwise the module might show unexpected behavior or return error messages.
-### Service `lock_regulator`
+### Service: `lock_regulator`
Locks a regulator setpoint.
If `state` is not defined, it is assumed to be `False`.
@@ -704,7 +901,7 @@ data:
state: true
```
-### Service `send_keys`
+### Service: `send_keys`
Send keys (which executes bound commands).
The keys attribute is a string with one or more key identifiers. Example: `a1a5d8`
@@ -741,7 +938,7 @@ data:
time_unit: s
```
-### Service `lock_keys`
+### Service: `lock_keys`
Locks keys.
If the table is not defined, it is assumed to be table `a`.
@@ -778,7 +975,7 @@ data:
time_unit: s
```
-### Service `dyn_text`
+### Service: `dyn_text`
Send dynamic text to LCN-GTxD displays.
The displays support four rows for text messages.
@@ -801,7 +998,7 @@ data:
text: "text in row 1"
```
-### Service `pck`
+### Service: `pck`
Send arbitrary PCK command. Only the command part of the PCK command has to be specified in the `pck` string.
From f9907ef906514ce451e536d2ceb58acc5cc09eb0 Mon Sep 17 00:00:00 2001
From: Penny Wood
+It's also supported in script or automation `condition` actions:
-While conditions can be used in script sequences or automation actions, the
-shorthand for template conditions cannot be used directly in those constructs.
+{% raw %}
-However, if an used action supports conditions itself, like `choose` and
- `repeat`, the shorthand template conditions will be accepted in those cases.
+```yaml
+- condition: "{{ is_state('device_tracker.iphone', 'away') }}"
+```
-
+{% endraw %}
[template]: /topics/templating/
[automation-templating]: /getting-started/automation-templating/
From 1a75e8db503937601a1d540f8f19a187f0745f18 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `mcp23017` integration is the base for all related mcp23017 platforms in Home Assistant. There is no setup needed for the integration itself, for the platforms please check their corresponding sections.
For more details about the MCP23017 I2C I/O port expander you can find its datasheet here: [MCP23017](https://www.microchip.com/wwwproducts/en/MCP23017).
From a203df28ef851f77f9461172b4c8ad367dac535a Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `pcal9535a` integration is the base for all related pcal9535a platforms in Home Assistant. There is no setup needed for the integration itself, for the platforms, please check their corresponding sections.
One of the use cases is [Seeed studio Raspberry Pi Relay Board](http://wiki.seeedstudio.com/Raspberry_Pi_Relay_Board_v1.0/).
From b337e5605e7cb9c2379140522426d6e8c75a6fd2 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `sht31` sensor platform allows you to get the current temperature and humidity from a Sensirion SHT31 device.
## Configuration
From 424bf851077003407d822e7aaf5ff819276b6e59 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `dht` sensor platform allows you to get the current temperature and humidity from a DHT11, DHT22 or AM2302 device.
## Setup
From 31931ef3188dc3e4001ad02dbe3b50027b1610c4 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `bh1750` sensor platform allows you to read the ambient light level in Lux from a [BH1750FVI sensor](https://www.mouser.com/ds/2/348/bh1750fvi-e-186247.pdf) connected via [I2c](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins). It allows you to use all the resolution modes of the sensor described in its datasheet.
Tested devices:
From 5e18ca163e52a6a8a32a6ee7205d83124532520b Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `pi4ioe5v9xxxx` integration provides support for the quasi-bidirectional devices PI4IOE5V9570, PI4IOE5V9674, PI4IOE5V9673, PI4IOE5V96224 and PI4IOE5V96248 from [diodes.com](https://www.diodes.com).
For more details about the pi4ioe5v9xxxx I2C I/O port expander you can find the datasheets here:
From eb83510f0899e651f161e6dd772f0d8e3fae51ba Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `bbb_gpio` integration is the base for all [BeagleBone Black](https://beagleboard.org/black) related GPIO platforms in Home Assistant.
There is no setup needed for the integration itself.
From b76d2db200e4c1fcf239c016fb38f545064e1192 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
If you create the API key using a dedicated user (and not your main user),
then in the Sensibo app log you will be able to distinguish between actions
done in the app and actions done by Home Assistant.
-## Full configuration example
-
-```yaml
-climate:
- - platform: sensibo
- api_key: YOUR_API_KEY
- id:
- - id1
- - id2
-```
+{% include integrations/config_flow.md %}
## Adding a quick switch example
From 24c4bca7f4c3891216b27306f8bac5175e3ccef8 Mon Sep 17 00:00:00 2001
From: Simone Chemelli
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `bme680` sensor platform allows you to read temperature, humidity, pressure and gas resistance values of a [Bosch BME680 Environmental sensor](https://cdn-shop.adafruit.com/product-files/3660/BME680.pdf) connected via an [I2C](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins). It allows you to use all the operation modes of the sensor described in its datasheet. In addition, it includes a basic air quality calculation that uses gas resistance and humidity measurements to calculate a percentage based air quality measurement.
Tested devices:
From b390ad46ec4c9a4a4fd495b7608785eeccfc7207 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `bmp280` sensor platform allows you to read temperature and pressure values of a [Bosch BMP280 Environmental sensor](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp280/) connected via [I2C](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins).
This integration has been tested on a Raspberry Pi 4B, but it should work on any device which is supported by [CircuitPython](https://circuitpython.org/).
From 9bff704fcf3791bd3fb098e95fd44d5988cd7676 Mon Sep 17 00:00:00 2001
From: epenet <6771947+epenet@users.noreply.github.com>
Date: Tue, 28 Dec 2021 21:38:09 +0100
Subject: [PATCH 053/247] Add CO device classes to binary_sensor (#20721)
---
source/_integrations/binary_sensor.markdown | 1 +
1 file changed, 1 insertion(+)
diff --git a/source/_integrations/binary_sensor.markdown b/source/_integrations/binary_sensor.markdown
index 47fc263c988..fb769c6d3cf 100644
--- a/source/_integrations/binary_sensor.markdown
+++ b/source/_integrations/binary_sensor.markdown
@@ -46,6 +46,7 @@ The full list of supported binary sensor device classes is below
- **None**: Generic on/off. This is the default and doesn't need to be set.
- **battery**: `on` means low, `off` means normal
- **battery_charging**: `on` means charging, `off` means not charging
+- **carbon_monoxide**: `on` means carbon monoxide detected, `off` no carbon monoxide (clear)
- **cold**: `on` means cold, `off` means normal
- **connectivity**: `on` means connected, `off` means disconnected
- **door**: `on` means open, `off` means closed
From d8e33385859b994271e3b3d9566d9f3ed33191b2 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The Time of Flight sensor uses an invisible laser to measure distance with millimeter resolution.
Tested devices:
From 5f1a08883e5129309c0f52745a6c442f6f1cebb2 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
+
+This integration is deprecated and will be removed in Home Assistant Core 2022.4.
+
+For more information see: [Architectural Decision Record 0019](https://github.com/home-assistant/architecture/blob/master/adr/0019-GPIO.md).
+
+
+
The `htu21d` sensor platform allows you to read the temperature and humidity from a [HTU21D sensor](https://cdn-shop.adafruit.com/datasheets/1899_HTU21D.pdf) connected via [I2c](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins).
Tested devices:
From 1e96488917ba8b61e928220676990bb2401ca940 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sebastian=20L=C3=B6vdahl?=
-New users are not currently able to set up a Works With Nest Developer account. The documentation is preserved here for existing users of the API.
+
+The [Works with Nest](https://developers.nest.com/) API is deprecated and will be removed in Home Assistant Core 2022.5.
+
{% details "Legacy Works with Nest Configuration Steps" %}
From 13f953afd5d9c7bcc6c8d2523c44ed10836e3306 Mon Sep 17 00:00:00 2001
From: Franck Nijhof