mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-21 08:16:53 +00:00
Refactor Enocean part 1 (#13853)
Co-authored-by: Franck Nijhof <git@frenck.dev>
This commit is contained in:
parent
3e7233cff1
commit
8552e97929
@ -43,9 +43,21 @@ The available profiles are usually listed somewhere in the device manual.
|
||||
|
||||
Support for tech-in messages is not implemented.
|
||||
|
||||
## Hub
|
||||
## Configuration
|
||||
|
||||
To integrate an EnOcean controller with Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
To integrate an EnOcean controller with Home Assistant, add the integration from the UI.
|
||||
|
||||
Menu: **Configuration** -> **Integrations**.
|
||||
|
||||
If your hub is detected automatically, you will be able to select its path from a list. Most often, this list should only contain one path, and a "manual" option.
|
||||
If your hub is not detected, you will have to manually enter the path.
|
||||
|
||||
Despite the UI-based configuration of the hub, the entities are still configured using YAML see mext chapters).
|
||||
|
||||
### Text based configuration (deprecated)
|
||||
|
||||
If you have an enocean entry in your `configuration.yaml` file, the setup will be imported.
|
||||
Note that once imported in the ui-based configuration, the text-based configuration will be ignored. Changing it will have no effect, unless you delete the integration from the UI.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
Loading…
x
Reference in New Issue
Block a user