[Errno 113] No route to host hangs in Home Assistant #2393
-
I use ModbusTcpClient in my Home Assistant Integration https://github.com/OStrama/weishaupt_modbus Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht Logger: pymodbus.logging Connection to (192.168.42.144, 502) failed: timed out and Logger: homeassistant Error doing job: Task exception was never retrieved (None) What I do in my code, is simply reading and writing single values in this class: https://github.com/OStrama/weishaupt_modbus/blob/main/custom_components/weishaupt_modbus/modbusobject.py What do I do wrong? How can I avoid blocking? Thanks in advance for your help! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
As you can see the shelly integration also have a problem, indicating this is a hass problem Anyhow why report it here, this is not the homeassistant project, nor do we have anything to do with the homeassistant modbus integration (which for some reason you do not use) |
Beta Was this translation helpful? Give feedback.
-
you are using the sync. client, so of course everything blocks, when a call is active. Homeassistant also uses an old version of pymodbus which we do not support. |
Beta Was this translation helpful? Give feedback.
you are using the sync. client, so of course everything blocks, when a call is active.
Homeassistant also uses an old version of pymodbus which we do not support.