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
I think I kind of found why it gets bugged. Homekit compares the current position of your blind with the target position. When these values dont equal each other it says either opening or closing depending on the values.
When the blind is at 0%, you set it to 100% but before it reaches the 100% you set is at 50% is stops. So anytime you give the blind a command before it finishes the first command it gets out of sync. Then it for some reason messes up the current and target positions. And thus gets out of sync and says either closing or opening.
A possible solution I found is to first send a stop command, and right after that, a set position command.
The text was updated successfully, but these errors were encountered:
I think I kind of found why it gets bugged. Homekit compares the current position of your blind with the target position. When these values dont equal each other it says either opening or closing depending on the values.
When the blind is at 0%, you set it to 100% but before it reaches the 100% you set is at 50% is stops. So anytime you give the blind a command before it finishes the first command it gets out of sync. Then it for some reason messes up the current and target positions. And thus gets out of sync and says either closing or opening.
A possible solution I found is to first send a stop command, and right after that, a set position command.
The text was updated successfully, but these errors were encountered: