Hello everybody,
I do not want to hijack this thread. But this is true I made an other version of f the free@home binding and I am using this binding since some weeks without any problem.
This binding is based on the REST API for setting values and Event Socket communication is used for status updates. This current version is complete re-design of the first my binding which I developed because I cannot make working the binding from @kjoglums on my Raspberry. (sorry… but it was maybe my fault 
)
The usage of the current version is very simple, it needs only configuration of the SysAP (gateway) the further devices and channels are detected automatically, no user interaction or any additional configuration is needed.
The automatic detection is based on the REST API available function ID and pairing ID information. Due to this the binding can adapt itself and able to detect and control new/unknown devices.
Further on the binding is not splitting the multi-channel free@home devices into multiple but single channel Things, this means a 4xChannel actuator will be kept as one multi-channel Thing. For this it is important to give a name to the channels on the free@home dashboard, because it is used for the openHAB representation.
Introduce new Input/Output (Sensor/Actuator) functionalities is very simple, it just needed to define on which channel, and which “idp/odp” are used for the communication.
I made my test based on my free@home system and based on some shared configuration file.
If somebody would like to have a binary to test, to try it, I am happily sharing my current binary build.
In case of any question, or request to implement a new feature please contact me, the best would be in private message.
and again… I did not wanted to hijack this thread.
Thank you