NEWS
Ziel aio IOBroker mit pivccu Pi HM-MOD-RPI-PCB Module und zigbee cc2531
-
hallo zusammen,
kurze Schilderung der Ausgangssituation bzw Zielsetzung:
stretch lite mit IoBroker und pivccu mit Pi HM-MOD-RPI-PCB Module und zigbee cc2531 das alles auf einem Raspberry Pi 3 Model B Plus Rev 1.3
Wo stehe ich:
-
erster Versuch mit dem aio Image aus dem Downloadbereich, lief alles durch nur massive Probleme mit pivccu (dazu weiter unten mehr), io lief einwandfrei auch der zigbee cc2531 wurde erkannt.
-
alles "selber" machen, aktuelles stretch dann pivccu installiert und den ioBroker. Gleiches Ergebnis wie beim ersten Versuch.
Das Problem ist, dass ich im pivccu immer ReGa Probleme bekomme.
` > ReGaEine Komponente der HomeMatic Zentrale reagiert nicht mehr. `
Mein verdacht ist, dass es was mit dem Modul und dem Stick zutun hat aber keinen Ansatz finde wie ich dem Problem auf die Spur kommeDie CCU ist auch fast nicht erreichbar und in der App komm die Meldung mit zu vielen Benutzern angemeldet
Ausgabe
sudo pivccu-attach cat /var/log/messages
Aug 19 11:21:09 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2 Aug 19 11:21:09 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2018-07-03 14:19:59 CEST) Aug 19 09:21:09 homematic-ccu2 daemon.info ifplugd(eth0)[117]: ifplugd 0.28 initializing. Aug 19 09:21:09 homematic-ccu2 daemon.info ifplugd(eth0)[117]: Using interface eth0/7A:A5:3D:4F:03:E2 with driver <veth>(version: 1.0) Aug 19 09:21:09 homematic-ccu2 daemon.info ifplugd(eth0)[117]: Using detection mode: SIOCETHTOOL Aug 19 09:21:09 homematic-ccu2 daemon.info ifplugd(eth0)[117]: Initialization complete, link beat detected. Aug 19 09:21:09 homematic-ccu2 daemon.warn ifplugd(eth0)[117]: Could not open /dev/tty, cannot beep. Aug 19 09:21:09 homematic-ccu2 daemon.info ifplugd(eth0)[117]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Aug 19 09:21:09 homematic-ccu2 daemon.warn ifplugd(eth0)[117]: client: net.ipv4.tcp_timestamps = 0 Aug 19 09:21:09 homematic-ccu2 daemon.warn ifplugd(eth0)[117]: client: eth0 carrier detected Aug 19 09:21:09 homematic-ccu2 daemon.info ifplugd(eth0)[117]: Program executed successfully. Aug 19 11:21:10 homematic-ccu2 user.debug setclock: Try to get time from 0.de.pool.ntp.org Aug 19 11:21:11 homematic-ccu2 user.debug setclock: Try to get time from 192.168.0.1 Aug 19 11:21:11 homematic-ccu2 user.debug setclock: Sun Aug 19 11:21:11 CEST 2018 Aug 19 09:21:15 homematic-ccu2 auth.info sshd[198]: Server listening on 0.0.0.0 port 22. Aug 19 09:21:15 homematic-ccu2 auth.info sshd[198]: Server listening on :: port 22. Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: write_pid /var/run/cuxd.pid [210] Aug 19 11:21:15 homematic-ccu2 user.info homematic: started cux-daemon Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: system(touch /dev/ttyUSB0) Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: CUx-Daemon(2.1.0) on CCU(2.35.16) start PID:210 Aug 19 09:21:15 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:1741 update(-39s):Sun Aug 19 11:20:36 2018 Aug 19 09:21:15 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3 Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: 3 device-paramset(s) loaded ok! Aug 19 09:21:15 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: write_proxy /var/cache/cuxd_proxy.ini (210 /usr/local/addons/cuxd/ 2.1.0 2.35.16 0) Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: add interface 'CUxD' Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: write interface(1) 'BidCos-RF' to /usr/local/etc/config/InterfacesList.xml Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: write interface(2) 'VirtualDevices' to /usr/local/etc/config/InterfacesList.xml Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: write interface(3) 'HmIP-RF' to /usr/local/etc/config/InterfacesList.xml Aug 19 11:21:15 homematic-ccu2 daemon.info cuxd[210]: write interface(4) 'CUxD' to /usr/local/etc/config/InterfacesList.xml Aug 19 09:21:15 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf Aug 19 09:21:15 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware Aug 19 09:21:15 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf Aug 19 11:21:35 homematic-ccu2 user.info kernel: [ 48.873356] eq3loop: eq3loop_close_slave() ttyS0 Aug 19 11:21:35 homematic-ccu2 user.info kernel: [ 48.883333] eq3loop: eq3loop_open_slave() ttyS0 Aug 19 11:21:35 homematic-ccu2 user.notice kernel: [ 48.885544] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D Aug 19 11:21:42 homematic-ccu2 daemon.warn cuxd[210]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request Aug 19 11:21:44 homematic-ccu2 daemon.warn cuxd[210]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request Aug 19 11:21:57 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=TEMPERATURE failed getting physical value. Aug 19 11:21:57 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"NEQ0533403:3","TEMPERATURE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605] Aug 19 11:21:57 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:21:57 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130] Aug 19 11:21:59 homematic-ccu2 local0.err ReGaHss: Error: IseESP::ScriptRuntimeError: var url = "http://api.wunderground.com/api/eaf556bdcca41a3c/conditions/lang:DL/q/Germany/Gommersheim.xml"; !hier ist die Abfrage mit CUxD !dom.GetObject("CUxD.CUX2801001:1 Aug 19 11:22:00 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value. Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"MEQ0477222:7","DECISION_VALUE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130] Aug 19 11:22:00 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value. Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"MEQ0477255:7","DECISION_VALUE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130] Aug 19 11:22:00 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value. Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"MEQ0477580:7","DECISION_VALUE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130] Aug 19 11:22:00 homematic-ccu2 daemon.warn cuxd[210]: use CUX2801001:1.CMD_QUERY_RET=1 to activate CUX2801001:1.CMD_RETS command! Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"CUX2801001:1","CMD_RETS"} result= [faultCode:-4,faultString:"Unknown parameter"] [iseXmlRpc.cpp:2605] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = [iseDOMdpHSS.cpp:130] Aug 19 11:22:00 homematic-ccu2 daemon.warn cuxd[210]: use CUX2801001:1.CMD_QUERY_RET=1 to activate CUX2801001:1.CMD_RETL command! Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"CUX2801001:1","CMD_RETL"} result= [faultCode:-4,faultString:"Unknown parameter"] [iseXmlRpc.cpp:2605] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:22:00 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = [iseDOMdpHSS.cpp:130] Aug 19 11:22:07 homematic-ccu2 daemon.info cuxd[210]: INIT 'xmlrpc_bin://127.0.0.1:1999' '2045' Aug 19 11:24:01 homematic-ccu2 cron.info crond[71]: crond: USER root pid 721 cmd /usr/local/addons/hm-watchdog/bin/hm-watchdog.sh 2>&1 >/dev/null Aug 19 11:24:01 homematic-ccu2 user.info ReGaHss: SIGTERM: ReGaHss Halting Aug 19 11:24:04 homematic-ccu2 user.warn hm-watchdog: ReGaHss restarted Aug 19 11:24:04 homematic-ccu2 local0.err ReGaHss: Error: IseESP::ScriptRuntimeError: dom.GetObject("Alarmzone 1").State(true); dom.GetObject("Alarmzone 1").DPInfo("hm-watchdog: ReGaHss restarted"); [iseESPexec.cpp:12500] Aug 19 11:24:05 homematic-ccu2 local0.err ReGaHss: Error: Bind socket failed (errno=98, port=8183, address=0)! [iseSysLx.cpp:1379] Aug 19 11:24:05 homematic-ccu2 local0.err ReGaHss: Error: Binding listener to port 8183 failed! {"HTTP-Listener"} [httpListener.cpp:62] Aug 19 11:24:06 homematic-ccu2 user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"1007","MEQ0477222:2","ACTUAL_TEMPERATURE",24.700000}]}) on binary://127.0.0.1:1999/RPC2: Aug 19 11:24:06 homematic-ccu2 user.err rfd: XmlRpc transport error Aug 19 11:24:06 homematic-ccu2 user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"1007","MEQ0477222:2","ACTUAL_HUMIDITY",55.000000}],[methodName:"event",params:{"1007","MEQ0477222:2","SET_TEMPERATURE",4.500000}],[methodName:"event",params:{"1007","M Aug 19 11:24:06 homematic-ccu2 user.err rfd: XmlRpc transport error Aug 19 11:24:09 homematic-ccu2 user.err rfd: XmlRpcClient error calling event({[methodName:"event",params:{"1007","LTK0120392:2","BOOT",true}],[methodName:"event",params:{"1007","LTK0120392:2","ENERGY_COUNTER",1709.700000}],[methodName:"event",params:{"1007","LTK0120392:2"," Aug 19 11:24:09 homematic-ccu2 user.err rfd: XmlRpc transport error Aug 19 11:24:14 homematic-ccu2 local0.err ReGaHss: Error: IseESP::ScriptRuntimeError: var url = "http://api.wunderground.com/api/eaf556bdcca41a3c/conditions/lang:DL/q/Germany/Gommersheim.xml"; !hier ist die Abfrage mit CUxD !dom.GetObject("CUxD.CUX2801001:1 Aug 19 11:24:15 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value. Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"MEQ0477255:7","DECISION_VALUE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605] Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130] Aug 19 11:24:15 homematic-ccu2 daemon.warn cuxd[210]: use CUX2801001:1.CMD_QUERY_RET=1 to activate CUX2801001:1.CMD_RETS command! Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"CUX2801001:1","CMD_RETS"} result= [faultCode:-4,faultString:"Unknown parameter"] [iseXmlRpc.cpp:2605] Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = [iseDOMdpHSS.cpp:130] Aug 19 11:24:15 homematic-ccu2 daemon.warn cuxd[210]: use CUX2801001:1.CMD_QUERY_RET=1 to activate CUX2801001:1.CMD_RETL command! Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"CUX2801001:1","CMD_RETL"} result= [faultCode:-4,faultString:"Unknown parameter"] [iseXmlRpc.cpp:2605] Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432] Aug 19 11:24:15 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = [iseDOMdpHSS.cpp:130] Aug 19 11:24:22 homematic-ccu2 daemon.info cuxd[210]: INIT 'xmlrpc_bin://127.0.0.1:1999' '2045'</veth>
Ausgabe
sudo pivccu-attach cat /var/log/hmserver.log
Aug 19 11:21:25 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory Aug 19 11:21:25 de.eq3.lib.util.dynamics.GenericFactory INFO [main] creating instance of HMServerConfiguration with no-arg constructor Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 20 classes to Vert.x Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 20 VertxDeployers initialized Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (3103ec8e-3c3b-4ba3-bb46-557172d15692) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (9a6f393a-47eb-4ec8-8698-24c4cf849deb) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (099299eb-f008-4052-8db7-8d437d44a7af) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of TransactionSubsystemHandler succeeded (7f405870-fcb7-4bc9-aab1-050b3e7f034e) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of CheckDeviceExistHandler succeeded (3eb8ec50-d01f-47bc-bc5d-d82b97fada9e) Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (c0eeba23-6b26-4a13-9f18-da7b0e1c4026) Aug 19 11:21:33 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL Aug 19 11:21:33 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of KeyServerWorker succeeded (f1282c37-096e-4153-81cb-faa2aee29e83) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of KryoPersistenceWorker succeeded (3b794115-b02e-4a42-8145-673076ef2f20) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerPersistentDataLoader succeeded (3a3d1f65-7cfc-4414-a9c1-681dda87d62f) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (6e25d646-7bea-4713-af1c-f4d1fcd8bb87) Aug 19 11:21:34 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-3] SYSTEM: Firmware update directory is set to /etc/config/firmware Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of FirmwareLoaderFileSystem succeeded (371a579b-a74b-42f1-82a8-54f244a81416) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of BackendCommandHandler succeeded (b49f4034-a0e8-45c6-908b-4adeb45c0fb7) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of IncomingHMIPFrameHandler succeeded (1fc69772-1de0-4589-b951-457211d9fc68) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (95713be0-b888-4b1c-a750-528ee52145a7) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LegacyNotificationHandler succeeded (4c9dc665-1efc-4ad5-af95-5db15a5c6ef1) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of LegacyBackendNotificationHandler succeeded (e3ee9c4f-39be-430d-b345-9cd44e0e10b5) Aug 19 11:21:34 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LegacyAPIWorker succeeded (ea8b526f-9723-4291-b91c-f24c98f92c3d) Aug 19 11:21:35 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerAdapterInitialization succeeded (f6b36f51-8327-4690-8362-0bdce0b874af) Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRX_App Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ... Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 11828372... Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A061A7D5699DBD40 to 3 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version... Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 2.8.6 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.3 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.20.3 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] MCU type: Si1002_8051 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Duty Cycle: 0.0 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] set DutyCycle limit to ffffffc8 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set Duty Cycle Limit Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Current Security Counter: 319483392 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Update security counter to calculation: 319483743 Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter has no linkpartner Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Adapter with Access Point id 3014F711A061A7D5699DBD40 initialized Aug 19 11:21:35 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized Aug 19 11:21:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (566ceb0e-acff-4d80-902f-5281c0c14cc3) Aug 19 11:21:36 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-5] SYSTEM: Checking all devices on all accesspoints for updates Aug 19 11:21:36 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-5] SYSTEM: There are 0 APs queued with updatable devices Aug 19 11:21:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyInitializion succeeded (382c5d87-a102-42ce-8516-8c09fc6cc41d) Aug 19 11:21:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ Aug 19 11:21:37 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bind XML-RPC api to port 2010 Aug 19 11:21:40 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Default MaxEventLoopExecuteTime: 2000000000 Aug 19 11:21:40 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Default BlockedThreadCheckInterval: 1000 Aug 19 11:21:40 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Default MaxWorkerExecuteTime: 60000000000 Aug 19 11:21:40 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Default EventLoopPoolSize: 8 Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [RegaClientWorker] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: deploying 9 classes to Vert.x Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: 9 VertxDeployers initialized Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of BackendWorker succeeded (f586706e-4c39-4267-b596-3dbba4f8ed4b) Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (1d827e73-a10e-457d-a171-4420dc54b177) Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of RegaClientWorker succeeded (96bae43a-8ac1-4b3a-adb1-b369bb46ab15) Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of EnergyPriceRequestWorker succeeded (f60fb556-0e5c-4b9f-849f-577fa0d59b63) Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of CouplingRequestWorker succeeded (1b403fb6-a65a-471e-9500-9792717b2738) Aug 19 11:21:40 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of StorageRequestWorker succeeded (ae3fdeb3-9e52-4ed5-b711-5ebac3033f7f) Aug 19 11:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of DiagramRequestWorker succeeded (01b20db3-f0ae-4fff-9b23-af27cac13536) Aug 19 11:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of GroupRequestWorker succeeded (0c507625-d972-4e2d-817c-0d18eecbfed4) Aug 19 11:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (d7fc8f35-af23-4cdd-aa2f-3b7e9919bd7a) Aug 19 11:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-2] SYSTEM: initial deployment complete _____________________________________________________ Aug 19 11:21:41 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Starting HMServer at 127.0.0.1:9292 Aug 19 11:21:41 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Read Configuration Aug 19 11:21:41 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create Bidcos Dispatcher Aug 19 11:21:41 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] InitBidCosCache Aug 19 11:21:42 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create groupDefinitionProvider Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create VirtualDeviceHolder Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create VirtualDeviceHandlerRega Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create GroupAdministrationService Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create GroupDeviceDispatcher Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create GroupDeviceHandler Aug 19 11:21:43 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-2] @GroupDeviceHandler - initializing... Aug 19 11:21:43 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-2] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) Aug 19 11:21:43 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-2] --> created virtualDeviceHandler (GroupDeviceService to ReGa) Aug 19 11:21:43 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-2] --> got groupDefinitionProvider Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create BidCosGroupMemberProvider Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Init groupAdministrationService Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Init Virtual OS Device Aug 19 11:21:43 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Init ESHLight Bridge Aug 19 11:21:44 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create RrdDatalogging Aug 19 11:21:44 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create MeasurementService Aug 19 11:21:44 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Init MeasurementService Aug 19 11:21:44 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create HTTP Server Aug 19 11:21:44 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create BidCos context and start handler Aug 19 11:21:44 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Create group context and start handler Aug 19 11:21:44 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:9292/bidcos Aug 19 11:21:44 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] init finished Aug 19 11:21:44 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-2] Added InterfaceId: HmIP-RF_java Aug 19 11:21:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-2] Starting HMServer done Aug 19 11:21:57 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-1] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999 Aug 19 11:21:57 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-1] Added InterfaceId: 1008 Aug 19 11:21:57 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-9] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand Aug 19 11:22:07 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:1999 Aug 19 11:22:07 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-3] init finished Aug 19 11:22:07 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-4] Added InterfaceId: 4221 Aug 19 11:24:12 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-1] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999 Aug 19 11:24:12 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-1] Added InterfaceId: 1008 Aug 19 11:24:12 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-10] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand Aug 19 11:24:22 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:1999 Aug 19 11:24:22 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-4] init finished Aug 19 11:24:22 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-4] Added InterfaceId: 4221 Aug 19 11:26:34 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-5] SYSTEM: 0 Accesspoints in Queue Aug 19 11:26:34 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-5] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used Aug 19 11:26:34 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-5] SYSTEM: Eventlistener Handler utilization: 0/50 used Aug 19 11:27:12 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-1] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999 Aug 19 11:27:12 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-1] Added InterfaceId: 1008 Aug 19 11:27:12 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-11] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Bin für jede Hilfe oder Tipp dankebar,
Gruß anselra
-
-
-
Hallo Rainer,
@Home für Homematic (Apple)
Gruß Ralf
-
Der Absturz der Rega liegt definitiv in der (piV)CCU begründet.
Ich bin da nicht so fit drin, villeicht meldet sich Alex (@deimos) ja noch.
Hast du die richtige CuxD-Version?
Gruß
Rainer
-
Danke, Ich habe die
CuXD Version 2.1.0 (für ccu2 da ich von einem Raspmatic System umgezogen bin musst diese installieren nach der Rückspielen der Sicherung)
CCU-Firmware: 2.35.16 (pivccu)
Gruß Ralf
-
CuXD Version 2.1.0 (für ccu2 `
Darauf kommt es an, dennda ich von einem Raspmatic System umgezogen bin `
Das war meine Vermutung, deswegen die Frage.nach der Rückspielen der Sicherung `
aber CuxD wurde vor Erstellung des Backups auf RaspiMatic entfernt, oder?
Gruß
Rainer
-
nein CUXD habe ich auf Raspmatic nicht deinstalliert sondern mit der Sicherung in die pivccu eingespielt.
Dort dann die CUXD gelöscht, reboot und dann die CUXD 2.1.0 für CCU2 installiert.
Meinst du, dass ist das Problem?
Ich kann eine Sicherung ohne CUXD erstellen und einspielen, hast du einen Tipp was ich auf dem pivccu alles löschen soll,
Danke
Gruß Ralf
-
Hallo zusammen
So nachgefühlt unzähligen Installationen läuft das System jetzt,
allerdings nicht auf dem
Raspberry Pi 3 Model B Plus Rev 1.3
die Anleitung von
> [https://github.com/alexreinert/piVCCU/b … berrypi.md](https://github.com/alexreinert/piVCCU/blob/master/docs/setup/raspberrypi.md)
schritt für schritt befolgt habe mit Option 1 und auch mit Option 2sondern auf dem
Raspberry Pi 2 Model B Rev 1.1
mit der Sicherung hat es auch nichts zutun da man die CUxD einfach darüber installieren kann.
was man tun kann um die Meldung im Syslog
homematic-ccu2 daemon.err cuxd[209]: USB(1-1.4) mknod '/dev/ttyACM0' error!
zu entfernen ist im Setup des CUxD folgendes einzugeben.
TTYPARAM=NONE
dies wird m.E. nur benötigt wenn der CC2531 Stick dran hängt
vllt hilft dies ja dem ein oder andern
Gruß Ralf