Conversation
The coordinator's async_request_refresh still fires so the poll confirms real state, but the UI now flips instantly rather than waiting on a Crestron response round-trip. Selecting a source also flips power to ON since that's what the device does. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
After turn_on / turn_off / set_volume / select_source, push the expected new state straight into the coordinator's data so the UI flips immediately instead of waiting on the next poll.
async_request_refresh()still fires so the poll confirms actual state — if the command didn't take, the UI self-corrects on the next update.turn_on→power: …ONturn_off→power: …OFFset_volume_level(x)→volume: round(x*100)select_source(s)→source: <code>andpower: …ON(selecting a source turns the zone on)volume_up/volume_down— left as plain refresh, since we don't know the target valuemute— already optimistic via_mutedTest plan
coordinator.dataand reflects in the entity'sstate/volume_level/sourceimmediately🤖 Generated with Claude Code