VELUX roller shutter no stop command - safety issue

Configuration
1

I am using VELUX KLF 200 with Home Assistant.

I have a roof window and a shutter.

Problem:
If I trigger “close shutter” while the window is open, the shutter starts closing immediately.
This is dangerous because it can physically damage the shutter if the window is not fully closed.
This in fact already happened, the frame of the roller shutter broke.

Additionally:

  • There is no reliable “stop” command available during movement
  • Commands are queued by the VELUX gateway, so sending:
    1. close window
    2. close shutter
      results in the shutter closing first, then the window. This is the sequence to break the cover.

Expected behavior:
Home Assistant should allow safe sequencing, for example:

  • close window first
  • wait until closed
  • then close shutter

Or at least:

  • provide a built-in safeguard / option to prevent shutter closing when window is open

This is not just a convenience feature, but a safety issue that can lead to hardware damage.

Workarounds exist with automations, but they are unreliable due to command queueing and lack of stop control.

Request:

  • expose a reliable stop command if available
  • allow sequential execution (wait for state before next command)
  • or provide a built-in safety lock between related devices
2

If this is an HA core integration and not a custom integration, then feature requests go here: home-assistant · Discussions · GitHub

If it is a custom integration related directly to that device, then see the repo for that software.

If you have a sensor on the window, then an automation with a condition that the window must be closed would be the easy fix.

3

Disclaimer: I am one of the “code owners” of the Velux integration.

It is really unfortunate that your shutter was damaged while using the integration. That said, I don’t think it is the integration’s responsibility to add the safeguards you’re asking for. As far as I know (I don’t own a window/shutter combination with that issue), you can reach the same “result” (a damaged shutter) simply by using the original remote. So, in my opinion, this is a problem with the Velux hardware, not the integration.

As Sir_Goodenough mentioned, HA allows you to improve the Velux system by using the window position to prevent shutter movement when the window is open. Pyvlx (the library used in HA) recently added support for setting open/close limits for cover devices. Once this is integrated into HA, you will be able to completely prevent forbidden movements, even when using the Velux remote. However, I still don’t think such automatic limitations should be built into HA itself; rather, HA can (and does) provide ways to improve upon the original Velux hardware.

One thing you mentioned that I’d be curious to learn more about: you said you need a reliable stop command. Does this mean that issuing a stop command to the shutter does not work if the shutter is already moving? If so, please open an issue in the core repo and provide debug logs for such a situation. This is something that should work, or at least, I haven’t heard of a device where it doesn’t.