Debugging Homematic IP: no updates on some HmIP devices after some time

Thanks, will try it this weekend and give feedback

1 Like

I would like to give feedback:
I tried the upper patch within OH 3.1.0 as an addon after uninstalling the originally homatic binding.
After a while the bridge was initializing but still none of the homatic things/items receives updates.
But still e.g. changes on switches are still sent correctly to homematic.

Are the switches “old” HM devices or HmIP? The problem only occurs with HmIP.
Is it a CCU3 or CCU2? The CCU2 probably needs more retries. Therefore I will make it configurable.

Maybe you can enable DEBUG log mode, try again what happens and attach the log file. It would be interesting to see if the maximum number of retries is reached.

I have uploaded a new test version (https://github.com/MHerbst/openhab-addons-test). You can now configure the number of retries and the wait time as advanced options in the Bridge configuration.

I tested, but without success. I sent traces via mail.

I have not received any logs yet. Please also answer the quests from my post 5d ago.

Thanks.

I replied to [openHAB] [Add-ons/Bindings] Debugging Homematic IP: no updates on some HmIP devices after some time from [openHAB] [Add-ons/Bindings] Debugging Homematic IP: no updates on some HmIP devices after some time. :thinking:

OH 3.1.0.zip.txt (115.8 KB)
OH.zip.txt (358.7 KB)
Please remove the extension txt from the ZIP files.

The test version of the add on needs a 3.2 milestone version. Otherwise it won’t load correctly.

It also seems that maybe the binding version 3.1 has not be uninstalled before you copied the binding to the add-on folder.

Yes, I’ve seen that part in the traces too. But the argument type exception ‘java.lang.IllegalArgumentException: argument type mismatch’ also exists for the 3.1.0 binding.
I see no other way to uninstall a binding other that the UI, removing the test binding fron the addonb folder and restarting the service. There seems to be some hidding caching. Is there something further to be done?
I found other hints to this problem in this forum as well: e.g. Downgrade from 3.1.0 to 3.0.1.

It is important to clean the cache after the uninstall. Otherwise the binding will be loaded again from the cache.

With the help of traces and MHerbst we could find the root cause of the problem:
The homematic bridge configuration had chosen a wrong default ‘callback network address’.
The respective configuration item should be set to the OH servers address in such a problem scenario.
Thank you very much for the support.

openhab-log.zip.txt (162.1 KB)
Servus,
I have the same problem only with all my HmIP devices. There are one-time updates after the startup of OpenHAB, but then no more updates of the HmIP items.

My system:
openHAB Version: 3.1.0 Docker-Container on Synology NAS
RaspberryMatic CCU version: 3.59.6.20211009 with HM-MOD-RPI-PCB

Bridge config:

UID: homematic:bridge: *blanked*
label: RaspberryMatic
thingTypeUID: homematic:bridge
configuration:
  cuxdPort: 8701
  socketMaxAlive: 900
  installModeDuration: 60
  timeout: 15
  hmIpPort: 2010
  factoryResetOnDeletion: false
  discoveryTimeToLive: -1
  wiredPort: 2000
  gatewayType: auto
  callbackHost: *blanked-OH-IP*
  groupPort: 9292
  gatewayAddress: *blanked-CCU-IP*
  unpairOnDeletion: false
  rfPort: 2001
  bufferSize: 2048

Thing code:

UID: homematic:HmIP-SWDM-B2:5c9554f9f7:001559939598D4
label: HaustĂŒr Kontakt
thingTypeUID: homematic:HmIP-SWDM-B2
configuration:
  HMP_0_CYCLIC_INFO_MSG_DIS_UNCHANGED: 0
  HMP_1_EVENT_DELAY_UNIT: 100MS
  HMP_0_CYCLIC_INFO_MSG_DIS: 30
  HMP_1_SAMPLE_INTERVAL: 0.5
  HMP_0_ENABLE_ROUTING: true
  HMP_0_LOCAL_RESET_DISABLED: false
  HMP_0_ARR_TIMEOUT: 10
  HMP_0_LOW_BAT_LIMIT: 2.2
  HMP_0_DUTYCYCLE_LIMIT: 180
  HMP_1_EVENT_DELAY_VALUE: 0
  HMP_1_MSG_FOR_POS_B: CLOSED
  HMP_0_CYCLIC_INFO_MSG: 1
  HMP_1_MSG_FOR_POS_A: OPEN
  HMP_0_CYCLIC_INFO_MSG_OVERDUE_THRESHOLD: 2
bridgeUID: homematic:bridge: *blanked*
location: Wardrobe

In RaspberryMatic all changes are displayed correctly.
In OpenHAB the status does not change, but the change arrives correctly according to TRACE log.

I already set the callback address for the bridge.

I would appreciate ideas and suggestions to solve the problem.

Log file is too large. Had to zip it and then rename it as txt.

Log snippet:

2021-11-01 21:43:12.155 [TRACE] [nal.communicator.server.XmlRpcServer] - Server parsed XmlRpcMessage:
system.multicall()
[
	{
		methodName=event
		params=
		[
			HMIP-*blanked-UID*
			00201BE98C12FF:0
			CONFIG_PENDING
			false
		]
	}
	{
		methodName=event
		params=
		[
			HMIP-*blanked-UID*
			00201BE98C12FF:0
			DUTY_CYCLE
			false
		]
	}
	{
		methodName=event
		params=
		[
			HMIP-*blanked-UID*
			00201BE98C12FF:0
			LOW_BAT
			false
		]
	}
	{
		methodName=event
		params=
		[
			HMIP-*blanked-UID*
			00201BE98C12FF:0
			UNREACH
			false
		]
	}
	{
		methodName=event
		params=
		[
			HMIP-*blanked-UID*
			00201BE98C12FF:0
			RSSI_DEVICE
			-62
		]
	}
	{
		methodName=event
		params=
		[
			HMIP-*blanked-UID*
			00201BE98C12FF:0
			OPERATING_VOLTAGE_STATUS
			0
		]
	}
	{
		methodName=event
		params=
		[
			HMIP-*blanked-UID*
			00201BE98C12FF:0
			OPERATING_VOLTAGE
			2.7
		]
	}
]

2021-11-01 21:43:12.155 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '19.0' for '00201BE98C12FF:1#SET_POINT_TEMPERATURE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.155 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00201BE98C12FF:0#CONFIG_PENDING' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.155 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00201BE98C12FF:1#BOOST_TIME' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.155 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00201BE98C12FF:0#DUTY_CYCLE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.155 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00201BE98C12FF:1#PARTY_MODE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.156 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00201BE98C12FF:1#LEVEL_STATUS' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.156 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00201BE98C12FF:0#LOW_BAT' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.156 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00201BE98C12FF:1#QUICK_VETO_TIME' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.156 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00201BE98C12FF:0#UNREACH' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.156 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '-62' for '00201BE98C12FF:0#RSSI_DEVICE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.157 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00201BE98C12FF:0#OPERATING_VOLTAGE_STATUS' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.157 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '2.7' for '00201BE98C12FF:0#OPERATING_VOLTAGE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.157 [TRACE] [nal.communicator.server.XmlRpcServer] - Server XmlRpcResponse:
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodResponse><params><param><value><array><data><value>event</value></data></array></value></param></params></methodResponse>
2021-11-01 21:43:12.157 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00201BE98C12FF:1#FROST_PROTECTION' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.158 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00201BE98C12FF:1#SET_POINT_MODE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.159 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '0.25' for '00201BE98C12FF:1#LEVEL' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.159 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00201BE98C12FF:1#ACTUAL_TEMPERATURE_STATUS' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.159 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00201BE98C12FF:1#SWITCH_POINT_OCCURED' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.159 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '4' for '00201BE98C12FF:1#VALVE_STATE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.160 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '1' for '00201BE98C12FF:1#ACTIVE_PROFILE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.160 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Integer) value '0' for '00201BE98C12FF:1#WINDOW_STATE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.160 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '19.0' for '00201BE98C12FF:1#ACTUAL_TEMPERATURE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.160 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'false' for '00201BE98C12FF:1#BOOST_MODE' from gateway with id '*blanked-UID*'
2021-11-01 21:43:12.161 [TRACE] [nal.communicator.server.XmlRpcServer] - Server XmlRpcResponse:
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodResponse><params><param><value><array><data><value>event</value></data></array></value></param></params></methodResponse>
2021-11-01 21:43:19.706 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:43:19.710 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:43:34.712 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:43:34.717 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:43:49.719 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:43:49.723 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:44:04.742 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:44:04.747 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:44:19.749 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:44:19.754 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:44:34.755 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:44:34.760 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:44:49.763 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:44:49.767 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:45:04.769 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:45:04.774 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:45:19.776 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:45:19.781 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

2021-11-01 21:45:34.783 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcRequest (port 2001):
<?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>listBidcosInterfaces</methodName>
<params></params></methodCall>
2021-11-01 21:45:34.787 [TRACE] [nal.communicator.client.XmlRpcClient] - Client XmlRpcResponse (port 2001):
<?xml version="1.0" encoding="iso-8859-1"?>
<methodResponse><params><param>
	<value><array><data><value><struct><member><name>ADDRESS</name><value>QEQ0407627</value></member><member><name>CONNECTED</name><value><boolean>1</boolean></value></member><member><name>DEFAULT</name><value><boolean>1</boolean></value></member><member><name>DESCRIPTION</name><value></value></member><member><name>DUTY_CYCLE</name><value><i4>2</i4></value></member><member><name>FIRMWARE_VERSION</name><value>2.8.6</value></member><member><name>TYPE</name><value>CCU2</value></member></struct></value></data></array></value>
</param></params></methodResponse>

I have a similar issue, but all advices I could find in the forum didn’t help. Formerly, I had OH 2.5 on a synology. But since there were some issues migrating to OH3 I am running now OH3.2.0 on an raspi 4. Installation was ok. A first binding (avm Fritzbox) works. I have a number of homematic devices running on CCU2, both HM and HmIP. But the OH3.2.0 homematic binding recognizes only the HmIP devices. Does anyone has the same problem?

I also observe missing updates with openhab 3.2 release + raspberrymatic 3.61.7.20220115 on raspbeerry pi 4.

When installing the addon from @MHerbst, i get the following log output:

2022-01-21 12:51:42.832 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.homematic-3.2.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.homematic [234]
  Unresolved requirement: Import-Package: org.openhab.core.config.discovery.upnp
	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.16.300.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:445) ~[org.eclipse.osgi-3.16.300.jar:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.7.2]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.7.2]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.7.2]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.7.2]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.7.2]
2022-01-21 12:51:43.926 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.

Nevertheless, after a while, the things and items receive first updates - I will have to check mid/long term effects.

Thanks and best
Matthias

If you put the binding jar into the addon folder you have to install the upnp manually (with feature:install).

But you don’t need this jar any longer because all changes have been merged into the 3.2 release version.

Thank you for the reply - I was assuming the same as it was called 3.2 Snapshot.

Any hint for the observed behavior? Does anybody know how a raspberrymatic on RPi 4 should be recognized correctly (ccu2 still does not “feel” correct as its more a ccu3+ :smiley:)?

Thanks

For completeness, the currently reduced thing file:

Bridge homematic:bridge:ccu3 [ 
  callbackHost="192.168.186.31",
  cuxdPort= "8701",
  socketMaxAlive= "900",
  InstallModeDuration= "60",
  callbackRegTimeout= "120",
  timeout= "15",
  hmIpPort= "2010",
  factoryResetOnDeletion= "false",
  discoveryTimeToLive= "-1",
  wiredPort= "2000",
  gatewayType= "ccu",
  groupPort= "9292",
  gatewayAddress= "192.168.186.31",
  unpairOnDeletion= "false",
  rfPort= "2001",
  bufferSize= "2048"
 ]
{
    // Thermostate
    Thing HmIP-BWTH    xxxxxxxx "BĂŒro Matthias Thermostat" @ "Roehrmoos"
}

By the way: Any hint for a good buffer size in case of ~40 devices?

I just read your post more carefully. You mention upnp. This is not activated on my network and I could not find it in the homematic binding documentation as well. Anyhow: The hint was for manual jar installation or is this also valid for using the binding itself?

upnp ist only needed for the automatic discovery of the CCU. As you have have configured the bridge in text file, this is not a problem.

By the way: Any hint for a good buffer size in case of ~40 devices?

Buffer size is OK. You would only have to increase it if the log shows xml parsing errors.

Can you explain your problem a bit more in detail. From your description I don’t really understand what’s going wrong.

Thank you for the very fast feedback!

I only get initial updates from the homematic devices when reloading the things file. After that I get zero updates from the system. E.g. when changing the set point temperature, there is no action on the thing / item at all.

I started using homematic with openhab resently, so not an expert with this binding yet.

Thanks