Update 5.201.18 - KNX integration - what does that mean actually

[Neo Andersson 230]

Hello
Anyone can give some closer info what does this changelog mean? regarding KNX?

How to integrate into fibaro for example a KNX switch? because using Eutonomy converter this was possible long time, but i dont understand what does this changelog actually mean.
Thanks in advance

Please login or register to see this image.

/monthly_2026_02/image.png.3c9972172601f4dd78ce8a5a845511a0.png" />

Edited February 3 by Neo Andersson

[Brors94 115]

Ah finaly they might support KNX iot/ip!
My guess is that  
And if I am correct then it should work with most KNX ip gateways

 

[marczu_83 29]

Please login or register to see this attachment.

[Brors94 115]

Just now, marczu_83 said:

Please login or register to see this attachment.

Nice, I am just at it and installing the update  

 

[Brors94 115]

@m.roszak Hi  Are we getting a "how to" on knx config?

I guess the grupp id example 1/1/5 (on 1bit gruppeadress) is place in the action or state tile?

Please login or register to see this attachment.

[m.roszak 763]

There will mode detailed info closer to stable release.

 

57 minutes ago, Brors94 said:

Ah finaly they might support KNX iot/ip!
My guess is that  
And if I am correct then it should work with most KNX ip gateways

 

 

Exactly.

32 minutes ago, Brors94 said:

@m.roszak Hi  Are we getting a "how to" on knx config?

I guess the grupp id example 1/1/5 (on 1bit gruppeadress) is place in the action or state tile?

Please login or register to see this attachment.

For every supported device, according to its type it is neccesary to fill the group addresses for controlling (actions) and actual state reading.

 

[Brors94 115]

3 hours ago, m.roszak said:

There will mode detailed info closer to stable release.

 

 

Exactly.

For every supported device, according to its type it is neccesary to fill the group addresses for controlling (actions) and actual state reading.

 

Okey  

Ah the state is the "feedback" group  

May I ask if thermostats will be supported?

Or maybe an api so we can send bits/bytes to a groupe? (this would be nice to make custom Quickapps)  


 

[cag014 731]

6 hours ago, m.roszak said:

For every supported device, according to its type it is neccesary to fill the group addresses for controlling (actions) and actual state reading.

 

 

Can you please recommend specific KNX IP Routers or KNX IP Interfaces that are confirmed to work reliably with the HC3?

I’d like to avoid a ‘buy‑and‑try’ experience similar to what happens with some Zigbee devices.

A list of officially tested or validated KNX IP interfaces would be extremely helpful.

Edited February 3 by cag014

[m.roszak 763]

11 hours ago, Brors94 said:

Okey  

Ah the state is the "feedback" group  

May I ask if thermostats will be supported?

Or maybe an api so we can send bits/bytes to a groupe? (this would be nice to make custom Quickapps)  


 

 

Feature for custom handling events from the bus and sending those in QuickApps is something already done, to be released on 5.202

Thermostats are also on its way but those are tricky and this will take some time to finish.

[m.roszak 763]

On 2/3/2026 at 8:53 PM, cag014 said:

Can you please recommend specific KNX IP Routers or KNX IP Interfaces that are confirmed to work reliably with the HC3?

There is no specific one, its - in general, super simple device.
If it works according to KNX community it will work with us

[jakub.jezek 370]

@m.roszak, I think @cag014 probably ment if we could use KNX Multicast IP or should we use Unicast IP.

 

I attempted for some sort of KNX integration and I was using UDP Multicast address in KNX just fine in the Quick App.

 

Edid: Unicast IP I mean IP adress of the KNX/IP Router/Interface via KNX Tunneling protocol and Multicast IP via KNX Routing protocol is default IP I think 224.0.23.12.

 

Edid 2: ROuting Protocl is great as you do not need confirmation. Via Tunneling you need confirmation.

Edited February 12 by jakub.jezek

[jakub.jezek 370]

Just tested it out and I cannot use Routing, pity.

[m.roszak 763]

Not now, we are evaluating this internally

[jakub.jezek 370]

Thanks @m.roszak,

 

I think Routing is better because it just listens on Multicast and KNX installers/dealers can choose what goes to area/backbone, so you do not need to hear everything on the bus.

 

Also in case of Routing, if you decide to add it, please, add field for device physical address, so in ETS we can see what command came from Yubii/Fibaro gateway.

[tinman 1,070]

let me guess loud - iptables not configured properly for xknx multicast @m.roszak

[cag014 731]

So anyone can recommend specific KNX IP Routers or KNX IP Interfaces that are confirmed to work reliably with the HC3?

[jakub.jezek 370]

9 hours ago, cag014 said:

So anyone can recommend specific KNX IP Routers or KNX IP Interfaces that are confirmed to work reliably with the HC3?

Any KNX IP Router/Interface that is KNX certified, meaning having KNX logo on the device itself, should work. We are using brands MDT and Ekinex.

 

Also, if you have KNX/IP Router on your site, you can also use Shelly KNX integration.