-
-
Notifications
You must be signed in to change notification settings - Fork 32.8k
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
Detected blocking call to open inside the event loop by integration 'jvc_projector' #119979
Comments
Hey there @SteveEasley, @msavazzi, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) jvc_projector documentation |
Thanks jgus. PR for fix was submitted. |
Not sure if this is the same issue, sharing and interested in feedback if I should open a new Issue. I am seeing the JVC integration going greyed out after using it a few times. Logs give me a warning: and I also have a long Error: Unexpected error fetching JVC Projector data Note that the Projector itself is still having proper LAN connectivity, so is the rest of the HA server. |
This looks like a new issue. Would you mind creating a new one, including the projector model you are using? |
@home-assistant close |
The problem
WARNINGs in HA logs on startup, requesting me to file a bug (see log details below)
What version of Home Assistant Core has the issue?
core-2024.6.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
jvc_projector
Link to integration documentation on our website
https://www.home-assistant.io/integrations/jvc_projector/
Diagnostics information
The integration doesn't appear to give me the option to download diagnostic data; sorry. Here's the debug log:
home-assistant_jvc_projector_2024-06-19T17-01-17.061Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: