Make cloud switch entity _update_state function a coro
#647
Conversation
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
|
_update_state function a coro
frenck
approved these changes
Mar 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Make the
_update_statefunction of the cloud switch entities a coro.Motivation and Context
The
async_listen_updatesof the cloud client requires the function to be a coro, as the function uses theasync_create_catching_corologging helper of core, which (in some nested functions) always awaits.How has this been tested?
This appeared while beta testing home-assistant/core#111797.
I applied this change on my prod system and the log went away.
Screenshots (if appropriate):
Types of changes
Checklist