hm-rega startet nicht (gelb) ioBroker

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

meicker
Beiträge: 11
Registriert: 05.02.2019, 23:42

hm-rega startet nicht (gelb) ioBroker

Beitrag von meicker » 06.02.2019, 12:44

Guten Morgen,

ich hoffe mir kann jemand einen Tip geben. Ich hatte bis eben alles am laufen. Das pivccu image läuft zusammen mit iobroker und ich hatte eben auch irgendwann einmal noch die Homematic ccu3 Oberfläche auf.... Dann ist mir eben aufgefallen das hm.rega nur noch gelb ist ...

Ich habe alles mögliche versucht aber nichts hat etwas gebracht. Reset, Neustart, Ganz ausschalten und neu booten - Updates ... nix ...

Hat jemand eine Idee ? M.E kam der Ausfall mehr oder weniger überraschend, evtl aber auch nach einem Update von einem iobroker adapter ...

hm-rega bleibt gelb
Die HomeMatic Oberfläche ist erreichbar - dort steht aber ein Hinweis das sie noch geladen wird o.ä - eben noch nicht bereit ...
Das Log im ioBroker sagt folgendes: -->> hm-rega.0 2019-02-06 12:43:50.435 error ReGaHSS down

Viele Grüße,
Marc

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

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von deimos » 06.02.2019, 13:17

Hi,

starte bitte mal den gesamte Pi neu, warte ca. 5 Minuten und poste dann die Ausgabe folgender Befehle:

Code: Alles auswählen

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
Viele Grüße
Alex

meicker
Beiträge: 11
Registriert: 05.02.2019, 23:42

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von meicker » 06.02.2019, 14:10

Hallo Alex,

mache ich heite Abend wenn ich zu hause bin ! Danke schon einmal vorab.

vg
Marc

meicker
Beiträge: 11
Registriert: 05.02.2019, 23:42

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von meicker » 06.02.2019, 19:13

Hallo Alex,

wie gewünscht:

Code: Alles auswählen

sudo pivccu-info
piVCCU version: 3.37.8-6
Kernel modules: Available
Raw UART dev:   Available
HMRF Hardware:  RPI-RF-MOD
HMIP Hardware:  RPI-RF-MOD
Board serial:   58A992FB3B
Radio MAC:      unknown
SGTIN:          3014F711A0001F58A992FB3B
State:          RUNNING
PID:            1682
IP:             192.168.1.30
CPU use:        260.99 seconds
BlkIO use:      65.40 MiB
Memory use:     179.01 MiB
KMem use:       3.70 MiB
Link:           vethpivccu
 TX bytes:      128.67 KiB
 RX bytes:      374.90 KiB
 Total bytes:   503.58 KiB

Code: Alles auswählen

sudo pivccu-attach cat /var/hm_mode
HM_HMIP_ADDRESS=''
HM_HMIP_DEV='RPI-RF-MOD'
HM_HMIP_DEVNODE='/dev/raw-uart'
HM_HMIP_SERIAL='58A992FB3B'
HM_HMIP_SGTIN='3014F711A0001F58A992FB3B'
HM_HMIP_VERSION='3.4.8'
HM_HMRF_ADDRESS=''
HM_HMRF_DEV='RPI-RF-MOD'
HM_HMRF_DEVNODE='/dev/raw-uart'
HM_HMRF_SERIAL='58A992FB3B'
HM_HMRF_VERSION='3.4.8'
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=''

Code: Alles auswählen

sudo pivccu-attach cat /var/log/messages
Feb  6 19:04:05 piVCCU syslog.info syslogd started: BusyBox v1.28.4
Feb  6 19:04:05 piVCCU user.notice kernel: klogd started: BusyBox v1.28.4 (2018-08-29 11:23:30 CEST)
Feb  6 19:04:06 piVCCU syslog.info syslogd exiting
Feb  6 19:04:06 ccu3-webui syslog.info syslogd started: BusyBox v1.28.4
Feb  6 19:04:06 ccu3-webui user.notice kernel: klogd started: BusyBox v1.28.4 (2018-08-29 11:23:30 CEST)
Feb  6 19:04:07 ccu3-webui user.info firewall: configuration set
Feb  6 19:04:07 ccu3-webui daemon.info ifplugd(eth0)[212]: ifplugd 0.28 initializing.
Feb  6 19:04:07 ccu3-webui daemon.info ifplugd(eth0)[212]: Using interface eth0/9A:BA:55:FC:53:A0 with driver <veth> (version: 1.0)
Feb  6 19:04:07 ccu3-webui daemon.info ifplugd(eth0)[212]: Using detection mode: SIOCETHTOOL
Feb  6 19:04:07 ccu3-webui daemon.info ifplugd(eth0)[212]: Initialization complete, link beat detected.
Feb  6 19:04:07 ccu3-webui daemon.warn ifplugd(eth0)[212]: Could not open /dev/tty, cannot beep.
Feb  6 19:04:07 ccu3-webui daemon.info ifplugd(eth0)[212]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Feb  6 19:04:07 ccu3-webui daemon.warn ifplugd(eth0)[212]: client: ifup: interface eth0 already configured
Feb  6 19:04:07 ccu3-webui daemon.info ifplugd(eth0)[212]: Program executed successfully.
Feb  6 19:04:14 ccu3-webui daemon.notice ntpdate[217]: step time server 81.14.202.21 offset -0.000130 sec
Feb  6 19:04:14 ccu3-webui daemon.notice ntpd[218]: ntpd 4.2.8p11@1.3728-o Wed Aug 29 10:08:05 UTC 2018 (1): Starting
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[218]: Command line: /usr/sbin/ntpd -g ntp.homematic.com
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[220]: proto: precision = 0.583 usec (-21)
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[220]: Listen and drop on 0 v6wildcard [::]:123
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[220]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[220]: Listen normally on 2 lo 127.0.0.1:123
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[220]: Listen normally on 3 eth0 192.168.1.30:123
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[220]: Listen normally on 4 lo [::1]:123
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[220]: Listen normally on 5 eth0 [fe80::98ba:55ff:fefc:53a0%8]:123
Feb  6 19:04:14 ccu3-webui daemon.info ntpd[220]: Listening on routing socket on fd #22 for interface updates
Feb  6 19:04:14 ccu3-webui daemon.err xinetd[240]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Feb  6 19:04:14 ccu3-webui daemon.crit xinetd[240]: 240 {init_services} no services. Exiting...
Feb  6 19:04:14 ccu3-webui user.info root: Updating RF Lan Gateway Coprocessor Firmware
Feb  6 19:04:14 ccu3-webui user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Feb  6 19:04:14 ccu3-webui user.info root: Updating RF Lan Gateway Firmware
Feb  6 19:04:14 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Feb  6 19:04:14 ccu3-webui user.info root: Updating Wired Lan Gateway Firmware
Feb  6 19:04:14 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Feb  6 19:04:14 ccu3-webui daemon.info snmpd[295]: Created directory: /var/lib/snmp
Feb  6 19:04:14 ccu3-webui daemon.info snmpd[295]: Created directory: /var/lib/snmp/cert_indexes
Feb  6 19:04:14 ccu3-webui daemon.info snmpd[295]: Created directory: /var/lib/snmp/mib_indexes
Feb  6 19:04:14 ccu3-webui daemon.info snmpd[295]: Turning on AgentX master support.
Feb  6 19:04:14 ccu3-webui daemon.info snmpd[297]: NET-SNMP version 5.7.3
Feb  6 19:04:16 ccu3-webui user.info kernel: [   38.416543] eq3loop: eq3loop_open_slave() mmd_bidcos
Feb  6 19:04:28 ccu3-webui user.info kernel: [   49.977493] eq3loop: eq3loop_open_slave() mmd_hmip
Feb  6 19:04:28 ccu3-webui user.info kernel: [   49.977629] eq3loop: eq3loop_close_slave() mmd_hmip
Feb  6 19:04:28 ccu3-webui user.info kernel: [   49.980292] eq3loop: eq3loop_open_slave() mmd_hmip
Feb  6 19:04:28 ccu3-webui user.info kernel: [   49.980543] eq3loop: eq3loop_close_slave() mmd_hmip
Feb  6 19:04:28 ccu3-webui user.info kernel: [   49.987602] eq3loop: eq3loop_open_slave() mmd_hmip
Feb  6 19:04:28 ccu3-webui user.notice kernel: [   49.989486] eq3loop: eq3loop_ioctl_slave() mmd_hmip: unhandled ioctl 0x545D
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IsePersist::LoadObject -> Error ReadIsTag tag =id [iseDOMpersist.cpp:727]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> Error loading from file. ObjectID: 1022 type: CHANNEL [iseDOM.cpp:2363]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]
Feb  6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> ReadElement failed! OID: oid Value: 1022 [iseDOM.cpp:2373]

Code: Alles auswählen

sudo pivccu-attach cat /var/log/hmserver.log
Feb 6 19:04:21 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Feb 6 19:04:21 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor 
Feb 6 19:04:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_1 subtype=default 
Feb 6 19:04:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_2 subtype=default 
Feb 6 19:04:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_1 subtype=default 
Feb 6 19:04:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_2 subtype=default 
Feb 6 19:04:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_BUS_CONFIG_MISMATCH subtype=default 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 20 classes to Vert.x 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 20 VertxDeployers initialized 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (dfbf64e6-842b-488d-b0eb-4296c14a0be1) 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (21a8c341-d4fb-4ff9-9dbc-0a91bce98a93) 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of CheckDeviceExistHandler succeeded (7469b5f5-6ece-4dbf-8432-f5ac5c97607a) 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (6d9aafb6-2320-40ac-9bd4-a96a1aaf4793) 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (bdddecdf-3682-43d7-a99d-9358b9e7e70c) 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of TransactionSubsystemHandler succeeded (fcb1a8e7-14be-4556-bd10-2ddbb76223bc) 
Feb 6 19:04:26 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Feb 6 19:04:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KeyServerWorker succeeded (859e227c-ad30-4cff-8dec-539cd0646b1b) 
Feb 6 19:04:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of KryoPersistenceWorker succeeded (63d7a230-1183-4cb2-b732-0457960b6fc0) 
Feb 6 19:04:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerPersistentDataLoader succeeded (5d91d316-ecdf-47be-a591-66b6ef7c4010) 
Feb 6 19:04:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (ef644176-7181-4e84-afb0-73a89d403b72) 
Feb 6 19:04:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (db27b08e-3bd2-4e47-970b-607663dd7687) 
Feb 6 19:04:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBackendNotificationHandler succeeded (bd5af437-fb66-437d-89d3-1e30ea57ebfa) 
Feb 6 19:04:28 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Feb 6 19:04:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendCommandHandler succeeded (cec710b0-5e9d-4894-a737-2d035997f7fb) 
Feb 6 19:04:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of IncomingHMIPFrameHandler succeeded (f76ccd1d-9b40-421e-a448-4518bff95c00) 
Feb 6 19:04:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LegacyAPIWorker succeeded (cb577a34-1640-4522-a38f-7226d7e3cbe2) 
Feb 6 19:04:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LegacyNotificationHandler succeeded (458fe1da-329f-4df4-8b33-6f535eb28faa) 
Feb 6 19:04:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerAdapterInitialization succeeded (036e1740-6319-43ee-aa23-3254d355359f) 
Feb 6 19:04:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of FirmwareLoaderFileSystem succeeded (9fda5cda-21f2-467b-be9a-d92463bbfe47) 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 11784546... 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A0001F58A992FB3B to 3 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 3.4.8 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.1 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.34.0 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: CC1310 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 44382976 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 44615470 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A0001F58A992FB3B initialized 
Feb 6 19:04:28 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Feb 6 19:04:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyInitializion succeeded (49ff7aa0-c607-46b2-9ee7-7406fd0cdd4f) 
Feb 6 19:04:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (cf691129-c3bc-4ed8-a035-4541e0ace275) 
Feb 6 19:04:29 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-0] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware 
Feb 6 19:04:29 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-6] SYSTEM: Checking all devices on all accesspoints for updates 
Feb 6 19:04:29 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-6] SYSTEM: There are 0 APs queued with updatable devices 
Feb 6 19:04:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Feb 6 19:04:30 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 2010 
Feb 6 19:04:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxEventLoopExecuteTime: 2000000000 
Feb 6 19:04:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default BlockedThreadCheckInterval: 1000 
Feb 6 19:04:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxWorkerExecuteTime: 60000000000 
Feb 6 19:04:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default EventLoopPoolSize: 8 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: deploying 10 classes to Vert.x 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: 10 VertxDeployers initialized 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (7819f57c-4f4a-4792-aa63-423a21d37066) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (97f9400f-d526-4408-a323-0fe0377efafa) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of RegaClientWorker succeeded (a6fedbef-8288-46cf-9b7c-3155af799508) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of StorageRequestWorker succeeded (f8221d5c-fd00-4ee5-97fa-35b60b6c14fb) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CouplingRequestWorker succeeded (0900d936-1266-464f-97f5-d2d0156c1fb1) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (8ac7369d-a033-430c-a31c-3ec167e83319) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of GroupRequestWorker succeeded (2822c397-f0e1-45b8-8f16-220ab1ce0556) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (1237c345-4a69-4971-aa23-43acb31df7e4) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DiagramRequestWorker succeeded (6f719e35-e61e-492e-a33b-7a0db0231e9c) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (16299212-ca58-4f06-9c4f-58a6aa7e2ea7) 
Feb 6 19:04:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: initial deployment complete _____________________________________________________ 
Feb 6 19:04:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Starting HMServer at 127.0.0.1:9292 
Feb 6 19:04:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Read Configuration 
Feb 6 19:04:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create Bidcos Dispatcher 
Feb 6 19:04:33 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] InitBidCosCache 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create groupDefinitionProvider 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create VirtualDeviceHolder 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create VirtualDeviceHandlerRega 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupAdministrationService 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupDeviceDispatcher 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupDeviceHandler 
Feb 6 19:04:34 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] @GroupDeviceHandler - initializing... 
Feb 6 19:04:34 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Feb 6 19:04:34 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Feb 6 19:04:34 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> got groupDefinitionProvider 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create BidCosGroupMemberProvider 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init groupAdministrationService 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init Virtual OS Device 
Feb 6 19:04:34 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init ESHLight Bridge 
Feb 6 19:04:35 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create RrdDatalogging 
Feb 6 19:04:35 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create MeasurementService 
Feb 6 19:04:35 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init MeasurementService 
Feb 6 19:04:35 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create HTTP Server 
Feb 6 19:04:35 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create BidCos context and start handler 
Feb 6 19:04:35 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create group context and start handler 
Feb 6 19:04:35 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:9292/bidcos 
Feb 6 19:04:35 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished 
Feb 6 19:04:35 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-1] Added InterfaceId: HmIP-RF_java 
Feb 6 19:04:35 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-1] updateDevicesForClient HmIP-RF_java -> 3 device addresses will be added 
Feb 6 19:04:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Starting HMServer done 
Feb 6 19:04:43 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:9099/mediola 
Feb 6 19:04:43 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Feb 6 19:04:43 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: mediola_2010_000000000000 
Feb 6 19:04:43 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-4] updateDevicesForClient mediola_2010_000000000000 -> 3 device addresses will be added 
Feb 6 19:06:24 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.1.31:2010 
Feb 6 19:06:24 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Feb 6 19:06:24 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: hm-rpc.0 
Feb 6 19:06:25 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient hm-rpc.0 -> 3 device addresses will be added 
Feb 6 19:09:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-6] SYSTEM: 0 Accesspoints in Queue 
Feb 6 19:09:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-6] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Feb 6 19:09:27 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-6] SYSTEM: Eventlistener Handler utilization: 0/50 used


Gruß,
Marc

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

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von deimos » 06.02.2019, 19:55

Hi,

Code: Alles auswählen

Feb 6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IsePersist::LoadObject -> Error ReadIsTag tag =id [iseDOMpersist.cpp:727] Feb 6 19:04:36 ccu3-webui local0.err ReGaHss: Error: IseDOM::PersistLoad -> Error loading from file. ObjectID: 1022 type: CHANNEL [iseDOM.cpp:2363] 
Deine RegaDOM ist kaputt. Da hilft nur noch Backup der CCU einspielen.

Viele Grüße
Alex

meicker
Beiträge: 11
Registriert: 05.02.2019, 23:42

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von meicker » 06.02.2019, 21:39

Hi Alex,

hab ich glaube ich nicht mehr ... es sei denn im pivccu ist ein backup vorhanden. Das vom ioBroker hatte ich gelöscht. Hatte zu viele Backups und die SD war voll ... Ist da was ? Oder muss ich neu installieren bzw. gibt es die Möglichkeit da drüber zu bügeln ?

vg
Marc

klassisch
Beiträge: 3974
Registriert: 24.03.2011, 04:32
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 110 Mal
Danksagung erhalten: 71 Mal

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von klassisch » 07.02.2019, 00:29

IoBroker hat mit der Regadom nichts zu tun.
Man kann von der CCU auch im webUi ein Back-up machen, welches dann auf dem PC landet , von dem aus man das Back-up angestoßen hat. Vielleicht hast du noch ein solches Backup.

meicker
Beiträge: 11
Registriert: 05.02.2019, 23:42

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von meicker » 07.02.2019, 09:50

schaue ich mal nach später ...

Ich habe eh nur ein gerät drin, der Schaden ist nicht besonders hoch. Das eine angelerne Gerät funktioniert auch noch ... Also ist diese defekte datei nur für das Webinterface zuständig ?

Kann man nicht einfach drüber installieren ? Wie kann ich den Fehler beheben wenn ich kein Backup habe ?

vg
Marc

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

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von deimos » 07.02.2019, 09:57

Hi,

ich äußere mal den Verdacht, dass deine RegaDOM kaputt gegangen ist, weil kein Platz mehr auf der SD war, dann kann das natürlich gnadenlos scheitern beim Speichern.

Die weiteren Schritte:

Erstmal einen "Werksreset" der virtuellen CCU:

Code: Alles auswählen

sudo systemctl stop pivccu
sudo rm -rf /var/lib/piVCCU3/userfs/*
sudo systemctl start pivccu
Danach dann entweder das Backup per WebUI einspielen oder das bisherige Geräte in den Werkszustand zurücksetzen und neu anlernen.

Viele Grüße
Alex

meicker
Beiträge: 11
Registriert: 05.02.2019, 23:42

Re: hm-rega startet nicht (gelb) ioBroker

Beitrag von meicker » 07.02.2019, 21:56

Hi Alex,

perfekt ! Backup hatte ich auch eines gefunden, läuft alles wieder ...

Wie läuft das eigentlich mit der Firmware ? Ich habe jetzt 3.37.8 und es gibt ja bald 3.41.11 oder es gibt sie schon ...
Was muss ich für das Update machen ?

Viele Grüße,
Marc

Antworten

Zurück zu „piVCCU“