Modbus entities unavailable after HA restart #134602
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
The problem
Every time I restart Home assistant, often for config changes, the modbus entities from my heatpump go unavailable. And then some hours later, they are back, with this gap of several hours of being unavailable.
This has been present in several HA versions last 3-4 months. I have not yet upgraded to 2025.1
All observations point at something that may be related to the connection between HA and the heatpump not getting closed properly, or not being picked up again properly, and so there would be some timeout or keepalive that need some fixing. As I dont know better, I consider this a bug. I tried to ask for help in the HA facebook group, where people suggested several things for debugging modbus, but I have really now clue what I would be looking for.
https://www.facebook.com/groups/HomeAssistant/posts/3927615277509813/?comment_id=3928347694103238¬if_id=1734645203921105¬if_t=group_comment
I was inspired by this config when doing mine: https://github.com/gribber/ha/blob/main/modbus/ctc.yaml
Heatpump is CTC, and several people have gotten this integrated with modbus.
Here are some of my config lines:
I can see the following in the log when HA was restarted (with debug logging enabled):
Looking back at the previous event when the entities started to appear again, here are some log lines that show what happens
What version of Home Assistant Core has the issue?
core-2024.12.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Modbus
Link to integration documentation on our website
https://www.home-assistant.io/integrations/modbus/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: