Homematic HmIP devices not updating OpenHABian 2.4 & CCU3 3.47.15

Hey Guys,

decided to ask help from the community again. My last problem involved data from Homematic->openHAB not coming through to my influx database. I Could not fix this problem in the end even with the suggestions provided by some helpfull users. I was planning to give openHABian a try in the future but now that my setup is not working anymore I figured that now was good time to start.

So I installed openHABian on my raspberry pi 3B+ which was suprissingly easy. Loved the fact that the shared folders are setup and also that dailout and tty was already added to the openhab user. This gave me quit a search last time. Now my DSMR binding worked out of the box.

Hardware:

Raspberry Pi 3B+
CCU3

Software:

openHABian (openHAB) 2.4.0 with the following bindings:

  • DSMR binding
  • Homematic binding (snapshot: 0.10.0.201812191738 taken from here.
  • MQTT thing binding

CCU2 firmware 3.47.15

ISSUE:

After I restart the openHAB service openHAB will receive values from the CCU but only for an hour or so. After that suddenly the values will no be updated any more. They will not be changed to NULL or something similiar. Somehow they “freeze” in openHAB. These values will continue be send to my influx database where they will then just create a continous straight line. When I restard openHAB again everything will be fine again for an hour or so.

Worth mentioning: ONLY my HmIP deviced are having this problem.

THINGS TRIED / DONE

  • Installed Homematic binding 0.10.0.20181219173 as per this thread. Tried to use the bind adress 0.0.0.0 which did not work.
  • Restarted openHAB service and Raspberry Pi numerous times. Each time values are being send after that but again for only a short time.
  • Tried to find some clues in the openhab log
  • Tried to find some clues in the syslog
  • A few days ago I did a clean install of the CCU3 (back to factory settings but it did not downgrade).

I am really at a loss guys. Been trying to fix this for 5 days now but I am not getting any closer to finding a solution. Any help is appreciated.

Here is a screenshot of my openHAB setting for the CCU3 and a screenshot from the firewall setting on my CCU3.


Here is a part of the openhab.log with the smarthome binding in DEBUG. Sorry for the long piece if anybody has a good tip how to make this more post/read friendly let me know.

There is a lot off clutter regarding this “communicator.parser.CommonRpcParser” which I have no idea what it means.

2019-11-08 14:43:57.389 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
2019-11-08 14:43:58.238 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (String) value '3014F711A0001F98A99F9530' for 'CENTRAL:0#PONG' from gateway with id '3014F711A0001F98A99F9530'
2019-11-08 14:44:00.603 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (String) value '3014F711A0001F98A99F9530' for 'CENTRAL:0#PONG' from gateway with id '3014F711A0001F98A99F9530'
2019-11-08 14:44:04.032 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicThingTypeProvider, org.eclipse.smarthome.core.thing.binding.ThingTypeProvider}={service.id=380, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicThingTypeProviderImpl, component.id=237} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.037 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicTypeGenerator}={service.id=386, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicTypeGeneratorImpl, component.id=239} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.041 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=387, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.handler.HomematicThingHandlerFactory, component.id=240} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.162 [DEBUG] [matic.handler.HomematicBridgeHandler] - Disposing bridge '3014F711A0001F98A99F9530'
2019-11-08 14:44:04.169 [DEBUG] [very.HomematicDeviceDiscoveryService] - Stopping Homematic discovery scan
2019-11-08 14:44:04.173 [DEBUG] [very.HomematicDeviceDiscoveryService] - Waiting for finishing Homematic device discovery scan
2019-11-08 14:44:04.175 [DEBUG] [very.HomematicDeviceDiscoveryService] - Finished Homematic device discovery scan on gateway '3014F711A0001F98A99F9530'
2019-11-08 14:44:04.182 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=388, service.bundleid=222, service.scope=singleton} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.247 [DEBUG] [nal.communicator.server.XmlRpcServer] - Stopping XML-RPC server
2019-11-08 14:44:04.289 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=381, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.discovery.CcuDiscoveryService, component.id=238} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.298 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicConfigDescriptionProvider, org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=382, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicConfigDescriptionProviderImpl, component.id=241} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.308 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.discovery.UpnpDiscoveryParticipant}={service.id=383, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.discovery.HomegearDiscoveryParticipant, component.id=242} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.314 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicChannelTypeProvider, org.eclipse.smarthome.core.thing.type.ChannelTypeProvider}={service.id=384, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicChannelTypeProviderImpl, component.id=243} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.320 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicChannelGroupTypeProvider, org.eclipse.smarthome.core.thing.type.ChannelGroupTypeProvider}={service.id=385, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicChannelGroupTypeProviderImpl, component.id=244} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.328 [DEBUG] [.eclipse.smarthome.binding.homematic] - BundleEvent STOPPING - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.332 [DEBUG] [.eclipse.smarthome.binding.homematic] - BundleEvent STOPPED - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:04.549 [INFO ] [io.openhabcloud.internal.CloudClient] - Shutting down openHAB Cloud service connection
2019-11-08 14:44:04.934 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler DSMRBridgeHandler tried updating the thing status although the handler was already disposed.
2019-11-08 14:44:04.954 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler DSMRBridgeHandler tried updating the thing status although the handler was already disposed.
2019-11-08 14:44:04.970 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler DSMRBridgeHandler tried updating the thing status although the handler was already disposed.
2019-11-08 14:44:05.719 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Stopped Paper UI
2019-11-08 14:44:05.753 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@1efa577{STOPPING,10<=10<=40,i=0,q=6}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/11690752@1731524] Couldn't stop Thread[ESH-httpClient-common-193,5,main]
2019-11-08 14:44:05.757 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@1efa577{STOPPING,10<=10<=40,i=0,q=6}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/11690752@1731524] Couldn't stop Thread[ESH-httpClient-common-192,5,main]
2019-11-08 14:44:05.779 [INFO ] [panel.internal.HABPanelDashboardTile] - Stopped HABPanel
2019-11-08 14:44:05.791 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Stopped Home Builder
2019-11-08 14:44:05.827 [INFO ] [.dashboard.internal.DashboardService] - Stopped Dashboard
2019-11-08 14:44:17.749 [WARN ] [.MqttBrokerConnectionServiceInstance] - MqttBroker connection configuration faulty: host : You need to provide a hostname/IP!
2019-11-08 14:44:19.970 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2019-11-08 14:44:20.188 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2019-11-08 14:44:20.295 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Europe/Amsterdam'.
2019-11-08 14:44:20.302 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'en_NL'.
2019-11-08 14:44:20.305 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Measurement system set to 'SIUnits'.
2019-11-08 14:44:27.790 [ERROR] [io.openhabcloud.internal.CloudClient] - Socket.IO error: not authorized
2019-11-08 14:44:28.365 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'default.items'
2019-11-08 14:44:29.231 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'influxdb.persist'
2019-11-08 14:44:31.732 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2019-11-08 14:44:32.764 [INFO ] [el.core.internal.ModelRepositoryImpl] - Validation issues found in configuration model 'default.sitemap', using it anyway:
Sitemap should contain either only frames or none at all
2019-11-08 14:44:32.771 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'default.sitemap'
2019-11-08 14:44:33.158 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'dsmr.things'
2019-11-08 14:44:34.936 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.2.4:8080
2019-11-08 14:44:34.940 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.2.4:8443
2019-11-08 14:44:35.338 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2019-11-08 14:44:37.520 [DEBUG] [.eclipse.smarthome.binding.homematic] - BundleEvent STARTING - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.531 [DEBUG] [.eclipse.smarthome.binding.homematic] - BundleEvent STARTED - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.552 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to '192.168.2.4' with clientid paho58031132045118 and file store '/var/lib/openhab2/mqtt/192.168.2.4'
2019-11-08 14:44:37.582 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicThingTypeProvider, org.eclipse.smarthome.core.thing.binding.ThingTypeProvider}={service.id=380, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicThingTypeProviderImpl, component.id=237} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.621 [DEBUG] [ternal.discovery.CcuDiscoveryService] - Starting Homematic CCU discovery scan
2019-11-08 14:44:37.630 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=381, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.discovery.CcuDiscoveryService, component.id=238} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.649 [DEBUG] [ternal.discovery.CcuDiscoveryService] - Discovered a CCU gateway with serial number '3014F711A0001F98A99F9530'
2019-11-08 14:44:37.678 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicConfigDescriptionProvider, org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=382, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicConfigDescriptionProviderImpl, component.id=241} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.688 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.UpnpDiscoveryParticipant}={service.id=383, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.discovery.HomegearDiscoveryParticipant, component.id=242} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.703 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicChannelTypeProvider, org.eclipse.smarthome.core.thing.type.ChannelTypeProvider}={service.id=384, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicChannelTypeProviderImpl, component.id=243} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.720 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicChannelGroupTypeProvider, org.eclipse.smarthome.core.thing.type.ChannelGroupTypeProvider}={service.id=385, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicChannelGroupTypeProviderImpl, component.id=244} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.771 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.binding.homematic.internal.type.HomematicTypeGenerator}={service.id=386, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.internal.type.HomematicTypeGeneratorImpl, component.id=239} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:37.922 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=387, service.bundleid=222, service.scope=bundle, component.name=org.eclipse.smarthome.binding.homematic.handler.HomematicThingHandlerFactory, component.id=240} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:38.097 [DEBUG] [matic.handler.HomematicBridgeHandler] - HomematicConfig[gatewayAddress=192.168.2.14,callbackHost=192.168.2.4,bindAddress=0.0.0.0,xmlCallbackPort=9125,binCallbackPort=9126,gatewayType=ccu,rfPort=2001,wiredPort=2000,hmIpPort=2010,cuxdPort=8701,groupPort=9292,timeout=15,discoveryTimeToLive=-1,installModeDuration=60,socketMaxAlive=900]
2019-11-08 14:44:38.142 [DEBUG] [.eclipse.smarthome.binding.homematic] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=388, service.bundleid=222, service.scope=singleton} - org.eclipse.smarthome.binding.homematic
2019-11-08 14:44:38.330 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'WIRED' on gateway '3014F711A0001F98A99F9530' not available, disabling support
2019-11-08 14:44:38.376 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'CUXD' on gateway '3014F711A0001F98A99F9530' not available, disabling support
2019-11-08 14:44:38.622 [DEBUG] [ommunicator.AbstractHomematicGateway] - Initializing gateway with id '3014F711A0001F98A99F9530'
2019-11-08 14:44:38.626 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=CCU,type=CCU2,firmware=3.47.15,address=PEQ1453360,rf=true,wired=false,hmip=true,cuxd=false,group=true]
2019-11-08 14:44:38.635 [DEBUG] [ommunicator.AbstractHomematicGateway] - Used Homematic transfer modes: RF:XML_RPC, HMIP:XML_RPC, GROUP:XML_RPC
2019-11-08 14:44:38.755 [DEBUG] [nal.communicator.server.XmlRpcServer] - Initializing XML-RPC server at port 9125
2019-11-08 14:44:43.098 [INFO ] [internal.device.DSMRSerialAutoDevice] - Start receiving telegrams on port /dev/ttyUSB0 with settings: Baudrate:115200, databits:8, parity:none, stopbits:1
2019-11-08 14:44:45.706 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (String) value '3014F711A0001F98A99F9530' for 'CENTRAL:0#PONG' from gateway with id '3014F711A0001F98A99F9530'
2019-11-08 14:44:48.974 [DEBUG] [very.HomematicDeviceDiscoveryService] - Stopping Homematic discovery scan
2019-11-08 14:44:48.977 [DEBUG] [very.HomematicDeviceDiscoveryService] - Waiting for finishing Homematic device discovery scan
2019-11-08 14:44:48.981 [DEBUG] [very.HomematicDeviceDiscoveryService] - Finished Homematic device discovery scan on gateway '3014F711A0001F98A99F9530'
2019-11-08 14:44:48.988 [DEBUG] [very.HomematicDeviceDiscoveryService] - Starting Homematic discovery scan
2019-11-08 14:44:49.003 [DEBUG] [very.HomematicDeviceDiscoveryService] - Will not attempt to set controller in install mode, because bridge is not ONLINE.
2019-11-08 14:44:49.010 [DEBUG] [very.HomematicDeviceDiscoveryService] - Waiting for finishing Homematic device discovery scan
2019-11-08 14:44:49.391 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device 'BidCoS-RF' (HM-RCV-50) with 206 datapoints
2019-11-08 14:44:49.396 [DEBUG] [rnal.type.HomematicTypeGeneratorImpl] - Generating ThingType for device 'HM-RCV-50' with 206 datapoints
2019-11-08 14:44:49.536 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device 'OEQ0325682' (HM-LC-Sw1-SM) with 28 datapoints
2019-11-08 14:44:49.539 [DEBUG] [rnal.type.HomematicTypeGeneratorImpl] - Generating ThingType for device 'HM-LC-Sw1-SM' with 28 datapoints
2019-11-08 14:44:50.300 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device '000A18A9A3C026' (HmIP-eTRV-2) with 631 datapoints
2019-11-08 14:44:50.302 [DEBUG] [rnal.type.HomematicTypeGeneratorImpl] - Generating ThingType for device 'HmIP-eTRV-2' with 631 datapoints
2019-11-08 14:44:50.419 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device '000A18A9A3BFF0' (HmIP-eTRV-2) with 631 datapoints
2019-11-08 14:44:51.575 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device '000A98A9A4D320' (HmIP-WTH-2) with 1172 datapoints
2019-11-08 14:44:51.578 [DEBUG] [rnal.type.HomematicTypeGeneratorImpl] - Generating ThingType for device 'HmIP-WTH-2' with 1172 datapoints
2019-11-08 14:44:51.707 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device '000A18A9940AB3' (HmIP-eTRV-2) with 631 datapoints
2019-11-08 14:44:51.737 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device '000A18A9A39AAB' (HmIP-eTRV-2) with 631 datapoints
2019-11-08 14:44:51.761 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device '000A18A9A39A23' (HmIP-eTRV-2) with 631 datapoints
2019-11-08 14:44:53.030 [ERROR] [io.openhabcloud.internal.CloudClient] - Socket.IO error: {}
io.socket.engineio.client.EngineIOException: xhr post error
	at io.socket.engineio.client.Transport.onError(Transport.java:71) [223:org.openhab.io.openhabcloud:2.4.0]
	at io.socket.engineio.client.transports.PollingXHR.access$000(PollingXHR.java:19) [223:org.openhab.io.openhabcloud:2.4.0]
	at io.socket.engineio.client.transports.PollingXHR$4$1.run(PollingXHR.java:88) [223:org.openhab.io.openhabcloud:2.4.0]
	at io.socket.thread.EventThread$2.run(EventThread.java:80) [223:org.openhab.io.openhabcloud:2.4.0]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: java.io.IOException: 502
	at io.socket.engineio.client.transports.PollingXHR$Request$1.run(PollingXHR.java:218) ~[?:?]
	... 1 more
2019-11-08 14:44:53.071 [INFO ] [io.openhabcloud.internal.CloudClient] - Disconnected from the openHAB Cloud service (UUID = 417aa899-0071-4c96-b2c0-0b67a5329b05, base URL = http://localhost:8080)
2019-11-08 14:44:53.601 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loaded device '001F98A99F9530' (HmIP-RCV-50) with 154 datapoints
2019-11-08 14:44:53.608 [DEBUG] [rnal.type.HomematicTypeGeneratorImpl] - Generating ThingType for device 'HmIP-RCV-50' with 154 datapoints
2019-11-08 14:44:53.841 [DEBUG] [.communicator.parser.CommonRpcParser] - Failed converting HM_IP_APPLICATION to a Number
java.lang.NumberFormatException: HM_IP_APPLICATION is not a valid number.
	at org.apache.commons.lang.math.NumberUtils.createNumber(NumberUtils.java:597) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.toNumber(CommonRpcParser.java:82) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.assembleDatapoint(CommonRpcParser.java:187) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.GetParamsetDescriptionParser.parse(GetParamsetDescriptionParser.java:54) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.client.RpcClient.addChannelDatapoints(RpcClient.java:183) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.CcuGateway.addChannelDatapoints(CcuGateway.java:137) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.loadAllDeviceMetadata(AbstractHomematicGateway.java:402) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.lambda$0(HomematicDeviceDiscoveryService.java:191) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
2019-11-08 14:44:53.866 [DEBUG] [.communicator.parser.CommonRpcParser] - Failed converting ANY to a Number
java.lang.NumberFormatException: ANY is not a valid number.
	at org.apache.commons.lang.math.NumberUtils.createNumber(NumberUtils.java:597) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.toNumber(CommonRpcParser.java:82) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.assembleDatapoint(CommonRpcParser.java:188) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.GetParamsetDescriptionParser.parse(GetParamsetDescriptionParser.java:54) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.client.RpcClient.addChannelDatapoints(RpcClient.java:183) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.CcuGateway.addChannelDatapoints(CcuGateway.java:137) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.loadAllDeviceMetadata(AbstractHomematicGateway.java:402) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.lambda$0(HomematicDeviceDiscoveryService.java:191) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
2019-11-08 14:44:53.886 [DEBUG] [.communicator.parser.CommonRpcParser] - Failed converting HM_IP_APPLICATION to a Number
java.lang.NumberFormatException: HM_IP_APPLICATION is not a valid number.
	at org.apache.commons.lang.math.NumberUtils.createNumber(NumberUtils.java:597) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.toNumber(CommonRpcParser.java:82) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.assembleDatapoint(CommonRpcParser.java:187) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.GetParamsetDescriptionParser.parse(GetParamsetDescriptionParser.java:54) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.client.RpcClient.addChannelDatapoints(RpcClient.java:183) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.CcuGateway.addChannelDatapoints(CcuGateway.java:137) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.loadAllDeviceMetadata(AbstractHomematicGateway.java:402) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.lambda$0(HomematicDeviceDiscoveryService.java:191) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
2019-11-08 14:44:53.907 [DEBUG] [.communicator.parser.CommonRpcParser] - Failed converting ANY to a Number
java.lang.NumberFormatException: ANY is not a valid number.
	at org.apache.commons.lang.math.NumberUtils.createNumber(NumberUtils.java:597) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.toNumber(CommonRpcParser.java:82) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.assembleDatapoint(CommonRpcParser.java:188) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.GetParamsetDescriptionParser.parse(GetParamsetDescriptionParser.java:54) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.client.RpcClient.addChannelDatapoints(RpcClient.java:183) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.CcuGateway.addChannelDatapoints(CcuGateway.java:137) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.loadAllDeviceMetadata(AbstractHomematicGateway.java:402) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.lambda$0(HomematicDeviceDiscoveryService.java:191) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
2019-11-08 14:44:53.930 [DEBUG] [.communicator.parser.CommonRpcParser] - Failed converting HM_IP_APPLICATION to a Number
java.lang.NumberFormatException: HM_IP_APPLICATION is not a valid number.
	at org.apache.commons.lang.math.NumberUtils.createNumber(NumberUtils.java:597) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.toNumber(CommonRpcParser.java:82) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.CommonRpcParser.assembleDatapoint(CommonRpcParser.java:187) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.GetParamsetDescriptionParser.parse(GetParamsetDescriptionParser.java:54) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.client.RpcClient.addChannelDatapoints(RpcClient.java:183) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.CcuGateway.addChannelDatapoints(CcuGateway.java:137) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.loadAllDeviceMetadata(AbstractHomematicGateway.java:402) ~[?:?]
	at org.eclipse.smarthome.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.lambda$0(HomematicDeviceDiscoveryService.java:191) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
1 Like

I have exactly the same problem. Using OH3.2, CCU2 with firmware 2.59.7, Raspi with latest openhabian 5.10.63. I switched from synology to raspi only a few weeks ago. On synology, homematic binding worked perfectly (therefore, there were other issues with OH3…) .
I tried similar things as described above, without success.
The only difference to the behaviour described by Peter is that the problem occurs not only on HMIP devices but on HM devicves as well.
Any help is appreciated.

If the binding does not receive any values, please make sure that all necessary ports are open on the Raspi. Also it may be necessary to configure a callback IP address in the bridge configuration.

If this does not help, set log mode for the HM binding to DEBUG, restart openHAB and attach the log file.

Many thanks for the quick reply. I will do it tomorrow and send you all Information.

Here are the results of the Raspi port scan. The raspi address is 192.168.178.70. I used the command ss -tulw. Seemingly, homematic ports are not in the list.I do not understand why port 8080 is also not in the list… Wrong command???
I am not a network specialist, but I assumed that openhabian does not install a firewall, so imho all ports should be open. Is it right or, maybe, the port scan shows only those ports where somebody is listening???
If I have to open the homematic ports manually: How can I manage that the port opening will be not neccessary after each restart? Thanks for your help.
portscan_raspi.txt (3.9 KB)

I don’t use openhabian and have no idea about how the firewall is configured by detail. But you can check it with the following command:

sudo iptables -L -nv

If the output is empty no ports are blocked.

I would also recommend to check the bridge settings in Paper UI and explicitely set a callback IP address.

It is in your list.
Port 8080 is equivalent to http-alt which is listed.
You may use switch -n to show the numeric values and not the service name if you are looking for numbers.
For a translation list you may have a look to /etc/serivces.

grep http /etc/services

ss is not a port scan I would say. ss lists sockets and their connections states.

thanks for the hint. I am rather new in Linux…

Here is the output of the iptable command. Seems to be empty…
Attached also screenshots of the bridge settings.
A naive question: Should the callback address be the same as the gateway address?
iptables.txt (923 Bytes)
homematic bridge settings #1.pdf (92.6 KB)
homematic bridge settings #2.pdf (67.1 KB)

log debug will follow soon.
Regards
Ulrich

here is the logfile.

No the callback address must be the IP address of the raspi running openHAB. How is your raspi connected to the network?

The iptables output looks fine. I can’t see any blocked ports (but I am also not an iptables expert).

The log file looks fine. I can’t see any messages about possible problems.

IT WORKS!!! Many many thanks :grinning: :grinning: :grinning:
Obviously, the whole trouble arised from my misunterstanding of the word “callback”. Who calls back to whom? To avoid such trouble for other users it might probably be useful to add a short explanation in the binding documentation.
How can I mark this thread as “Problem solved”?
Best regards
Ulrich