You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have two problems with version 1.4. At the moment I switched back to version 1.3.
The covers can't be stopped while they are moving. They move all the way down and don't respond to the stop button.
By activating a scene with several covers all covers move one by one. The first cover moves and when that one is finished the next cover moves. Until version 1.3 all covers moves all together.
To Reproduce
Steps to reproduce the behavior:
Move a cover and click the stop button - the cover do not respond to that click
or
Create a scene with several covers.
Activate the scene
Expected behavior
The cover stops by clicking the stop button while moving
All covers should move together (and not one by one)
Screenshots
No screenshot
Environment (please complete the following information):
Home Assistant version: 0.111.4
Platform: cover
Device: (if your problem is related to a specific device)
Model: PositionableRollerShutter
Type: io:RollerShutterGenericIOComponent
Device details
no further details
Additional context
No additional context necessary
The text was updated successfully, but these errors were encountered:
thank you for your report. we'll have a look rapidly. @iMicknl regarding the second issue, I think this is related to the addition of the wait to the apply_action. could an async function allow to keep the wait while sending several commands without waiting for the previous ones to finish?
Describe the bug
I have two problems with version 1.4. At the moment I switched back to version 1.3.
To Reproduce
Steps to reproduce the behavior:
or
Expected behavior
Screenshots
No screenshot
Environment (please complete the following information):
Device: (if your problem is related to a specific device)
no further details
Additional context
No additional context necessary
The text was updated successfully, but these errors were encountered: