wollew
wollew
The linked log is rather short but it shows that your KLF200 does not react to a request within one second which is the timeout for the command sent: ```...
@home-assistant rename Velux: KLF200 does not reboot at restart
> This could be confirmed by having a look at the log from at least 30 seconds before that @pergolafabio: can you provide these? If not, I don't think I...
> the klf is working as expected As shown [here](https://github.com/home-assistant/core/issues/154294#issuecomment-3570988292), not really, at least not fully, because it doesn't react to a command sent to it within the specified timeout....
Let's try this: 1. disable all Velux reboot automations if still active 2. enable debug logging for the Velux integration 3. do "stuff" with your Velux integration (open/close a cover,...
See https://github.com/home-assistant/core/issues/154294#issuecomment-3526726869
Nice, thanks. This shows 2 things: One, your KLF 200 is still connected. Two, your KLF 200 does not react fast enough (i.e. within the 1 second timeout) to the...
This looks like the "normal" behaviour of the KLF200, which does not handle being disconnected from without also being restarted. This is why HA initiates a reboot of the KLF200...
1+2+3 all sound like this is _not_ the usual KLF200 problem, because a clean shutdown should not always lead to a working integration after HA startup, if deleting and adding...
BTW, I did a little bit of analysis and the problem seems to be that at the time the JPG file is opened to read, it still has a file...