-
AuthorPosts
-
sinn3rParticipant2023-01-09 at 18:13Post count: 368
The GUI of Home Assistant is very cool, but it fails at the KNX integration, as there is no automated import workflow for devices and group addresses. Also you cannot write directly to KNX but need to use Node-RED or some other tool to connect logic from Home Assistant with KNX.
But then you can even use Node-RED alone, as Node-RED can also interface with KNX.
Overall a Homeserver 4 offers much more KNX functionality.xxxParticipant2023-01-10 at 13:40Post count: 68xxx
- This reply was modified 1 year, 3 months ago by xxx.
sinn3rParticipant2023-01-10 at 14:22Post count: 368Node-RED <> node.js
Node-RED is a graphical logic software, that has alot of plugins and also some KNX plugins. The KNX plugin communicates with the IP router/interface to exchange data with the bus, no BAOS needed.
There are alot of different projects to build own KNX connected devices, which is not hard to do at all, but these devices don’t integrate with ETS for configuration, as you need an expensive license from KNX.org for that.Sorry I have no idea about ABB fancoil modules, only regular floorheating here, which is very simple to integrate. I even skipped room contollers and only set the heating temperatures of the different rooms with Homeserver QuadClient, as you do not change this very often at all.
My air conditioning devices don’t have any KNX interfaces but WLAN and are integrated in ioBroker, which is connected to KNX with Node-RED.xxxParticipant2023-01-10 at 15:05Post count: 68xxx
- This reply was modified 1 year, 3 months ago by xxx.
sinn3rParticipant2023-01-10 at 15:25Post count: 368Hmm, not sure what you mean.
ETS is for installation only, you don’t use it later to run your KNX.
The KNX router/interface and you BAOS can transfer data from LAN to KNX using some library or with the BAOS by using simple webservices, that need no library at all.xxxParticipant2023-01-10 at 15:56Post count: 68xxx
- This reply was modified 1 year, 3 months ago by xxx.