Skip to content

Comments

Don't buffer cover commands#65

Merged
seime merged 1 commit intoseime:masterfrom
ccutrer:cover-no-buffer
Jan 28, 2026
Merged

Don't buffer cover commands#65
seime merged 1 commit intoseime:masterfrom
ccutrer:cover-no-buffer

Conversation

@ccutrer
Copy link
Contributor

@ccutrer ccutrer commented Jan 28, 2026

For common UP/DOWN/STOP commands, it just makes the device seem very laggy. If your device supports position, and you're actually using a UI that continuously sends position commands as you're dragging a slider around, it should be the responsibility of the device to handle that gracefully (either by throttling them itself, or not restarting movement when the new command continues movement in the same direction). Given ESPHome is all over TCP, a high rate of commands shouldn't be a connection issue.

For common UP/DOWN/STOP commands, it just makes the device seem
very laggy. If your device supports position, and you're actually
using a UI that continuously sends position commands as you're
dragging a slider around, it should be the responsibility of the
device to handle that gracefully (either by throttling them itself,
or not restarting movement when the new command continues movement
in the same direction). Given ESPHome is all over TCP, a high
rate of commands shouldn't be a connection issue.

Signed-off-by: Cody Cutrer <cody@cutrer.us>
@ccutrer ccutrer marked this pull request as ready for review January 28, 2026 17:21
@seime seime merged commit 490a52f into seime:master Jan 28, 2026
2 checks passed
@seime
Copy link
Owner

seime commented Jan 28, 2026

Thanks @ccutrer

@ccutrer ccutrer deleted the cover-no-buffer branch January 28, 2026 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants