Thank you, do you have control over LAN or you need to have internet access to control them via the KIG/Homekit integration?
My understanding is that HomeKit is entirely local. I haven’t tried disabling the KIG from seeing the internet, but I can tell you that once I got it paired to HA (no Apple products in sight, although I did have to do a bit of a reset dance to get it to pair properly) I’ve completely ignored the Velux app.
I have now had both, KFL200 and KIG300.
For the setup (pairing/copying of the devices) of the KIG300 I have granted internet-access to the KIG300. I have blocked the access to the internet, and it still works well.
Ahhhhhh Velux! The company that doesn’t want to share control or provide a professional controller… this is also worth a mention a is a simple ESP32 conversion to get a possibly better HA integration and function… for shutter position, time how long your blind takes to open in % or cm then use that to roughly equate the shutter position. Same for the window opening…I doubt anyone want to open their Velux to fully open as its very wide!
Somebody with a 3D printer and some basic electronics knowledge could fabricate a new back plate with spring contacts in the right place to avoid soldering directly on to the CLI original switch…
Nice ! Thank you so much !
Very nice to see that it uses a remote so if anything goes sidesways, it’s not too expensive to fix the mistake. You know what, I think you might have provided the little push I need to try a first soldering project with esphome 
Hi together,
I have the KIG 300 in use with Velux DFF (roof windows) and try to implement some functionalities for my blinds. I have the Homekit integration in use.
Side note: I also have Bosch Smart Home with other windows where this works perfect and once a new target is defined for the blind I get immediately an event with the new target value.
But with Velux I get in NodeRed only an event with the old position before the new command (not the target value). The intended target value I only get once the target position has been reached which is really anoying. I compared with the velux app itself and there I see it changes right away and it shows immediately the target position.
And in rare sporadic cases I see even a random value in between current position and target position.
This is really bad, as I can trust only the “open” and “closed” related values, but not “opening” or “closing”.
Not possible e.g., to catch the closing even with opened window where otherwise I could easily block the blind going down, before hitting the open window.
Does anybody has an idea what I could do? Do you have the same trouble?!
Many many thanks!!!
I’ve been working on a custom HA integration for VELUX ACTIVE / VELUX App Control (KIG 300 / KIX 300): ha-velux-active
It talks to the VELUX/Netatmo cloud API directly, so no HomeKit bridge workaround is needed. Right now it supports the NXG gateway and NXO cover devices I have in my setup.
If anyone wants to try it on a similar setup, feedback is welcome.
Interesting , if my klf dies someday, then I switch to yours 
Not good to bring in a cloud dependency to an HA ecosystem where we are trying to ensure everything is local control 
Not true, lots of integrations are cloud based by reverse engineering.. eliminating extra hardware is the way to go!!