Homematic binding: Bridge offline, communication_error

Add-ons Bindings
, ,
1

I’m using the latest openhab 2.2.0 Snapshot #1102 and have installed the homematic binding via PaperUI. But I can’t establish a connection with the homematic bridge for some reason. I checked the firewall on the CCU2 and I have previously used the binding and bridge successfully with the opehab build 2.1.0.

(Although in the 2.1.0 build for openhab the variables for the homematic gateway and devices didn’t get updated in PaperUI and Basic. I read that I was supposed to update the binding in order to get it to work but I could not get the snapshot version of the binding to work with the openhab build 2.1.0 so that’s the reason for using the latest snapshot of openhab and homematic binding).

I’m on Windows10. This is the TRACE log when starting the homematic binding:

2017-12-01 18:08:32.692 [DEBUG] [org.openhab.binding.homematic       ] - BundleEvent STARTING - org.openhab.binding.homematic
2017-12-01 18:08:32.693 [DEBUG] [org.openhab.binding.homematic       ] - BundleEvent STARTED - org.openhab.binding.homematic
2017-12-01 18:08:32.701 [DEBUG] [org.openhab.binding.homematic       ] - ServiceEvent REGISTERED - {org.openhab.binding.homematic.internal.type.HomematicConfigDescriptionProvider, org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={component.name=org.openhab.binding.homematic.internal.type.HomematicConfigDescriptionProviderImpl, component.id=185, service.id=320, service.bundleid=203, service.scope=bundle} - org.openhab.binding.homematic
2017-12-01 18:08:32.703 [DEBUG] [org.openhab.binding.homematic       ] - ServiceEvent REGISTERED - {org.openhab.binding.homematic.internal.type.HomematicChannelTypeProvider, org.eclipse.smarthome.core.thing.type.ChannelTypeProvider}={component.name=org.openhab.binding.homematic.internal.type.HomematicChannelTypeProviderImpl, component.id=186, service.id=321, service.bundleid=203, service.scope=bundle} - org.openhab.binding.homematic
2017-12-01 18:08:32.705 [DEBUG] [org.openhab.binding.homematic       ] - ServiceEvent REGISTERED - {org.openhab.binding.homematic.internal.type.HomematicThingTypeProvider, org.eclipse.smarthome.core.thing.binding.ThingTypeProvider}={component.name=org.openhab.binding.homematic.internal.type.HomematicThingTypeProviderImpl, component.id=187, service.id=322, service.bundleid=203, service.scope=bundle} - org.openhab.binding.homematic
2017-12-01 18:08:32.707 [DEBUG] [org.openhab.binding.homematic       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.UpnpDiscoveryParticipant}={component.name=org.openhab.binding.homematic.internal.discovery.HomegearDiscoveryParticipant, component.id=188, service.id=323, service.bundleid=203, service.scope=bundle} - org.openhab.binding.homematic
2017-12-01 18:08:32.709 [DEBUG] [org.openhab.binding.homematic       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.homematic.handler.HomematicThingHandlerFactory, component.id=189, service.id=325, service.bundleid=203, service.scope=bundle} - org.openhab.binding.homematic
2017-12-01 18:08:32.721 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.0.195,callbackHost=192.168.0.175,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,groupPort=9292,timeout=15,socketMaxAlive=900]
2017-12-01 18:08:32.722 [TRACE] [matic.handler.HomematicBridgeHandler] - Registering HomematicDeviceDiscoveryService for bridge '6752d3b6'
2017-12-01 18:08:32.723 [DEBUG] [org.openhab.binding.homematic       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=326, service.bundleid=203, service.scope=singleton} - org.openhab.binding.homematic
2017-12-01 18:08:32.725 [DEBUG] [org.openhab.binding.homematic       ] - ServiceEvent REGISTERED - {org.openhab.binding.homematic.internal.type.HomematicTypeGenerator}={component.name=org.openhab.binding.homematic.internal.type.HomematicTypeGeneratorImpl, component.id=190, service.id=324, service.bundleid=203, service.scope=bundle} - org.openhab.binding.homematic
2017-12-01 18:08:32.736 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>getDeviceDescription</methodName>
<params><param><value>BidCoS-RF</value></param></params></methodCall>
2017-12-01 18:08:47.739 [DEBUG] [nal.communicator.client.XmlRpcClient] - XmlRpcMessage failure, sending message again 1/1
2017-12-01 18:09:02.742 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge '6752d3b6'
2017-12-01 18:09:02.743 [DEBUG] [very.HomematicDeviceDiscoveryService] - Stopping Homematic discovery scan

Any help on the issue would be much appreciated!

2

I have a similar Problem.
After update to 2.2.0 Build #1117, the homematic bridge first works for a minite or so, and then suddenly stops working.

Setting the log to debug or TRACE does not show any more than:

17:40:52.542 [WARN ] [communicator.AbstractHomematicGateway] - Connection lost on gateway 'ccu'
17:40:52.552 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'homematic:bridge:ccu' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Connection lost

Unfortunately, going back to the stable 2.1, leaves the system unusable…
Any advice is greatly appreciated.

3

I guess issue #3090 is about just this topic: https://github.com/openhab/openhab2-addons/issues/3090

4

I switched from running openHAB on Windows 10 to running it on a RPi and everything has been working fine ever since. Don’t really know what the issue was and if it is the same as the one you are describing. But I suppose the issue is a little bit different as you are not getting more information from the TRACE log. I don’t think my connection was ever really established. Anyway, I hope you’ll be able to solve your issue!