Open shanemcw opened 1 month ago
On further thought, it looks like from the logs the targetPosition is being sent one at a time in fine detail instead of just the end state. I.e. "set to 1% and stop there" "OK now set to open to 2% and stop there," "OK now set to 3% and stop there" and so forth, instead of "set to 100% and stop there" once?
4.4.15 behavior:
[5/29/2024, 12:12:41 PM] [Broadlink RM pro] Study South Blinds setTargetPosition: (currentPosition: 100)
[5/29/2024, 12:12:41 PM] [Broadlink RM pro] Study South Blinds setTargetPosition: currently 100%, moving to 50%
[5/29/2024, 12:12:41 PM] [Broadlink RM pro] Study South Blinds setTargetPosition: 14.499999999999998s (29 / 100 * 50) until auto-stop
[5/29/2024, 12:12:55 PM] [Broadlink RM pro] Study South Blinds setTargetPosition: (stop window covering)
[5/29/2024, 12:13:28 PM] [Broadlink RM pro] Study South Blinds setTargetPosition: (currentPosition: 50)
On further thought, this new behavior may animate the blinds while moving in the Home app. The request in this ticket is to suppress the logging of the incremental current state updates while in transition from the initial to the target state.
Describe the bug Overreporting is status (blinds/shades) in 4.4.16-beta.0
To Reproduce Steps to reproduce the behavior:
Expected behavior Less detailed status reporting as in 4.4.15. In 4.4.15, every increment of the blind position is not reported as shown.
Screenshots