-
Notifications
You must be signed in to change notification settings - Fork 70
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
Govee Integration Causing Blocking Call Inside Event Loop in Home Assistant #189
Comments
I have a similar issue with blocking call to load verify locations.
|
Same here 2024.12.5 |
Same here on 2025.01.1
|
Same 2025.1.2 , nd also
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
I am encountering issues with the
govee
custom integration in Home Assistant, which appears to be making a blocking call inside the event loop. This issue is causing warnings and could be leading to stability problems within my setup, potentially affecting other functionalities, such as Google Assistant integrations. The specific warning and traceback are provided below.Home Assistant Version:
Custom Integration Version:
Installation Method:
Description of Problem:
Upon reviewing the Home Assistant logs, I found multiple warnings related to the
govee
custom integration, specifically indicating that it makes a blocking call (load_verify_locations
) inside the event loop. This kind of blocking behavior could potentially affect the overall performance and stability of Home Assistant.Here is the relevant log snippet:
The log shows that the blocking operation is called at
custom_components/govee/__init__.py, line 53
. This blocking behavior can impact the Home Assistant event loop and should ideally be refactored to use an asynchronous approach.Steps to Reproduce:
Expected Behavior:
Actual Behavior:
Relevant Logs:
Additional Information:
Suggested Solution:
load_verify_locations
call to be non-blocking, or use an async-compatible approach as recommended in the Home Assistant developer documentation.The text was updated successfully, but these errors were encountered: