Authentication, events: replace component by integration (#27775)

This commit is contained in:
c0ffeeca7 2023-06-13 11:02:36 +02:00 committed by GitHub
parent 45ca65d9d9
commit 44709e5803
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions

View File

@ -197,7 +197,7 @@ For now, meta variables are only respected the first time a particular user is a
This is a legacy feature for backwards compatibility and will be dropped in a future release. You should move to one of the other auth providers.
</div>
Activating this auth provider will allow you to authenticate with the API password set in the HTTP component.
Activating this auth provider will allow you to authenticate with the API password set in the HTTP integration.
```yaml
homeassistant:

View File

@ -98,7 +98,7 @@ This event is fired when a new service has been registered within Home Assistant
| Field | Description |
| --------- | ----------------------------------------------------------------------- |
| `domain` | The domain of the component that offers this service. Example: `light`. |
| `domain` | The domain of the integration that offers this service. Example: `light`. |
| `service` | The name of the service. Example: `turn_on` |
### `service_removed`
@ -107,7 +107,7 @@ This event is fired when a service has been removed from Home Assistant.
| Field | Description |
| --------- | ----------------------------------------------------------------------- |
| `domain` | The domain of the component that offers this service. Example: `light`. |
| `domain` | The domain of the integration that offers this service. Example: `light`. |
| `service` | The name of the service. Example: `turn_on` |
### `state_changed`