Problem bei der Umstellung von CCU2 auf pivccu

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

demel42
Beiträge: 147
Registriert: 12.11.2017, 20:35
Hat sich bedankt: 4 Mal
Danksagung erhalten: 9 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von demel42 » 17.10.2018, 18:08

ich habe eine SD-KArte, auf der ich schon ein PIVCCU mit der Version 2 habe. Damit hatte ich das gestern auch mal versucht, hatte aber keine Erfolg gesehen. War aber vielleicht schon zu müde.

Macht es Sinn, wenn ich das mal mit dieser Version probieren (also alles löschen und Backup neu einspielen)?

demel
Raspberrymatic 3.67.10.20230225 unter Proxmox (HM und HmIP) - IP-Symcon 6.3 auf Ubuntu 18.04.3 unter Proxmox - Mediola Gateway V5+, Warema WMS

Benutzeravatar
deimos
Beiträge: 5383
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 950 Mal
Kontaktdaten:

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von deimos » 17.10.2018, 22:26

Hi,

dukannst mir das Backup einfach üer PN schicken.

Viele Grüße
Alex

demel42
Beiträge: 147
Registriert: 12.11.2017, 20:35
Hat sich bedankt: 4 Mal
Danksagung erhalten: 9 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von demel42 » 18.10.2018, 07:50

Da sich mit dem PIVCCU3-Container auch heute morgen keine Änderung ergeben hatte, habe ich den raspi wieder mit der SD-Karte mit dem PIVCCU-Container gestartet.

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 2.35.16-35
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi3 UART:  Assigned to GPIO pins
HMRF Hardware:  unknown
HMIP Hardware:  unknown
Board serial:   unknown
Radio MAC:      unknown
SGTIN:          unknown
State:          RUNNING
PID:            1626
IP:             192.168.178.60
CPU use:        60.87 seconds
BlkIO use:      5.48 MiB
Link:           vethpivccu
 TX bytes:      9.38 MiB
 RX bytes:      2.33 MiB
 Total bytes:   11.71 MiB

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-attach cat /var/hm_mode
cat: can't open '/var/hm_mode': No such file or directory

Code: Alles auswählen

Oct 18 07:31:34 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Oct 18 07:31:34 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2018-07-03 14:19:59 CEST)
Oct 18 05:31:34 homematic-ccu2 daemon.info ifplugd(eth0)[114]: ifplugd 0.28 initializing.
Oct 18 05:31:34 homematic-ccu2 daemon.info ifplugd(eth0)[114]: Using interface eth0/0A:03:4D:11:24:6F with driver <veth> (version: 1.0)
Oct 18 05:31:34 homematic-ccu2 daemon.info ifplugd(eth0)[114]: Using detection mode: SIOCETHTOOL
Oct 18 05:31:34 homematic-ccu2 daemon.info ifplugd(eth0)[114]: Initialization complete, link beat detected.
Oct 18 05:31:34 homematic-ccu2 daemon.warn ifplugd(eth0)[114]: Could not open /dev/tty, cannot beep.
Oct 18 05:31:34 homematic-ccu2 daemon.info ifplugd(eth0)[114]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Oct 18 05:31:34 homematic-ccu2 daemon.warn ifplugd(eth0)[114]: client: net.ipv4.tcp_timestamps = 0
Oct 18 05:31:34 homematic-ccu2 daemon.warn ifplugd(eth0)[114]: client: eth0 carrier detected
Oct 18 07:31:34 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Oct 18 05:31:34 homematic-ccu2 daemon.info ifplugd(eth0)[114]: Program executed successfully.
Oct 18 07:31:34 homematic-ccu2 user.debug setclock: Thu Oct 18 07:31:34 CEST 2018
Oct 18 05:31:39 homematic-ccu2 auth.info sshd[188]: Server listening on 0.0.0.0 port 22.
Oct 18 05:31:39 homematic-ccu2 auth.info sshd[188]: Server listening on :: port 22.
Oct 18 05:31:39 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Oct 18 05:31:39 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Oct 18 05:31:39 homematic-ccu2 user.info update-coprocessor: performGatewayCoproUpdate(): updating OEQ0797337
Oct 18 05:31:41 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: OEQ0797337
Oct 18 05:31:41 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: OEQ0797337
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: (OEQ0797337) CCU2CommControllerMod::handleIdentifyEvent(): Coprocessor is in application.
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::CCU2CoprocessorCommandMod(): System frame
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::isResponseStatusOk(): System status OK
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: CCU2CommControllerMod::handleIncomingResponse() System response OK
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: (OEQ0797337) CCU2CommControllerMod::handleIdentifyEvent(): Coprocessor is in application.
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: CoprocessorUpdate::startApplication():Coprocessor entered application.
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::CCU2CoprocessorCommandMod(): System frame
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::isResponseStatusOk(): System status OK
Oct 18 05:31:43 homematic-ccu2 user.debug update-coprocessor: CCU2CommControllerMod::handleIncomingResponse() System response OK
Oct 18 05:31:43 homematic-ccu2 user.info update-coprocessor: Version: 1.4.1
Oct 18 05:31:43 homematic-ccu2 user.info update-coprocessor: Coprocessor firmware not necessary.
Oct 18 05:31:43 homematic-ccu2 user.info update-coprocessor: performGatewayCoproUpdate(): updating OEQ0796800
Oct 18 05:31:45 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: OEQ0796800
Oct 18 05:31:46 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: OEQ0796800
Oct 18 05:31:47 homematic-ccu2 user.debug update-coprocessor: (OEQ0796800) CCU2CommControllerMod::handleIdentifyEvent(): Coprocessor is in application.
Oct 18 05:31:47 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::CCU2CoprocessorCommandMod(): System frame
Oct 18 05:31:47 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::isResponseStatusOk(): System status OK
Oct 18 05:31:47 homematic-ccu2 user.debug update-coprocessor: CCU2CommControllerMod::handleIncomingResponse() System response OK
Oct 18 05:31:47 homematic-ccu2 user.debug update-coprocessor: (OEQ0796800) CCU2CommControllerMod::handleIdentifyEvent(): Coprocessor is in application.
Oct 18 05:31:47 homematic-ccu2 user.debug update-coprocessor: CoprocessorUpdate::startApplication():Coprocessor entered application.
Oct 18 05:31:48 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::CCU2CoprocessorCommandMod(): System frame
Oct 18 05:31:48 homematic-ccu2 user.debug update-coprocessor: CCU2CoprocessorCommandMod::isResponseStatusOk(): System status OK
Oct 18 05:31:48 homematic-ccu2 user.debug update-coprocessor: CCU2CommControllerMod::handleIncomingResponse() System response OK
Oct 18 05:31:48 homematic-ccu2 user.info update-coprocessor: Version: 1.4.1
Oct 18 05:31:48 homematic-ccu2 user.info update-coprocessor: Coprocessor firmware not necessary.
Oct 18 05:31:48 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Oct 18 05:31:48 homematic-ccu2 user.info update-lgw-firmware: LAN Gateway Firmware Update...
Oct 18 05:31:48 homematic-ccu2 user.info update-lgw-firmware: Gateway OEQ0797337
Oct 18 05:31:50 homematic-ccu2 user.info update-lgw-firmware: Gateway type is eQ3-HM-LGW-App
Oct 18 05:31:50 homematic-ccu2 user.info update-lgw-firmware: Available Firmware Version:   1.1.5
Oct 18 05:31:50 homematic-ccu2 user.info update-lgw-firmware: Lan Gateway Firmware Version: 1.1.5
Oct 18 05:31:50 homematic-ccu2 user.info update-lgw-firmware: Firmware is up to date
Oct 18 05:31:50 homematic-ccu2 user.info update-lgw-firmware: LAN Gateway Firmware Update...
Oct 18 05:31:50 homematic-ccu2 user.info update-lgw-firmware: Gateway OEQ0796800
Oct 18 05:31:52 homematic-ccu2 user.info update-lgw-firmware: Gateway type is eQ3-HM-LGW-App
Oct 18 05:31:52 homematic-ccu2 user.info update-lgw-firmware: Available Firmware Version:   1.1.5
Oct 18 05:31:52 homematic-ccu2 user.info update-lgw-firmware: Lan Gateway Firmware Version: 1.1.5
Oct 18 05:31:52 homematic-ccu2 user.info update-lgw-firmware: Firmware is up to date
Oct 18 05:31:52 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Oct 18 05:31:52 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Oct 18 07:31:52 homematic-ccu2 user.info multimac: Copro application running.
Oct 18 07:31:52 homematic-ccu2 user.info multimac: Vapp=030408 Vbl=010001 Vhmos=012200
Oct 18 07:31:52 homematic-ccu2 user.info multimac: SGTIN=30 14 F7 11 A0 00 1F 58 A9 92 F2 03
Oct 18 07:31:52 homematic-ccu2 user.info multimac: RF address=65535
Oct 18 07:31:52 homematic-ccu2 user.info multimac: Serial Number=PEQ0625155
Oct 18 07:31:52 homematic-ccu2 user.info multimac: Timer=22654
Oct 18 07:31:54 homematic-ccu2 user.info rfd: BidCoS-Service started
Oct 18 07:31:54 homematic-ccu2 user.info rfd: XmlRpc Server is listening on TCP port 2001
Oct 18 07:31:54 homematic-ccu2 user.warn rfd: opendir(/etc/config/firmware//) failed
Oct 18 07:31:54 homematic-ccu2 user.info rfd: CCU2CommController::init(): Coprocessor Bootloader Version is: 1.0.1
Oct 18 07:31:54 homematic-ccu2 user.info rfd: CCU2CommController::init(): Coprocessor Firmware Version is: 3.4.8
Oct 18 07:31:54 homematic-ccu2 user.info rfd: () CCU2CommController::setCSMACAEnabled(): CSMA/CA disabled.
Oct 18 07:31:54 homematic-ccu2 user.info rfd: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: OEQ0797337
Oct 18 07:31:54 homematic-ccu2 user.info rfd: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: OEQ0797337
Oct 18 07:31:55 homematic-ccu2 user.info rfd: CCU2CommController::init(): Coprocessor Bootloader Version is: 1.0.4
Oct 18 07:31:55 homematic-ccu2 user.info rfd: CCU2CommController::init(): Coprocessor Firmware Version is: 1.4.1
Oct 18 07:31:55 homematic-ccu2 user.info rfd: (OEQ0797337) CCU2CommController::setCSMACAEnabled(): CSMA/CA disabled.
Oct 18 07:31:55 homematic-ccu2 user.info rfd: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: OEQ0796800
Oct 18 07:31:55 homematic-ccu2 user.info rfd: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.5 Serial Number: OEQ0796800
Oct 18 07:31:55 homematic-ccu2 user.info rfd: CCU2CommController::init(): Coprocessor Bootloader Version is: 1.0.4
Oct 18 07:31:55 homematic-ccu2 user.info rfd: CCU2CommController::init(): Coprocessor Firmware Version is: 1.4.1
Oct 18 07:31:55 homematic-ccu2 user.info rfd: (OEQ0796800) CCU2CommController::setCSMACAEnabled(): CSMA/CA disabled.
Oct 18 07:31:55 homematic-ccu2 user.info rfd: Current AES key=0, previous AES key=0
Oct 18 07:32:01 homematic-ccu2 user.warn multimac: Bad cast: std::bad_cast
Oct 18 07:32:06 homematic-ccu2 user.info rfd: IPS-192.168.178.57 support system.multicall
Oct 18 07:32:06 homematic-ccu2 user.info rfd: IPS-192.168.178.57 support event
Oct 18 07:32:07 homematic-ccu2 user.warn multimac: Subsystem 1 refusing upstream disconnect. Client mismatch.
Oct 18 07:32:07 homematic-ccu2 user.info kernel: [  138.899187] eq3loop: eq3loop_open_slave() ttyS0
Oct 18 07:32:07 homematic-ccu2 user.notice kernel: [  138.901549] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support system.methodHelp
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support system.multicall
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support updateDevice
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support newDevices
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support deleteDevices
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support firmwareUpdateStatusChanged
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support replaceDevice
Oct 18 07:32:14 homematic-ccu2 user.info rfd: yes support replace device
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support readdedDevice
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support system.listMethods
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support event
Oct 18 07:32:14 homematic-ccu2 user.info rfd: BidCos-RF_java support listDevices
Oct 18 07:32:15 homematic-ccu2 user.info homematic: meine-homematic.de loophammer startet openvpn.
Oct 18 07:32:15 homematic-ccu2 daemon.warn openvpn[434]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:32:15 homematic-ccu2 daemon.warn openvpn[434]: WARNING: file '/usr/local/etc/config/addons/mh/client.key' is group or others accessible
Oct 18 07:32:22 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support deleteDevices
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support event
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support listDevices
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support newDevices
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support replaceDevice
Oct 18 07:32:27 homematic-ccu2 user.info rfd: yes support replace device
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support reportValueUsage
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support setReadyConfig
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support system.listMethods
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support system.methodHelp
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support updateDevice
Oct 18 07:32:27 homematic-ccu2 user.info rfd: 1009 support system.multicall
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D70995178E:6","ENERGY_COUNTER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"] [iseXmlRpc
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D709904342:6","ENERGY_COUNTER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"] [iseXmlRpc
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E5C07:5","ENERGY_COUNTER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"] [iseXmlRpc
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E6A25:5","ENERGY_COUNTER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"] [iseXmlRpc
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D70995178E:6","ENERGY_COUNTER_OVERFLOW"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVE
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E532E:5","ENERGY_COUNTER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"] [iseXmlRpc
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D709904342:6","ENERGY_COUNTER_OVERFLOW"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVE
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E5C58:5","ENERGY_COUNTER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"] [iseXmlRpc
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E5C07:5","ENERGY_COUNTER_OVERFLOW"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVE
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E58F1:5","ENERGY_COUNTER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"] 
[iseXmlRpc
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E6A25:5","ENERGY_COUNTER_OVERFLOW"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVE
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E54F1:5","ENERGY_COUNTER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"] [iseXmlRpc
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E532E:5","ENERGY_COUNTER_OVERFLOW"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVE
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000ED709B28322:1","HUMIDITY"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: HUMIDITY"] [iseXmlRpc.cpp:2605]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000ED709B28322:1","ACTUAL_TEMPERATURE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ACTUAL_TEMPERATURE"] [i
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E5C58:5","ENERGY_COUNTER_OVERFLOW"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVE
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E58F1:5","ENERGY_COUNTER_OVERFLOW"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVE
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000895699E54F1:5","ENERGY_COUNTER_OVERFLOW"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVE
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:32:27 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:32:28 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:32:35 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:32:37 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [iseXmlRpc.h:281]
Oct 18 07:32:37 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","1409"} result= nil [iseXmlRpc.cpp:2599]
Oct 18 07:32:37 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [iseXmlRpc.cpp:1204]
Oct 18 07:32:37 homematic-ccu2 local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=CUxD [iseRTHss.cpp:163]
Oct 18 07:32:41 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:32:47 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:32:54 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"00021709A0ED64:3","STATE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"] [iseXmlRpc.cpp:2605]
Oct 18 07:33:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:33:00 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:33:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"00021709A0ED64:6","WEEK_PROGRAM_CHANNEL_LOCKS"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: WEEK_PROGRAM_CH
Oct 18 07:33:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:33:00 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:33:01 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:02 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"00021709A0ED64:3","STATE",true} result= [faultCode:-1,faultString:"Generic error (TIMEOUT)"] [iseXmlRpc.cpp:2605]
Oct 18 07:33:02 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Oct 18 07:33:02 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = 00021709A0ED64:3 [iseDOMdpHSS.cpp:77]
Oct 18 07:33:07 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:14 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:19 homematic-ccu2 user.info rfd: OEQ0459587_2001_00113236afa7 support event
Oct 18 07:33:19 homematic-ccu2 user.info rfd: OEQ0459587_2001_00113236afa7 support listDevices
Oct 18 07:33:19 homematic-ccu2 user.info rfd: OEQ0459587_2001_00113236afa7 support newDevices
Oct 18 07:33:19 homematic-ccu2 user.info rfd: OEQ0459587_2001_00113236afa7 support deleteDevices
Oct 18 07:33:19 homematic-ccu2 user.info rfd: OEQ0459587_2001_00113236afa7 support updateDevice
Oct 18 07:33:19 homematic-ccu2 user.info rfd: OEQ0459587_2001_00113236afa7 support replaceDevice
Oct 18 07:33:19 homematic-ccu2 user.info rfd: yes support replace device
Oct 18 07:33:19 homematic-ccu2 user.info rfd: OEQ0459587_2001_00113236afa7 support readdedDevice
Oct 18 07:33:20 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:27 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:28 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Oct 18 07:33:31 homematic-ccu2 user.info multimac: ACK received after 0 repetitions: #01[BiDi|BC|Ren] 56EA10->5BF54A Info: 06 01 00 00 00
Oct 18 07:33:31 homematic-ccu2 user.info multimac: ACK received after 0 repetitions: #0A[BiDi|BC|Ren] 56EA10->5BF54A Info: 06 02 00 00 00
Oct 18 07:33:31 homematic-ccu2 user.info multimac: ACK received after 0 repetitions: #13[BiDi|BC|Ren] 56EA10->5BF54A Info: 06 03 00 00 00
Oct 18 07:33:31 homematic-ccu2 user.info multimac: ACK received after 0 repetitions: #1C[BiDi|BC|Ren] 56EA10->5BF54A Info: 06 04 00 00 00
Oct 18 07:33:32 homematic-ccu2 user.info multimac: ACK received after 0 repetitions: #25[BiDi|BC|Ren] 56EA10->5BF54A Info: 06 05 00 00 00
Oct 18 07:33:32 homematic-ccu2 user.info multimac: ACK received after 0 repetitions: #2E[BiDi|BC|Ren] 56EA10->5BF54A Info: 06 06 00 00 00
Oct 18 07:33:32 homematic-ccu2 user.info multimac: ACK received after 0 repetitions: #37[BiDi|BC|Ren] 56EA10->5BF54A Info: 06 07 00 00 00
Oct 18 07:33:33 homematic-ccu2 user.info multimac: ACK received after 0 repetitions: #40[BiDi|BC|Ren] 56EA10->5BF54A Info: 06 08 00 00 00
Oct 18 07:33:33 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:34 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Oct 18 07:33:34 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Oct 18 07:33:37 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Oct 18 07:33:37 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Oct 18 07:33:40 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:42 homematic-ccu2 user.info rfd: IPS-192.168.178.90 support system.multicall
Oct 18 07:33:42 homematic-ccu2 user.info rfd: IPS-192.168.178.90 support event
Oct 18 07:33:46 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:48 homematic-ccu2 user.info rfd: IPS-192.168.178.68 support system.multicall
Oct 18 07:33:48 homematic-ccu2 user.info rfd: IPS-192.168.178.68 support event
Oct 18 07:33:53 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:33:59 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:06 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:12 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:19 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:25 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:32 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:38 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:45 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:47 homematic-ccu2 user.warn multimac: Bad cast: std::bad_cast
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","SET_POINT_TEMPERATURE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: SET_POINT_TEMPERATUR
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","ACTUAL_TEMPERATURE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ACTUAL_TEMPERATURE"] [i
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","ACTIVE_PROFILE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: ACTIVE_PROFILE"] [iseXmlRpc
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","HUMIDITY"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: HUMIDITY"] [iseXmlRpc.cpp:2605]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","WINDOW_STATE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: WINDOW_STATE"] [iseXmlRpc.cpp
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","SET_POINT_MODE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: SET_POINT_MODE"] [iseXmlRpc
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","PARTY_TIME_START"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_TIME_START"] [iseXm
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal =  [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","PARTY_TIME_END"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_TIME_END"] [iseXmlRpc
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal =  [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","PARTY_SET_POINT_TEMPERATURE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_SET_POIN
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:1","PARTY_MODE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_MODE"] [iseXmlRpc.cpp:260
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:8","EMERGENCY_OPERATION"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: EMERGENCY_OPERATION"]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:8","FROST_PROTECTION"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: FROST_PROTECTION"] [iseXm
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:8","HUMIDITY_ALARM"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: HUMIDITY_ALARM"] [iseXmlRpc
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000C98A98AB0C9:8","STATE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"] [iseXmlRpc.cpp:2605]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:48 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:34:51 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:34:58 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:04 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:11 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:17 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:24 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:30 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:36 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:43 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:50 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:35:56 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:03 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:09 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:16 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:22 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:29 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:35 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:42 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:48 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:36:55 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:01 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:08 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D70995178E:3","STATE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"] [iseXmlRpc.cpp:2605]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D70995178E:6","VOLTAGE"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: VOLTAGE"] [iseXmlRpc.cpp:2605]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D70995178E:6","CURRENT"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: CURRENT"] [iseXmlRpc.cpp:2605]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D70995178E:6","POWER"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: POWER"] [iseXmlRpc.cpp:2605]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"0001D70995178E:6","FREQUENCY"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: FREQUENCY"] [iseXmlRpc.cpp:2605]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 18 07:37:08 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 18 07:37:11 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"0001D70995178E:3","STATE",true} result= [faultCode:-1,faultString:"Generic error (TIMEOUT)"] [iseXmlRpc.cpp:2605]
Oct 18 07:37:11 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Oct 18 07:37:11 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = 0001D70995178E:3 [iseDOMdpHSS.cpp:77]
Oct 18 07:37:12 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"0001D70995178E:3","STATE",false} result= [faultCode:-1,faultString:"Generic error (TIMEOUT)"] [iseXmlRpc.cpp:2605]
Oct 18 07:37:12 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Oct 18 07:37:12 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = 0001D70995178E:3 [iseDOMdpHSS.cpp:77]
Oct 18 07:37:14 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:21 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:27 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:34 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:40 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:47 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:37:53 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:00 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:06 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:13 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:19 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:26 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:32 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:39 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:45 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:52 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:38:58 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:05 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:11 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:18 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:24 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:31 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:37 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:44 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:50 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:39:56 homematic-ccu2 user.warn multimac: Bad cast: std::bad_cast
Oct 18 07:39:57 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Oct 18 07:40:03 homematic-ccu2 daemon.warn openvpn[435]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables

Code: Alles auswählen

Oct 18 07:32:01 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Oct 18 07:32:01 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 20 classes to Vert.x
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 20 VertxDeployers initialized
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (ae495767-8910-4bf3-97aa-d684f3f674b2)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CheckDeviceExistHandler succeeded (ab6bde96-f6ff-4ae6-bfca-9466c890160c)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of TransactionSubsystemHandler succeeded (b4956e29-63d5-4f76-968f-c1e7ac541034)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of HMIPTRXWriterWorker succeeded (40b214c8-69f4-4640-bb60-554b8259382e)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (ad80d672-13f0-44ff-982e-8c6bfb52a849)
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (ad12be93-5c5c-4832-be32-5bb9e8f9a9f2)
Oct 18 07:32:05 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Oct 18 07:32:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of KeyServerWorker succeeded (5b24f379-8ba8-4c36-bb60-100c4fe2de45)
Oct 18 07:32:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KryoPersistenceWorker succeeded (ff77c027-8ee0-47f8-80fa-f5f9be25c969)
Oct 18 07:32:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerPersistentDataLoader succeeded (aad25e63-e321-461e-8d65-fbc0e8080de3)
Oct 18 07:32:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (f9311005-6cc5-4e84-872e-4681b51f8398)
Oct 18 07:32:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (eeb5a0b2-dff8-4b24-8a5e-3df38afbe869)
Oct 18 07:32:07 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware
Oct 18 07:32:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of IncomingHMIPFrameHandler succeeded (f5a30e07-5162-4ac0-b83a-cf6f9034a0cc)
Oct 18 07:32:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LegacyBackendNotificationHandler succeeded (dca42b43-9237-4549-b640-2c216ff1a7f9)
Oct 18 07:32:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of BackendCommandHandler succeeded (15fda4ce-69fa-4ef3-8fe4-b310f99d1ea7)
Oct 18 07:32:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of FirmwareLoaderFileSystem succeeded (ebc2e605-a279-49bd-988f-bf3bcaf1a693)
Oct 18 07:32:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyNotificationHandler succeeded (bf15deed-00e9-4f1e-b754-641bb9637eb0)
Oct 18 07:32:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyAPIWorker succeeded (9e908f93-5455-429a-975b-7f7f6bcac46c)
Oct 18 07:32:07 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerAdapterInitialization succeeded (4fe46a31-bf4c-4948-b56b-b9d6167f64f2)
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ...
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12507592...
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A0001F58A992F203 to 3
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version...
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 3.4.8
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.1
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.34.0
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: CC1310
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 265669121
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 1 link partners
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A0001F58A992F203 initialized
Oct 18 07:32:07 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Oct 18 07:32:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (057011db-45a1-4ecc-8530-cf50a88ca94e)
Oct 18 07:32:08 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-3] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware
Oct 18 07:32:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Checking all devices on all accesspoints for updates
Oct 18 07:32:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: There are 0 APs queued with updatable devices
Oct 18 07:32:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyInitializion succeeded (9b1d1205-c991-4ade-b534-dbeac26c3dd7)
Oct 18 07:32:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Oct 18 07:32:09 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 2010
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxEventLoopExecuteTime: 2000000000
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default BlockedThreadCheckInterval: 1000
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxWorkerExecuteTime: 60000000000
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default EventLoopPoolSize: 8
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default BlockedThreadCheckInterval: 1000
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxWorkerExecuteTime: 60000000000
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default EventLoopPoolSize: 8
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: deploying 9 classes to Vert.x
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: 9 VertxDeployers initialized
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of RegaClientWorker succeeded (87ace2ac-7c17-480c-a383-0519c830b01e)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of EnergyPriceRequestWorker succeeded (21d8c237-8536-44ca-943c-ea7f07a078c5)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (d50fac6a-ff7e-4204-85ad-e4ce78760fe6)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CouplingRequestWorker succeeded (7720f519-d5c4-46a1-8527-55261113c11d)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of BackendWorker succeeded (3deb8119-5ae2-4c6a-b91e-65640150bb1b)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of StorageRequestWorker succeeded (459e531b-02d8-4750-88e7-d240d62c1fd4)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of GroupRequestWorker succeeded (4c4afacb-faf3-4713-bab4-4bf8253f0f14)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DiagramRequestWorker succeeded (4643961f-24d7-4d6a-9fc4-0425df253f92)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (8271313e-e909-4a5a-839f-39a6bbae3ea7)
Oct 18 07:32:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: initial deployment complete _____________________________________________________
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Starting HMServer at 127.0.0.1:9292
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Read Configuration
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create Bidcos Dispatcher
Oct 18 07:32:11 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] InitBidCosCache
Oct 18 07:32:12 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create groupDefinitionProvider
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create VirtualDeviceHolder
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create VirtualDeviceHandlerRega
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupAdministrationService
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupDeviceDispatcher
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupDeviceHandler
Oct 18 07:32:13 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] @GroupDeviceHandler - initializing...
Oct 18 07:32:13 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Oct 18 07:32:13 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Oct 18 07:32:13 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> got groupDefinitionProvider
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create BidCosGroupMemberProvider
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init groupAdministrationService
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init Virtual OS Device
Oct 18 07:32:13 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init ESHLight Bridge
Oct 18 07:32:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create RrdDatalogging
Oct 18 07:32:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create MeasurementService
Oct 18 07:32:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init MeasurementService
Oct 18 07:32:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create HTTP Server
Oct 18 07:32:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create BidCos context and start handler
Oct 18 07:32:14 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create group context and start handler
Oct 18 07:32:14 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:9292/bidcos
Oct 18 07:32:14 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished
Oct 18 07:32:14 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: HmIP-RF_java
Oct 18 07:32:14 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient HmIP-RF_java -> 150 device addresses will be added
Oct 18 07:32:15 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Starting HMServer done
Oct 18 07:32:27 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
Oct 18 07:32:27 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] Added InterfaceId: 1010
Oct 18 07:32:27 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-9] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Oct 18 07:32:37 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
Oct 18 07:32:37 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished
Oct 18 07:32:37 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: 1011
Oct 18 07:33:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.91:9099/OEQ0459587
Oct 18 07:33:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished
Oct 18 07:33:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.91:9099/OEQ0459587
Oct 18 07:33:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished
Oct 18 07:33:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: OEQ0459587_2010_00113236afa7
Oct 18 07:33:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-4] updateDevicesForClient OEQ0459587_2010_00113236afa7 -> 150 device addresses will be added
Oct 18 07:33:42 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.90:5544
Oct 18 07:33:42 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished
Oct 18 07:33:42 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: IPS-192.168.178.90
Oct 18 07:33:42 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-3] updateDevicesForClient IPS-192.168.178.90 -> 150 device addresses will be added
Oct 18 07:33:48 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.68:5544
Oct 18 07:33:48 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished
Oct 18 07:33:48 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: IPS-192.168.178.68
Oct 18 07:33:48 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-4] updateDevicesForClient IPS-192.168.178.68 -> 150 device addresses will be added
Oct 18 07:35:47 de.eq3.cbcs.server.core.framehandling.HMIPNetworkManagementHandler INFO  [vert.x-eventloop-thread-3] AP 3014F711A0001F58A992F203: Device included 3014F711A000021709A0ED64
Oct 18 07:37:06 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: 0 Accesspoints in Queue
Oct 18 07:37:06 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Oct 18 07:37:06 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Eventlistener Handler utilization: 0/50 used
Ich habe direkt die Schaltsteckdose von gestern "drüber gelernt" (also mit der ID 00021709A0ED64) - und siehe da, der ist nun bedienbar.

was mich wundert ist natürlich oben die Ausgabe vom pivccu-info und die fehlende Datei hm-mode - ist aber vielleicht bei einer 2'er-Version so.

dann habe ich einfach eine andere Schaltsteckdose kurz stromlos gemacht

Code: Alles auswählen

Oct 18 07:42:06 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Oct 18 07:42:06 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Eventlistener Handler utilization: 0/50 used
Oct 18 07:46:49 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN  [vert.x-worker-thread-2] AP 3014F711A0001F58A992F203: Frontend Server responded with HTTP Status 403 Forbidden
Oct 18 07:47:00 de.eq3.cbcs.server.core.framehandling.HMIPNetworkManagementHandler INFO  [vert.x-eventloop-thread-3] AP 3014F711A0001F58A992F203: Device included 3014F711A00001D70995178E
Oct 18 07:47:06 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: 0 Accesspoints in Queue
Oct 18 07:47:06 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Oct 18 07:47:06 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Eventlistener Handler utilization: 0/50 used
ist nun auch bedienbar.

ich lasse das jetzt erstmal in Ruhe und schaue heute nachmittag mal nach, ob sich weitere Komponenten von alleine registriert habe.

demel
Raspberrymatic 3.67.10.20230225 unter Proxmox (HM und HmIP) - IP-Symcon 6.3 auf Ubuntu 18.04.3 unter Proxmox - Mediola Gateway V5+, Warema WMS

demel42
Beiträge: 147
Registriert: 12.11.2017, 20:35
Hat sich bedankt: 4 Mal
Danksagung erhalten: 9 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von demel42 » 18.10.2018, 08:49

Leider musste ich gerade feststellen, das die 2. Schaltsteckdose nicht immer reagiert, weder von IP-Symcon noch über die HM-WebGui. Würde sagen, so 50/50.

Diese Meldung sehe ich in den messages

Code: Alles auswählen

Oct 18 08:45:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; m
ethod =setValue Params = {"0001D70995178E:3","STATE",false} result= [faultCode:-1,faultString:"Generic error (TI
MEOUT)"] [iseXmlRpc.cpp:2605]
Oct 18 08:45:00 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseX
mlRpc.cpp:1502]
Oct 18 08:45:00 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = 0
001D70995178E:3 [iseDOMdpHSS.cpp:77]
demel
Raspberrymatic 3.67.10.20230225 unter Proxmox (HM und HmIP) - IP-Symcon 6.3 auf Ubuntu 18.04.3 unter Proxmox - Mediola Gateway V5+, Warema WMS

Benutzeravatar
deimos
Beiträge: 5383
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 950 Mal
Kontaktdaten:

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von deimos » 18.10.2018, 08:58

Hi,

ich habe jetzt in das Backup geschaut, da ist was faul drin:

Es sind zwar diverse Geräte Dateien vorhanden, aber in der /etc/config/crRFD/data/linkData.conf ist definiert, dass es keine Link Partner gibt. Das erklärt dann, warum für kein Gerät ein Rekeying durchgeführt wird und weshalb das Modul die nicht steuern kann. Ich habe leider keine Ahnung, ob man die Datei in irgendeiner Form reparieren kann.

Ich fürchte, dass der einzig wirklich valide Weg wäre, alle HmIP Geräte abzulernen, das Verzeichnis /etc/config/crRFD/data komplett zu leeren und dann nach einem Neustart der CCU alle Geräte nach Werksreset frisch anzumelden. Bedeutet allerdings leider auch, dass man alle Einstellungen, Direktverknüpfungen und Programme von den Geräten neu erstellen muss. :-(

Viele Grüße
Alex

Benutzeravatar
deimos
Beiträge: 5383
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 950 Mal
Kontaktdaten:

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von deimos » 18.10.2018, 09:13

Hi,
demel42 hat geschrieben:
18.10.2018, 07:50
was mich wundert ist natürlich oben die Ausgabe vom pivccu-info und die fehlende Datei hm-mode - ist aber vielleicht bei einer 2'er-Version so.
Die Datei hm_mode gibt es erst seit der CCU3 Firmware, das du die nicht findest ist also normal.

Für die Ausgabe bei pivccu-info gibt es bereits eine aktualisierte Version, die ist leider nur mangels Zeit noch nicht im Image drin. Einmal mit apt updaten, dann sollte das passen. Ursache dafür war, dass mit der neuesten Firmware des RPI-RF-MOD von eQ-3 die Radio MAC nicht mehr auslesbar ist, was meine Hardware Erkennung durcheinander gebracht hat, bei welcher ich die Radio MAC als Merkmal verwendet habe, dass ein Funkmodul angeschlossen ist.

Viele Grüße
Alex

demel42
Beiträge: 147
Registriert: 12.11.2017, 20:35
Hat sich bedankt: 4 Mal
Danksagung erhalten: 9 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von demel42 » 18.10.2018, 09:58

deimos hat geschrieben:
18.10.2018, 09:13
Einmal mit apt updaten, dann sollte das passen
aber wenn ich "apt update && apt upgrade" ausführe bin ich ja wieder auf eine pivccu3-version, oder?

Ich habe in meinem jetzigen pivccu-container mal nachgeschaut,

in /etc/config/crRFD/data sind 19 *.dev-Einträge, von der Anzahl und flüchtigen Nachsehen sind das meine HmIP-Einträge.

Hilf das irgendwas?

demel
Raspberrymatic 3.67.10.20230225 unter Proxmox (HM und HmIP) - IP-Symcon 6.3 auf Ubuntu 18.04.3 unter Proxmox - Mediola Gateway V5+, Warema WMS

Benutzeravatar
deimos
Beiträge: 5383
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 950 Mal
Kontaktdaten:

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von deimos » 18.10.2018, 10:05

Hi,

nein, nur durch apt upgrade landest du nicht bei piVCCU3. Ich habe absichtlich ein neues Paket geschnürt, damit eben das nicht passiert und man selbst wählen kann, ob und wann man eine Migration durchführt. Und solange eQ-3 Updates für die CCU2 rausbringt, werde ich die auch weiterhin einpflegen.

Die dev Dateien habe ich gesehen, aber die sind nur die halbe Wahrheit, es gibt halt noch die linkdata.conf.

Viele Grüße
Alex

demel42
Beiträge: 147
Registriert: 12.11.2017, 20:35
Hat sich bedankt: 4 Mal
Danksagung erhalten: 9 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von demel42 » 18.10.2018, 16:30

deimos hat geschrieben:
18.10.2018, 10:05
nein, nur durch apt upgrade landest du nicht bei piVCCU3. Ich habe absichtlich ein neues Paket geschnürt, damit eben das nicht passiert und man selbst wählen kann, ob und wann man eine Migration durchführt. Und solange eQ-3 Updates für die CCU2 rausbringt, werde ich die auch weiterhin einpflegen.
ok, habe ich gemacht

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 2.35.16-38
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi3 UART:  Assigned to GPIO pins
HMRF Hardware:  RPI-RF-MOD
HMIP Hardware:  RPI-RF-MOD
Board serial:   58a992f203
Radio MAC:      unknown
SGTIN:          3014f711a0001f58a992f203
State:          RUNNING
PID:            3666
IP:             192.168.178.60
CPU use:        32.77 seconds
BlkIO use:      36.92 MiB
Link:           vethpivccu
 TX bytes:      2.33 MiB
 RX bytes:      621.36 KiB
 Total bytes:   2.94 MiB
deimos hat geschrieben:
18.10.2018, 10:05
Die dev Dateien habe ich gesehen, aber die sind nur die halbe Wahrheit, es gibt halt noch die linkdata.conf.
1. Versuch

Ich habe nun ein Gerät aus der PIVCCU gelöscht, die /etc/config/crRFD/data geleert und die PIVCCU rebootet. Ein Gerät (HmIP-BWTH) auf Werkseinstellung zurückgesetzt. Das Gerät konnte dann angelernt werden, wird richtig in der WebGUI dargestellt und es überträgt Werte (Temperatur, Feuchtigkeit, eingestellt Temperatur), aber es kann aber nicht bedient werden (z.B. Temperatur einstellen).

In dem o.g. Verzeichnis steht das

Code: Alles auswählen

# ls -l
total 44
-rw-r--r--    1 root     root         36860 Oct 18 16:02 3014F711A0000C98A98AB0C9.dev
-rw-r--r--    1 root     root           131 Oct 18 16:01 3014F711A0001F58A992F203.ap
-rw-r--r--    1 root     root           209 Oct 18 16:01 3014F711A0001F58A992F203.apkx
linkData.conf wird nicht angelegt.
In den Servicemeldungen steht diese Komponente als "Es stehen Konfigurationsdaten zur Übertragung an" und "Gerätekommunikation ist gestört".

2. Versuch:

data restauriert (also mit allen HmIP-Komponenten und leerer linkData.conf). Wieder das Gerät in HM gelöscht, Werksreste etc pp. Erfolgt wie oben.

linkData.conf hat den Inhalt wie zuvor (also leeres json-Array).

Ich habe auch mal auf die alte CCU2 kurz wieder in Betrieb genommen und schnell nachgeschaut linkData.conf ist da auch "leer".

D.h. wenn das leer bleibt habe ich ja bei jedem Einspielen einer Sicherung ein echtes Problem?

Ich habe nun den Lieferanten angeschrieben, weil ich nun noch wenig sehe, was an der Software zu machen ist sondern eher, das es ein Problem mit dem Funkmodul gibt.

Denn wenn ich aus einem leeren System keine Geräte anlernen und danach bedienen kann, hilft mir das nichts.

Danke erstmal für deine Hilfe

demel



, das
Raspberrymatic 3.67.10.20230225 unter Proxmox (HM und HmIP) - IP-Symcon 6.3 auf Ubuntu 18.04.3 unter Proxmox - Mediola Gateway V5+, Warema WMS

Benutzeravatar
deimos
Beiträge: 5383
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 950 Mal
Kontaktdaten:

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von deimos » 18.10.2018, 16:43

Hi,

ich habe mir deine Logs nochmal angeschaut. Ich bin immer davon ausgegangen, dass dein Funkmodul funktionieren muss, weil du die HmRF Geräte ja steuern kannst. Aber du hast ja noch ein LAN GW, welches die Kommunikation mit diesen Geräten sicherstellen kann.

Weil wir es erst vor ein paar Tagen hier im Forum hatten, du hast nicht zufällig ein Funkmodul gekauft mit zwei externen Antennen?

Viele Grüße
Alex

Antworten

Zurück zu „piVCCU“