Homematic1.x add-on can't connect to CCU3 with Firmware 3.41.11 (Read timed out)

Hi,

I tried to use the Homematic Binding 1.x since the binding included in Openhab 2.4.0 has a issue which is a showstopper for me.

I added “binding = homematic1” in the addons.cfg and added the IP address of the piVCCU3 as “host” in the homematic.cfg.

The issue I run into is that Homematic Binding cannot connect tothe piVCCU:

2019-01-19 18:19:46.105 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcRequest BinRpcRequest[methodName=getDeviceDescription,args={BidCoS-RF}]
2019-01-19 18:19:46.126 [DEBUG] [org.openhab.core                    ] - BundleEvent STARTING - org.openhab.core
2019-01-19 18:19:46.314 [DEBUG] [ntime.internal.engine.RuleEngineImpl] - Executing startup rule 'Switch Scene automatically'
2019-01-19 18:19:48.339 [DEBUG] [org.openhab.core                    ] - ServiceEvent REGISTERED - {javax.servlet.ServletContext}={osgi.web.version=2.4.0, osgi.web.contextpath=/, service.id=366, osgi.web.symbolicname=org.openhab.core, service.bundleid=180, service.scope=singleton, osgi.web.contextname=default} - org.openhab.core
2019-01-19 18:19:48.370 [DEBUG] [org.openhab.core                    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.model.sitemap.SitemapProvider}={service.id=367, service.bundleid=180, service.scope=bundle, component.name=org.openhab.defaultsitemapprovider, component.id=223} - org.openhab.core
2019-01-19 18:19:48.376 [DEBUG] [org.openhab.core                    ] - BundleEvent STARTED - org.openhab.core
2019-01-19 18:19:55.226 [DEBUG] [el.core.internal.ModelRepositoryImpl] - Refreshing resource 'main.rules'
2019-01-19 18:19:55.445 [DEBUG] [e.internal.engine.RuleTriggerManager] - Removed scheduled cron job 'main.rules#Switch Scene automatically#0 0/5 * * * ?'
2019-01-19 18:19:55.453 [DEBUG] [e.internal.engine.RuleTriggerManager] - Scheduled rule 'Switch Scene automatically' with cron expression '0 0/5 * * * ?'
2019-01-19 18:19:55.457 [DEBUG] [el.core.internal.ModelRepositoryImpl] - Refreshing resource 'main.rules'
2019-01-19 18:20:00.463 [DEBUG] [ntime.internal.engine.RuleEngineImpl] - Executing startup rule 'Switch Scene automatically'
2019-01-19 18:20:01.141 [ERROR] [l.communicator.HomematicCommunicator] - Could not start Homematic communicator: Read timed out (sending BinRpcRequest[methodName=getDeviceDescription,args={BidCoS-RF}])
org.openhab.binding.homematic.internal.communicator.client.HomematicClientException: Read timed out (sending BinRpcRequest[methodName=getDeviceDescription,args={BidCoS-RF}])
        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:226) ~[241:org.openhab.binding.homematic:1.13.0]
        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.getDeviceDescription(BinRpcClient.java:105) ~[241:org.openhab.binding.homematic:1.13.0]
        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.getServerId(BinRpcClient.java:117) ~[241:org.openhab.binding.homematic:1.13.0]
        at org.openhab.binding.homematic.internal.communicator.HomematicCommunicator.start(HomematicCommunicator.java:83) [241:org.openhab.binding.homematic:1.13.0]
        at org.openhab.binding.homematic.internal.bus.HomematicBinding.updated(HomematicBinding.java:95) [241:org.openhab.binding.homematic:1.13.0]
        at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189) [9:org.apache.felix.configadmin:1.9.4]
        at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152) [9:org.apache.felix.configadmin:1.9.4]
        at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85) [9:org.apache.felix.configadmin:1.9.4]
        at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1102) [9:org.apache.felix.configadmin:1.9.4]
        at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1058) [9:org.apache.felix.configadmin:1.9.4]
        at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138) [9:org.apache.felix.configadmin:1.9.4]
        at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105) [9:org.apache.felix.configadmin:1.9.4]
        at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method) ~[?:?]
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[?:?]
        at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[?:?]
        at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:?]
        at java.net.SocketInputStream.read(SocketInputStream.java:127) ~[?:?]
        at org.openhab.binding.homematic.internal.binrpc.BinRpcResponse.<init>(BinRpcResponse.java:48) ~[?:?]
        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:198) ~[?:?]
        ... 12 more
2019-01-19 18:20:01.180 [INFO ] [l.communicator.HomematicCommunicator] - Shutting down Homematic communicator

Since V3.41.11 BinRPC is obsolete, but XMLRPC has to be used. I have read in the documentation of the 1.x binding that…

If you enable HM-IP support, the binding uses XML-RPC. In the binding configuration, set homematicIP.enabled=true .

I have done so, but the error remains the same (and the log still says “BinRpcRequest” instead of “XmlRpcRequest” or so).

When taking a look at the binding’s source code, I also cannot find any spot where this setting is being considered as config setting, so I am wondering if the documentation is correct in this point.

I know that the 1.x binding is not maintained anymore, but I assume that the issue also affects all Openhab1 users who haven’t had time (or other reasons) and therefore haven’t migrated yet (might be quite a few).

Anyone else having the same issue and potentially any solution?

Any feedback/help is much appreciated.

And what would that be?
It may have been fixed in the snapshots

Unfortunately not, the issue is quite new still, please see here