Inbetriebnahme CCU mit HMCCU: RaspiMatic zickt

Begonnen von drache, 12 Mai 2020, 07:04:44

Vorheriges Thema - Nächstes Thema
Drucken
Nach unten Seiten1
Benutzer-Aktionen

drache

12 Mai 2020, 07:04:44
Hallo zusammen,

nun bin ich kein blutiger FHEM-Anfänger mehr, aber ich wollte von meinem HMLAN auf HMCCU wechseln, um auch Homematic IP nutzen zu können. Als CCU habe ich einen Raspberry Pi 4 mit RPI-RF-MOD mit RaspiMatic im Einsatz.
Dessen Inbetriebnahme hat mich jetzt aber schon einige Stunden gekostet und ich habe sogar ein zweites Exemplar als fertiges Gesamtpaket gekauft, um sicherzugehen, dass die Hardware nicht kaputt ist. Aber beide verhalten sich gleich schlimm.


  • Wenn ich die Geräte im RaspiMatic-WebUI auflisten lasse, reagiert der Raspi meist nicht mehr (> 30 Sekunden Wartezeit). Ich laufe dann in einen Timeout ("Sitzung ungültig oder abgelaufen!") und werde nach einem Reload des WebUI vom WatchDog-Alarm ReGaHss restarted begrüßt. Auch in der Systemsteuerung friert der ganze Spaß gerne mal ein.
  • In FHEM habe ich ein HMCCU-Device angelegt. Die Firewall des Raspi habe ich auf komplett zugelassen mit offenen Ports gesetzt. Authentifizierung für XML-RPC ist aus. Ich kann den RPC-Server starten, aber get devicelist schlägt immer fehl: HMCCU: RaspiMatic Execution of CCU script or command failed
  • Es ist unabhängig, ob ich schon ein Device gekoppelt habe oder nicht.

Logfile von FHEM:
Code Auswählen

2020.05.12 06:52:55 1: HMCCU: [RaspiMatic : 907] Internal RPC server is depricated and will be removed soon. Set ccuflags to procrpc
2020.05.12 06:52:55 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2020.05.12 06:52:55 0: HMCCU: Child process for server CB2001 started with PID 1316176
2020.05.12 06:52:55 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2020.05.12 06:52:55 0: CCURPC: Initializing RPC server CB2001
2020.05.12 06:52:55 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2020.05.12 06:52:55 0: HMCCU: Child process for server CB2010 started with PID 1316177
2020.05.12 06:52:55 0: CCURPC: CB2010 Creating file queue /tmp/ccuqueue_2010_1
2020.05.12 06:52:55 0: CCURPC: Initializing RPC server CB2010
2020.05.12 06:52:55 1: HMCCU: [RaspiMatic : 907] All RPC servers starting
2020.05.12 06:52:55 0: HMCCU: [RaspiMatic] RPC server(s) starting
2020.05.12 06:52:55 0: CCURPC: Callback server created listening on port 7411
2020.05.12 06:52:55 1: CCURPC: CB2001 Adding callback for events
2020.05.12 06:52:55 1: CCURPC: CB2001 Adding callback for new devices
2020.05.12 06:52:55 1: CCURPC: CB2001 Adding callback for deleted devices
2020.05.12 06:52:55 1: CCURPC: CB2001 Adding callback for modified devices
2020.05.12 06:52:55 1: CCURPC: CB2001 Adding callback for replaced devices
2020.05.12 06:52:55 1: CCURPC: CB2001 Adding callback for readded devices
2020.05.12 06:52:55 1: CCURPC: CB2001 Adding callback for list devices
2020.05.12 06:52:55 0: CCURPC: CB2001 Entering server loop
2020.05.12 06:52:55 0: CCURPC: Callback server created listening on port 7420
2020.05.12 06:52:55 1: CCURPC: CB2010 Adding callback for events
2020.05.12 06:52:55 1: CCURPC: CB2010 Adding callback for new devices
2020.05.12 06:52:55 1: CCURPC: CB2010 Adding callback for deleted devices
2020.05.12 06:52:55 1: CCURPC: CB2010 Adding callback for modified devices
2020.05.12 06:52:55 1: CCURPC: CB2010 Adding callback for replaced devices
2020.05.12 06:52:55 1: CCURPC: CB2010 Adding callback for readded devices
2020.05.12 06:52:55 1: CCURPC: CB2010 Adding callback for list devices
2020.05.12 06:52:55 0: CCURPC: CB2010 Entering server loop
2020.05.12 06:53:02 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2020.05.12 06:53:02 0: HMCCU: Received SL event. RPC server CB2010 enters server loop
2020.05.12 06:53:09 1: HMCCU: Registering callback http://192.168.1.10:7411/fh2001 with ID CB2001 at http://192.168.1.12:2001
2020.05.12 06:53:26 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2020.05.12 06:53:26 1: HMCCU: RPC callback with URL http://192.168.1.10:7411/fh2001 initialized
2020.05.12 06:53:26 1: HMCCU: Registering callback http://192.168.1.10:7420/fh2010 with ID CB2010 at http://192.168.1.12:2010
2020.05.12 06:53:26 1: HMCCU: RPC callback with URL http://192.168.1.10:7420/fh2010 initialized
2020.05.12 06:53:26 1: CCURPC: CB2010 ListDevices. Sending init to HMCCU
2020.05.12 06:53:26 2: CCURPC: CB2001 NewDevice received 52 device specifications
2020.05.12 06:53:26 2: CCURPC: CB2010 NewDevice received 52 device specifications
2020.05.12 06:53:31 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2020.05.12 06:53:31 0: HMCCU: Received IN event. RPC server CB2010 initialized.
2020.05.12 06:53:31 1: HMCCU: [RaspiMatic : 907] All RPC servers running
2020.05.12 06:53:31 2: HMCCU: [RaspiMatic : 907] HMCCU: Found no devices to update
2020.05.12 06:54:23 2: HMCCU: [RaspiMatic : 907] HMScript failed. http://192.168.1.12:8181/tclrega.exe: Select timeout/error:
2020.05.12 06:54:23 1: HMCCU: [RaspiMatic : 907] HMCCU: RaspiMatic Execution of CCU script or command failed

Logfile des Raspi:
Code Auswählen
May 12 06:41:02 homematic-raspi syslog.info syslogd started: BusyBox v1.31.1
May 12 06:41:02 homematic-raspi user.notice kernel: klogd started: BusyBox v1.31.1 (2020-04-20 05:38:59 CEST)
May 12 06:41:02 homematic-raspi daemon.info udhcpc[412]: started, v1.31.1
May 12 06:41:02 homematic-raspi daemon.info udhcpc[412]: sending discover
May 12 06:41:02 homematic-raspi daemon.info udhcpc[412]: sending select for 192.168.1.12
May 12 06:41:02 homematic-raspi daemon.info udhcpc[412]: lease of 192.168.1.12 obtained, lease time 864000
May 12 06:41:03 homematic-raspi user.info kernel: [   44.793594] NET: Registered protocol family 10
May 12 06:41:03 homematic-raspi user.info kernel: [   44.796770] Segment Routing with IPv6
May 12 06:41:03 homematic-raspi user.info firewall: configuration set
May 12 06:41:03 homematic-raspi user.notice rfkill: block set for type wlan
May 12 06:41:03 homematic-raspi daemon.info ifplugd(eth0)[495]: ifplugd 0.28 initializing.
May 12 06:41:03 homematic-raspi daemon.info ifplugd(eth0)[495]: Using interface eth0/DC:A6:32:7B:60:5D with driver <bcmgenet> (version: v2.0)
May 12 06:41:03 homematic-raspi daemon.info ifplugd(eth0)[495]: Using detection mode: SIOCETHTOOL
May 12 06:41:03 homematic-raspi daemon.info ifplugd(eth0)[495]: Initialization complete, link beat detected.
May 12 06:41:03 homematic-raspi daemon.info ifplugd(wlan0)[499]: ifplugd 0.28 initializing, using NETLINK device monitoring.
May 12 06:41:03 homematic-raspi daemon.info ifplugd(wlan0)[499]: Using interface wlan0/DC:A6:32:7B:60:5F with driver <brcmfmac> (version: 7.45.154)
May 12 06:41:03 homematic-raspi daemon.info ifplugd(wlan0)[499]: Using detection mode: wireless extension
May 12 06:41:03 homematic-raspi daemon.info ifplugd(wlan0)[499]: Initialization complete, link beat not detected, interface enabled.
May 12 06:41:03 homematic-raspi daemon.info ifplugd(eth0)[495]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
May 12 06:41:03 homematic-raspi daemon.warn ifplugd(eth0)[495]: client: ifup: interface eth0 already configured
May 12 06:41:03 homematic-raspi daemon.info ifplugd(eth0)[495]: Program executed successfully.
May 12 06:41:17 homematic-raspi daemon.notice ntpdate[505]: step time server 131.188.3.222 offset +0.464139 sec
May 12 06:41:23 homematic-raspi daemon.info chronyd[511]: chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP -SCFILTER -SIGND +ASYNCDNS -SECHASH +IPV6 -DEBUG)
May 12 06:41:23 homematic-raspi daemon.err xinetd[536]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
May 12 06:41:23 homematic-raspi daemon.crit xinetd[536]: 536 {init_services} no services. Exiting...
May 12 06:41:23 homematic-raspi user.info root: Updating RF Lan Gateway Coprocessor Firmware
May 12 06:41:23 homematic-raspi user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
May 12 06:41:23 homematic-raspi user.info root: Updating RF Lan Gateway Firmware
May 12 06:41:23 homematic-raspi user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
May 12 06:41:23 homematic-raspi user.info kernel: [   64.698643] eq3loop: created slave mmd_hmip
May 12 06:41:23 homematic-raspi user.info kernel: [   64.698905] eq3loop: created slave mmd_bidcos
May 12 06:41:25 homematic-raspi user.info kernel: [   66.867171] eq3loop: eq3loop_open_slave() mmd_bidcos
May 12 06:41:35 homematic-raspi user.info kernel: [   76.970535] eq3loop: eq3loop_open_slave() mmd_hmip
May 12 06:41:35 homematic-raspi user.info kernel: [   76.970651] eq3loop: eq3loop_close_slave() mmd_hmip
May 12 06:41:35 homematic-raspi user.info kernel: [   76.973080] eq3loop: eq3loop_open_slave() mmd_hmip
May 12 06:41:35 homematic-raspi user.info kernel: [   76.973176] eq3loop: eq3loop_close_slave() mmd_hmip
May 12 06:41:35 homematic-raspi user.info kernel: [   76.978333] eq3loop: eq3loop_open_slave() mmd_hmip
May 12 06:42:05 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:42:29 homematic-raspi daemon.info chronyd[511]: Selected source 157.230.114.16
May 12 06:42:30 homematic-raspi daemon.info chronyd[511]: Selected source 85.209.49.104
May 12 06:42:36 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 04:42:42 homematic-raspi daemon.info : starting pid 946, tty '/dev/null': '/usr/bin/monit -Ic /etc/monitrc'
May 12 06:42:42 homematic-raspi user.info monit[946]: Starting Monit 5.26.0 daemon with http interface at /var/run/monit.sock
May 12 06:42:42 homematic-raspi user.info monit[946]: 'homematic-raspi' Monit 5.26.0 started
May 12 06:43:02 homematic-raspi user.err monit[946]: 'sshdEnabled' status failed (1) -- no output
May 12 06:43:02 homematic-raspi user.err monit[946]: 'hs485dEnabled' status failed (2) -- grep: /var/etc/hs485d.conf: No such file or directory
May 12 06:43:02 homematic-raspi user.err monit[946]: 'hmlangwEnabled' status failed (1) -- no output
May 12 06:43:02 homematic-raspi user.warn monit[946]: 'hasUSB' status failed (1) -- no output
May 12 06:43:02 homematic-raspi user.err monit[946]: Lookup for '/media/usb1' filesystem failed  -- not found in /proc/self/mounts
May 12 06:43:02 homematic-raspi user.err monit[946]: Filesystem '/media/usb1' not mounted
May 12 06:43:02 homematic-raspi user.err monit[946]: 'usb1' unable to read filesystem '/media/usb1' state
May 12 06:43:02 homematic-raspi user.info monit[946]: 'usb1' trying to restart
May 12 06:43:08 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:43:20 homematic-raspi user.warn monit[946]: 'hasUSB' status failed (1) -- no output
May 12 06:43:20 homematic-raspi user.err monit[946]: 'wlan0CheckEnabled' status failed (1) -- no output
May 12 06:43:20 homematic-raspi user.err monit[946]: Filesystem '/media/usb1' not mounted
May 12 06:43:20 homematic-raspi user.err monit[946]: 'usb1' unable to read filesystem '/media/usb1' state
May 12 06:43:20 homematic-raspi user.info monit[946]: 'usb1' trying to restart
May 12 06:43:38 homematic-raspi user.warn monit[946]: 'hasUSB' status failed (1) -- no output
May 12 06:43:38 homematic-raspi user.err monit[946]: Filesystem '/media/usb1' not mounted
May 12 06:43:38 homematic-raspi user.err monit[946]: 'usb1' unable to read filesystem '/media/usb1' state
May 12 06:43:38 homematic-raspi user.info monit[946]: 'usb1' trying to restart
May 12 06:43:39 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:43:56 homematic-raspi user.warn monit[946]: 'hasUSB' status failed (1) -- no output
May 12 06:43:56 homematic-raspi user.err monit[946]: Filesystem '/media/usb1' not mounted
May 12 06:43:56 homematic-raspi user.err monit[946]: 'usb1' unable to read filesystem '/media/usb1' state
May 12 06:43:56 homematic-raspi user.info monit[946]: 'usb1' trying to restart
May 12 06:44:14 homematic-raspi user.err monit[946]: 'hasUSB' status failed (1) -- no output
May 12 06:44:21 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:44:52 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:45:24 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:45:55 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:46:24 homematic-raspi user.warn monit[946]: 'ReGaHss' failed protocol test [HTTP] at [localhost]:8183 [TCP/IP] -- HTTP: Error receiving data -- Resource temporarily unavailable
May 12 06:46:27 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:46:47 homematic-raspi user.warn monit[946]: 'ReGaHss' failed protocol test [HTTP] at [localhost]:8183 [TCP/IP] -- HTTP: Error receiving data -- Resource temporarily unavailable
May 12 06:46:58 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:46:58 homematic-raspi local0.err ReGaHss: ERROR: send() failed (nsize=2627, errno=32, m_sock=11) [Send():iseSysLx.cpp:1606]
May 12 06:46:58 homematic-raspi local0.err ReGaHss: ERROR: send() failed (nsize=2627, errno=32, m_sock=12) [Send():iseSysLx.cpp:1606]
May 12 06:47:10 homematic-raspi user.warn monit[946]: 'ReGaHss' failed protocol test [HTTP] at [localhost]:8183 [TCP/IP] -- HTTP: Error receiving data -- Resource temporarily unavailable
May 12 06:47:30 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:47:32 homematic-raspi user.warn monit[946]: 'ReGaHss' failed protocol test [HTTP] at [localhost]:8183 [TCP/IP] -- HTTP: Error receiving data -- Resource temporarily unavailable
May 12 06:47:55 homematic-raspi user.err monit[946]: 'ReGaHss' failed protocol test [HTTP] at [localhost]:8183 [TCP/IP] -- HTTP: Error receiving data -- Resource temporarily unavailable
May 12 06:47:55 homematic-raspi user.info monit[946]: 'ReGaHss' trying to restart
May 12 06:47:55 homematic-raspi user.info monit[946]: 'ReGaHss' restart: '/etc/init.d/S70ReGaHss restart'
May 12 06:48:01 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:48:05 homematic-raspi user.info ReGaHss: SIGTERM: ReGaHss Halting
May 12 06:48:30 homematic-raspi user.err monit[946]: 'ReGaHss' service restarted 1 times within 1 cycles(s) - exec
May 12 06:48:30 homematic-raspi user.info monit[946]: 'ReGaHss' exec: '/bin/triggerAlarm.tcl ReGaHss restarted WatchDog-Alarm'
May 12 06:48:30 homematic-raspi user.info monit[946]: 'ReGaHss' process is running after previous restart timeout (manually recovered?)
May 12 06:48:32 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:48:48 homematic-raspi user.info monit[946]: 'ReGaHss' connection succeeded to [localhost]:8183 [TCP/IP]
May 12 06:49:04 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:49:45 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:50:17 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:50:48 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:51:20 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:51:51 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:52:23 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:52:54 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:53:26 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:53:57 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:54:29 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:55:00 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:55:32 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:56:03 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:56:35 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:57:06 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:57:38 homematic-raspi user.err rfd: XmlRpc transport error calling listDevices({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:
May 12 06:58:09 homematic-raspi user.err rfd: XmlRpc transport error calling system.listMethods({"RF-70553bbe"}) on http://172.17.0.1:9125/RPC2:

hmserver.log:
Code Auswählen
May 12 06:41:29 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
May 12 06:41:29 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s)
May 12 06:41:29 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String]
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1) 
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 32 classes to Vert.x
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 32 VertxDeployers initialized
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (caac3f02-91aa-4430-abb2-3abd3949dc5e)
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of AccessPointElectroCardioGram succeeded (c987d1bb-7d60-4d9a-a418-ec2c85a2f0d0)
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (f9818f44-daa2-452c-85a3-22ba9de04793)
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of TransactionSubsystemHandler succeeded (9599e7c5-e9c4-43c7-81b6-64a370b775d9)
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (d34367bf-61f4-4b5d-85cf-5ebdec25c1cd)
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of HMIPTRXWriterWorker succeeded (1999c30f-4881-4095-b1b1-1175ecec461e)
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of AccessPointKeyServerWorker succeeded (edcf2552-4740-4c77-93bc-7fefb9d6126b)
May 12 06:41:34 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KeyServerWorker succeeded (7d2c6c16-bbe4-4d9e-bc5a-66129b8994cc)
May 12 06:41:34 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
May 12 06:41:34 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of RouterKeyServerWorker succeeded (b21825ec-0e4e-4f85-9849-dc9c6f67e39e)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (94f241f4-ecd6-41df-aef6-b9ae50b36bb4)
May 12 06:41:35 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-3] SYSTEM: DeviceLiveUpdateSubsystem started
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (93b5ead8-5d80-44e6-a4fd-f7ed8c4135db)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of CheckDeviceExistHandler succeeded (1a4c6f84-6199-4eb1-ad7c-61b03f27ddf2)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (e6da67cd-0bcc-4792-8d52-d3abe04298e2)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (2b71f6db-6535-413d-a37c-af388554901e)
May 12 06:41:35 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-1] SYSTEM: Firmware update directory is set to /etc/config/firmware
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of FirmwareLoaderFileSystem succeeded (e68838d1-8b8c-43d7-b5c0-1301d95d3338)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of RemoteCommAdapterInitialization succeeded (1a430951-97b6-4088-be08-48d50ebcf193)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of IncomingHMIPFrameHandler succeeded (aaf688a3-6c75-4c53-ab73-8256d38f8e7b)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of WebSocketManager succeeded (c5fd80b1-dd00-406b-9200-0577cc06c9fd)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointMessageDispatcher succeeded (25f93f46-e048-4816-89b2-db6ddd35de67)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (4ecd07f5-35b4-4d67-8c7b-2b38aa6dc41d)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of AccessPointWatchdog succeeded (37815221-180d-45b7-86bc-e751c68c07c4)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointCommDevice succeeded (2b87ab19-8659-4c4d-9877-d837b623d936)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointAuthorisationHandler succeeded (360208a1-7856-4c73-9625-fa2274599495)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of BackendCommandHandler succeeded (e2fd3b2f-12aa-4fea-acbd-f8c7d81f6e92)
May 12 06:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerAdapterInitialization succeeded (1e97609e-b200-4cd8-ba37-6a21573a5785)
May 12 06:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App
May 12 06:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started
May 12 06:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ...
May 12 06:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 11970224...
May 12 06:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A0001F5A4993FE77 to 3
May 12 06:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version...
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 4.0.20
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.1
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.40.1
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: CC1310
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 2048
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 145373
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A0001F5A4993FE77 initialized
May 12 06:41:36 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
May 12 06:41:37 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-4] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware
May 12 06:41:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (bc2cdf00-a039-4c0a-9f8a-40994a4b0dfd)
May 12 06:41:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Checking all devices on all accesspoints for updates
May 12 06:41:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updatable devices (RF)
May 12 06:41:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
May 12 06:41:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of RemoteCommAdapterFinalization succeeded (d1a58adc-1c5f-4f9c-b932-626e73bd9573)
May 12 06:41:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyNotificationHandler succeeded (44f41494-2d17-45dd-a09a-32b682518946)
May 12 06:41:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyBackendNotificationHandler succeeded (f59b1d06-b1f1-407f-83b2-9d5bd98a047f)
May 12 06:41:37 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 -> 192.168.1.12
May 12 06:41:39 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-2] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168.1.12)
May 12 06:41:39 de.eq3.cbcs.lib.hmiptrxcommadapter.internal.RoutingSubsystem WARN  [Thread-6] Received routing key 36C961302A28F480DAF53E90F1F1A543
May 12 06:41:39 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-3] UDP Routing multi cast established on network interface eth0 : 192.168.1.12
May 12 06:41:39 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-4] SYSTEM: Started Access Point WebSocket server with port 9293
May 12 06:41:39 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-4] SYSTEM: connector open
May 12 06:41:39 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyAPIWorker succeeded (28e46169-3db9-48d6-9300-72f53189e452)
May 12 06:41:39 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LanRoutingWorker succeeded (eb22051d-366b-4493-a77e-a71ca6b2ac9c)
May 12 06:41:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (7f864cff-f7f7-4c76-b9bc-a0af0a784948)
May 12 06:41:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
May 12 06:41:40 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
May 12 06:41:44 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
May 12 06:41:44 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000
May 12 06:41:44 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000
May 12 06:41:44 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of BackendWorker succeeded (b85b6ff7-5df4-4265-ad74-a497887ffe33)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of StorageRequestWorker succeeded (4b461bc5-2fb2-4344-9296-99f2a2a371fc)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of EnergyPriceRequestWorker succeeded (eb8d4137-9c7a-4045-90cf-5e67cf10ea47)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CouplingRequestWorker succeeded (c69ae4df-daa8-4751-a8c1-767c893b9e41)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (18f738f9-84a5-48df-a992-4d9559159655)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of RegaClientWorker succeeded (4a785fb4-6956-4551-9577-62796c80ac60)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (77c01a2e-e440-42a4-ba56-83958e48228a)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DiagramRequestWorker succeeded (6f3ac956-0244-4fd3-b2d8-ee3540986602)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of GroupRequestWorker succeeded (529c73c6-e275-4b25-9020-c3a38c2b98a1)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (41338939-55ca-4077-8969-32a1e41f687f)
May 12 06:41:44 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
May 12 06:41:44 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292
May 12 06:41:44 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration
May 12 06:41:44 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher
May 12 06:41:44 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache
May 12 06:42:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider
May 12 06:42:36 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:42:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder
May 12 06:42:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega
May 12 06:42:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService
May 12 06:42:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher
May 12 06:42:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler
May 12 06:42:36 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing...
May 12 06:42:36 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
May 12 06:42:36 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
May 12 06:42:36 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider
May 12 06:42:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler
May 12 06:42:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler
May 12 06:42:37 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos
May 12 06:42:37 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished
May 12 06:42:37 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: HmIP-RF_java
May 12 06:42:37 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-3] updateDevicesForClient HmIP-RF_java -> 52 device addresses will be added
May 12 06:42:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done
May 12 06:43:06 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:43:39 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999
May 12 06:43:39 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] Added InterfaceId: 1008
May 12 06:43:39 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-12] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
May 12 06:43:39 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:43:49 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:43:49 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999
May 12 06:43:49 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] init finished
May 12 06:43:49 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: 1009
May 12 06:44:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:44:19 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:44:52 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:44:52 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:45:22 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:45:22 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:45:55 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:45:55 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:46:25 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:46:25 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:46:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue
May 12 06:46:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
May 12 06:46:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used
May 12 06:46:58 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:46:58 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:47:28 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:47:28 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:48:01 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:48:01 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:48:31 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:48:31 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:49:04 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999
May 12 06:49:04 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] Added InterfaceId: 1008
May 12 06:49:04 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-13] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
May 12 06:49:04 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:49:14 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:49:14 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999
May 12 06:49:14 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] init finished
May 12 06:49:14 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-1] Added InterfaceId: 1009
May 12 06:49:44 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:49:44 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:50:17 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:50:17 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:50:47 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:50:47 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:51:20 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:51:20 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:51:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue
May 12 06:51:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
May 12 06:51:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used
May 12 06:51:35 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-1] SYSTEM: Access Point Watchdog running periodic connection check...
May 12 06:51:50 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:51:50 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:52:23 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:52:23 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:52:53 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:52:53 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:53:26 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.1.10:7420/fh2010
May 12 06:53:26 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished
May 12 06:53:26 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: CB2010
May 12 06:53:26 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:53:26 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-0] updateDevicesForClient CB2010 -> 52 device addresses will be added
May 12 06:53:26 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:53:56 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:53:56 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:54:29 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:54:29 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:54:59 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:54:59 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:55:32 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:55:32 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:56:02 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:56:02 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:56:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue
May 12 06:56:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
May 12 06:56:35 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used
May 12 06:56:35 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:56:35 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:57:05 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:57:05 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125
May 12 06:57:38 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://openhab.validation:1000
May 12 06:57:38 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://openhab.validation:1000
May 12 06:58:08 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://172.17.0.1:9125
May 12 06:58:08 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://172.17.0.1:9125

Was ich schon versucht habe:

  • RaspiMatic neu aufspielen
  • SD-Karte ersetzen
  • Raspi-Hardware komplett austauschen
  • Das Internet nach Lösungen durchwühlen

Ich bin ja ein zäher Hund, was solche Probleme angeht, aber hier sehe ich einfach kein Land. Ist das normal, dass so ein RaspiMatic-Raspberry PI 4 alle Nase lang einfriert? Was mache ich falsch?
Danke im Voraus für jede Hilfe!

Viele Grüße
der drache

iBeSmart

#1
12 Mai 2020, 19:10:45
Hi,

läuft denn die RaspberryMatic ohne HMCCU fehlerfrei ?

drache

#2
06 Juni 2020, 15:56:35
Falls jemand über diesen Beitrag stolpert und das gleiche Problem hat, hier eine Zusammenfassung der Ereignisse.

Ohne HMCCU funktionierte der Raspi einwandfrei, aber sobald die Verbindung aufgebaut wurde, gingen die Probleme los.
Letztendlich war die Ursache, dass ich in FHEM konfiguriert hatte, dass ich HomeMatic und HomeMatic IP nutzen möchte, aber zu dem Zeitpunkt hatte ich nur einen HmIP-Sensor verbunden. Meine Hm-Komponenten wollte ich erst umziehen, sobald das System verlässlich lief. Das war ein Fehler. Als ein Hm-Sensor mit gekoppelt war, hat FHEM den Raspi nicht mehr in den Tod gerissen.

Mir ist es nach wie vor unbegreiflich, wie das sein kann, dass das Lauschen auf nicht vorhandene Komponenten alles zum Absturz bringt.
Mittlerweile läuft aber alles einwandfrei und der alte HMLAN-Adapter wird nicht mehr gebraucht.
Ich hoffe, das hilft jemandem weiter. Nicht aufgeben!

Viele Grüße
der Drache
Drucken
Nach oben Seiten1
Benutzer-Aktionen