Event docs and integration: add related links (#34569)

This commit is contained in:
c0ffeeca7 2024-09-04 10:43:00 +02:00 committed by GitHub
parent 78b51127dd
commit 2bcd9ecfbb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 18 additions and 11 deletions

View File

@ -1,6 +1,11 @@
--- ---
title: "Events" title: "Events"
description: "Describes all there is to know about events in Home Assistant." description: "Describes all there is to know about events in Home Assistant."
related:
- docs: /docs/automation/trigger/#event-trigger
title: Event triggers
- docs: /integrations/event/
title: Event integration
--- ---
The core of Home Assistant is the event bus. The event bus allows any integration to fire or listen for events. It is the core of everything. The core of Home Assistant is the event bus. The event bus allows any integration to fire or listen for events. It is the core of everything.
@ -28,12 +33,12 @@ In addition, all events contain a `data` dictionary with event-specific informat
This event is fired when an service action is performed This event is fired when an service action is performed
| Field | Description | | Field | Description |
| ----------------- | ------------------------------------------------------------------------------ | | ----------------- | ---------------------------------------------------------------------- |
| `domain` | Domain of the action. Example: `light`. | | `domain` | Domain of the action. Example: `light`. |
| `service` | The service action that is performed. Example: `turn_on` | | `service` | The service action that is performed. Example: `turn_on` |
| `service_data` | Dictionary with the call parameters. Example: `{ 'brightness': 120 }`. | | `service_data` | Dictionary with the call parameters. Example: `{ 'brightness': 120 }`. |
| `service_call_id` | String with a unique call id. Example: `23123-4`. | | `service_call_id` | String with a unique call id. Example: `23123-4`. |
### `component_loaded` ### `component_loaded`
@ -98,19 +103,19 @@ If you want to trigger automation on a Home Assistant stop event, we recommend u
This event is fired when a new service action has been registered within Home Assistant. This event is fired when a new service action has been registered within Home Assistant.
| Field | Description | | Field | Description |
| --------- | ----------------------------------------------------------------------- | | --------- | ------------------------------------------------------------------------ |
| `domain` | The domain of the integration that offers this action. Example: `light`. | | `domain` | The domain of the integration that offers this action. Example: `light`. |
| `service` | The name of the service action. Example: `turn_on` | | `service` | The name of the service action. Example: `turn_on` |
### `service_removed` ### `service_removed`
This event is fired when a service action has been removed from Home Assistant. This event is fired when a service action has been removed from Home Assistant.
| Field | Description | | Field | Description |
| --------- | ----------------------------------------------------------------------- | | --------- | ------------------------------------------------------------------------ |
| `domain` | The domain of the integration that offers this action. Example: `light`. | | `domain` | The domain of the integration that offers this action. Example: `light`. |
| `service` | The name of the service action. Example: `turn_on` | | `service` | The name of the service action. Example: `turn_on` |
### `state_changed` ### `state_changed`

View File

@ -10,6 +10,8 @@ ha_codeowners:
- '@home-assistant/core' - '@home-assistant/core'
ha_integration_type: entity ha_integration_type: entity
related: related:
- docs: /docs/automation/trigger/#event-trigger
title: Event triggers
- docs: /docs/configuration/customizing-devices/ - docs: /docs/configuration/customizing-devices/
title: Customizing devices title: Customizing devices
- docs: /dashboards/ - docs: /dashboards/