Hi all,
I’ve been looking into different ways of connecting existing Home Assistant entities to KNX.
I noticed that the KNX integration already provides entity exposure functionality, and for more advanced use cases there are community blueprints that allow KNX to control entities such as lights. The existing solutions work well and clearly demonstrate the demand for this kind of integration.
This made me wonder whether there would be interest in a more native approach within the KNX integration itself.
The idea would be to bind existing Home Assistant entities (e.g. lights, covers/shutters, fans, …) to KNX group addresses and handle bidirectional communication directly from integration code instead of automations.
Potential benefits could be:
- Less reliance on complex automations
- Easier maintenance when Home Assistant internals evolve
- Better testability through unit tests
- Reuse of existing KNX integration infrastructure
Before investing time in a prototype, I’d like to understand whether this has been discussed before and whether there are architectural reasons why this functionality is currently implemented through expose and/or blueprints instead.
I’d be interested to hear the thoughts of the KNX maintainers and others who have experience with the existing solutions.
Thanks!
!