OH2 Homematic IP at ccu2 not really working

Hi,

I’ve set up my home automation mostly with Homematic devices.
For some cases I had to take the HM IP products and only these are making problems in my setup.
Most of the time they are working with a big delay and sometimes they don’t work at all.
All the time the non IP devices are fine.
When I switch the devices directly at the ccu2 there is no delay or timeout.
I’m using openHAB 2.1.0 Build #929
Is there some configuration I have to change for HM IP?

Additionaly some log output.
This happens after some time. After this all HM-IP devices are flagged as offline.

java.io.IOException
at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:113)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:117)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:82)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at org.openhab.binding.homematic.internal.communicator.client.RpcClient.listDevices(RpcClient.java:140)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.getDeviceDescriptions(AbstractHomematicGateway.java:447)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.newDevices(AbstractHomematicGateway.java:681)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleNewDevice(RpcResponseHandler.java:101)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:52)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at org.openhab.binding.homematic.internal.communicator.server.BinRpcResponseHandler.run(BinRpcResponseHandler.java:46)[209:org.openhab.binding.homematic:2.1.0.201706030751]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_131]
at java.lang.Thread.run(Thread.java:748)[:1.8.0_131]
Caused by: java.util.concurrent.TimeoutException
at org.eclipse.jetty.client.util.FutureResponseListener.get(FutureResponseListener.java:109)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:655)[69:org.eclipse.jetty.client:9.2.19.v20160908]
at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:99)[209:org.openhab.binding.homematic:2.1.0.201706030751]
… 11 more

regards
Yannick

Hi Yannick,

your problem seems to be similar to this one: https://github.com/openhab/openhab2-addons/issues/1873
In this case the problem was solved by setting the aliveInterval to 3600. Can you test whether it solves your problem, too?

Hi Martin,

I will give it a try and let you know if this will fix the Problem.
Thanks a lot!

Looks like this was the trick.
Log is clean since the implementation.
And all HMIP devices working fine.

Thanks a lot for the help :slight_smile:

1 Like