OK, so you both don’t have devices which sends events in regular intervals.
By default, the binding listens to events and if no message receives from the Homematic gateway, the binding thinks that something is wrong and restarts the RPC servers. That’s the aliveInterval setting.
In your case, you have to disable this setting and schedule a reconnect after a fixed period of time. That’s the reconnectInterval setting.
@michaeljoos
Previously, the communication was done with XML-RPC on port 9125. Now, RF, WIRED and CUxD is done with the faster BIN-RPC on port 9126 and only HomematicIP with XML-RPC on port 9125, because it does not support BIN-RPC. You can configure these ports in the bridge config.
What irritates me are the error messages in the CCU logfile. I will test the reconnect…
@whph
These warnings are from the core framework and looks like a config problem in the things file.