Callback blocked

[klauserber]

I agree to the following

• I have read the documentation right now
• I have read the FAQs right now
• I am aware of the latest release notes
• I am aware that an integration that was installed via HACS also needs to be updated via HACS
• The Backend (CCU/Homegear/...) is working as expected, devices are taught in and are controllable by its own UI.
• I am running the latest version of the custom_component (and Home Assistant)

The problem

Hello, I have issues with the callback. From time to time (every 1-2 days) the callback is completely blocked. The command:

curl http://10.9.1.51:29960

hangs forever.

On the RasberryMatic-Side I see errors like:

Mar 20 20:25:23 homematic-raspi user.err rfd: XmlRpc transport error
Mar 20 20:25:28 homematic-raspi user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"homematic-BidCos-RF","NEQ1490570:4","CONTROL_MODE",1}],[methodName:"event",params:{"homematic-
BidCos-RF","NEQ1490570:4","FAULT_REPORTING",0}],[methodName:"event",params:{"homematic-BidCos-RF","NEQ1490570:4","BATTERY_STATE",2.800000}],[methodName:"event",params:{"homematic-BidCos-RF","NEQ1490570:4
","VALVE_STATE",0}],[methodName:"event",params:{"homematic-BidCos-RF","NEQ1490570:4","BOOST_STATE",0}],[methodName:"event",params:{"homematic-BidCos-RF","NEQ1490570:4","ACTUAL_TEMPERATURE",23.100000}],[m
ethodName:"event",params:{"homematic-BidCos-RF","NEQ1490570:4","SET_TEMPERATURE",21.000000}],[methodName:"event",params:{"homematic-BidCos-RF","NEQ1490570:4","PARTY_TEMPERATURE",5.000000}],[methodName:"e
vent",params:{"homematic-BidCos-RF","NEQ1490570:4","PARTY_START_TIME",0}],[methodName:"event",params:{"homematic-BidCos-RF","NEQ1490570:4","PARTY_START_DAY",1}],[methodName:"event",params:{"homematic-Bid
Cos-RF","NEQ1490570:4","PARTY

And in the homeassistent log (nothing more about homematic):

2025-03-20 19:09:48.838 WARNING (MainThread) [hahomematic.client] IS_CALLBACK_ALIVE: Callback for homematic-BidCos-RF has not received events for 608s

After a restart of the Homeassistent Pod everything works normal for the next 1-2 days. And a get responses on my curl-tests.

Some facts about the system:

• Homeassistent runs in a Container on a Kubernetes Cluster on the host network. RaspberryMatic on a RaspberryPI 4 standalone.
• There is no CPU or memory pressure on both sides.
• The Homeassistent Pod was not evicted, stays always on the same node.
• I have tried to Rollback to a much older Version of the integration (version 1.76.1) but the behaviour is the same
• TLS is not enabled

I am working with a custom port (29960) for the callback, because I have to expose it with a MetalLB-based loadbalancer service over a fixed IP and port. This concept works well for all my applications on the cluster even with the TLS enabled Ingress controller. The curl command hangs as well, wenn try is directly in the container with the node IP without going over the virtual IP from the loadbalancer.

What version of HomematicIP (local) has the issue?

1.81.2

What was the last working version of HomematicIP (local)?

No response

What type of installation are you running?

Home Assistant Container

What type of installation are you running for your homematic backend?

RaspberryMatic Standalone

Which version of your homematic backend are you running?

No response

What hardware are you running for your system?

BareMetal Ryzon 5700G (3 Nodes Kubernetes Cluster)

Which config details do you use

• TLS
• callback data (see)

Which interfaces do you use?

• Homematic IP
• Homematic (Bidcos-RF)
• Groups (Heating-Group)
• BidCos-Wired (HM-Wired)

Diagnostics information (very helpful) (no logs here)

No response

Log file extract (very helpful). Anything in the logs that might be useful for us? The log (Setting/System/Logs -> load full log) is the best source to support trouble shooting!

Additional information

No response

[SukramJ]

... to make it short:

Ensure that communication is always possible from CCU to HA, no matter how complex you setup is.
I see no issue with the integration so converting this to a discussion.