I have searched the log file. The channels of the weather station are updated only once when the sitemap is reloaded (e.g. after editing and then saving).
openhab (2).log (165.6 KB)
Unfortunately the log-file is to big for uploading. I zipped it and changed .zip to .log. Just change it back for decompressing.
In fact the weather station is my only HmIP device. Is there not also a way to manually update the values or force an update?
The warnings still occur with OH 3.3.0. Please see my newest comment for that issue.
Thanks for the log. To me it seems that your OH installation does not receive any events from CCU. I can’t see any messages like this in the log (this is an example from my installation):
2022-10-08 10:49:23.983 [TRACE] [nal.communicator.server.XmlRpcServer] - Server parsed XmlRpcMessage:
This means the CCU can not send messages to port 9125 on the machine where OH is running. This is the reason why you don’t get any value updates.
Many thanks for analyzing the log-files. Unfortunately I’m a litle bit confused now. My OpenHab runs on a raspberry PI4 with openhabian. I tought this is an easy setup made especially for openhab. I googled now for I while but was not able to find some tutorials how to check an open ports. May be you can give me a hint.
I think, openHabian is really good for a simple installation of OH but it probably does not now about all ports that may be required by other devices.
I don’t know how the firewall is configured in openHabian, but you can try whether ufw is active with ufw status. If ufw is active it will display all open ports. With ufw allow you can open additional ports.
If ufw is not available, you can use iptables --list to see all rules that are configured.
Many thanks for your reply Martin. It seems there is neither ufw nor iptables installed on my system. So I installed ufw with: sudo apt-get install ufw
Active ufw with: sudo ufw enable
and allowed any connection: sudo ufw default allow
Now any incomming connection or request should be allowed. Shouldn’t it?
sudo ufw app list
shows the following list:
Available applications:
AIM
Bonjour
CIFS
CUPS
DNS
Deluge
IMAP
IMAPS
IPP
KTorrent
Kerberos Admin
Kerberos Full
Kerberos KDC
Kerberos Password
LDAP
LDAPS
LPD
MSN
MSN SSL
Mail submission
NFS
OpenSSH
POP3
POP3S
PeopleNearby
SMTP
SSH
Samba
Socks
Telnet
Transmission
Transparent Proxy
VNC
WWW
WWW Cache
WWW Full
WWW Secure
XMPP
Yahoo
qBittorrent
svnserve
I really wonder why there is nothing about Homematic or something similar.
If neither ufw nor iptables was installed maybe no firewall was installed at all.
You can check the port status with ufw status verbose.
ufw app list shows only known ports, i.e. standard ports with numbers less then 1024. The binding and Homematic are using non-standard ports.
Maybe there is another possible cause for the problem: how did you connect your raspi to your network? Via WiFi or ethernet cable? I would highly recommend ethernet cable with a fixed ip address.
To verify whether the binding is listening on the correct address and port you can run: netstat -apn | grep 9125
Output should be similar to this:
tcp6 0 0 192.168.2.80:9125 192.168.2.93:59522 ESTABLISHED 12626/java
tcp6 0 0 192.168.2.80:9125 192.168.2.93:37658 ESTABLISHED 12626/java
I also suspect that no firewall was active before.
sudo ufw status verbose
gives just a Staus: active back.
the other option gives the folling back realted to port 9125
tcp 0 224 192.168.8.112:22 192.168.8.31:49909 VERBUNDEN 11659/sshd: openhab
tcp6 0 0 :::9125 :::* LISTEN 1161/java
tcp6 0 0 :::8101 :::* LISTEN 1161/java
tcp6 0 0 ::1:3350 :::* LISTEN 553/xrdp-sesman
tcp6 0 0 :::445 :::* LISTEN 1269/smbd
tcp6 0 0 :::5007 :::* LISTEN 1161/java
tcp6 0 0 :::8080 :::* LISTEN 1161/java
tcp6 0 0 :::3389 :::* LISTEN 592/xrdp
tcp6 0 0 :::1883 :::* LISTEN 730/mosquitto
tcp6 0 0 :::139 :::* LISTEN 1269/smbd
tcp6 0 0 :::8443 :::* LISTEN 1161/java
tcp6 0 0 127.0.0.1:33583 :::* LISTEN 1161/java
tcp6 0 0 ::1:631 :::* LISTEN 30235/cupsd
tcp6 0 0 :::22 :::* LISTEN 583/sshd: /usr/sbin
tcp6 0 0 192.168.8.112:34520 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:33900 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:35182 192.168.8.135:2001 VERBUNDEN 1161/java
tcp6 0 0 192.168.8.112:46054 194.195.245.175:443 VERBUNDEN 1161/java
tcp6 0 0 192.168.8.112:8080 192.168.8.31:49894 VERBUNDEN 1161/java
tcp6 1 0 192.168.8.112:8080 192.168.8.31:50701 CLOSE_WAIT 1161/java
tcp6 0 0 192.168.8.112:49372 192.168.8.194:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:48308 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:44596 192.168.8.194:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:33912 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:46560 192.168.8.135:2010 VERBUNDEN 1161/java
tcp6 0 0 192.168.8.112:39050 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 2a02:6d40:3b9b:9801:445 2a02:6d40:3b9b:98:49732 VERBUNDEN 10996/smbd
tcp6 0 1 192.168.8.112:48076 192.168.49.1:60000 SYN_SENT 1161/java
tcp6 0 0 192.168.8.112:55368 192.168.8.196:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:58394 192.168.8.197:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:51626 192.168.8.135:8181 VERBUNDEN 1161/java
tcp6 0 0 192.168.8.112:41734 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:55370 192.168.8.196:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:58380 192.168.8.197:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:41742 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:48314 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:39054 192.168.8.192:80 TIME_WAIT -
tcp6 0 0 192.168.8.112:34510 192.168.8.192:80 TIME_WAIT -
udp 0 0 0.0.0.0:68 0.0.0.0:* 1156/dhcpcd
udp 0 0 0.0.0.0:631 0.0.0.0:* 30238/cups-browsed
udp 0 0 192.168.8.255:137 0.0.0.0:* 1160/nmbd
udp 0 0 192.168.8.112:137 0.0.0.0:* 1160/nmbd
udp 0 0 0.0.0.0:137 0.0.0.0:* 1160/nmbd
udp 0 0 192.168.8.255:138 0.0.0.0:* 1160/nmbd
udp 0 0 192.168.8.112:138 0.0.0.0:* 1160/nmbd
udp 0 0 0.0.0.0:138 0.0.0.0:* 1160/nmbd
udp 0 0 0.0.0.0:43236 0.0.0.0:* 362/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 362/avahi-daemon: r
udp6 0 0 :::546 :::* 1156/dhcpcd
udp6 0 0 :::59940 :::* 362/avahi-daemon: r
udp6 0 0 192.168.8.112:33326 :::* 1161/java
udp6 0 0 :::5683 :::* 1161/java
udp6 0 0 :::67 :::* 1161/java
udp6 0 0 :::5353 :::* 1161/java
udp6 0 0 :::5353 :::* 1161/java
udp6 0 0 :::5353 :::* 362/avahi-daemon: r
udp6 0 0 :::1900 :::* 1161/java
udp6 0 0 :::55713 :::* 1161/java
raw6 0 0 :::58 :::* 7 1156/dhcpcd
after that a lot of lines starting with unix are following. But I think they are not relevant.
As I can see there is just one line relted to port 9125 that says the system is listening. It looks to me like there is no connection. Is ist possible that there is a problem with the CCU2? I think I have changed noting. It was working well with OH2.5.
My Raspberry is connected via ethernet cable and has a static IP.
It seems that it is only listining on the tcp6 address :::9125, because there is no entry for “0.0.0.0:9125” or 192.168.8.118:9125. This can cause the problem.
If you don’t need IPV6 on your Raspi, you can disable it. You can find a description here How to Really Disable IPv6 on Raspberry PI – How to Raspberry
ok I disabled tcp6 but that did not fix the problem. I also disable tcp6 in the settings of OH3.
Now I have an entry like you mentioned:
tcp 0 0 0.0.0.0:9125 0.0.0.0:* LISTEN 1168/java
It seems also not to be a problem of homematic or homematic IP I just changed the setpoint temperature of one of my thermostats (normal homematic) manually, but this changed not the value displayed in the OH app or in the webUI. I realy think that its a special homatic binding problem. I can send commands to the ccu2 but I can not receive data from it. All other devices work well (shelly/tp-link)
The problem is that every binding uses a different technology stack.
I have never seen this kind of problems with the binding before. According to the output the binding is now listening on the correct and waiting for messages from the CCU.
You could try to ssh into the CCU and check the log files in /var/log especially hmserver.log would contain messages if something goes wrong when it tries to send an event to the Homematic binding.
So I was realy able to get access via ssh. I took me a lot of time to find out that umlauts are not working in the password which has to be defined in the CCU2 system configuration. (how to - SSH-Zugang auf CCU2 einrichten - HomeMatic-Dokumentation)
after succesfull login ein typed:
cat /var/log/hmserver.log
(more on: Fehlerlog per SSH auf Raspberry, Rapsberrymatic, CCU2 - Mein Homematicblog)
and I found:
Oct 14 09:02:57 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
and
Oct 14 09:04:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer ERROR [vert.x-worker-thread-0] IO Exception: Could not add interface: 9e682990-c394-4ce6-8180-e89f18016007
de.eq3.cbcs.legacy.communication.rpc.RpcIOException: java.net.ConnectException: Connection refused (Connection refused)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:110)
at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.sendRequest(RpcClient.java:94)
at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.invoke(RpcClient.java:82)
at com.sun.proxy.$Proxy19.listDevices(Unknown Source)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendClient.listDevices(LegacyBackendClient.java:139)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.synchronizedBackendDevices(DeviceUtil.java:150)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:109)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:26)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
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.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:120)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:179)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:612)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:884)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:106)
... 15 more
and the following warnings:
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerPersistentDataLoader still not met - check deployment configuration
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of TransactionManagementVerticle still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of KryoPersistenceWorker still not met - check deployment configuration
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Oct 14 09:02:59 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerPersistentDataLoader still not met - check deployment configuration
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of TransactionManagementVerticle still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of KryoPersistenceWorker still not met - check deployment configuration
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Oct 14 09:03:06 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:13 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of KryoPersistenceWorker succeeded (67350049-cd01-4282-a534-7e24f420777f)
Oct 14 09:03:13 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:13 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of TransactionManagementVerticle still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:13 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:13 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:13 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Oct 14 09:03:13 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:14 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem Verticle or Worker started
Oct 14 09:03:14 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem started
Oct 14 09:03:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (d9f5f808-9583-4848-90d6-e48a7eae3293)
Oct 14 09:03:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of KeyServerWorker succeeded (8a4068e7-b14c-4395-b752-b125f1373f7e)
Oct 14 09:03:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (a91fa1f2-072f-410a-a3da-d8cc00592352)
Oct 14 09:03:14 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO [vert.x-eventloop-thread-0] SYSTEM: DeviceBackgroundUpdateSubsystem Verticle or Worker started
Oct 14 09:03:15 de.eq3.cbcs.server.local.base.internal.LocalServerPersistentDataLoader INFO [vert.x-eventloop-thread-0] SYSTEM: LocalServerPersistentDataLoader Verticle or Worker started
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerPersistentDataLoader succeeded (14649a6a-6e4c-492c-a742-8a2e7735e6fe)
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (6be745e8-1ae4-4875-9d0f-a810bc53ee5a)
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (45ebd11a-1aa4-4796-ab92-125eabc688b8)
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration (still unfulfilled: [transaction.management.ready])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [legacy.api.worker][connector.open][persistent.data.loaded])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 11 out of 22
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration (still unfulfilled: [transaction.management.ready])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [legacy.api.worker][connector.open][persistent.data.loaded])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration (still unfulfilled: [transaction.management.ready])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration (still unfulfilled: [persistent.data.loaded])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [legacy.api.worker][connector.open][persistent.data.loaded])
Oct 14 09:03:18 de.eq3.cbcs.server.core.vertx.IncomingHMIPFrameHandler INFO [vert.x-eventloop-thread-0] SYSTEM: IncomingHMIPFrameHandler Verticle or Worker started
Oct 14 09:03:18 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of IncomingHMIPFrameHandler succeeded (34bc0525-72e5-4d80-8ef5-7c36a3b71a84)
Oct 14 09:03:19 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware
Oct 14 09:03:19 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-0] SYSTEM: FirmwareLoaderFileSystem Verticle or Worker started
Oct 14 09:03:19 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of FirmwareLoaderFileSystem succeeded (aca13c63-3170-40c1-8397-ec687a14e432)
Oct 14 09:03:20 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:20 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:20 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:21 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [vert.x-eventloop-thread-0] SYSTEM: LocalServerAdapterInitialization Verticle or Worker started
Oct 14 09:03:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerAdapterInitialization succeeded (678d4a6a-724e-477d-b3b6-003e60687bab)
Oct 14 09:03:21 de.eq3.cbcs.server.core.vertx.DeviceInclusionAcceptHandler INFO [vert.x-eventloop-thread-0] SYSTEM: DeviceInclusionAcceptHandler Verticle or Worker started
Oct 14 09:03:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (4434579b-64ff-410f-98bb-0f73cc2ef1a4)
Oct 14 09:03:21 de.eq3.cbcs.server.core.transaction.TransactionManagementVerticle INFO [vert.x-eventloop-thread-0] SYSTEM: TransactionManagementVerticle Verticle or Worker started
Oct 14 09:03:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of TransactionManagementVerticle succeeded (d3207821-2e5c-451e-8b68-5df6fa62d070)
Oct 14 09:03:21 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 16 out of 22
Oct 14 09:03:21 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration (still unfulfilled: [transaction.management.ready])
Oct 14 09:03:21 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: [connector.open])
Oct 14 09:03:21 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [legacy.api.worker][connector.open])
I think these lines contain the relevant information:
Oct 14 09:04:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer ERROR [vert.x-worker-thread-0] IO Exception: Could not add interface: 9e682990-c394-4ce6-8180-e89f18016007
de.eq3.cbcs.legacy.communication.rpc.RpcIOException: java.net.ConnectException: Connection refused (Connection refused)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:110)
at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.sendRequest(RpcClient.java:94)
at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.invoke(RpcClient.java:82)
at com.sun.proxy.$Proxy19.listDevices(Unknown Source)
The exception clearly shows that the CCU can not connect to openHAB. Something seems to block the connection.
But the first line is also a bit strange. Normally there should be issued the name of interface (like HmIP-RF).
There is one idea left that you can check and try. I saw this in your bridge configuration:
Bridge homematic:bridge:ccu2 [ gatewayType="ccu", gatewayAddress="192.xxx.xxx.xxx", callbackHost="192.168.8.135" ]{
Is callbackHost the correct address of the Raspi where OP is running? The CCU will try to send the messages to this address.
OMG! I’m so stupid 
This was the problem!
I thought callbackHost is some kind of alternate address where you usually put the same address or zero.
Of course the 192.168.8.135 was not the address of the Raspi but the address of the CCU2. This would probably have been noticed immediately if I had not overwritten the first address with x.
In the logs I see now incoming values of the CCU2 and the data of the weather station update now also.
Many thanks for your persistent support, Martin!