Update 23.01.2022
– Changed structure of the post, so that the experiences are all documented in the Summary without judging, if a point is a pro or con and deleted not necessary questions.
– Added experiences with KLF200, because I got one too.
From my gathered experiences I have still one question: Is it possible to get an update of the current postion of the cover lets say every second while the cover is moving?
Update 17.01.2022
– Added new experiences in regards to the State update time for KIG300
Summary
Dear all,
I’m currently thinking which Gateway from Velux I should finally use. I gathered some information for the two devices below. I have solar covers with the remote control 3LID13WW, Model: BG-RC011-01.
KLF200
Functionality
– Provides the “cover.stop_cover” functionality
– Uses pyvlx, which is still very good maintained
– No updates from the manufacturer anymore
State update time
– State is not updated => Home Assistant shows always open
Current position update
– Update of the current possition is only done at the end of moving
Connection
– Needs wired LAN connection
Costs
– Costs € 50 more (~€ 150)
Robustness
– ???
KIG300
Functionality
– Gateway is still maintained by Velux
– Doesn’t provide the “cover.stop_cover” functionality
State update time
– If the cover is set to a position (e.g. 75) the state change happens immediately.
– More then 5s-10s from e.g. “open” to “closing” if you move manually via remote control
– No change if the manual closing command is given too short (below 5s-10s) if you move manually via remote control
Current position update
– If you try to get the position via a triggered state node (e.g. every second) in Node-Red while the cover is moving , you will not get the current position every time. Here you also only get a new position after 5s-10s of moving cover.
Connection
– Can be connected and cotrolled via WLAN
Costs
– Cost € 50 less (~€ 100)
Robustness
– Tests for about on week with timely scheduled mvong onece per day to different position were done without errors