Removing the integration (#38675)

2025-07-13 20:36:52 +00:00 · 2025-04-22 17:22:10 +02:00 · 2025-04-22 17:22:10 +02:00 · 2196f95537
commit 2196f95537
parent 163103c6f9
32 changed files with 37 additions and 38 deletions
--- a/source/_integrations/acaia.markdown
+++ b/source/_integrations/acaia.markdown
@ -108,7 +108,7 @@ actions:

 - While this integration is configured for your device, you won't be able to use the official app, as only one connection at a time is supported.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/airgradient.markdown
+++ b/source/_integrations/airgradient.markdown
@ -84,7 +84,7 @@ The following entities are supported:
 - NOx learning offset
 - Total volatile organic compounds learning offset

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/aquacell.markdown
+++ b/source/_integrations/aquacell.markdown
@ -98,7 +98,7 @@ There are no known limitations for this integration.

 There are no commonly known issues with this integration.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/bring.markdown
+++ b/source/_integrations/bring.markdown
@ -218,7 +218,7 @@ The **Bring!** integration relies on an active internet connection to communicat

 In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue reoccurs, stop the debug logging again (*download of debug log file will start automatically*). Further, if still possible, please also download the [diagnostics](/integrations/diagnostics) data. If you have collected the debug log and the diagnostics data, provide them with the issue report.

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/cookidoo.markdown
+++ b/source/_integrations/cookidoo.markdown
@ -111,7 +111,7 @@ The Home Assistant to-do list interface allows both renaming items and changing

 The Cookidoo integration fetches data from the device every 90 seconds by default.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/eheimdigital.markdown
+++ b/source/_integrations/eheimdigital.markdown
@ -49,7 +49,7 @@ Currently, the following devices and entities are supported:

 Support for additional EHEIM Digital devices and entities will be added in future updates.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/electric_kiwi.markdown
+++ b/source/_integrations/electric_kiwi.markdown
@ -70,7 +70,7 @@ actions:
 {% endraw %}
 {% enddetails %}

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/enigma2.markdown
+++ b/source/_integrations/enigma2.markdown
@ -90,7 +90,7 @@ There are two possible solutions to resolve this problem:
 If you choose to enable VPN access without authentication, ensure your network is properly secured as OpenWebif is not designed for publicly facing the internet.
 {% endnote %}

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/flick_electric.markdown
+++ b/source/_integrations/flick_electric.markdown
@ -103,7 +103,7 @@ actions:

 The integration will {% term polling poll %} the Flick Electric API every 5 minutes to check for the current power price. You can also use the `homeassistant.update_entity` action to trigger a refresh on-demand.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/fronius.markdown
+++ b/source/_integrations/fronius.markdown
@ -196,7 +196,7 @@ The Solar API used by this integration is read-only. It does not provide any mea
 Some data, like photovoltaic production, is only provided by the Fronius device when non-zero.
 When the integration is added at night, there might be no entities added providing photovoltaic related data. Entities will be added on sunrise, when the Fronius devices begin to provide more data.

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/fyta.markdown
+++ b/source/_integrations/fyta.markdown
@ -115,7 +115,7 @@ The integration provides the data exposed by means of the plant API. The light m

 Please note that in order to be able to access your plant data over the API, you need a [FYTA hub](https://fyta.de/collections/all/products/single-hub) that uploads the data from the Beam sensor to the FYTA server. Alternatively, the mobile app can serve as a gateway to upload the data from the Beam to the server. No direct connection to the FYTA Beam is supported (as the Beam only provides raw data, that needs to be processed on the FYTA server).

-## Remove integration
+## Removing the integration

 For this integration the general process to remove integrations applies:

--- a/source/_integrations/habitica.markdown
+++ b/source/_integrations/habitica.markdown
@ -574,7 +574,7 @@ The Habitica integration relies on an active internet connection to communicate

 In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue reoccurs stop the debug logging again (*download of debug log file will start automatically*). Further, if still possible, please also download the [diagnostics](/integrations/diagnostics) data. If you have collected the debug log and the diagnostics data, provide them with the issue report.

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/homewizard.markdown
+++ b/source/_integrations/homewizard.markdown
@ -181,7 +181,7 @@ It may happen that you can't find your devices or they won't show up in the inte

 Some sensors are disabled by default. You can enable them in the integration setup. See the [enabling or disabling entities](/common-tasks/general/#enabling-or-disabling-entities) documentation for more information.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal.

--- a/source/_integrations/husqvarna_automower.markdown
+++ b/source/_integrations/husqvarna_automower.markdown
@ -226,7 +226,7 @@ data:
 - The mower can only be started using the `lawn_mower.start_mowing` action during the schedules configured in the Automower Connect App. To start the mower outside the scheduled times, use the `husqvarna_automower.override_schedule` action. In both cases, the battery must be fully charged beforehand.
 - Stay-out zone handling is not supported for mowers equipped with EPOS technology.

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/incomfort.markdown
+++ b/source/_integrations/incomfort.markdown
@ -93,7 +93,7 @@ In case setting up an older gateway type fails, then try to leave `username` and

 The Intergas gateway will fetch state data from the gateway every 30 seconds. When the target temperature on the thermostat is changed, it might take some time for the set point to be updated on the Home Assistant climate {% term entity %}.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/iometer.markdown
+++ b/source/_integrations/iometer.markdown
@ -59,7 +59,7 @@ The following sensors are supported:

 There are no commonly known issues with this integration.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal. No extra steps are required.

--- a/source/_integrations/ista_ecotrend.markdown
+++ b/source/_integrations/ista_ecotrend.markdown
@ -113,7 +113,7 @@ The **ista EcoTrend** integration relies on an active internet connection to com

 In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue reoccurs, stop the debug logging again (*download of debug log file will start automatically*). Further, if still possible, please also download the [diagnostics](/integrations/diagnostics) data. If you have collected the debug log and the diagnostics data, provide them with the issue report.

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/knx.markdown
+++ b/source/_integrations/knx.markdown
@ -2456,7 +2456,7 @@ The `unique_id` for KNX entities is generated based on required configuration va

 There can not be multiple entities on the same platform sharing these exact group addresses, even if they differ in other configuration.

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/lcn.markdown
+++ b/source/_integrations/lcn.markdown
@ -813,7 +813,7 @@ The motor values specify which hardware relay or outputs configuration will be u
 Whenever a key has to be provided, it is defined by a joint string consisting of the table identifier (`a`, `b`, `c`, `d`) and the corresponding key number.
 Examples: `a1`, `a5`, `d8`.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/letpot.markdown
+++ b/source/_integrations/letpot.markdown
@ -114,7 +114,7 @@ When **Light on** and **Light off** are set to the same time, the built-in light

 The integration receives updates when the device state changes, enabling immediate updates of the data in Home Assistant.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/mcp.markdown
+++ b/source/_integrations/mcp.markdown
@ -94,8 +94,7 @@ general tips on debugging MCP. If you are developing your own MCP server and hav
 with Home Assistant, you can also use the [MCP Inspector](https://github.com/modelcontextprotocol/inspector)
 to verify that your MCP server is working correctly.

-
-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/mcp_server.markdown
+++ b/source/_integrations/mcp_server.markdown
@ -234,7 +234,7 @@ To understand the root cause, first check debug logs on the client. For example
     this means that the long live access token is not correct.
 ...

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/nut.markdown
+++ b/source/_integrations/nut.markdown
@ -434,7 +434,7 @@ In this example, the user `my_user` has permission to execute all commands (`ins

 Please note that Home Assistant cannot determine whether a user can access a specific action without executing it. If you attempt to perform an action for which the user does not have permission, an exception will be thrown at runtime.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal. No extra steps
 are required.
--- a/source/_integrations/overseerr.markdown
+++ b/source/_integrations/overseerr.markdown
@ -139,7 +139,7 @@ There are a few known limitations for using the integration:
 This means you can only have 1 Home Assistant instance connected to your Overseerr instance at a time.
 - The integration is not able to function with <abbr title="cross-site request forgery">CSRF</abbr> protection turned on. In Overseer, go to **Settings** and turn off the **CSRF Protection**.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.

--- a/source/_integrations/powerfox.markdown
+++ b/source/_integrations/powerfox.markdown
@ -92,7 +92,7 @@ It will create the following sensors:

 There are no commonly known issues with this integration.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal. No extra steps are required.

--- a/source/_integrations/pyload.markdown
+++ b/source/_integrations/pyload.markdown
@ -162,7 +162,7 @@ This integration {% term polling polls %} your **pyLoad** instance every 20 seco

 In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue reoccurs, stop the debug logging again (*download of debug log file will start automatically*). Further, if still possible, please also download the [diagnostics](/integrations/diagnostics) data. If you have collected the debug log and the diagnostics data, provide them with the issue report.

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/rainbird.markdown
+++ b/source/_integrations/rainbird.markdown
@ -146,7 +146,7 @@ not be possible for Home Assistant to send commands to the device while you
 are also using the Rain Bird App. Home Assistant tries to carefully limit
 connections to the device to avoid failures.

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/reolink.markdown
+++ b/source/_integrations/reolink.markdown
@ -493,7 +493,7 @@ Then power up the camera while pointing it at the QR code. It takes about a minu

 Set up the Reolink integration in Home Assistant using the credentials you set in step 1.

-## Remove integration
+## Removing the integration

 ### Removing a directly connected camera/NVR/Home Hub

--- a/source/_integrations/slide_local.markdown
+++ b/source/_integrations/slide_local.markdown
@ -77,7 +77,7 @@ The integration fetches data from the device every 15 seconds.
 The integration only provides connection with Slide devices via the local API. The cloud API is no longer available. 


-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/solarlog.markdown
+++ b/source/_integrations/solarlog.markdown
@ -56,12 +56,6 @@ Password:

 The integration has no additional configuration options.

-## Remove integration
-
-This integration can be removed by following these steps:
-
-{% include integrations/remove_device_service.md %}
-
 ## Supported functionality
 ### Sensors

@ -143,3 +137,9 @@ The integration provides no additional actions.

 The integration only provides the (limited) data exposed by means of the JSON interface. This also entails that the values for the self-consumption are rounded to full kWh.
 Firmware versions below 3.x are not supported, as they do not expose the JSON interface. Please contact the Solar-Log support if you need assistance with updating the firmware of your Solar-Log device.
+
+## Removing the integration
+
+This integration can be removed by following these steps:
+
+{% include integrations/remove_device_service.md %}
--- a/source/_integrations/suez_water.markdown
+++ b/source/_integrations/suez_water.markdown
@ -61,7 +61,7 @@ Extra attributes of `Water usage yesterday` sensor:
 - Last year total consumption
 - Current year total consumption

-## Remove integration
+## Removing the integration

 This integration can be removed by following these steps:

--- a/source/_integrations/weheat.markdown
+++ b/source/_integrations/weheat.markdown
@ -81,7 +81,7 @@ There is currently no way to control the heat pump via this integration.

 In case no devices are discovered, make sure that you can log in to the [Weheat portal](https://portal.weheat.nl) and the correct heat pumps are visible there. If they are available there, contact Weheat support.

-## Remove integration
+## Removing the integration

 This integration follows standard integration removal, no extra steps are required.