From 8552e97929b943e7693f786ef1df81906e798c01 Mon Sep 17 00:00:00 2001 From: jduquennoy <2641687+jduquennoy@users.noreply.github.com> Date: Tue, 14 Jul 2020 21:19:32 +0200 Subject: [PATCH] Refactor Enocean part 1 (#13853) Co-authored-by: Franck Nijhof --- source/_integrations/enocean.markdown | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/source/_integrations/enocean.markdown b/source/_integrations/enocean.markdown index ae8aefc4caa..7e4303d58d3 100644 --- a/source/_integrations/enocean.markdown +++ b/source/_integrations/enocean.markdown @@ -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