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
There appears to be bug in the Bali Motorization API where the final position updates are not transmitted and then blind missing updates becomes unreachable.
Investigate a workaround for this and make extra sure the issue isn't within the plugin code.
Reproducer: try moving a blind from 100% -> 95% and then back to 100%. Sometimes the blind actually moves to 100% but the position updates received via websocket only go to 99% leaving the blind in an "Opening..." state.
The text was updated successfully, but these errors were encountered:
It seems like at least one shade per day becomes unreachable. The Bali API is reporting its unreachable which suggests to me the issue could be my Gateway (ZWave transmitter), the blinds, or the Bali API. Nothing really suggesting there's a bug in the homebridge plugin code.
I have found that if I "poke" the blind after its reported as unreachable it typically comes back. For example, after raising all blinds, if one becomes unresponsive, I just set that one blind to 100% again.
For reference, here's the ui_broadcast received when a shade becomes unreachable.
There appears to be bug in the Bali Motorization API where the final position updates are not transmitted and then blind missing updates becomes unreachable.
Investigate a workaround for this and make extra sure the issue isn't within the plugin code.
Reproducer: try moving a blind from 100% -> 95% and then back to 100%. Sometimes the blind actually moves to 100% but the position updates received via websocket only go to 99% leaving the blind in an "Opening..." state.
The text was updated successfully, but these errors were encountered: