Ok, thats weird ?
The actuator have the same function like the older one.
That means the new functionID “1821”, should be the same like the old “61”.
Also all 4 channels should be the same.
The best description is therefore “blind actuator”.
Thx for your work !
Below you will find the new binding with the updated list of FIDs. The new 0x182x FIDs are handled correctly.
Could you make a test with this version?
Hello everyone.
I’m currently migrating a large installation to the API version. Most of it is going very well. Thank you for that.
In the “old” version, I used the free@home groups. These were found during the scan, but they don’t have any channels. Therefore, I can no longer use them in rules.
Does anyone have any ideas on how I could proceed?
Thank you very much.
Hi all,
I am now using the binding for around six months and it is working well. However, when starting openhab, I still get a warning message for each and every item:
2026-06-07 23:03:50.992 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for new thing during update 'freeathome:device:sysap:<ID>': {thing/channel=Config description channel-type:freeathome:config for freeathome:device:sysap:<ID>:ch0000#brightness-alarm not found, although we checked the presence before.}
2026-06-07 23:03:50.993 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.993 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.994 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.994 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.994 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.994 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.994 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.995 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.995 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.995 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.995 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.995 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.995 [WARN ] [ation.ConfigDescriptionValidatorImpl] - No config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.996 [WARN ] [ation.ConfigDescriptionValidatorImpl] - Skipping config description validation because no config description found for URI 'channel-type:freeathome:config'
2026-06-07 23:03:50.996 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for new thing during update 'freeathome:device:sysap:<ID>': {thing/channel=Config description channel-type:freeathome:config for freeathome:device:sysap:<ID>:ch0000#brightness-alarm not found, although we checked the presence before.}
The warning message itself is not a problem but it slows down the start. Does anyone see the same messages? It seems to be connected with the dynamic channel discovery but I don’t get that with other bindings. @UhA gave me that hint, but I was not able to fix it.
Thanks for your experience and view…
Best, Lui
Two loose ends from this thread:
@LuiSauberhorn the startup warnings you posted come from the binding, not from your configuration: the channel types only exist after the SysAP has answered, and the types carry a config description URI that nothing registers. I have opened openhab-addons#21558 for it, the PR is #21559 - with the fix the boot is warning-free from the second start on (tested on a production system with 22 devices). Testing is welcome, there is a test build for 5.2.x.
And on the missing blind actuator channels from last October (openhab-addons#19468): the fix exists in Andras’ fork release fh-5.0.x-1.0.1, but it never went upstream - current main still only knows 0x1821. Noting it here so it does not stay orphaned.