Resync thermostat card setpoint values if service call fails #15497
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.
Proposed change
If user uses thermostat card to update a thermostat setpoint, it optimistically assumes the setpoint value actually changes. If the call service fails for some reason and the entity setpoints never update, then the thermostat card remains out of sync with the entity, showing the wrong setpoints.
This change waits 2 seconds after the call service, and if the entity has not updated its setpoints within that time, it reverts the thermostat card to showing the current entity setpoints.
This copies the same behavior as the thermostat more-info dialog, which already does this.
Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: