Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

Antworten
maschbaer
Beiträge: 25
Registriert: 07.01.2020, 23:29

Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Beitrag von maschbaer » 05.08.2020, 11:30

Hallo zusammen,

Bis dato lief die piVCCU3 bei mir problemlos.

Heute habe ich auf meinem Handy piHelper installiert und musste feststellen, dass eine recht hohe CPU Last von den Prozessen ReGaHSS.com und node-red ausgehen (in letzter Zeit war der Zugriff per shh auch etwas träge muss ich zugeben).
Node-red hatte ich mal testweise in Homematic installiert, um Sensoren von Homematic in Homekit einzubinden. Hat aber leider nicht geklappt, dies mache ich mittlerweile über Homeassistant. Ich habe Node-red aber vergessen zu deinstallieren.
Beim Zugriff auf die Weboberfläche kommt "Die Homematic CCU ist noch nicht bereit".
Die Sensorwerte (ein Lichtsensor und 3 Türsensoren) werden weiterhin sauber über Homeassistant ans Homekit weitergereicht.

Woran könnte es liegen, dass die Weboberfläche nicht hochkommt?
Ich habe dir mal die Ausgaben von
sudo pivccu-info
sudo pivccu-attach cat /var/hm_mode
sudo pivccu-attach cat /var/log/messages
sudo pivccu-attach cat /var/log/hmserver.log
angehängt. Vielleicht kannst du mal einen Blick darauf werfen.

Thx,
Jan

sudo pivccu-info

Code: Alles auswählen

piVCCU version: 3.49.17-33
Kernel modules: Available
Raw UART dev: Available
Rasp.Pi3 UART: Assigned to GPIO pins
HMRF Hardware: HM-MOD-RPI-PCB
HMIP Hardware: HM-MOD-RPI-PCB
Board serial: QEQ0411868
Radio MAC: 0x6d12b4
SGTIN: 3014F711A061A7DA498FB0DC
State: RUNNING
PID: 1219
IP: 192.168.255.1
CPU use: 1528.71 seconds
BlkIO use: 135.70 MiB
Memory use: 343.91 MiB
KMem use: 9.95 MiB
Link: vethpivccu
TX bytes: 2.08 MiB
RX bytes: 217.83 KiB
Total bytes: 2.29 MiB
sudo pivccu-attach cat /var/hm_mode

Code: Alles auswählen

HM_HMIP_ADDRESS='0x6d12b4'
HM_HMIP_DEV='HM-MOD-RPI-PCB'
HM_HMIP_DEVNODE='/dev/raw-uart'
HM_HMIP_SERIAL='QEQ0411868'
HM_HMIP_SGTIN='3014F711A061A7DA498FB0DC'
HM_HMIP_VERSION='2.8.6'
HM_HMRF_ADDRESS='0x6d12b4'
HM_HMRF_DEV='HM-MOD-RPI-PCB'
HM_HMRF_DEVNODE='/dev/raw-uart'
HM_HMRF_SERIAL='QEQ0411868'
HM_HMRF_VERSION='2.8.6'
HM_HOST='rpi3'
HM_HOST_GPIO_RESET=''
HM_HOST_GPIO_UART='/dev/raw-uart'
HM_LED_GREEN=''
HM_LED_RED=''
HM_LED_YELLOW=''
HM_MODE='NORMAL'
HM_RTC=''
sudo pivccu-attach cat /var/log/messages

Code: Alles auswählen

Aug 4 20:38:54 piVCCU syslog.info syslogd started: BusyBox v1.29.2
Aug 4 20:38:54 piVCCU user.notice kernel: klogd started: BusyBox v1.29.2 (2019-12-02 17:04:43 CET)
Aug 4 20:38:55 piVCCU syslog.info syslogd exiting
Aug 4 20:38:55 homematic-ccu3 syslog.info syslogd started: BusyBox v1.29.2
Aug 4 20:38:55 homematic-ccu3 user.notice kernel: klogd started: BusyBox v1.29.2 (2019-12-02 17:04:43 CET)
Aug 4 20:38:55 homematic-ccu3 user.info firewall: iptables v1.6.2: invalid port/service 310000' specified Try iptables -h' or 'iptables --help' for more information.
Aug 4 20:38:55 homematic-ccu3 user.info firewall: ip6tables v1.6.2: invalid port/service 310000' specified Try ip6tables -h' or 'ip6tables --help' for more information.
Aug 4 20:38:55 homematic-ccu3 user.info firewall: configuration set
Aug 4 20:38:55 homematic-ccu3 daemon.info ifplugd(eth0)[252]: ifplugd 0.28 initializing.
Aug 4 20:38:55 homematic-ccu3 daemon.info ifplugd(eth0)[252]: Using interface eth0/BA:67:35:5D:89:E6 with driver (version: 1.0)
Aug 4 20:38:55 homematic-ccu3 daemon.info ifplugd(eth0)[252]: Using detection mode: SIOCETHTOOL
Aug 4 20:38:55 homematic-ccu3 daemon.info ifplugd(eth0)[252]: Initialization complete, link beat detected.
Aug 4 20:38:55 homematic-ccu3 daemon.warn ifplugd(eth0)[252]: Could not open /dev/tty, cannot beep.
Aug 4 20:38:55 homematic-ccu3 daemon.info ifplugd(eth0)[252]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Aug 4 20:38:55 homematic-ccu3 daemon.warn ifplugd(eth0)[252]: client: ifup: interface eth0 already configured
Aug 4 20:38:55 homematic-ccu3 daemon.info ifplugd(eth0)[252]: Program executed successfully.
Aug 4 20:39:05 homematic-ccu3 daemon.notice ntpdate[260]: step time server 131.188.3.223 offset -0.003024 sec
Aug 4 20:39:05 homematic-ccu3 daemon.notice ntpd[261]: ntpd 4.2.8p12@1.3728-o Mon Dec 2 16:03:15 UTC 2019 (1): Starting
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[261]: Command line: /usr/sbin/ntpd -g 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: proto: precision = 0.468 usec (-21)
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: Listen and drop on 0 v6wildcard [::]:123
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: Listen normally on 2 lo 127.0.0.1:123
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: Listen normally on 3 eth0 192.168.255.1:123
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: Listen normally on 4 lo [::1]:123
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: Listen normally on 5 eth0 [fe80::b867:35ff:fe5d:89e6%5]:123
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: Listening on routing socket on fd #22 for interface updates
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Aug 4 20:39:05 homematic-ccu3 daemon.info ntpd[263]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Aug 4 20:39:05 homematic-ccu3 daemon.err xinetd[281]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Aug 4 20:39:05 homematic-ccu3 daemon.crit xinetd[281]: 281 {init_services} no services. Exiting...
Aug 4 20:39:06 homematic-ccu3 user.info root: Updating RF Lan Gateway Coprocessor Firmware
Aug 4 20:39:06 homematic-ccu3 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Aug 4 20:39:06 homematic-ccu3 user.info root: Updating RF Lan Gateway Firmware
Aug 4 20:39:06 homematic-ccu3 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Aug 4 20:39:06 homematic-ccu3 user.info kernel: [ 36.558114] eq3loop: created slave mmd_hmip
Aug 4 20:39:06 homematic-ccu3 user.info kernel: [ 36.558490] eq3loop: created slave mmd_bidcos
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: Error ReadValue tag =1022 [LoadObject():iseDOMpersist.cpp:751]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: Error loading from file. ObjectID: 1022 type: CHANNEL [PersistLoad():iseDOM.cpp:2364]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:36 homematic-ccu3 local0.err ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Aug 4 20:39:39 homematic-ccu3 daemon.info redmatic: Starting Node-RED after reboot ... waiting 30 seconds...
Aug 4 20:40:09 homematic-ccu3 daemon.info redmatic: RedMatic v5.3.10 (c) Sebastian Raff https://github.com/rdmtc/RedMatic
Aug 4 20:40:09 homematic-ccu3 daemon.info redmatic: Starting Node-RED
Aug 4 20:40:13 homematic-ccu3 daemon.info node-red[627]: Welcome to Node-RED
Aug 4 20:40:13 homematic-ccu3 daemon.info node-red[627]: ===================
Aug 4 20:40:13 homematic-ccu3 daemon.info node-red[627]: Node-RED version: v1.0.3
Aug 4 20:40:13 homematic-ccu3 daemon.info node-red[627]: Node.js version: v10.18.1
Aug 4 20:40:13 homematic-ccu3 daemon.info node-red[627]: Linux 4.19.66-v7+ arm LE
Aug 4 20:40:13 homematic-ccu3 daemon.err node-red: (node:627) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Aug 4 20:40:15 homematic-ccu3 daemon.info node-red[627]: Loading palette nodes
Aug 4 20:40:24 homematic-ccu3 daemon.info node-red[627]: Dashboard version 2.19.3 started at /addons/red/ui
Aug 4 20:40:26 homematic-ccu3 daemon.info node-red[627]: node-red-contrib-ccu version: 3.1.4
Aug 4 20:40:27 homematic-ccu3 daemon.info node-red[627]: Settings file : /usr/local/addons/redmatic/lib/settings.js
Aug 4 20:40:27 homematic-ccu3 daemon.info node-red[627]: Context store : 'default' [module=memory]
Aug 4 20:40:27 homematic-ccu3 daemon.info node-red[627]: Context store : 'file' [module=localfilesystem]
Aug 4 20:40:27 homematic-ccu3 daemon.info node-red[627]: User directory : /usr/local/addons/redmatic/var
Aug 4 20:40:27 homematic-ccu3 daemon.warn node-red[627]: Projects disabled : editorTheme.projects.enabled=false
Aug 4 20:40:27 homematic-ccu3 daemon.info node-red[627]: Flows file : /usr/local/addons/redmatic/var/flows.json
Aug 4 20:40:27 homematic-ccu3 daemon.info node-red[627]: Starting flows
Aug 4 20:40:27 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] local connection on ccu >= v3.41 detected
Aug 4 20:40:29 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] paramsets loaded from /usr/local/addons/redmatic/var/paramsets.json
Aug 4 20:40:29 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] metadata loaded from /usr/local/addons/redmatic/var/ccu_localhost.json
Aug 4 20:40:29 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] regadata loaded from /usr/local/addons/redmatic/var/ccu_rega_localhost.json
Aug 4 20:40:29 homematic-ccu3 daemon.info node-red[627]: Started flows
Aug 4 20:40:29 homematic-ccu3 daemon.info node-red[627]: Server now running at http://127.0.0.1:1880/addons/red/
Aug 4 20:40:29 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] Error: rega getChannels connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:40:29 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] Interfaces: ReGaHSS, BidCos-RF, HmIP-RF, VirtualDevices
Aug 4 20:40:29 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] Interface ReGaHSS connected
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] init BidCos-RF binrpc://127.0.0.1:2047 nr_AKHydZ_BidCos-RF
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] init HmIP-RF http://127.0.0.1:2048 nr_D24DjW_HmIP-RF
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] init VirtualDevices http://127.0.0.1:2048 nr_D24DjW_VirtualDevices
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] binrpc server listening on binrpc://127.0.0.1:2047
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] xmlrpc server listening on http://127.0.0.1:2048
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] Interface BidCos-RF binrpc port 32001 connected
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] Interface HmIP-RF http port 32010 connected
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] Interface VirtualDevices http port 39292 connected
Aug 4 20:40:30 homematic-ccu3 daemon.info node-red[627]: [redmatic-homekit-homematic-devices:ba7726b5.96798] publish 6 devices
Aug 4 20:40:31 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] metadata saved to /usr/local/addons/redmatic/var/ccu_localhost.json
Aug 4 20:40:31 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] Interface ReGaHSS disconnected
Aug 4 20:40:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:40:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:40:31 homematic-ccu3 daemon.info node-red[627]: [ccu-connection:localhost] regadata saved to /usr/local/addons/redmatic/var/ccu_rega_localhost.json
Aug 4 20:40:31 homematic-ccu3 daemon.info node-red[627]: [redmatic-homekit-homematic-devices:ba7726b5.96798] publish done
Aug 4 20:40:36 homematic-ccu3 daemon.info node-red[627]: [redmatic-homekit-bridge:RedMatic Bridge] published bridge (4 Accessories) RedMatic Bridge CC:22:3D:E9:6C:30 on port 51827
Aug 4 20:41:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:41:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:41:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:41:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:42:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:42:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:42:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:42:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:43:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:43:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:43:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:43:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:44:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:44:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:44:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:44:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:45:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:45:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:45:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:45:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:46:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:46:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:46:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:46:31 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:47:01 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:47:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:47:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:47:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:48:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:48:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:48:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:48:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:49:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:49:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:49:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:49:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:50:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:50:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:50:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:50:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:51:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:51:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:51:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:51:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:52:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:52:02 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:52:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:52:32 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:53:03 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:53:03 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:53:33 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:53:33 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:54:03 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:54:03 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:54:33 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:54:33 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:55:03 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:55:03 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:55:35 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:55:35 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:56:06 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:56:06 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:56:36 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaVariables Error: connect ECONNREFUSED 127.0.0.1:8183
Aug 4 20:56:36 homematic-ccu3 daemon.err node-red[627]: [ccu-connection:localhost] getRegaPrograms Error: connect ECONNREFUSED 127.0.0.1:8183
sudo pivccu-attach cat /var/log/hmserver.log

Code: Alles auswählen

Aug 4 20:39:14 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory
Aug 4 20:39:14 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created instance of HMServerConfiguration with parameter(s)
Aug 4 20:39:14 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 parameter(s), in declarative order [String]
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 32 classes to Vert.x
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 32 VertxDeployers initialized
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (f28e4c0d-5e8c-4861-9170-a3010904f48d)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of CheckDeviceExistHandler succeeded (f2281102-d6bb-403c-add6-d52393de6c68)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of TransactionSubsystemHandler succeeded (f55087c1-f519-4124-b283-e95c71d22a46)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of AccessPointElectroCardioGram succeeded (9fada85a-7c2c-43bb-9438-e5038cd4ee17)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointKeyServerWorker succeeded (15fdaa20-c0dc-4237-bec7-f9b6afe51868)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (8253a1b8-d213-4283-b167-9f280add1bdb)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of HMIPTRXWriterWorker succeeded (8bef6462-78e6-4823-b684-f01fa90ea38c)
Aug 4 20:39:21 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Aug 4 20:39:21 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of KeyServerWorker succeeded (88a94711-054a-43fd-b405-f7e226f64211)
Aug 4 20:39:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of RouterKeyServerWorker succeeded (e604e69b-3de4-467c-9925-fc020e195164)
Aug 4 20:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (b24b492c-1930-45ba-a2f9-5b5b6e170313)
Aug 4 20:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (2b510fed-6402-4b25-957c-e889de467072)
Aug 4 20:39:22 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: DeviceLiveUpdateSubsystem started
Aug 4 20:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (14c62f69-a881-4b71-9d2b-d3246c92514d)
Aug 4 20:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (eda672c3-8fe8-4049-8ff9-97a8684c59ac)
Aug 4 20:39:22 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (4cf7fd1d-f52c-45ba-8013-2a8e6495cef7)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (b78c7289-66f5-4411-9fb1-508b165d4ae0)
Aug 4 20:39:24 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of FirmwareLoaderFileSystem succeeded (0f6b77eb-6265-45ce-b70a-2eb8576f0270)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of RemoteCommAdapterInitialization succeeded (07a2bf9d-ebe9-4828-b3c2-27997910a839)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointAuthorisationHandler succeeded (8f75a5a6-97a2-485c-9c86-7bad188da258)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointWatchdog succeeded (ab56b2d9-0bac-455b-b843-9e8b41d9639d)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointMessageDispatcher succeeded (1d20eb80-922e-4e9d-8fa8-e6781b7ae256)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of WebSocketManager succeeded (30d6c033-2cf4-42bf-a08b-012abfb93495)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of IncomingHMIPFrameHandler succeeded (a841efcc-6c37-494b-8361-f5d782fd4af4)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of AccessPointCommDevice succeeded (c3878421-48c7-4ad8-a333-ac35fab50bf4)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of BackendCommandHandler succeeded (3c9d04a4-3e9c-4652-9ab1-dd74419cde72)
Aug 4 20:39:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerAdapterInitialization succeeded (db9f7ceb-0190-4360-bc93-d2d4fd8009ac)
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRX_App
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running or started
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ...
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 12116636...
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A061A7DA498FB0DC to 3
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version...
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 2.8.6
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.3
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.20.3
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] MCU type: Si1002_8051
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Duty Cycle: 0.0
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] set DutyCycle limit to ffffffc8
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set Duty Cycle Limit
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Current Security Counter: 60528641
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Update security counter to calculation: 60534843
Aug 4 20:39:24 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter has 4 link partners
Aug 4 20:39:25 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Adapter with Access Point id 3014F711A061A7DA498FB0DC initialized
Aug 4 20:39:25 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Aug 4 20:39:25 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (fcc4c6c8-4a60-4a43-9f75-7d4bd24b2857)
Aug 4 20:39:25 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
Aug 4 20:39:25 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of RemoteCommAdapterFinalization succeeded (53b2e5ff-23b5-48d4-bc86-f0321c69936d)
Aug 4 20:39:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: Checking all devices on all accesspoints for updates
Aug 4 20:39:25 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-2] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 -> 192.168.255.1
Aug 4 20:39:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (RF)
Aug 4 20:39:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
Aug 4 20:39:25 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBackendNotificationHandler succeeded (536e678a-c92a-47ab-bb8c-6ef9c9ab36d7)
Aug 4 20:39:25 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LegacyNotificationHandler succeeded (27e221fb-0dd3-49dd-a913-7f803db63104)
Aug 4 20:39:25 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of LegacyAPIWorker succeeded (4cd67b0b-99ef-494b-8783-652e47b4c416)
Aug 4 20:39:26 de.eq3.cbcs.lib.lanrouting.LanRoutingWorker INFO [vert.x-worker-thread-2] AP 3014F711A061A7DA498FB0DC: Could not initialize routing of access point, version is 2.8.6
Aug 4 20:39:26 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LanRoutingWorker succeeded (085432d1-2cf3-4f43-91b6-e73a27202cf5)
Aug 4 20:39:26 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-1] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168.255.1)
Aug 4 20:39:26 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-3] UDP Routing multi cast established on network interface eth0 : 192.168.255.1
Aug 4 20:39:26 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-5] SYSTEM: Started Access Point WebSocket server with port 9293
Aug 4 20:39:26 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-5] SYSTEM: connector open
Aug 4 20:39:27 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (646ae16a-6841-4683-b07e-5212b6e1f37a)
Aug 4 20:39:27 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Aug 4 20:39:27 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
Aug 4 20:39:29 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
Aug 4 20:39:29 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default BlockedThreadCheckInterval: 1000
Aug 4 20:39:29 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxWorkerExecuteTime: 60000000000
Aug 4 20:39:29 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default EventLoopPoolSize: 8
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: deploying 10 classes to Vert.x
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: 10 VertxDeployers initialized
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of EnergyPriceRequestWorker succeeded (1cc8d636-0f27-4772-a2ad-dba6110346df)
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of BackendWorker succeeded (957857cb-c447-43ad-8a92-d42d83e3a4d3)
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (bc44d536-af65-458e-9216-02f196727e8e)
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of CouplingRequestWorker succeeded (bc3a4561-b890-4888-b68b-8ae5bb81a1bb)
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of StorageRequestWorker succeeded (30daf6fe-3844-49ad-98f0-f80c524e0539)
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of RegaClientWorker succeeded (308b4f4a-abf2-436d-8b11-251645916243)
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DiagramRequestWorker succeeded (da2d1c1d-3377-4f86-8578-893e0ea9d131)
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of GroupRequestWorker succeeded (b8d79243-9106-4543-984b-374c96ae17c8)
Aug 4 20:39:29 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (073bd510-bf7a-4a77-b985-0fb095fb2de6)
Aug 4 20:39:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (ddb21ab4-8de3-4767-864c-f66c35688505)
Aug 4 20:39:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
Aug 4 20:39:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer at 127.0.0.1:39292
Aug 4 20:39:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Read Configuration
Aug 4 20:39:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Bidcos Dispatcher
Aug 4 20:39:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] InitBidCosCache
Aug 4 20:39:32 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create groupDefinitionProvider
Aug 4 20:39:32 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHolder
Aug 4 20:39:32 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHandlerRega
Aug 4 20:39:32 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupAdministrationService
Aug 4 20:39:32 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceDispatcher
Aug 4 20:39:33 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceHandler
Aug 4 20:39:33 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] @GroupDeviceHandler - initializing...
Aug 4 20:39:33 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Aug 4 20:39:33 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Aug 4 20:39:33 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> got groupDefinitionProvider
Aug 4 20:39:33 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCosGroupMemberProvider
Aug 4 20:39:33 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init groupAdministrationService
Aug 4 20:39:33 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Virtual OS Device
Aug 4 20:39:33 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init ESHLight Bridge
Aug 4 20:39:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create RrdDatalogging
Aug 4 20:39:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create MeasurementService
Aug 4 20:39:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init MeasurementService
Aug 4 20:39:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create HTTP Server
Aug 4 20:39:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCos context and start handler
Aug 4 20:39:34 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group context and start handler
Aug 4 20:39:34 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos
Aug 4 20:39:34 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-1] init finished
Aug 4 20:39:34 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-3] Added InterfaceId: HmIP-RF_java
Aug 4 20:39:34 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-3] updateDevicesForClient HmIP-RF_java -> 69 device addresses will be added
Aug 4 20:39:35 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer done
Aug 4 20:39:40 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.255.254:45761
Aug 4 20:39:40 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] init finished
Aug 4 20:39:40 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-2] Added InterfaceId: homeassistant-ip
Aug 4 20:39:40 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-2] updateDevicesForClient homeassistant-ip -> 69 device addresses will be added
Aug 4 20:40:30 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:2048
Aug 4 20:40:30 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-1] init finished
Aug 4 20:40:30 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-3] Added InterfaceId: nr_D24DjW_HmIP-RF
Aug 4 20:40:30 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: http://127.0.0.1:2048
Aug 4 20:40:30 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] Added InterfaceId: nr_D24DjW_VirtualDevices
Aug 4 20:40:30 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-13] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Aug 4 20:40:30 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-3] updateDevicesForClient nr_D24DjW_HmIP-RF -> 52 device addresses will be added
Aug 4 20:44:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue
Aug 4 20:44:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Aug 4 20:44:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used
Aug 4 20:49:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue
Aug 4 20:49:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Aug 4 20:49:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used
Aug 4 20:49:24 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO [vert.x-eventloop-thread-3] SYSTEM: Access Point Watchdog running periodic connection check...
Aug 4 20:54:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue
Aug 4 20:54:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Aug 4 20:54:22 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used
Nach oben
Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:
Kontaktdaten von deimos

Re: Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Beitrag von deimos » 05.08.2020, 14:47

Hi,

wäre schön, wenn du einen Verweis auf Github gemacht hättest, wenn du das schon an zwei Stellen postest.

Was mir aufgefallen ist: Der Container hat die IP 192.168.255.1. Ist das Absicht?

Abgesehen davon, scheint deine Rega-DOM kaputt zu sein:

Code: Alles auswählen

ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Das liegt klassicherweise an einen Stromlosmachen ohne Shutdown zu einem dummen Zeitpunkt oder an einer sterbenden SD Karte.

Viele Grüße
Alex
Nach oben
maschbaer
Beiträge: 25
Registriert: 07.01.2020, 23:29

Re: Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Beitrag von maschbaer » 05.08.2020, 20:50

Ja stimmt. Doppelt hält besser ;)

Ich habe meinen Post in Github gelöscht und einen Link auf diesen Thread gemacht.

Das mit der IP ist Absicht und kommt von hier
https://homematic-forum.de/forum/downl ... p?id=45763

Die Frage ist jetzt wie kann ich die Rega DOM reparieren?
Ich habe Backups von meinem Pi bis 5 Wochen zurück.

Gruß
Jan

P.s. Ich würde gerne bevor ich etwas mache ein Backup ziehen aber "pivccu-backup" läuft nicht

Code: Alles auswählen

sudo pivccu-backup /home/pi
Error connecting to peer
    while executing
"rega_script {system.Save();}"
    (file "/etc/piVCCU3/save-rega.tcl" line 3)
Nach oben
Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:
Kontaktdaten von deimos

Re: Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Beitrag von deimos » 05.08.2020, 21:59

Hi,

erstmal den Container stoppen (sudo systemctl stop pivccu"), dann geht das auch mit dem Backup,ohne, dass versucht wird die laufende (bzw. bei dir nicht laufende) Rega zu speichern.

Danach alle Dateien unter /var/lib/piVCCU3/userfs löschen, dann ist die CCU wieder komplett jungfreulich und man kann das Backup einspielen. Bei dir kommt noch die Anpassung der IP Einstellungen wegen der WLAN Bridge vor dem Einspielen des Backups.

Viele Grüße
Alex
Nach oben
maschbaer
Beiträge: 25
Registriert: 07.01.2020, 23:29

Re: Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Beitrag von maschbaer » 09.08.2020, 12:09

Ok danke für die Anleitung, werde ich mal so probieren.

Zur Ursachenforschung: Kann es damit zusammenhängen, dass ich von meinem System wöchentlich ein Backup ziehe und zwar per cron job ohne Homematic vorher zu stoppen?

Code: Alles auswählen

#!/bin/bash
#Festplatte einbinden
mount -t cifs -o user=USERNAME,password=PASSWORD,rw,file_mode=0777,dir_mode=0777 //IP/FREIGABE /mnt/nas
#Variablen
BACKUP_PFAD="/mnt/nas/Backup"
BACKUP_ANZAHL="5"
BACKUP_NAME="Sicherung"
#Backup erstellen
dd if=/dev/mmcblk0 of=${BACKUP_PFAD}/${BACKUP_NAME}-$(date +%Y%m%d).img bs=1MB
#Alte Sicherung löschen
pushd ${BACKUP_PFAD}; ls -tr ${BACKUP_PFAD}/${BACKUP_NAME}* | head -n -${BACKUP_ANZAHL} | xargs rm; popd
#Festplatte auswerfen
umount /mnt/nas
Quelle: https://hobbyblogging.de/raspberry-pi-v ... ch-sichern
Nach oben
maschbaer
Beiträge: 25
Registriert: 07.01.2020, 23:29

Re: Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Beitrag von maschbaer » 16.08.2020, 23:23

Hallo Alex,

ich bin mal so vorgegangen wie du beschrieben hast:
1. piVCCU stoppen
2. Backup erstellen
3. /var/lib/piVCCU3/userfs löschen
4. Pi Reboot
5. Einspielen des Backups unter der Weboberfläche
6. piVCCU startet neu

Ergebnis: "Die Homematic CCU ist noch nicht bereit", also wie gehabt. Unter

Code: Alles auswählen

sudo pivccu-attach cat /var/log/messages
kommt auch wieder der von dir gefundene Fehler

Code: Alles auswählen

ReGaHss: ERROR: ReadElement failed! OID: oid Value: 1022 [PersistLoad():iseDOM.cpp:2374]
Die Sensoren werden korrekt erkannt und ich sehe sie im Homeassistant.

Hast du noch eine Idee?

Gruß
Jan

P.s. An den Netzwerkeinstellungen musste ich zum Glück nichts machen.
Nach oben
Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:
Kontaktdaten von deimos

Re: Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Beitrag von deimos » 17.08.2020, 00:12

Hi,

gleicher Fehler, immer noch defekte RegaDOM. Also älteres Backup nehmen.

Viele Grüße
Alex
Nach oben
maschbaer
Beiträge: 25
Registriert: 07.01.2020, 23:29

Re: Kein Zugriff auf Web Interface "Die Homematic CCU ist noch nicht bereit"

Beitrag von maschbaer » 17.08.2020, 22:04

Hallo Alex,

habe es hinbekommen.
Ich musste zwar ein altes Raspi Backup einspielen und dann die piVCCU Sicherung nochmals durchführen und dann zurück auf meine aktuelle installation wechseln aber jetzt läuft wieder alles.

Danke für deine Hilfe. Weiter so. Bis bald.

Gruß
Jan
Nach oben
Antworten

Zurück zu „piVCCU“