search

alexreinert / piVCCU

piVCCU is a project to install the original Homematic CCU3 firmware inside a virtualized container (lxc) on ARM based single board computers.
Apache License 2.0
302 stars 64 forks source link

Homematic IP Schaltsteckdose (HMIP-PS) nicht mehr erreichbar #219

Closed wineworld13 closed 4 years ago

wineworld13 commented 4 years ago

Hallo Alex,

ich habe seit gestern das Problem, dass meine Schaltsteckdosen (HMIP-PS) nicht mehr erreichbar sind.

Das aktuelle System (3.41.11-17) lief seit einem Jahr stabil mit normalen Homematic Komponenten.

Homeatic-IP-Komponenten wurden im November 2019 ohne Probleme hinzugefügt:

2 x Homematic IP Schaltsteckdose (HMIP-PS) 1 x Homematic IP Wandtaster - 2-fach (HMIP-WRC2)

Mit dem Wandtaster steuerte ich bisher die beiden Steckdosen.

Seit gestern ist keine Steckdose mehr erreichbar:

2019-12-29 08:15:54.428 [hingStatusInfoChangedEvent] - 'homematic:HMIP-PS:ccu:00021A4…' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR)

2019-12-29 08:37:39.813 [WARN ] [ematic.handler.HomematicThingHandler] - Device '00021A4…' is OFFLINE, can't send command 'OFF' for channel 'homematic:HMIP-PS:ccu:00021A4…:3#STATE'

Nun habe ich versucht eine der beiden Steckdosen aus der Zentrale zu löschen, um sie neu anzulernen. Die Steckdose habe ich gemäß Anleitung in den Werkszustand zurückgesetzt. Dies blieb jedoch ohne Erfolg, da die Steckdose nicht erkannt wird und nicht im Posteingang erscheint.

Anschließend habe ich die puvccu3 auf die neueste Version (3.49.17-33) gebracht. Dies hat leider auch nicht den erwünschten Erfolg gebracht.

Aktuelle Systeminfos:

pi@raspberrypi:~ $ sudo pivccu-info piVCCU version: 3.49.17-33 Kernel modules: Available Raw UART dev: Available Rasp.Pi3 UART: Assigned to GPIO pins HMRF Hardware: RPI-RF-MOD HMIP Hardware: RPI-RF-MOD Board serial: 58A9A72172 Radio MAC: unknown SGTIN: 3014F711A0001F58A9A72172 State: RUNNING PID: 805 IP: 192.168.2.111 CPU use: 52.77 seconds BlkIO use: 51.19 MiB Memory use: 160.80 MiB KMem use: 5.51 MiB Link: vethpivccu TX bytes: 9.05 MiB RX bytes: 888.45 KiB Total bytes: 9.92 MiB

pi@raspberrypi:~ $ sudo pivccu-attach cat /var/hm_mode HM_HMIP_ADDRESS='' HM_HMIP_DEV='RPI-RF-MOD' HM_HMIP_DEVNODE='/dev/raw-uart' HM_HMIP_SERIAL='58A9A72172' HM_HMIP_SGTIN='3014F711A0001F58A9A72172' HM_HMIP_VERSION='4.0.20' HM_HMRF_ADDRESS='' HM_HMRF_DEV='RPI-RF-MOD' HM_HMRF_DEVNODE='/dev/raw-uart' HM_HMRF_SERIAL='58A9A72172' HM_HMRF_VERSION='4.0.20' HM_HOST='rpi3' HM_HOST_GPIO_RESET='' HM_HOST_GPIO_UART='/dev/raw-uart' HM_LED_GREEN='' HM_LED_RED='' HM_LED_YELLOW='' HM_MODE='NORMAL' HM_RTC=''

pi@raspberrypi:~ $ sudo pivccu-attach cat /var/log/messages Dec 29 08:12:44 piVCCU syslog.info syslogd started: BusyBox v1.29.2 Dec 29 08:12:44 piVCCU user.notice kernel: klogd started: BusyBox v1.29.2 (2019- 12-02 17:04:43 CET) Dec 29 08:12:46 piVCCU syslog.info syslogd exiting Dec 29 08:12:46 ccu3-webui syslog.info syslogd started: BusyBox v1.29.2 Dec 29 08:12:46 ccu3-webui user.notice kernel: klogd started: BusyBox v1.29.2 (2 019-12-02 17:04:43 CET) Dec 29 08:12:46 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:46 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:46 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:46 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: iptables v1.6.2: host/network fc 00::' not found Tryiptables -h' or 'iptables --help' for more information. Dec 29 08:12:47 ccu3-webui user.info firewall: configuration set Dec 29 08:12:47 ccu3-webui daemon.info ifplugd(eth0)[318]: ifplugd 0.28 initiali zing. Dec 29 08:12:47 ccu3-webui daemon.info ifplugd(eth0)[318]: Using interface eth0/ 0A:67:12:5E:0B:63 with driver (version: 1.0) Dec 29 08:12:47 ccu3-webui daemon.info ifplugd(eth0)[318]: Using detection mode: SIOCETHTOOL Dec 29 08:12:47 ccu3-webui daemon.info ifplugd(eth0)[318]: Initialization comple te, link beat detected. Dec 29 08:12:47 ccu3-webui daemon.warn ifplugd(eth0)[318]: Could not open /dev/t ty, cannot beep. Dec 29 08:12:47 ccu3-webui daemon.info ifplugd(eth0)[318]: Executing '/etc/ifplu gd/ifplugd.action eth0 up'. Dec 29 08:12:47 ccu3-webui daemon.warn ifplugd(eth0)[318]: client: ifup: interfa ce eth0 already configured Dec 29 08:12:47 ccu3-webui daemon.info ifplugd(eth0)[318]: Program executed succ essfully. Dec 29 08:12:57 ccu3-webui daemon.notice ntpdate[326]: step time server 80.237.1 28.148 offset -0.422498 sec Dec 29 08:12:57 ccu3-webui daemon.notice ntpd[327]: ntpd 4.2.8p12@1.3728-o Mon D ec 2 16:03:15 UTC 2019 (1): Starting Dec 29 08:12:57 ccu3-webui daemon.info ntpd[327]: Command line: /usr/sbin/ntpd - g 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: proto: precision = 0.468 usec (-21) Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: Listen and drop on 0 v6wildcar d [::]:123 Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: Listen and drop on 1 v4wildcar d 0.0.0.0:123 Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: Listen normally on 2 lo 127.0. 0.1:123 Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: Listen normally on 3 eth0 192. 168.2.111:123 Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: Listen normally on 4 lo [::1]: 123 Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: Listen normally on 5 eth0 [fe8 0::867:12ff:fe5e:b63%5]:123 Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: Listening on routing socket on fd #22 for interface updates Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: kernel reports TIME_ERROR: 0x4 1: Clock Unsynchronized Dec 29 08:12:57 ccu3-webui daemon.info ntpd[329]: kernel reports TIME_ERROR: 0x4 1: Clock Unsynchronized Dec 29 08:12:57 ccu3-webui daemon.err xinetd[347]: Unable to read included direc tory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14] Dec 29 08:12:57 ccu3-webui daemon.crit xinetd[347]: 347 {init_services} no servi ces. Exiting... Dec 29 08:12:57 ccu3-webui user.info root: Updating RF Lan Gateway Coprocessor F irmware Dec 29 08:12:57 ccu3-webui user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3 Dec 29 08:12:57 ccu3-webui user.info root: Updating RF Lan Gateway Firmware Dec 29 08:12:57 ccu3-webui user.info update-lgw-firmware: No gateway found in co nfig file /etc/config/rfd.conf Dec 29 08:12:57 ccu3-webui user.info kernel: [ 32.553765] eq3loop: created sla ve mmd_hmip Dec 29 08:12:57 ccu3-webui user.info kernel: [ 32.554461] eq3loop: created sla ve mmd_bidcos Dec 29 08:13:00 ccu3-webui user.info kernel: [ 35.593421] eq3loop: eq3loop_ope n_slave() mmd_bidcos Dec 29 08:13:23 ccu3-webui user.info kernel: [ 58.365745] eq3loop: eq3loop_ope n_slave() mmd_hmip Dec 29 08:13:23 ccu3-webui user.info kernel: [ 58.366027] eq3loop: eq3loop_clo se_slave() mmd_hmip Dec 29 08:13:23 ccu3-webui user.info kernel: [ 58.386084] eq3loop: eq3loop_ope n_slave() mmd_hmip Dec 29 08:13:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:13:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:13:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:13:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:37 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcC lient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"OEQ0581323: 7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcM ethod():iseXmlRpc.cpp:2608] Dec 29 08:14:37 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call fai led (interface: 1007, params: {"OEQ0581323:7","DECISION_VALUE"}) [CallGetValue() :iseXmlRpc.cpp:1435] Dec 29 08:14:37 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124] Dec 29 08:14:37 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:37 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcC lient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"OEQ1993740: 7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcM ethod():iseXmlRpc.cpp:2608] Dec 29 08:14:37 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call fai led (interface: 1007, params: {"OEQ1993740:7","DECISION_VALUE"}) [CallGetValue() :iseXmlRpc.cpp:1435] Dec 29 08:14:37 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124] Dec 29 08:14:38 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:38 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:38 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:38 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcC lient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"OEQ1990158: 7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcM ethod():iseXmlRpc.cpp:2608] Dec 29 08:14:38 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call fai led (interface: 1007, params: {"OEQ1990158:7","DECISION_VALUE"}) [CallGetValue() :iseXmlRpc.cpp:1435] Dec 29 08:14:38 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124] Dec 29 08:14:39 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:40 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:40 ccu3-webui user.err rfd: HSSParameter::GetValue() id=DECISION_VA LUE failed getting physical value. Dec 29 08:14:40 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcC lient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"OEQ1990150: 7","DECISION_VALUE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcM ethod():iseXmlRpc.cpp:2608] Dec 29 08:14:40 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call fai led (interface: 1007, params: {"OEQ1990150:7","DECISION_VALUE"}) [CallGetValue() :iseXmlRpc.cpp:1435] Dec 29 08:14:40 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]

pi@raspberrypi:~ $ sudo pivccu-attach cat /var/log/hmserver.log Dec 29 08:13:10 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory Dec 29 08:13:10 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created instance of HMServerConfiguration with parameter(s) Dec 29 08:13:10 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 parameter(s), in declarative order [String] Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) worker Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 32 classes to Vert.x Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 32 VertxDeployers initialized Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (21dd044) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of CheckDeviceExistHandler succeeded (e3912481 Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger -aec8-34f00557a17e) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeededa75dbfd48) Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of TransactionSubsystemHandler succeeded (aa5a769) Dec 29 08:13:20 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) fo Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of HMIPTRXWriterWorker succeeded (5097a03d-3b7 Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of KeyServerWorker succeeded (f8b633f4-2c98-49 Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointKeyServerWorker succeeded (cb2960d) Dec 29 08:13:20 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration mode: KEYSERVER_LOCAL Dec 29 08:13:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of RouterKeyServerWorker succeeded (2691a5c1-1 Dec 29 08:13:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (6244fee3-0 Dec 29 08:13:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (92b25a6) Dec 29 08:13:22 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-6] SYSTEM: DeviceLiveUpdateSubsystem started Dec 29 08:13:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of AccessPointElectroCardioGram succeeded (7304b50) Dec 29 08:13:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (9f353b3) Dec 29 08:13:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (e95efea) Dec 29 08:13:23 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-4] SYSTEM: Firmware update directory is set to /e Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of IncomingHMIPFrameHandler succeeded (12691b7) Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of FirmwareLoaderFileSystem succeeded (375c651) Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointMessageDispatcher succeeded (6755774) Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of RemoteCommAdapterInitialization succeeded (5d551f4) Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of AccessPointAuthorisationHandler succeeded (bec1103) Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointWatchdog succeeded (3c4305af-e97 Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of WebSocketManager succeeded (3d5cc1b4-6613-4 Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (882e2f5) Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of BackendCommandHandler succeeded (0b56e6d4-4 Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointCommDevice succeeded (6822af92-9 Dec 29 08:13:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerAdapterInitialization succeeded cea736f7) Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRXApp Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running or sta Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ... Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 11920597... Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A0001F58A9A7217 Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version... Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 4.0.20 Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.1 Dec 29 08:13:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.40.1 Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] MCU type: CC1310 Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Duty Cycle: 1.0 Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] set DutyCycle limit to ffffffc8 Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set Duty Cycle Limit Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Current Security Counter: 95581952 Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Update security counter to calculation: 95730088 Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter has no linkpartner Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Adapter with Access Point id 3014F711A0001F58A9A7 Dec 29 08:13:24 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [Thread-6] HMIPTRXInitialResponseListener said that Adapte Dec 29 08:13:25 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-0] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 Dec 29 08:13:25 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of LocalServerFirmwareUpdateInitialization suc5a-d1df2176d66a) Dec 29 08:13:25 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN [vert.x-worker-thread-2] SYSTEM: Firmware update directory in config fic/config/firmware Dec 29 08:13:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Checking all devices on all acces Dec 29 08:13:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updat Dec 29 08:13:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updat Dec 29 08:13:25 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded dbe2f2c2) Dec 29 08:13:25 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyAPIWorker succeeded (45cbedfb-be0e-45 Dec 29 08:13:26 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LanRoutingWorker succeeded (c4395b37-072f-4 Dec 29 08:13:26 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-1] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168 Dec 29 08:13:26 de.eq3.cbcs.lib.hmiptrxcommadapter.internal.RoutingSubsystem WARN [Thread-6] Received routing key 492465494D2FE2210355533E46DD7346 Dec 29 08:13:26 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-1] UDP Routing multi cast established on network interface eth0 : 192.1 Dec 29 08:13:26 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (2636da1e-a584 Dec 29 08:13:26 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-0] SYSTEM: Started Access Point WebSocket server Dec 29 08:13:26 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-0] SYSTEM: connector open Dec 29 08:13:26 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of RemoteCommAdapterFinalization succeeded (70df853) Dec 29 08:13:26 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LegacyNotificationHandler succeeded (a79847b) Dec 29 08:13:26 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: initial deployment complete ____ Dec 29 08:13:26 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 Dec 29 08:13:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 Dec 29 08:13:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default BlockedThreadCheckInterval: 1000 Dec 29 08:13:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxWorkerExecuteTime: 60000000000 Dec 29 08:13:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default EventLoopPoolSize: 8 Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) w Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) worker Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: deploying 10 classes to Vert.x Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: 10 VertxDeployers initialized Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (9a4975f0-38c4-417c Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of GroupConfigurationPersistenceFileSystem suc9f-37df0ce1af30) Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of EnergyPriceRequestWorker succeeded (bfb4774) Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of RegaClientWorker succeeded (35d35631-eef6-4 Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of CouplingRequestWorker succeeded (1dad6bfa-7 Dec 29 08:13:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of StorageRequestWorker succeeded (f2f7104f-39 Dec 29 08:13:31 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DiagramRequestWorker succeeded (f03e6bb2-bf Dec 29 08:13:31 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of GroupRequestWorker succeeded (4e5f8903-9003 Dec 29 08:13:31 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (eb953dd) Dec 29 08:13:31 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of HmIPGatewayManagementRequestWorker succeedeb3306b6826) Dec 29 08:13:31 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: initial deployment complete _____ Dec 29 08:13:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer at 127.0.0.1:39292 Dec 29 08:13:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Read Configuration Dec 29 08:13:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Bidcos Dispatcher Dec 29 08:13:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] InitBidCosCache Dec 29 08:13:33 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create groupDefinitionProvider Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHolder Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHandlerRega Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupAdministrationService Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceDispatcher Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceHandler Dec 29 08:13:34 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] @GroupDeviceHandler - initializing... Dec 29 08:13:34 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dec 29 08:13:34 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) Dec 29 08:13:34 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> got groupDefinitionProvider Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCosGroupMemberProvider Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init groupAdministrationService Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Virtual OS Device Dec 29 08:13:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init ESHLight Bridge Dec 29 08:13:35 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create RrdDatalogging Dec 29 08:13:35 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create MeasurementService Dec 29 08:13:35 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init MeasurementService Dec 29 08:13:36 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create HTTP Server Dec 29 08:13:36 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCos context and start handler Dec 29 08:13:36 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group context and start handler Dec 29 08:13:36 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called fr2/bidcos Dec 29 08:13:36 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-3] init finished Dec 29 08:13:36 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-3] Added InterfaceId: HmIP-RF_java Dec 29 08:13:36 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-3] updateDevicesForClient HmIP-RF_java -> 64 device addres Dec 29 08:13:37 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer done Dec 29 08:13:49 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] (un)registerCallback on Virtuam url: xmlrpc_bin://127.0.0.1:31999 Dec 29 08:13:49 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] Added InterfaceId: 1008 Dec 29 08:13:49 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-13] Execute BackendCommand: de.eq3.ccu.virtualdackendUpdateDevicesCommand Dec 29 08:13:49 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] updateDevicesForClient -> 16 d Dec 29 08:13:59 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called fr1:31999 Dec 29 08:13:59 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] init finished Dec 29 08:13:59 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-2] Added InterfaceId: 1009 Dec 29 08:14:00 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of INT000000 Dec 29 08:14:00 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of INT000000 Dec 29 08:14:00 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of INT000000 Dec 29 08:14:00 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of INT000000 Dec 29 08:14:02 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called frtion:1000 Dec 29 08:14:17 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] (un)registerCallback on Virtuam url: http://openhab.validation:1000 Dec 29 08:14:18 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called fr9125 Dec 29 08:14:18 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-1] init finished Dec 29 08:14:18 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-1] Added InterfaceId: HMIP-ccu Dec 29 08:14:18 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] (un)registerCallback on Virtuam url: http://192.168.2.110:9125 Dec 29 08:14:18 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] Added InterfaceId: GROUP-ccu Dec 29 08:14:18 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-15] Execute BackendCommand: de.eq3.ccu.virtualdackendUpdateDevicesCommand Dec 29 08:14:18 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-1] updateDevicesForClient HMIP-ccu -> 64 device addresses Dec 29 08:14:18 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-15] updateDevicesForClient -> 16 d Dec 29 08:14:18 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-15] set ready config of INT000000 Dec 29 08:14:18 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-15] set ready config of INT000000 Dec 29 08:14:18 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-15] set ready config of INT000000 Dec 29 08:14:18 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-15] set ready config of INT000000 Dec 29 08:18:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue Dec 29 08:18:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler Dec 29 08:18:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization Dec 29 08:23:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue Dec 29 08:23:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler Dec 29 08:23:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization Dec 29 08:23:23 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO [vert.x-eventloop-thread-2] SYSTEM: Access Point Watchdog runk...

pi@raspberrypi:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)" NAME="Raspbian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" VERSION_CODENAME=stretch ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Ich hoffe auf deine Hilfe.

Gruß

wineworld13 commented 4 years ago

Update: Nach einer Weile erscheint die Schaltsteckdose (welche noch im System existiert) wieder ONLINE. Jedoch beim Versuch sie Anzusteuern wechselt sie sofort in den Zustand OFFLINE.

alexreinert commented 4 years ago

Kannst du die Geräte über die WebUI der CCU steuern? Welche Version von OpenHab hast du?

wineworld13 commented 4 years ago

Hallo Alex,

danke für die schnelle Antwort.

Über die WebUI lässt sich die Steckdose auch nicht steuern. Gleiches Verhalten wie über OpenHab - Gerät ist ONLINE, beim Ansteuern OFFLINE (laut Log) Servicemeldung in WebUI CCU: Gerätekommunikation gestört.

OpenHab-Version: 2.4.0-1

alexreinert commented 4 years ago

Kann es sein, dass beim HmIP-PS ein Firmware Update gemacht wurde und jetzt der erste Reboot der CCU seit dem gemacht wurde? Bei der 3.41 musste man nach einem Firmware Update von HmIP Geräten diese Ab- und wieder neu Anlernen, da es sonst nach einem Reboot der Zentrale (und zwar erst dann) genau zu einem Problem kam. Aufgrund det Routing Funktionalität der Zwischensteckern hatte das aucv nicht nur Einfluß auf die Geräte selbst, sondern auch auf alle Geräte, welche darüber geroutet werden.

wineworld13 commented 4 years ago

Das Problem ist behoben!

Generell war zwar das Problem, dass die Schaltsteckdosen von einen auf den anderen Tag nicht mehr erreichbar waren und ich erst im nachhinein alle Aktualisierungen durchgeführt habe.

Dennoch, das mit dem Reboot könnte die Lösung gewesen sein. Ich habe auf jeden Fall ein bisschen herumprobiert und die Geräte ab-/angelernt. Es hat jedoch etwas gedauert, da man die Schaltsteckdosen auf Werkszustand zurücksetzen musste und das Handling dafür etwas "kompliziert" ist.

Danach konnte ich die Geräte in der WebUI der CCU neu hinzufügen.

Zusätzlich musste ich noch den Cache von OpenHAB leeren, da die geräte bereits mit Ihrer UID hinterlegt waren:

Nochmals vielen Dank.