After lengthy research I thought I’d address the elephant in the room: The KLF 200 has been discontinued by Velux. It is very hard to get hold of one now and will be almost impossible soon. Since the thread [velux] New OpenHAB2 binding - feedback welcome! has become really, really long I thought I’d start a new one.
The situation is that my KLF 200 has died. Since I needed a solution soon I ordered a Velux Gateway (KIG 300) to be at least able to integrate my roller shutters via Apple Homekit. Unfortunately this has ended openHAB integration for me.
There is the KLF 150 which seems to be the official successor. I did not want to order one out of the blue just to find out it is not compatible with the openHAB binding. For starters, it no longer has an easily accessible LAN port. I am not sure if it has one at all, tbh. Information is scarce as Velux are not really community friendly. I read somewhere that there is one internally, but only “for use by Velux”. Also the API seems to be gone. Has anyone tried to use the KLF 150 with the openHAB Velux binding an can confirm that it works (or not)?
That leaves me with the question what you guys suggest I should do to get my Velux devices back into openHAB. Since I already own the Velux Gateway: Is there any way to control that Gateway via openHAB? There already is a Github issue to make openHAB act as HAP (HomeKit Accessory Protocol) client (not a server!) but there doesn’t seem to be a solution in the foreseeable future.
I read some things about integration via Somfy, but tbh. I could not make heads or tails of it. It seemed very complicated to me.
Aren’t these devices somfy I/O based? If so a Conexoon / TaHoma gateway should work.
Only relies on the cloud I guess. I lost track of efforts to get a developer mode for local access working.
I used to control a Somfy roof window (IO) via a TaHoma box.
(I eventually shut the TaHoma down because I control all my Somfy RTS stuff locally through an RFXTRX, and the one remaining IO device via a KLF 050.)
Adding the IO device back then was super easy and it worked really well with openHAB. I’ll probably reactivate it soon anyway, since a couple of new Velux roof windows are on the way.
Of course I’d prefer a completely cloud-free setup. If I remember correctly, the TaHoma box actually worked cloud-free in daily operation – only the admin part (adding new devices, etc.) required the cloud connection.
It’s almost off-topic, but that helped me. I just desoldered the fuse and bridged the trace. Everything works, but you need to be careful with the USB adapter.
I have the Tahoma Box in place for Velux and Somfy stuff. It works like a charm with OH for years now. Only tradeoff is the Cloud use for Updating, adding devices (Velux, Somfy, IO).
Currently I use both gateways (Connexoon and KLF200). The KLF200 does not support silent mode of roller shutters, whereas the Connexoon is very strange when it comes to item states. This is an example.
2025-11-20 17:03:05.745 [INFO ] [openhab.event.ItemCommandEvent ] - Item ‘RL_Bu_l’ received command 95
2025-11-20 17:03:05.749 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item ‘RL_Bu_l’ predicted to become 95
2025-11-20 17:03:05.753 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘RL_Bu_l’ changed from 61 to 95
2025-11-20 17:03:14.792 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘RL_Bu_l’ changed from 95 to 79
2025-11-20 17:03:20.850 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘RL_Bu_l’ changed from 79 to 95
As you can see the item state changed from 0 to 95, to 79 and back to 95 within 15 seconds. This is annoying in rules which are fired when a roller shutter reaches a certain state. Therefore I use the silent mode of Connexoon to move the roller shutters and the item state of the KLF200 to trigger rules.
As I prefer LAN for devices which are 24/7 online I’m afraid the successor KLF150 will not be an option.
