KNX Integration - my two cents so far

[jakub.jezek 370]

My setup is made from 100% MDT Hardware now at my test bench. Sometimes I use Ekinex.

 

I set-up some test lights and it works for now. With how YUBII works I see this as potential for Hybrid system and if priced correctly it would be high enough competitive.

 

I see issue with Multi-level Switch category where you can select Outdoor Blind. I would recommend to delete role Blind for Multilevel-Switch in KNX integration. You still get settings for Group Addresses for Light. Blinds have different layout for control via Group Adresses.

 

I have tried to use Energy/power meter, but we have it set to 4 byte Float which is DTP 14.056 (Watts) or DTP 13.013 (kWh). I do not know if Voltage (DTP 14.027) or Amperage (DTP 14.019) are relevant or not.

 

I pretty much work with KNX now on Daily basis as tech support in Czech republic distributor for brands MDT, Ekinex and few others and I am KNX Tutor.

 

Feature requests for KNX communication:

• KNX/IP Secure: There is EU Cyber Resilience Act that will come in the end of 2027 (December 11, 2027). This also applies for new KNX devices, and new devices from that date should have KNX Data security as mandatory and with KNX Secure devices, if Data security is enabled, you need to communicate with interfaces or routers (multicast) enabled for KNX IP Secure.
• KNX Routing: There is less over-head as you just listens or send send commands to multicast. There is no need for any handshake and keep IP communication (unicast) connection to IP interface. Also, as Fibaro would sit in different "line" (Area or Backbone) this would also filter Group Addresses on KNX site, that are not needed to get through Router as KNX/IP Routers acts as Line and Media coupler.
  • KNX proffesionals are taught how to use filter tables, so they should know how to work around it.
• YUBII/Fibaro gateway as Time server: Sending Time (with correct timezone addition) and Date (separate or combined) to KNX would be great as many visualizations have this feature.
• Write to KNX as a Block in Block scenes: It should have Group Adress, Datapoint and Value. This would be then Great tool in Easy to use Automation.

 

 

 

Home automation Features I personally find missing right now. Fore Datapoint, I would recommend to check file at 

Please login or register to see this link.

. I believe developers have this document, but just in case for those who do not know the Datapoints (DTP) for Interworking.

 

Blinds and Shutters would be welcomed feature. For those following is needed:

• Movement Up/Down (DTP 1.008 up/down): ONLY WRITE COMMAND!
  ATTENTION: In KNX specification is stated, that such Group obbjects is no allowed to read, as it could cause to blind motor to move and blind could get damaged. KNX Manufacturer has to make it Write only, so pay attention to this.
• Stop or Stop/Step (DTP 1.017 for Stop DTP 1.009 for Stop/Step)
• Height (DTP 5.001 Percent): Here it would be for both command and status
• Lamelas rotation (DTP 5.001 Percent or DTP 5.003 Angle): Here it would be for both command and status

 

Heating and Cooling control (Heat, Cool and Auto like Quick Apps) would be also welcomed feature. For those following is needed:

• Setpoint (DTP 9.001): Here it would be both command and status.
• Thermostat Mode (DTP 20.102): Here it would be both command and status. Modes are Comfort, Standby, Night/Economy, Building Protection. These modes sets pre-defined setpoint in KNX temperature regulator.
  • Alternative: AC Modes (DTP 20.105): Those modes are for ACs.
• Heat/Cool Mode (DTP 1.100): Here it would be both command and status. 
• Heating request (DTP 1.001 or DTP 5.001): Just Read. We only need to see if regulator wants to Heat or not.
  • Thermostat type in YUBII: Heating or Auto type
• Cooling request (DTP 1.001 or DTP 5.001): Just Read. We only need to see if regulator wants to Cool or not.
  • Thermostat type in YUBII: Cooling or Auto type
     
• Following Features are for Ventilation control in case of AC or Fancoils
  • Fan Auto/Man (DTP 1.001): Here it would be both command and status.
  • Fan Speed (DTP 5.005 or 5.001): Here it would be both command and status.

 

Keypad type would be really welcomed, as the most expensive cable is the one you cannot add (finished walls). This could somewhat mittigate if Z-Wave devices are added.

• Press/release (DTP 1.001): Read and Optional Write.
  • Internal timer could emulate Short/Long press and multi-clicks.
  • Could be used in scenes to control Z-Wave devices.

 

Edited March 5 by jakub.jezek

[Gonia 5]

Hello @jakub.jezek,

Thanks for the input! We appreciate you sharing these ideas. We're going to take a closer look at them.

Best Regards,
Gonia 
Fibaro Team

[m.roszak 763]

Thanks Jakub, some of the things you mention are already in plans for next release/releases.
Great and concrete feedback.

As for the options, there is one thing coming (actually came 30 minutes ago) in 5.202 which you should like, from now on its possible to send and listen to the events on the bus from the quickapp environment.
This means that till we don't have natively something right now you will be able to make custom solution for your customers and/or community.  

EDIT:

 

[jakub.jezek 370]

Hello @m.roszak, 

 

This looks great for custom project, that we do from time to time. 

[jakub.jezek 370]

Additional Update.

 

@m.roszak and @Gonia, Can you add KNX to Yubii Home with limited devices? For example 15-20? Same like with Z-Wave, Scenes and Quick Apps limitation

 

USE-CASE:

• Use Yubii Home in KNX Real Estate development projects for Up-to 2 bedroom apartments, where KNX is standard and use YUBII sensors and actuators to enhance smart home experience.

[m.roszak 763]

@jakub.jezek small Yubii (Yubii Home) won't get KNX unfortunatelly, it is available on "big" brother only due the technical limitations of the small platform. 

[jakub.jezek 370]

@m.roszak, Is it possible to have it somewhere officially mentioned, when it comes to release non-beta version? Something like "Due to technical limitation of Yubii Home / Home Center 3 Lite platform the KNX integration would not work."

[m.roszak 763]

Please login or register to see this attachment.

We mentioned that it is for "big" hubs, it will be the same for the stable release.
According to your suggestion we may add additonal note somewhere that its ONLY for those to make sure its clear 👌

[Willem-Jan 8]

I have a issue with KNX IP interface from ABB 2CDG110177R0011 (IPS/S3.1.1)
When I add this in the KNX project, I don't see an option to select an unsecure tunnel.
I can update the modules from ETS6 but I cannot connect from HC3 to the modules via the ABB Ip interface.

 

I've tested earlier with a Jung IPS300SREG which has this option and can be connected with the HC3.

 

Any idea what the problem can be?

 

Update: there was a separate function in ETS to add a tunnel in UDP with NAT and that worked.
 

Edited April 4 by Willem-Jan