Reconnecting sometimes fails for HmIp

[eikowagenknecht]

Sometimes reconnecting fails when the CCU3 is rebooted, then it looks like this:

All HmIp devices failed, all Hm devices are there.

custom_component/hahomematic version (if applicable):
latest

Home Assistant version (if applicable):
latest

CCU version:
CCU3 with Raspberrymatic

To Reproduce
Steps to reproduce the behavior:

1. Have HA running
2. Reboot CCU

Expected behavior
Reconnection should not result in missing entities.

Restarting the integration fixes this as a workaround, but this should be handled automatically.

In the old integration there was a service homematic.reconnect which could be used to mitigate the problems. This service does not exist in the hahm.* namespace. A better solution would of course be if this wasn't even needed anymore.

Additional context
I've had a very similar bug in openHAB, see openhab/openhab-addons#8808 (comment) for the explanation of the addon developer there.

[SukramJ]

What happens if you click on reload integration. That should be the equivalent to a service reload.

Please add logs

[SukramJ]

Please give me a summary of the attached openhab issue. Why is this relevant?
hahomematic waits until a successful API PING (not icmp ping) do reinit the client.

[eikowagenknecht]

Please give me a summary of the attached openhab issue. Why is this relevant?

It showed the same behaviour after reboot (HmIp not available while Hm is available), so I thought it might be the same issue. The most relevant finding is this:

This XML-RPC message appears because the CCU returns HTML code containing a message that it is not ready. Would be much better if it would return a correct error state ...

In combination with this:

hahomematic waits until a successful API PING (not icmp ping) do reinit the client.

it maybe would explain why your API PING succeeds even though the API is not really booted up correctly.

[eikowagenknecht]

What happens if you click on reload integration. That should be the equivalent to a service reload.

Yes, reload integration fixed it.

Please add logs

Unfortunately after enabling the debug logging the error hasn't occurred for 5 CCU restarts in a row now which speaks for an error that could probably be dependent on the exact timing of the reconnection attempt . I'll keep restarting and hope that it fails again to privide better data :-)

[SukramJ]

Yes, i guess the CCU is too slow for the current reconnect.

[SukramJ]

Current config is a check interval of 30s, and reconnect immediately if check is successful again.
I will switch to less aggressive solution:
Check every 60s and wait 120s after successful connection check to reconnect.

[eikowagenknecht]

I think the "wait 120s after successful connection check" will mostly fix it when there is no other way to reliably check if the service is running correctly yet. The correct time to wait would depend on the hardware the CCU is running on and maybe some other things like number of devices and/or programs, addons installed etc. :-/

Don't know why you would set the check interval from 30s to 60s though, this just increases the variation of the timespan (ccu_is_available to do_the_reconnect), doesn't it?

[SukramJ]

I already planned to raise it to 60s before. Should be enough for a connection check.

[SukramJ]

addressed in 0.23.0

[eikowagenknecht]

Thanks. I have restarted about 20 times now and currently can't reproduce. I'll close this and reopen if I catch it another time.