VELUX KLF 200
VELUX roof windows and blinds on Control4 through the KLF 200 gateway, each one individually, with position feedback.
£ 249.00
£ 249.00
Invalid email
VELUX KLF 200
VELUX roof windows and blinds on Control4 through the KLF 200 gateway, each one individually, with position feedback.
The KLF 200 is VELUX's io-homecontrol interface. Wired through its contact inputs it gives five channels per unit. Its IP API controls every product registered in it individually and reports where each one is. This driver uses the API, and nothing is wired to the inputs.
Two drivers work together. A gateway driver, one per KLF, holds the single TLS session, logs in with the Wi-Fi password from the KLF label, scans the products and queues commands. A node driver, one per window or blind, is a standard Control4 shade with a position slider that means something, because the KLF reports real positions.
With House Status Monitor on, moves made from VELUX remotes and keypads come back to Control4 too. The KLF accepts only two connections, so other systems such as Lutron come in through the gateway's optional text command server rather than connecting to the KLF themselves.
- Every product on its own
- Each window and blind registered in the KLF becomes its own Control4 shade, with Open, Close, Stop and Set Level from the tile, Blind Groups, keypads and programming.
- A slider that is true
- Positions come from the KLF, so the slider shows where the window or blind actually is, including moves made from a VELUX remote.
- Makes its own shade devices
- Create Node Devices adds one shade per product, named after the product. Wink makes a product identify itself when the names are unclear.
- Limits for obstructed windows
- A per-product Maximum Open (%) clamps every way of moving it: slider, Open, programming, Open All and the text server.
- Never touches the wrong thing
- Garage doors, gates and door or window locks registered in the same KLF are listed but never commanded. Open All, the text server and programming cannot reach them.
- Lutron through Control4
- The text command server takes plain ASCII lines such as VELUX OPEN 3 and pushes position changes back, so a Lutron HomeWorks QSX processor can drive the products without its own connection to the KLF. It answers only addresses on its allow-list.
- Keeps the session up
- The KLF drops an idle connection after 15 minutes, so the gateway pings it on a configurable interval and reconnects after two missed pings, retrying when the KLF reports it is busy.
| Model | VELUX INTEGRA KLF 200, on the LAN by Ethernet |
|---|---|
| Manufacturer | VELUX |
| Products | Roof windows, blinds, shutters and awnings registered in the KLF |
| Protocol | VELUX KLF 200 API, specification v3.18, over TLS on TCP 51200 |
| Feedback | Live positions through the KLF's House Status Monitor |
| Control4 proxy | Blind, one node per product, with a position slider |
| Third-party control | Optional plain-text TCP command server, default port 51210, off by default and deny by default |
| Requires | Control4 OS 3.1.0 or later |
| Platform | Control4 DriverWorks, Lua |
Which password does the driver need?
The Wi-Fi password printed on the KLF label, not the web logon password. The driver moves it into Control4's encrypted storage and never writes it to the log.
Does the driver pair windows and blinds?
No. The products must already be registered in the KLF, copied from a VELUX remote or added through the KLF's own set-up page. The driver controls what the KLF knows about.
Will a window closed by the rain sensor show as closed?
Yes, but not at once. VELUX's built-in rain sensor closes the window without telling the KLF, so the closure appears at the next position poll.
Does every KLF 200 expose the API?
The driver uses the KLF's documented IP API, and some units or firmware may not expose it. The installation guide covers checking a unit before relying on it.