-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of "async_setup_platforms" #102
Comments
I opened a PR to fix the issue, however, the owner of the repo hasn’t done any changes to it since August. |
Thank you |
Thank you! I will switch to your fork as it appears you are on the ball! Krs Mark |
Hi, Could you be a bit more specific about the steps involved here - it might be obvious to you, but it's not to me:- To switch first remove the files but keep the configuration and then install from the other repo. OK, so remove what files from where ? Where is the configuration held - so that I can 'keep it' ? Do I then need to add this github as a custom repository to HACS ? Sorry for the all the questions.... |
Yes, you should add the forked repo as a custom repository on hacs. |
Much appreciated - thanks! |
Version of the custom_component
latest
Configuration
n/a
Describe the bug
After updating HA to version 2023.2 started to get the message:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:77
First occurred: 23:08:22 (1 occurrences)
Last logged: 23:08:22
Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for midea_dehumidifier_lan using this method at custom_components/midea_dehumidifier_lan/init.py, line 68: hass.config_entries.async_setup_platforms(config_entry, PLATFORMS)
Debug log
The text was updated successfully, but these errors were encountered: