# HA Integration notes

## Points of attention

This section is here to note what we learn from the feedbacks we receive from the core team.

- We have to find a way to split the changes in small, incremental PRs.
- We have to use async every time IOs are done
- All the code we write will have to be covered by unit tests

## Steps
(to be discussed)

A huge work has been done recently on the rfxtrx component. This component was also based on a yaml config, and is now configured through the UI.
The work done on this component can certainly inspire us.

1. Update to a new format of YAML configuration, similar to what was done in the rfxtrx component (see link bellow)
2. Setup the architecture to support a first device, with only one entity (to be decided, I would suggest a fairly simple one, such as a door sensor (A5-30-02), or a plug (D2-01-01) )
4. Add support for event-based devices (switches)
3. Add support for one more class of device, with multiple entities

## Links

### PRs
- https://github.com/home-assistant/core/pull/37742 A PR on RFXTRX that migrates the yaml-based config to a new format. This PR was a first step to update the RFXTRX component.
- https://github.com/home-assistant/core/pull/39117 A PR containing links to a serie of PRs done on the RFXTRX integration to add UI-based configuration. Could probably be a source of inspiration for what we will do on the ENOcean integration
- https://github.com/home-assistant/core/pull/35927 A first PR on ENOcean, adding ui-based configuration for the integration