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.

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.

It seems like the issue is in the name/diacritics, in my case character ě.

Device itself its added, but it then instantly looses any configuration I put in.

Error:

[12.02.2026] [14:21:29] [WARNING] [KNX]: [ZmqServer] Error while handling message[12.02.2026] [14:21:29]

[WARNING] [KNX]: [] Traceback (most recent call last): File "src/rpc/zmq_server.py", line 74, in handle_message_ File "src/device_management/device_service.py", line 89, in handle_action File "src/device_management/device_service.py", line 94, in call_action File "src/device_management/devices/device.py", line 48, in action File "src/device_management/devices/knx_engine.py", line 71, in action_ File "src/device_management/devices/knx_engine.py", line 125, in create_device File "src/device_management/device_service.py", line 32, in create_device File "src/device_management/device_factory.py", line 58, in create_device File "/usr/lib/python3.13/json/__init__.py", line 346, in loads File "/usr/lib/python3.13/json/decoder.py", line 345, in decode File "/usr/lib/python3.13/json/decoder.py", line 361, in raw_decode json.decoder.JSONDecodeError: Invalid control character at: line 1 column 264 (char 263)[12.02.2026]

First connection with the HC3 (v 5.201.18 (beta)) went smooth.

When I unplugged the setup for a few days and reconnected the setup with the network, the HC3 was not able to connect to the KNX IP interface. 

The IP adres of both HC3 and KNX ip interface are the same.
I've tried some things but at the end, I had to remove and reconfigure it to get it working. 

This caused the removal of all devices.

Any idea why this happens?

Any news on weather conditions?

From what I can see it is still mixed up. Is there a chance when this is finalized that you give us a list of available weather conditions and weather condition codes?

Thank you!

Few updates back this get broken and is still broken. Quick apps of remoteController type still allow users to add custom icons and select, but when custom icon is selected then this is how it looks like:

Please login or register to see this image.

I know this is just another minor bug, but also another annoying one. 

By mistake I used function: self:updateProperty("deviceIcon",icon) on some of my Quick apps of colorController type and now they do not show icon in Yubii app:

Please login or register to see this attachment.

Since this type of devices does not have custom icons, setting custom icon should not be possible to do by the users. Can your team add some checks not to allow this to happen in next firmware update.

Now I need to find the way how to correct this on my devices. Any suggestions?

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.

There is still problem with weather providers on every browser that I try on macOS and Windows 11 including MS Edge, Firefox, Chrome and Safari. After logging in to my HC3 locally then weather provider shows proper wind speed unit:

Please login or register to see this image.

After refreshing home page in any browser then it looks like this:

This is same for all weather providers including YR weather and that very basic example provided by Fibaro.

Since there are still some problems with refreshing page in all browsers in some cases that only using browser refresh page can solve, this above is annoying.

BTW - logging out and then logging in solves this until the next page refresh.

-Wave Engine 3.0
    Some Z-Wave devices are not fully compatible with the new version of Z-Wave engine.
    Gateway connection is not available in the new Z-Wave engine version.

Please login or register to see this attachment.

Please login or register to see this code.

the above call doesn't seem to work. (maybe it was not working at all even before the update??)
I have tested it on Fibaro device that has an update available, but it doesn't do anything..

Maybe it needs some other paramater (updateVersion) or something else??

Main features:

KNX integration

From now on, your KNX system can work even smarter thanks to integration with our Yubii Home Pro and Home Center 3 hubs. Gain full control over lighting, switches, RGBW controllers, and sensors within one unified ecosystem.

What's new:

Devices

    Improved display of device families on the device list so that child devices are always located under their parent device.

Elero

    Integration with ELERO Lighting Receivers: TTDTW-E (Combio-868 LI W), TTDRGBW-E (Combio-868 LI RGBW),  TTDW-E (Combio-868 LI PW).

Gateway connection

    When the Slave hub is turned off or there is no connection, the devices added to it are visible as inactive (dead) in the Master hub.

Nice*

    Upgraded NICE chip firmware version to the newest one.

Other

    Added the information about the zone where the alarm occurred.
 

Scenes

    Added a new scene activation/deactivation block as an action in block scenes.
    Added possibility to enable/disable local and remote device protection via scenes and profiles.
  

Z-Wave

    Adjusted parameters templates for sensors to reduce number of reports for various devices.
    Fixed setting of parameter 5 for the MCO Home MH7H-EH device.
    Improved clearing Z-Wave network reset procedure.

Bug Fixes:

Backups

    Fixed an issue where the “Update and restore” buttons for backups with higher software versions were inactive.

Climate

    Fixed an issue where the schedule was not cleared from the Heat-Control/Fibaro Heat Controller when it was removed from the climate zone.

Devices

    Fixed an issue where the Color component view was not updating correctly.
    Fixed an issue with changing icon for Dahua cameras.
    Improved performance for the DoubleDimmer-Control binding Wizard.

Nice*

    Fixed setting favorite position for the screen devices which does not support this natively.

Other

    Removed a non-functional option (checkbox) for sending notifications on the list of mobile devices.
    Fixed visibility of device name when adding Z-wave devices in the mobile application.
    Fixed tooltips positioning in the interface.
    Fixed the message screen displayed after using the factory reset option in Recovery mode.
    Minor UI/UX fixes.

Quick Apps

    Allowed additional parameters to hub.alert function in QuickApp to keep backward compatibility with old code.
    Variable edit box character limit has been increased from 1024 to 2048.

Scenes

    Fixed an issue that icons other than the default ones are not displayed when selecting profiles in scenarios.

Z-Wave

    Fixed redundant stopping of Z-Wave3 engine.**

Known issues:

Z-Wave Engine 3.0

    Some Z-Wave devices are not fully compatible with the new version of Z-Wave engine.

* - Does not apply to HC3L (Home Center 3 Lite).
** - Applies only to Z-Wave 3.0 engine.

Security:

    Angular vulnerabilities update.
    Updated Rust toolchain version.