Update 5.202 BETA Latest Topics

FIBARO System Update 5.202.54 Hotfix for Yubii Home

Wed, 11 Mar 2026 11:35:08 +0000

Thank you for using our gateway! Be sure to update to the latest version to enjoy new features and improvements.

Important notice:

Version 5.202.54 is a hotfix for version 5.202.51.

The update resolves:

Fixed problem of the system hanging on Starting Services in rare cases when Thermostat Linked Device is used.
Fixed problem that migration may fail when device model does not contain information about security level when devices were added in legacy versions.

Main features:

Migration of Z-Wave engine from 2.0 to 3.0 version (BETA)

In this version of the software, it is possible to migrate the Z-Wave engine to version 3.0. Migration will allow you to take advantage of all the features of the new Z-Wave engine, including using Smart Start, better generic support for Z-Wave Plus devices and the availability of Security S2, which can be considered the first fully secure communication method for the Smart Home.

Smart Start

From now on, you can use the Smart Start function using QR Scanner in Yubii App. This function will allow you to add devices to the system even faster using binding process.***

What's new:

Devices

Added thermostatOperatingState interface for Linked thermostats.
Added direct access to KNX communication (both sending and recieving packets) from the API.

Gateway connection

Enabling Support Access and Remote Access on the Master hub also enables access on slave hubs.

Nice*

Added the option to disable the sun impact (setting the value to 0 lux in parameter 10) for the Domi WSC device v3.9.0.
The default values of parameters 1, 3, and 10 have been changed for all versions of DOMI WSC devices.

Other

Verification of the checksum when downloading the update file at the beginning of the process instead of at the end.

Bug Fixes:

Climate

Fixed an issue where an added temperature sensor was removed from the climate panel when editing other settings in that panel.
Fixes an error occurs after deleting a device in the climate schedule.

Devices

Fixed a problem with KNX device configuration caused by the lack of support for diacritical marks in device names.
Fixed an issue with function settings for Z-Wave devices with an empty template during the binding process in the mobile application.
Fixed incorrect KNX Bridge connection status after IP change.
Restored missing temperature graphs on FGT device version 4.10.
Fixed the appearance of the dialog in the user interface for BiDi-Awning and AV Controller.

Elero

Fixed color component values for the Elero Lighting RGBW device.
Fixed the appearance and behavior of the Elero Lighting RGBW device icon in the user interface.
Fixed invalid settings for temperature color in profiles for the Elero Lighting RGBW device.

Gateway connection

Fixed errors and incorrect display of options in association settings.
Fixed IP address validation in the Gateway Connection tab.

Nice*

Fixed keep-alive support for Domi WSR/WS device, which caused the device to be shown as disconnected in the system.

Other

Fixed handling of events from the NICE camera plugin when devices are added via NVR.
Fixed icons for Sonos and XBMC plugins.
Fixed errors displayed in the Z-wave tab of the Master hub when using the interface via Remote Access.
Fixed the input validator for variables.
Fixed non-functioning group actions in profiles.

Quick Apps

Added support for climate zone control functions in QuickApps.
Fixed restarting the Quick App process when editing it.
Fixed Heat Activator which stopped working in rare cases.
Fixed an issue with saving the Quick Apps view to a file when encrypting (applies to QA exported from version 5.191 or later).

Scenes

Fixed refreshing of the scene activity switch in the interface when calling activation/deactivation action from the scene level.
Fixed inactive color temperature slider for device Elero Lighting TW in scenarios created in the mobile app.

Known issues:

Z-Wave Engine 2.0 to 3.0 migation

Device updates from both the server and the file are not working, reconfiguration of the device resolves the issue.

* - Does not apply to HC3L (Home Center 3 Lite).
** - Applies only to Z-Wave 3.0 engine.
*** - Fully supported in the upcoming Yubii v2.5.3 application

FIBARO System Update 5.202 Beta for Yubii Home

Wed, 04 Mar 2026 12:00:33 +0000

Thank you for using our gateway! Be sure to update to the latest version to enjoy new features and improvements.

Main features:

Migration of Z-Wave engine from 2.0 to 3.0 version (BETA)

Smart Start

From now on, you can use the Smart Start function using QR Scanner in Yubii App. This function will allow you to add devices to the system even faster using binding process.***

What's new:

Devices

Added thermostatOperatingState interface for Linked thermostats.
Added direct access to KNX communication (both sending and recieving packets) from the API.

Gateway connection

Enabling Support Access and Remote Access on the Master hub also enables access on slave hubs.

Nice*

Other

Verification of the checksum when downloading the update file at the beginning of the process instead of at the end.

Bug Fixes:

Climate

Fixed an issue where an added temperature sensor was removed from the climate panel when editing other settings in that panel.
Fixes an error occurs after deleting a device in the climate schedule.

Devices

Elero

Gateway connection

Fixed errors and incorrect display of options in association settings.
Fixed IP address validation in the Gateway Connection tab.

Nice*

Fixed keep-alive support for Domi WSR/WS device, which caused the device to be shown as disconnected in the system.

Other

Quick Apps

Scenes

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.
*** - Fully supported in the upcoming Yubii v2.5.3 application

KNX Custom Commands

Wed, 04 Mar 2026 11:59:15 +0000

To extend the functionality of KNX integration, we added the ability to send custom commands to KNX network, and to register your own listener to handle reports from the devices. This allows you to control devices that may not be fully supported by the default KNX integration, or to implement specific behaviors that are unique to your setup. The easiest way to handle this is to do it with a QuickApp. Be aware that this functionality is at a testing stage. It may not be fully stable yet, and also the API may change in the future.

Sending Custom Commands

You can send custom commands to the KNX network by calling the sendCommand action on the KNX integration device (ID 9). This action takes three parameters:

The group address to which you want to send the command (e.g. "0/2/0").
DPT of the value you want to send (e.g. "5.001" for DPT_Scaling).
The value you want to send. The encoding depends on the DPT you are using.

A few simple examples of how to send different DPTs:

-- DPT 1.001 (DPT_Switch):

function QuickApp:turnOn()

hub.call(9, "sendCommand", "0/2/0", "\"1.001\"", true)

self:debug("binary switch turned on")

self:updateProperty("value", true)

end

function QuickApp:turnOff()

hub.call(9, "sendCommand", "0/2/0", "\"1.001\"", false)

self:debug("binary switch turned off")

self:updateProperty("value", false)

end

-- DPT 5.001 (DPT_Scaling):

-- Representation of open/close mapping to percentage may differ based on the device you're integrating.

function QuickApp:open()

hub.call(9, "sendCommand", "0/2/0", "\"5.001\"", 0)

self:debug("roller shutter opened")

self:updateProperty("value", 99)

end

function QuickApp:close()

hub.call(9, "sendCommand", "0/2/0", "\"5.001\"", 100)

self:debug("roller shutter closed")

self:updateProperty("value", 0)

end

-- 232.600 (Colour_RGB)

function QuickApp:setPresetColor()

local r = 0

local g = 74

local b = 147

local payload = {r, g, b}

hub.call(9, "sendCommand", "2/0/16", "232.600", payload)

self:updateProperty("colorComponents", {red=r, green=g, blue=b})

end

Since we're using device actions to send KNX commands, you can send them in whatever way you want. You can use QuickApps, but you can also use scenes, or direct REST API calls (POST /api/devices/9/action/sendCommand).

Listener registration

By registering a listener, you can receive updates from the group address and handle them in your QuickApp. This is useful for monitoring device states or reacting to specific events. For now there is no way to register to a specific group address, so you will receive all updates from the KNX network. You can then filter them in your code to react only to the relevant ones.

A callback can be registered by calling the registerListener action on the KNX integration device (ID 9). This action takes one argument:

The callback URL (an action in your QuickApp) that will be called when there is an update from the KNX network. The URL should be in the format /api/devices//action/{callback name} e.g. /api/devices/123/action/myCallback.

The provided callback will be called with the group address and the value of the update whenever there is an update from the KNX network. Here is an example of how to handle this in a QuickApp:

function QuickApp:onInit()

-- Register a listener for KNX updates.

-- ID 9 is a device that represents the KNX integration. Don't change it.

-- "registerListener" is the action to register a listener. Don't change it.

-- 3rd parameter is the callback URL (an action), that will be called when there is an update from the KNX network. You can choose any action you want, just make sure to handle it in your QuickApp. In

this example we will call "myCallback" action.

local callbackURL= "/api/devices/" .. tostring(self.id) .. "/action/myCallback"

self:debug("Register KNX callback:", callbackURL)

hub.call(9, "registerListener", callbackURL)

self:debug("KNX QA started")

end

-- Callback function to handle KNX updates. The address and value parameters will contain the group address and the value of the update.

function QuickApp:myCallback(address, value)

self:debug("address:", address, "value:", json.encode(value))

end

Debugging

You can change the log level of the KNX integration to "debug" or "trace" in order to see more information about the KNX communication itself and about the communication exchanged between the KNX integration and your QuickApp. To do so, just go to the KNX settings in the web interface, and change the system log level in the network communication section.