-
-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
OpenTherm/config: blocking call to sleep inside the event loop #117599
Comments
Hey there @mvn23, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) opentherm_gw documentation |
Thank you for the report. Unfortunately I have not been able to reproduce the issue so far. We had a similar issue in the past (see #67430 for example) but it was supposed to be fixed with the change to |
Any hints on how can I reproduce? |
What do you mean by "direct connection with client"? If there is a successful connection from Home Assistant to the gateway then the debug logging should show all messages as well. If they don't show then there is no data being received by Home Assistant. For the reproduction, do I understand correctly that the log message shows up on a restart of Home Assistant? |
HA cannot make successful connection even once. I am testing connection on putty to make sure it's not OTGW gateway fault. I've turned on "debug" on OpenTherm integration but messages I pasted are the only ones I have in my log file Restart of OS or HA does not solve the situation, HA still can't connect to OTGW even once (so no debug messages in logfile). I guess problem is with how HA interprets "socket://" in URI to the OTGW and that's the issue, but I'm not sure on this - I just interpret the error. |
If you have the |
➜ ~ |
If it changes anything - updating to |
Error 111 means 'Connection Refused'. Since you seem to be able to connect with nc I don't see why this would happen. |
Unfortunately I do not have more debug logs, as it seems that OTGW is not even "used" in this connection. |
The problem
I have issue with OpenTherm (OTGW) integration.
It uses socket:// to connect to gateway and I see warning in logfile:
2024-05-16 15:30:33.962 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to sleep inside the event loop by integration 'config' at homeassistant/components/config/config_entries.py, line 120: await hass.config_entries.async_reload(entry_id) (offender: /usr/local/lib/python3.12/site-packages/serial/urlhandler/protocol_socket.py, line 104: time.sleep(0.3)), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+config%22
I do not see any other errors regarding OpenTherm.
Only informational that it can't connect to socket:// in UI (when I hover on the error, I see `Could not connect to gateway at socket://ip:port <Errno 111>)
It was working all releases before 2024.5.
What version of Home Assistant Core has the issue?
core-2024.5.3
What was the last working version of Home Assistant Core?
core-2024.4.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
OpenTherm Gateway
Link to integration documentation on our website
https://www.home-assistant.io/integrations/opentherm_gw/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Turning debug and reloading integration doesn't provide much info, as it seems it's issue with config/HA interpretation of 'socket://' connection?
2024-05-17 01:16:38.208 DEBUG (MainThread) [pyotgw.status] Starting reporting routine 2024-05-17 01:16:38.225 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to sleep inside the event loop by integration 'config' at homeassistant/components/config/config_entries.py, line 120: await hass.config_entries.async_reload(entry_id) (offender: /usr/local/lib/python3.12/site-packages/serial/urlhandler/protocol_socket.py, line 104: time.sleep(0.3)), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+config%22
Additional information
Could be connected with #116635
The text was updated successfully, but these errors were encountered: