OpenHAB 2, homegear, Homematic HM-CFG-LAN: No Connection (Offline connection refused)

Add-ons Bindings
1

Hi all!

I tried two days now to get my openHAB 2 System running…

I used the OpenHabian Installation as my last option on an Raspberry 3.

Both (Homegear and OpenHAB2) are still running, but I didn’t get a connection to the homematic…

In homegear I paired my devices w/o any problems. That’s working (same behaviour like OpenHAB1). I saw with “peers list” my devices.

In openHAB 2 I install with PaperUI the homematic-binding and bring in the IP Address for the HM-CFG-LAN.

But no connection…
I look several hints here in the forum, but nothing helps me…
Perhaps I have made a bigger mistake?
I don’t know.

Here some part of my Logfile:

event.log:
2016-11-06 20:45:42.843 [ThingAddedEvent ] - Thing ‘homematic:bridge:c5bd2aa0’ has been added.
2016-11-06 20:45:42.889 [hingStatusInfoChangedEvent] - ‘homematic:bridge:c5bd2aa0’ changed from UNINITIALIZED to INITIALIZING
2016-11-06 20:45:43.139 [hingStatusInfoChangedEvent] - ‘homematic:bridge:c5bd2aa0’ changed from INITIALIZING to OFFLINE (COMMUNICATION_ERROR): java.net.ConnectException: Connection refused

openhab.log

2016-11-06 21:26:07.979 [DEBUG] [org.openhab.binding.homematic ] - BundleEvent STARTING - org.openhab.binding.homematic
2016-11-06 21:26:08.056 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.UpnpDiscoveryParticipant}={component.name=org.eclipse.smarthome.binding.homematic.discovery.bridge, component.id=175, service.id=304, service.bundleid=215, service.scope=bundle} - org.openhab.binding.homematic
2016-11-06 21:26:08.073 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingTypeProvider, org.openhab.binding.homematic.type.HomematicThingTypeProvider}={component.name=org.openhab.binding.homematic.type.HomematicThingTypeProviderImpl, component.id=177, service.id=306, service.bundleid=215, service.scope=bundle} - org.openhab.binding.homematic
2016-11-06 21:26:08.105 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider, org.openhab.binding.homematic.type.HomematicConfigDescriptionProvider}={component.name=org.openhab.binding.homematic.type.HomematicConfigDescriptionProviderImpl, component.id=179, service.id=307, service.bundleid=215, service.scope=bundle} - org.openhab.binding.homematic
2016-11-06 21:26:23.410 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandler}={thing.type=homematic:bridge, thing.id=homematic:bridge:c5bd2aa0, service.id=311, service.bundleid=215, service.scope=singleton} - org.openhab.binding.homematic
2016-11-06 21:26:23.413 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=org.openhab.binding.homematic.handler.HomematicThingHandlerFactory, component.id=176, service.id=310, service.bundleid=215, service.scope=bundle} - org.openhab.binding.homematic
2016-11-06 21:26:23.414 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.openhab.binding.homematic.type.HomematicTypeGenerator}={component.name=org.openhab.binding.homematic.type.HomematicTypeGenerator, component.id=178, service.id=309, service.bundleid=215, service.scope=bundle} - org.openhab.binding.homematic
2016-11-06 21:26:23.415 [DEBUG] [org.openhab.binding.homematic ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.type.ChannelTypeProvider, org.openhab.binding.homematic.type.HomematicChannelTypeProvider}={component.name=org.openhab.binding.homematic.type.HomematicChannelTypeProviderImpl, component.id=180, service.id=308, service.bundleid=215, service.scope=bundle} - org.openhab.binding.homematic
2016-11-06 21:26:23.418 [DEBUG] [org.openhab.binding.homematic ] - BundleEvent STARTED - org.openhab.binding.homematic
2016-11-06 21:26:23.585 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:26:23.634 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:26:23.707 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:26:33.711 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:26:33.715 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:26:33.731 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:26:36.635 [WARN ] [nce.extensions.PersistenceExtensions] - There is no default persistence service configured!
2016-11-06 21:26:36.636 [WARN ] [nce.extensions.PersistenceExtensions] - There is no queryable persistence service registered with the id 'null’
2016-11-06 21:26:36.639 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Error during the execution of startup rule ‘ut’: cannot invoke method public abstract org.eclipse.smarthome.core.types.State org.eclipse.smarthome.core.persistence.HistoricItem.getState() on null
2016-11-06 21:26:36.838 [WARN ] [nce.extensions.PersistenceExtensions] - There is no default persistence service configured!
2016-11-06 21:26:36.838 [WARN ] [nce.extensions.PersistenceExtensions] - There is no queryable persistence service registered with the id 'null’
2016-11-06 21:26:36.839 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Error during the execution of startup rule ‘ut’: cannot invoke method public abstract org.eclipse.smarthome.core.types.State org.eclipse.smarthome.core.persistence.HistoricItem.getState() on null
2016-11-06 21:26:43.736 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:26:43.742 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:26:43.756 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:26:53.761 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:26:53.770 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:26:53.776 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:27:03.780 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:27:03.786 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:27:03.794 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:27:13.797 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:27:13.804 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:27:13.811 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:27:23.814 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:27:23.820 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:27:23.828 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:27:33.831 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:27:33.838 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:27:33.845 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:27:43.848 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:27:43.855 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:27:43.863 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:27:53.867 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:27:53.874 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:27:53.882 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:28:03.885 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:28:03.892 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:28:03.900 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:28:13.904 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:28:13.914 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:28:13.924 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:28:23.928 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:28:23.934 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:28:23.944 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:28:33.949 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:28:33.966 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:28:33.974 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:28:43.977 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:28:43.983 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:28:43.994 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:28:54.002 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:28:54.008 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:28:54.014 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:29:04.018 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:29:04.082 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:29:04.086 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:29:14.090 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:29:14.098 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:29:14.104 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:29:24.108 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:29:24.115 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:29:24.123 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:29:34.128 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:29:34.136 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:29:34.145 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:29:44.149 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:29:44.161 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:29:44.181 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:29:54.186 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:29:54.194 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:29:54.203 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:30:04.209 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:30:04.224 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

getDeviceDescription
BidCoS-RF
2016-11-06 21:30:04.235 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge 'c5bd2aa0’
2016-11-06 21:30:14.239 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.178.45,callbackHost=192.168.178.64,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=auto,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,aliveInterval=300,reconnectInterval=0,timeout=15,socketMaxAlive=900]
2016-11-06 21:30:14.246 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):

<?xml version="1.0" encoding="ISO-8859-1"?>

So, I have at the moment no more ideas how to handle it and to get a proper connection…

The same configuration was running as test with OpenHAB 1. I could switch the lights on or off with my smartphone…
And now with my new installation OpenHAB 2…
Nothing…
And my wife is waiting…

Thanks for any hints…

If you are missing any further information, please ask.

Thanks in advance.

Homegear version is 0.6.7.-1545

2

How does you Config file for homematic in openhab look like? If both are on the same maschine the gateway adress and the callback adress should be the same

Thomas

3

Hi Thomas!

Thank you for the hint.

I hope I checked it on the right place (via my samba share on the Raspberry PI):
mb://openhabianpi/openhab-config/services/homematic.cfg

The base installation package of this openHAB instance

Eintragungen für homematic Anbindung

homematic:host=192.168.178.45
homematic:callback.host=192.168.178.45

The IP Adress is from the HM-CFG-LAN.

But if I try to change it with Paper UI or with HABmin I got an error.

And like before no connection to my HM Devices…

Any hints for me?

Thanks.

4

you cannot use the CFG-Lan directly. You need homegear or a ccu. the chainis as follows

Homatic device-------ccu---------openhab (i am not sure about the HM-CFG_Lan in this chain)
or
Homematic device--------cfg_lan-------homegear--------openhab

so the required part is the ccu or homegear that is a kind of ccu

What is your setup

Thomas

5

Hi Thomas!

That is ok.

I have a setup based on a Raspberry Pi 3 with openhabian as installation base.

On the Rasperry Pi is Openhab 2 running together with homegear version 0.6.7.-1545.

Homegear is running without any problems with the HM-CFG-LAN. I connected two HM-TCIT-WM-W-EU and one HM-ES-PMSw1-PL for testing purpose.
I can see alle the HM devices with peers list in homegear.

But like described above I have no connection with openhab2 (Error messages you can see in my first post).

Please ask if it’s anything not clear or if I have forgotten a important detail.

Thanks!

6

OK, That is fine so far. Another Thing i found is that the homatic:host and the callback.host are not the same and if openhab and homeager are on the same host the ips should be the same.

Thomas

7

Hi Thomas!

Thanks for the hint.

I tried to put in the same IP at the paper UI as callback.host.
But I got an error. I couldn’t reach it.
Can I modify any config-Files to do this?
Or any other possibilites?

Thanks!

8

Hi Daniel,

that sounds strange. Could you post the error from the log.

Thanks
Thomas

9

Hi Thomas!

From which log File?

I ask because there are several files…

So I will check it this evening after work…
Perhaps we could solve the problem togehter.

With openhab V 1.8 I had no problems concerning the Connections to my HM devices.
I use the same configuration with the same HM devices, also with the same HM-CFG-LAN.
That’s the thing, why I don’t understand the different behaviour to the new openhab 2 Version. ;-(

Thanks.

10

Hi Daniel,
you wrote “I got an Error” where did you get this error. Please post the startup process from the openhab log and herer the part where homematic is started.

Thomas

11

Hi Thomas!

I tried to get all relevant information together…
Here the openhab.log file complete from beginning with the event.log file.

I took three screenshots from my paper UI, where you can see which Message I got…

The first screenshot is the Config Page:

PaperUI_1.png937×298 24.8 KB

There you can see the information that the bridge is offline.

The second screenshot shows the configuration:

PaperUI_2.png1452×847 57.2 KB

The third screenshot shows my try changing the IP address for the callback…
I tried the IP address from the HM-CFG-LAN himself, and as second step the IP address from my raspberry Pi with openhab 2 running.

PaperUI_3.png1212×396 31.6 KB

Here comes the both files (Only added the extension xml):

events.log.xml (1.5 KB)

openhab.log.xml (24.9 KB)

Thanks for your support!

12

Hi!

I solved the “problem”…

Small cause, great effect…

:slight_smile:

PaperUI_5.png1099×669 45.5 KB

There is the error…
As Callback Networt Address and Gateway Address must be entered the IP Address of the Raspberry PI running OpenHAB 2 and homegear…

I always thougt that the IP Address of the HM-CFG-LAN would have to be…

And now, this is the result:

PaperUI_4.png790×357 26 KB

It’s online…
I found all my HM-Devices…

Now, the next task is to setup the system…

Thanks to Thomas for the hints…

1 Like
13

Great and have fun with the system

thomas

14

Heya Can you give me your homematicbidcos file ?

i got homegear running with the hm-cfg-lan adapter but i dont see any homematic device.

i can pair enocean devices via homegear into openhab2 but i just cant find my homematic devices behind the hm-cfg-lan adapter.

cheers.

15

First Step is to setup your Homematic devices correctly in homegear and then head over to openHAB.

Have your paired your homematic devices with homegear successfully and do you see them on the homegear console?

You may also move to the homegear forum to solve the first step https://forum.homegear.eu/