"Unable to send command" debug about pyvlx HOT 10 CLOSED

To clarify some details on this, this is with Home Assistant 2023.8.4. I'm pretty sure I didn't used to see this, so guessing it's an upgrade change at some point, but not sure exactly when as I was doing auto-upgrades for a while. Generally, this only happens when I'm running a scene (i.e. a bunch of velux changes in one go), although I was able to reproduce this earlier when just clicking a whole set of windows at once, so guessing it's probably to do with the gap between commands?

from pyvlx.

I had the same issue in Home Assistant 2023.8.1 and I had to revert to 2023.7.3 which is the last working version.

I tried every new HA version since but they all have the same behavior.

from pyvlx.

I have a very hacky workaround with time.sleep filed in Core (home-assistant/core#100523) and we'll see where that gets to...

from pyvlx.

I mainly see this issue when activating a scene that closes all my velux window covers. It seems that the library or klf200 is overwhelmed by the requests?
When playing around with only one window cover, it works as expected. When activating the scene mentioned before, not all window covers are closing/opening - and the ones not moving are always the same.
I was using an automation for opening and closing, which isn't working currently. Maybe I have to work around that like @palfrey and change the automation to issue only one command at a time.

from pyvlx.

See also pawlizio/my_velux#27 and home-assistant/core#98168 (comment)

from pyvlx.

I mainly see this issue when activating a scene that closes all my velux window covers. It seems that the library or klf200 is overwhelmed by the requests? When playing around with only one window cover, it works as expected. When activating the scene mentioned before, not all window covers are closing/opening - and the ones not moving are always the same. I was using an automation for opening and closing, which isn't working currently. Maybe I have to work around that like @palfrey and change the automation to issue only one command at a time.

for me they are always different. If I run my close or open scene again in HA they eventually get to the right state.

from pyvlx.

@Julius2342 Any thoughts on a PR to add the option for minimum delays between calls to KLF 200 devices? Like home-assistant/core#100523, but folded into the library and redone to only add delays on subsequent rapid calls, not all of them.

from pyvlx.

I implemented a semaphore to avoid parallel commands as the HA solution seems not work... Here the corresponding commit:

pawlizio@7032496

from pyvlx.

Hmm, probably a semaphore. I would have done it quite highlevel, e.g. in ApiEvent/do_api_call . What do you think?

from pyvlx.

Hmm, probably a semaphore. I would have done it quite highlevel, e.g. in ApiEvent/do_api_call . What do you think?

That seems sensible to me. #353 does this, and also solves the "why doesn't this first call respond?" issue I was seeing before in HA by making sure we're connected before entering the Semaphore section.

from pyvlx.