jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

s-integrations-3: restart HA after changing config (#32724)

Browse Source
This commit is contained in:
c0ffeeca7 2024-05-13 17:41:50 +02:00 committed by GitHub
parent fb0fd4a6cb
commit 4dd8196a62
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
14 changed files with 121 additions and 65 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_integrations/spc.markdown
View File

@ -12,6 +12,9 @@ ha_platforms:
- alarm_control_panel - alarm_control_panel
- binary_sensor - binary_sensor
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
Home Assistant has support to integrate your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) alarm panel and any connected motion, door, smoke and technical sensors. Home Assistant has support to integrate your [Vanderbilt SPC](https://www.spcsupportinfo.com/SPCConnectPro/) alarm panel and any connected motion, door, smoke and technical sensors.
@ -23,7 +26,8 @@ There is currently support for the following device types within Home Assistant:
- [Alarm](#alarm) - [Alarm](#alarm)
- [Binary sensor](#binary-sensor) - [Binary sensor](#binary-sensor)
Home Assistant needs to know where to find the SPC Web Gateway API endpoints, to configure this add the following section to your `configuration.yaml` file: Home Assistant needs to know where to find the SPC Web Gateway API endpoints, to configure this add the following section to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

6
source/_integrations/splunk.markdown
View File

@ -9,13 +9,17 @@ ha_domain: splunk
ha_codeowners: ha_codeowners:
- '@Bre77' - '@Bre77'
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `splunk` integration makes it possible to log all state changes to an external [Splunk](https://splunk.com/) database using Splunk's HTTP Event Collector (HEC) feature. You can either use this alone, or with the Home Assistant for Splunk [app](https://github.com/miniconfig/splunk-homeassistant). Since the HEC feature is new to Splunk, you will need to use at least version 6.3. The `splunk` integration makes it possible to log all state changes to an external [Splunk](https://splunk.com/) database using Splunk's HTTP Event Collector (HEC) feature. You can either use this alone, or with the Home Assistant for Splunk [app](https://github.com/miniconfig/splunk-homeassistant). Since the HEC feature is new to Splunk, you will need to use at least version 6.3.
## Configuration ## Configuration
To use the `splunk` integration in your installation, add the following to your `configuration.yaml` file: To use the `splunk` integration in your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

8
source/_integrations/sql.markdown
View File

@ -14,9 +14,12 @@ ha_domain: sql
ha_platforms: ha_platforms:
- sensor - sensor
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `sql` sensor platform enables you to use values from an [SQL](https://en.wikipedia.org/wiki/SQL) database supported by the [sqlalchemy](https://www.sqlalchemy.org) library, to populate a sensor state (and attributes). The `sql` sensor {% term integration %} enables you to use values from an [SQL](https://en.wikipedia.org/wiki/SQL) database supported by the [sqlalchemy](https://www.sqlalchemy.org) library, to populate a sensor state (and attributes).
This can be used to present statistics about Home Assistant sensors if used with the `recorder` integration database. It can also be used with an external data source. This can be used to present statistics about Home Assistant sensors if used with the `recorder` integration database. It can also be used with an external data source.
**This integration can be configured using both config flow and by YAML.** **This integration can be configured using both config flow and by YAML.**
@ -27,7 +30,8 @@ This can be used to present statistics about Home Assistant sensors if used with
To configure this sensor, define the sensor connection variables and a list of queries to your `configuration.yaml` file. A sensor will be created for each query. To configure this sensor, define the sensor connection variables and a list of queries to your `configuration.yaml` file. A sensor will be created for each query.
To enable it, add the following lines to your `configuration.yaml` file (example by required fields): To enable it, add the following lines to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
{% raw %} {% raw %}
```yaml ```yaml

8
source/_integrations/starlingbank.markdown
View File

@ -9,9 +9,12 @@ ha_domain: starlingbank
ha_platforms: ha_platforms:
- sensor - sensor
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The Starling Bank sensor platform allows you to monitor your account balance data as sensors in Home Assistant. The Starling Bank sensor {% term integration %} allows you to monitor your account balance data as sensors in Home Assistant.
- Turn off the lights when money's tight? - Turn off the lights when money's tight?
- Play a song when you reach a savings goal? - Play a song when you reach a savings goal?
@ -37,7 +40,8 @@ Once you've signed up:
## Configuration ## Configuration
To add Starling account balance sensors to your installation, add the following to your `configuration.yaml` file: To add Starling account balance sensors to your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry
sensor: sensor:

6
source/_integrations/startca.markdown
View File

@ -9,6 +9,9 @@ ha_domain: startca
ha_platforms: ha_platforms:
- sensor - sensor
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
Integrate your [Start.ca](https://www.start.ca/) account information into Home Assistant. Integrate your [Start.ca](https://www.start.ca/) account information into Home Assistant.
@ -19,7 +22,8 @@ You can get your API key from: [Start.ca Usage API](https://portal.start.ca/acco
## Configuration ## Configuration
To use your Start.ca sensor in your installation, add the following to your `configuration.yaml` file: To use your Start.ca {% term integration %} in your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

8
source/_integrations/statsd.markdown
View File

@ -7,11 +7,15 @@ ha_iot_class: Local Push
ha_release: 0.12 ha_release: 0.12
ha_domain: statsd ha_domain: statsd
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `statsd` integration makes it possible to transfer all state changes to an external [StatsD](https://github.com/etsy/statsd) instance. The `statsd` {% term integration %} makes it possible to transfer all state changes to an external [StatsD](https://github.com/etsy/statsd) instance.
To use the `statsd` integration in your installation, add the following to your `configuration.yaml` file: To use the `statsd` {% term integration %} in your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

8
source/_integrations/stiebel_eltron.markdown
View File

@ -11,9 +11,12 @@ ha_domain: stiebel_eltron
ha_platforms: ha_platforms:
- climate - climate
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `stiebel_eltron` integration lets you control integral ventilation or heat pump units of [STIEBEL ELTRON](https://www.stiebel-eltron.com). The `stiebel_eltron` {% term integration %} lets you control integral ventilation or heat pump units of [STIEBEL ELTRON](https://www.stiebel-eltron.com).
It requires the following components: It requires the following components:
@ -48,7 +51,8 @@ The following preset modes are supported. The STIEBEL ELTRON modes are mapped an
## Configuration ## Configuration
To enable this integration, add the following lines to your `configuration.yaml` file: To enable this integration, add the following lines to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

48
source/_integrations/sun.markdown
View File

@ -13,9 +13,12 @@ ha_config_flow: true
ha_integration_type: integration ha_integration_type: integration
ha_platforms: ha_platforms:
- sensor - sensor
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The sun integration will use the location as The sun {% term integration %} will use the location as
{% my general title="configured in your Home Assistant configuration" %} to {% my general title="configured in your Home Assistant configuration" %} to
track if the sun is above or below the horizon. The sun can be used within track if the sun is above or below the horizon. The sun can be used within
automations as automations as
@ -27,7 +30,7 @@ automations as
## Configured by default ## Configured by default
This integration is by default configured and installed, and you don't need This {% term integration %} is by default configured and installed, and you don't need
to configure it yourself, unless you've disabled or removed the to configure it yourself, unless you've disabled or removed the
[`default_config:`](/integrations/default_config/) line from your [`default_config:`](/integrations/default_config/) line from your
YAML configuration. YAML configuration.
@ -40,7 +43,8 @@ If that is the case, you can configure it as described in the next paragraphs.
Alternatively, this integration can be configured and set up manually via YAML Alternatively, this integration can be configured and set up manually via YAML
instead. To enable the sun integration in your installation, add the instead. To enable the sun integration in your installation, add the
following to your `configuration.yaml` file: following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry
@ -65,30 +69,30 @@ trigger:
offset: "-01:00:01" offset: "-01:00:01"
``` ```
| Key name | Description | | Key name | Description |
| --------- | ----------- | | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `event` | Possible values: `sunset` or `sunrise` | `event` | Possible values: `sunset` or `sunrise` |
| `offset` | An optional offset for the sun event trigger, in a positive or negative number of seconds, or specified in `HH:MM:SS` (after sun event trigger) or `-HH:MM:SS` (before sun event trigger). | `offset` | An optional offset for the sun event trigger, in a positive or negative number of seconds, or specified in `HH:MM:SS` (after sun event trigger) or `-HH:MM:SS` (before sun event trigger). |
### Maintains entity `sun.sun` ### Maintains entity `sun.sun`
| Possible state | Description | | Possible state | Description |
| --------- | ----------- | | --------------- | ---------------------------------- |
| `above_horizon` | When the sun is above the horizon. | `above_horizon` | When the sun is above the horizon. |
| `below_horizon` | When the sun is below the horizon. | `below_horizon` | When the sun is below the horizon. |
## Sensors ## Sensors
The sensors are also available as attributes on the `sun.sun` entity for backwards compatibility reasons. The sensors are also available as attributes on the `sun.sun` entity for backwards compatibility reasons.
| Sensors | Description | | Sensors | Description |
| --------- | ----------- | | ------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Next rising | Date and time of the next sun rising (in UTC). | Next rising | Date and time of the next sun rising (in UTC). |
| Next setting | Date and time of the next sun setting (in UTC). | Next setting | Date and time of the next sun setting (in UTC). |
| Next dawn | Date and time of the next dawn (in UTC). | Next dawn | Date and time of the next dawn (in UTC). |
| Next dusk | Date and time of the next dusk (in UTC). | Next dusk | Date and time of the next dusk (in UTC). |
| Next noon | Date and time of the next solar noon (in UTC). | Next noon | Date and time of the next solar noon (in UTC). |
| Next midnight | Date and time of the next solar midnight (in UTC). | Next midnight | Date and time of the next solar midnight (in UTC). |
| Elevation | Solar elevation. This is the angle between the sun and the horizon. Negative values mean the sun is below the horizon. | Elevation | Solar elevation. This is the angle between the sun and the horizon. Negative values mean the sun is below the horizon. |
| Azimuth | Solar azimuth. The angle is shown clockwise from north. | Azimuth | Solar azimuth. The angle is shown clockwise from north. |
| `rising` | True if the Sun is currently rising, after solar midnight and before solar noon. | `rising` | True if the Sun is currently rising, after solar midnight and before solar noon. |

8
source/_integrations/supervisord.markdown
View File

@ -9,9 +9,12 @@ ha_domain: supervisord
ha_platforms: ha_platforms:
- sensor - sensor
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `supervisord` platform allows you to track the states of [Supervisord](http://supervisord.org/). The `supervisord` {% term integration %} allows you to track the states of [Supervisord](http://supervisord.org/).
It required that you enable the HTTP feature in the `/etc/supervisord.conf` configuration file. It required that you enable the HTTP feature in the `/etc/supervisord.conf` configuration file.
@ -26,7 +29,8 @@ After a restart of `supervisord` you should be able to access the web interface.
<img src='/images/screenshots/supervisor.png' /> <img src='/images/screenshots/supervisor.png' />
</p> </p>
To use this sensor in your installation, add the following to your `configuration.yaml` file: To use this {% term integration %} in your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

8
source/_integrations/swiss_hydrological_data.markdown
View File

@ -11,9 +11,12 @@ ha_domain: swiss_hydrological_data
ha_platforms: ha_platforms:
- sensor - sensor
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `swiss_hydrological_data` sensor will show you details (temperature, level, and discharge) of rivers and lakes in Switzerland. The `swiss_hydrological_data` {% term integration %} will show you details (temperature, level, and discharge) of rivers and lakes in Switzerland.
## Setup ## Setup
@ -21,7 +24,8 @@ The [station overview](https://www.hydrodaten.admin.ch/en/stations-and-data.html
## Configuration ## Configuration
To enable this sensor, add the following lines to your `configuration.yaml` file: To enable this {% term integration %}, add the following lines to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

8
source/_integrations/swisscom.markdown
View File

@ -9,15 +9,19 @@ ha_iot_class: Local Polling
ha_platforms: ha_platforms:
- device_tracker - device_tracker
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `swisscom` platform offers presence detection by looking at connected devices to an [Internet-Box](https://www.swisscom.ch/en/residential/help/device/internet-router.html) router from [Swisscom](https://www.swisscom.ch) which is an Internet provider in Switzerland. The `swisscom` {% term integration %} offers presence detection by looking at connected devices to an [Internet-Box](https://www.swisscom.ch/en/residential/help/device/internet-router.html) router from [Swisscom](https://www.swisscom.ch) which is an Internet provider in Switzerland.
<div class='note'> <div class='note'>
There are three models of Internet-Box (light, standard and plus). The platform has only been tested on the Internet-Box plus but the others should work as well because they have the same web interface. There are three models of Internet-Box (light, standard and plus). The platform has only been tested on the Internet-Box plus but the others should work as well because they have the same web interface.
</div> </div>
To use an Internet-Box router in your installation, add the following to your `configuration.yaml` file: To use an Internet-Box router in your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

8
source/_integrations/synology_chat.markdown
View File

@ -9,13 +9,17 @@ ha_domain: synology_chat
ha_platforms: ha_platforms:
- notify - notify
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `synology_chat` notification platform allows you to deliver notifications to your [Synology Chat](https://www.synology.com/en-us/dsm/feature/chat) install as a Synology Chat bot. The `synology_chat` notification {% term integration %} allows you to deliver notifications to your [Synology Chat](https://www.synology.com/en-us/dsm/feature/chat) install as a Synology Chat bot.
To configure a Synology Chat bot, first you must create a [Synology Chat Integration Incoming Webhook](https://www.synology.com/en-us/knowledgebase/DSM/tutorial/Collaboration/How_to_configure_webhooks_and_slash_commands_in_Chat_Integration#t2.1). After this is complete, you will have a Webhook URL. This is what will be required in the Home Assistant configuration. To configure a Synology Chat bot, first you must create a [Synology Chat Integration Incoming Webhook](https://www.synology.com/en-us/knowledgebase/DSM/tutorial/Collaboration/How_to_configure_webhooks_and_slash_commands_in_Chat_Integration#t2.1). After this is complete, you will have a Webhook URL. This is what will be required in the Home Assistant configuration.
To enable the Synology Chat notification in your installation, add the following to your `configuration.yaml` file: To enable the Synology Chat notification in your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

8
source/_integrations/synology_srm.markdown
View File

@ -11,13 +11,17 @@ ha_domain: synology_srm
ha_platforms: ha_platforms:
- device_tracker - device_tracker
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
This platform allows you to detect presence by looking at connected devices to a [Synology SRM](https://www.synology.com/srm) router. This {% term integration %} allows you to detect presence by looking at connected devices to a [Synology SRM](https://www.synology.com/srm) router.
## Configuration ## Configuration
To use this device tracker in your installation, add the following to your `configuration.yaml` file: To use this device tracker in your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry

48
source/_integrations/syslog.markdown
View File

@ -9,11 +9,15 @@ ha_domain: syslog
ha_platforms: ha_platforms:
- notify - notify
ha_integration_type: integration ha_integration_type: integration
related:
- docs: /docs/configuration/
title: Configuration file
--- ---
The `syslog` platform allows you to deliver notifications from Home Assistant to the local syslog. The `syslog` {% term integration %} allows you to deliver notifications from Home Assistant to the local syslog.
To enable syslog notifications in your installation, add the following to your `configuration.yaml` file: To enable syslog notifications in your installation, add the following to your {% term "`configuration.yaml`" %} file.
{% include integrations/restart_ha_after_config_inclusion.md %}
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry
@ -47,26 +51,26 @@ priority:
The table contains values to use in your `configuration.yaml` file. The table contains values to use in your `configuration.yaml` file.
| facility | option | priority | | facility | option | priority |
| :-------- |:--------| :---------| | :------- | :----- | :------- |
| kernel | pid | 5 | | kernel | pid | 5 |
| user | cons | 4 | | user | cons | 4 |
| mail | ndelay | 3 | | mail | ndelay | 3 |
| daemon | nowait | 2 | | daemon | nowait | 2 |
| auth | perror | 1 | | auth | perror | 1 |
| LPR | | 0 | | LPR | | 0 |
| news | | -1 | | news | | -1 |
| uucp | | -2 | | uucp | | -2 |
| cron | | | | cron | | |
| syslog | | | | syslog | | |
| local0 | | | | local0 | | |
| local1 | | | | local1 | | |
| local2 | | | | local2 | | |
| local3 | | | | local3 | | |
| local4 | | | | local4 | | |
| local5 | | | | local5 | | |
| local6 | | | | local6 | | |
| local7 | | | | local7 | | |
For details about facility, option, and priority please consult the [wikipedia article](https://en.wikipedia.org/wiki/Syslog) and [RFC 3164](https://tools.ietf.org/html/rfc3164). For details about facility, option, and priority please consult the [wikipedia article](https://en.wikipedia.org/wiki/Syslog) and [RFC 3164](https://tools.ietf.org/html/rfc3164).