#45: Replace async_setup_platforms with async_forward_entry_setups #50
Conversation
This file contains 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
…y_setups The old `async_setup_platforms` will be removed with 2023.3, and according to https://developers.home-assistant.io/blog/2022/07/08/config_entry_forwards/ just replacing it with an awaited `async_forward_entry_setups` should be enough.
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.
Fixes #45 (when combined with #50) and #49. The old
async_setup_platformswill be removed with 2023.3, and according to https://developers.home-assistant.io/blog/2022/07/08/config_entry_forwards/ just replacing it with an awaitedasync_forward_entry_setupsshould be enough.Seems to work here, reconfigured my Envoy D7 in HASS after locally applying this change. I am still seeing the data come in, and no more log entries 🎉