mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-14 21:06:50 +00:00
h-integrations: restart HA after changing config (#32641)
This commit is contained in:
c0ffeeca7
GitHub
parent
1339cd9760
commit
97edda3db4
@ -9,6 +9,9 @@ ha_domain: harman_kardon_avr
|
||||
ha_platforms:
|
||||
- media_player
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
The `harman_kardon_avr` platform allows you to control Harman Kardon Network Receivers from Home Assistant.
|
||||
@ -18,7 +21,8 @@ Supported devices:
|
||||
- Harman Kardon AVR-151S
|
||||
- Other Harman Kardon AVR receivers (untested)
|
||||
|
||||
To add a Harman Kardon Network Receiver to your installation, add the following to your `configuration.yaml` file:
|
||||
To add a Harman Kardon Network Receiver to your installation, add the following to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -9,9 +9,12 @@ ha_domain: haveibeenpwned
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
The `haveibeenpwned` sensor platform creates sensors that check for breached email accounts on [haveibeenpwned](https://haveibeenpwned.com).
|
||||
The `haveibeenpwned` sensor {% term integration %} creates sensors that check for breached email accounts on [haveibeenpwned](https://haveibeenpwned.com).
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -19,7 +22,8 @@ In order to use this integration you need to purchase an API key. Visit the [API
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml`, it will list every specified email address as a sensor showing the number of breaches on that email account.
|
||||
To enable this sensor, add the following lines to your {% term "`configuration.yaml`" %} file. It will list every specified email address as a sensor showing the number of breaches on that email account.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry using cloud based emoncms
|
||||
|
||||
@ -9,9 +9,12 @@ ha_domain: hddtemp
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
The `hddtemp` sensor platform is using the data provided by [HDDTemp](https://savannah.nongnu.org/projects/hddtemp).
|
||||
The `hddtemp` sensor {% term integration %} is using the data provided by [HDDTemp](https://savannah.nongnu.org/projects/hddtemp).
|
||||
|
||||
## Setup
|
||||
|
||||
@ -30,7 +33,8 @@ hddtemp -dF
|
||||
|
||||
## Configuration
|
||||
|
||||
To setup a HDDTemp to your installation, add the following to your `configuration.yaml` file:
|
||||
To setup a HDDTemp to your installation, add the following to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -11,15 +11,19 @@ ha_domain: hikvisioncam
|
||||
ha_platforms:
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
This `hikvisioncam` switch platform allows you to control your motion detection setting on your [Hikvision](https://www.hikvision.com/) camera.
|
||||
This `hikvisioncam` switch {% term integration %} allows you to control your motion detection setting on your [Hikvision](https://www.hikvision.com/) camera.
|
||||
|
||||
<div class='note warning'>
|
||||
Currently works using default https port only.
|
||||
</div>
|
||||
|
||||
To use your Hikvision cam in your installation, add the following to your `configuration.yaml` file:
|
||||
To use your Hikvision cam in your installation, add the following to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -11,11 +11,14 @@ ha_domain: history_stats
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
The **History stats** {% term integration %} provides quick statistics about another integration or platforms, using data from the [`history`](/integrations/history/) integration.
|
||||
|
||||
It can track how long the integration has been in a specific state, in a custom time period.
|
||||
It can track how long the {% term integration %} has been in a specific state, in a custom time period.
|
||||
|
||||
Examples of what you can track:
|
||||
|
||||
@ -25,7 +28,8 @@ Examples of what you can track:
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable the history statistics sensor, add the following lines to your `configuration.yaml`:
|
||||
To enable the history statistics sensor, add the following lines to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
||||
@ -14,7 +14,8 @@ ha_integration_type: integration
|
||||
This integration offers presence detection by examining devices connected to a [Rogers Hitron CODA](https://www.rogers.com/customer/support/article/wi-fi-password-hitron-coda4582-cgn3amr-cgnm3552-cgn3acr-cgn3)
|
||||
or [Shaw Hitron CGNM](https://community.shaw.ca/docs/DOC-4066) Router.
|
||||
|
||||
To use a Hitron router in your installation, add the following to your `configuration.yaml` file:
|
||||
To use a Hitron router in your installation, add the following to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -26,9 +26,12 @@ ha_platforms:
|
||||
- sensor
|
||||
- switch
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
The [Homematic](https://www.eq-3.com/products/homematic.html) integration provides bi-directional communication with your CCU/Homegear. It uses an XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
|
||||
The [Homematic](https://www.eq-3.com/products/homematic.html) {% term integration %} provides bi-directional communication with your CCU/Homegear. It uses an XML-RPC connection to set values on devices and subscribes to receive events the devices and the CCU emit.
|
||||
If you are using Homegear with paired [Intertechno](https://intertechno.at/) devices, uni-directional communication is possible as well.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
@ -57,7 +60,8 @@ You can manually rename the created entities by using Home Assistant's [Customiz
|
||||
|
||||
## Configuration
|
||||
|
||||
To set up the integration, add the following information to your `configuration.yaml` file:
|
||||
To set up the integration, add the following information to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
homematic:
|
||||
|
||||
@ -9,11 +9,15 @@ ha_domain: horizon
|
||||
ha_platforms:
|
||||
- media_player
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
The `horizon` integration allows you to control a [Unitymedia](https://www.unitymedia.de) Horizon HD Recorder from Home Assistant.
|
||||
The `horizon` {% term integration %} allows you to control a [Unitymedia](https://www.unitymedia.de) Horizon HD Recorder from Home Assistant.
|
||||
|
||||
To add a Horizon HD Recorder to your installation, add the following to your `configuration.yaml` file:
|
||||
To add a Horizon HD Recorder to your installation, add the following to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -37,7 +41,6 @@ media_player:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
#### Preparation of the Horizon HD Recorder
|
||||
|
||||
The Home Networking ("Heimnetzwerk") service needs to be enabled at the settings menu of the Horizon receiver. Once you have set up the Media Library ("Medienbibliothek"), we can determine whether the device is turned on or off. Without this, the integration will fail to start.
|
||||
|
||||
@ -9,9 +9,12 @@ ha_domain: hp_ilo
|
||||
ha_platforms:
|
||||
- sensor
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
The `hp_ilo` platform allows you to do an API call to the HP ILO (Integrated Lights-Out) sensor of your server, and use this data in Home Assistant sensors.
|
||||
The `hp_ilo` {% term integration %} allows you to do an API call to the HP ILO (Integrated Lights-Out) sensor of your server, and use this data in Home Assistant sensors.
|
||||
|
||||
If the ILO or specified jsonpath query returns only a single value (e.g., a temperature or state), it will be put in the state field. If a data structure is returned, it will be placed in the `ilo_data` attribute.
|
||||
|
||||
@ -23,7 +26,8 @@ Some more details about what can be retrieved from these sensors is available in
|
||||
|
||||
## Configuration
|
||||
|
||||
To use this integration in your installation, add the following to your `configuration.yaml` file:
|
||||
To use this integration in your installation, add the following to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -9,9 +9,12 @@ ha_domain: html5
|
||||
ha_platforms:
|
||||
- notify
|
||||
ha_integration_type: integration
|
||||
related:
|
||||
- docs: /docs/configuration/
|
||||
title: Configuration file
|
||||
---
|
||||
|
||||
The `html5` notification platform enables you to receive push notifications to Chrome or Firefox, no matter where you are in the world. `html5` also supports Chrome and Firefox on Android, which enables native-app-like integrations without actually needing a native app.
|
||||
The `html5` notification {% term integration %} enables you to receive push notifications to Chrome or Firefox, no matter where you are in the world. `html5` also supports Chrome and Firefox on Android, which enables native-app-like integrations without actually needing a native app.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
@ -21,7 +24,8 @@ HTML5 push notifications **do not** work on iOS versions below 16.4.
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable this platform, add the following lines to your `configuration.yaml` file:
|
||||
To enable this platform, add the following lines to your {% term "`configuration.yaml`" %} file.
|
||||
{% include integrations/restart_ha_after_config_inclusion.md %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user