piVCCU Update 3.47.10 und 2.47.10

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

g55
Beiträge: 79
Registriert: 02.10.2018, 19:24
Hat sich bedankt: 14 Mal
Danksagung erhalten: 2 Mal

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von g55 » 11.07.2019, 00:18

danke @ Alex
heute war ich nicht "online", hab aber im Log gesehen, dass der DC 2 mal bis auf 100% gestiegen ist. :shock:
An Scripts hab ich z.Zt. eigentlich nur das von alchy mit DC aktiv, eines für HM und eines für HMIP ... ok, hab schon gelesen, dass das eigentlich gleich sein sollte ... da ich mehr IP-Geräte habe als HM-Geräte, interesssiert mich der Unterschied schon ... macht bei mir grad max. 4% aus, als nicht die Welt. Alle anderen Test-Scripts sind grad deaktiviert .
Hab auch noch mal meine Programme durchforstet, sind ja nur ca. 3-4 ... da war bei einem noch nen "Anfängerfehler" drin. Statt "bei Änderung auslösen" hatte ich "bei Aktualisierung" ... prompt geändert.
Nach dem letzten Reboot heute 22:14 ist jetzt alles normal... DC bei 10-12 %, wer ich weiter beobachten.
Was mir dennoch auffällt, sind Meldungen der Rega in /var/log/messages, meist bez. HMIP-Komponenten, z.B.

Code: Alles auswählen

local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000A570998B66C:1","SMOKE_DETECTOR_ALARM_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SMOKE_DETECTOR_ALARM_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000A570998B66C:1","SMOKE_DETECTOR_ALARM_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000A58A991FC03:1","SMOKE_DETECTOR_ALARM_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SMOKE_DETECTOR_ALARM_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000A58A991FC03:1","SMOKE_DETECTOR_ALARM_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000A58A991FC54:1","SMOKE_DETECTOR_ALARM_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SMOKE_DETECTOR_ALARM_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000A58A991FC54:1","SMOKE_DETECTOR_ALARM_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000A58A991FC4E:1","SMOKE_DETECTOR_ALARM_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SMOKE_DETECTOR_ALARM_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000A58A991FC4E:1","SMOKE_DETECTOR_ALARM_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
ok, das war beim letzten Reboot, eben Rauchmelder, vorher waren es die Heizungsthermostate HMIP-eTRV*
Ich kann mir das grad nicht erklären... werde es weiter beobachten.
Meine Vermutungen bez. DC > 50% gehen z.Zt. eher Richtung "babbling Idiot", Batterie irgendwo leer, obwohl keine Meldung alá "Low_bat" erscheint...schau'n mer mal

btw. das mit dem DC hatte ich definitiv in der Vorgänger-Version nicht, kam erst mit 3.47.10 :?:
VG & gN8
RPi3 v1.2 mit piVCCU3 v3.47.22-32 (testing), ca. 14 HM- und 56 HMIP-Geräte

deimos
Beiträge: 3162
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Hat sich bedankt: 13 Mal
Danksagung erhalten: 76 Mal
Kontaktdaten:

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von deimos » 11.07.2019, 09:37

Hi,

ich habe gerade sowhl piVCCU 2.47.12 als auch piVCCU3 3.47.10 im stable Repository bereitgestellt.

Eigentlich wollte ich das ja bereits Anfang der Woche machen, aber aufgrund des Bugs mit den Energiezählern habe ich abgewartet, ob hier noch eine neue Firmware von eQ-3 bereitgestellt wird. Nachdem dies bisher leider nicht erfolgt ist, habe ich mich entschieden, den mehr oder weniger offiziellen Patch auch in piVCCU aufzunehmen, auch wenn das eigentlich der Philosophie von piVCCU widerspricht. Da die Alternative wäre, die neuen Versionen noch "ewig" zurückzuhalten, glaube ich aber, dass das die bessere Wahl ist.

Viele Grüße
Alex

raimundl
Beiträge: 40
Registriert: 22.09.2018, 15:49

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von raimundl » 12.07.2019, 14:33

Danke!
Nun auch "Produktivsystem" upgedatet, schaut bisher alles problemlos aus.

Eine Anmerkung/Frage:

In der "testing Version" am Testserver habe ich ein Balkendiagramm hinsichtlich Duty Cycle - bei der "stable" nicht mehr.

LG
System "Charly" mit RPi3+/RPI-RF-MOD und ca. 40 HM/2 HMIP auf piVCCU3 mit fhem

deimos
Beiträge: 3162
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Hat sich bedankt: 13 Mal
Danksagung erhalten: 76 Mal
Kontaktdaten:

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von deimos » 12.07.2019, 14:37

Hi,
raimundl hat geschrieben:
12.07.2019, 14:33
In der "testing Version" am Testserver habe ich ein Balkendiagramm hinsichtlich Duty Cycle - bei der "stable" nicht mehr.
Die beiden Versionen sind aktuell identisch, der Balken sollte also da sein und ist es bei mir auch. Browercache vielleicht nicht gelöscht? (Bzw. Strg-F5 für Forced Refresh)

Viele Grüße
Alex

raimundl
Beiträge: 40
Registriert: 22.09.2018, 15:49

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von raimundl » 12.07.2019, 14:50

deimos hat geschrieben:
12.07.2019, 14:37

Die beiden Versionen sind aktuell identisch, der Balken sollte also da sein und ist es bei mir auch. Browercache vielleicht nicht gelöscht? (Bzw. Strg-F5 für Forced Refresh)

Viele Grüße
Alex
Danke, super - ja das war es!

LG
System "Charly" mit RPi3+/RPI-RF-MOD und ca. 40 HM/2 HMIP auf piVCCU3 mit fhem

lonsimbt
Beiträge: 18
Registriert: 20.04.2016, 13:41
Wohnort: Ruhrgebiet
Hat sich bedankt: 2 Mal

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von lonsimbt » 14.07.2019, 15:12

So, ich bin auch endlich dazu gekommen: Das Update auf 3.47.10 ist auf meinem Tnkerboard problemlos durchgelaufen.

Besten Dank dafür und viele Grüße

Marco
--
debmatic in VM (debian Buster) unter proxmox 6.0 mit HB-RF-USB und RPI-RF-MOD
iobroker im Container unter proxmox 6.0
25 HomeMatic Geräte, Phillips Hue, Ikea Tradfri, Logitech Harmony Hub, Botvac Connected, Robonect

g55
Beiträge: 79
Registriert: 02.10.2018, 19:24
Hat sich bedankt: 14 Mal
Danksagung erhalten: 2 Mal

Re: piVCCU Update 3.47.10 und 2.47.10 - my DC problem ...

Beitrag von g55 » 16.07.2019, 19:52

Hi @Alex,
ich hab die letzten Tage nn wirklich alles probiert:
  • ein backup nach dem anderen der 3.47.10 eingespielt, mit / ohne meine gerade laufenden Tests mit CUxD, email etc.
  • mit Hilfe von @Black's SDV alle Inkonsistenzen in Variablen/Programmen/scripts beseitigt ... sagt SDV jedenfalls :wink:
Trotzdem geht der DC öfters durch die Decke... gestern hatte ich 100% :shock: und weitere Kommunikationsprobleme :?:

Ich hab jetzt mein letztes Backup der 3.45.7-26 aktiv ... da sieht der DC normal aus per alchy's scripts, auch hab ich derzeit keine weiteren Probleme mit "Kommunikation". Die Version 3.45.7-26 ist ja auch per "apt-cache policy pivccu3" die vorige Version in deinem Repo.

Schade eigentlich, ich bin eigentlich gerade dabei, meine Rollos zu automatisieren (Test-Motor heute gerade angekommen, BROLL liegt schon darum), bzw. Alarmanlage, Heizungssteuerung, Email/Push zu testen ... dafür brauch ich ein stabiles pivccu3 aufm Raspi ... die 3.47.10 isses wohl nicht, daher stelle ich meine Tests ein. Und beobachte mal die nächsten 1-2 Tage den DC im 3.45.7-26.

Hab eben gesehen, dass Jens im viewtopic.php?f=65&t=51682&start=50#p518593 was von "warten...warten" geschrieben hat ... kann ich grad nicht nachvollziehen, aber sieht für mich persönlich so aus, dass da noch was kommen wir / bzw. z.Zt. evtl im Argen liegt.

Wie immer, ich bin gerne bereit weiter zu testen, wenn weitere Infos benötigt werden, "sacht bScheid" :wink:

btw., ich habe gar kein LAN-Gateway ... hab auch gelesen, dass es mal Probleme gab bez. GTW in der DC-Anzeige in der 3.47.xx ... k.A., ob das hier relevant ist :roll:
RPi3 v1.2 mit piVCCU3 v3.47.22-32 (testing), ca. 14 HM- und 56 HMIP-Geräte

deimos
Beiträge: 3162
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Hat sich bedankt: 13 Mal
Danksagung erhalten: 76 Mal
Kontaktdaten:

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von deimos » 16.07.2019, 20:20

Hi,

aus dem Kontext raus würde ich die Aussage von Jens eher in die Richtung deuten, dass der DC nach einem Reboot gerne mal nach oben abhaut und Zeit braucht um sich zu berühigen.
Da ich jetzt weder bei der CCU3, noch bei piVCCU, noch bei RaspberryMatic von signifikant vielen DC Problemen gehört habe, würde ich stark vermuten, dass das Problem primär in deinem System zu suchen ist, wobei ich damit nicht ausschließen will, dass es mit dem Update zusammenhängt, ich sehe nur kein generelles Problem.

Falls du das RPI-RF-MOD hast und sofern drin System auf der 3.45 stabil läuft, könntest du in einem nächsten Schritt innerhalb des CCU Containers die Datei /etc/config/no-coprocessor-update anlegen und danach ein Update von piVCCU machen. Hierdurch bleibt die bisherige Firmware auf dem RPI-RF-MOD und man könnte dadurch ausschließen, dass es an diesem liegt.

Ansonsten empfiehlt sich natürlich das schon mehrfach im Forum diskutierte Verhalten bei DC Problemen und das kann ich bei deinen Beschreibungen jetzt noch nicht wirklich erkennen.

Viele Grüße
Alex

g55
Beiträge: 79
Registriert: 02.10.2018, 19:24
Hat sich bedankt: 14 Mal
Danksagung erhalten: 2 Mal

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von g55 » 16.07.2019, 21:33

danke Alex, aber nee, ich hab das alte Funkmodul, kein RPI-RF-MOD.
und in der alten Version 3.45.7-26, die ich vor 3 Std. gebootet hab, ist der DC auch beim Start stabil, da "haut nix nach oben ab", hab es gerade gecheckt, läuft jetzt ca 3 Std, die 3.45.7 , DC ist hier immer noch unter 10 :

Code: Alles auswählen

***** messages *****
Jul 16 18:57:49 piVCCU syslog.info syslogd started: BusyBox v1.29.2
Jul 16 18:57:49 piVCCU user.notice kernel: klogd started: BusyBox v1.29.2 (2019-04-02 13:27:46 CEST)
Jul 16 18:57:49 piVCCU syslog.info syslogd exiting
Jul 16 18:57:49 HasiMatic syslog.info syslogd started: BusyBox v1.29.2
Jul 16 18:57:49 HasiMatic user.notice kernel: klogd started: BusyBox v1.29.2 (2019-04-02 13:27:46 CEST)
Jul 16 18:57:50 HasiMatic user.info firewall: configuration set
Jul 16 18:57:50 HasiMatic daemon.info ifplugd(eth0)[259]: ifplugd 0.28 initializing.
Jul 16 18:57:50 HasiMatic daemon.info ifplugd(eth0)[259]: Using interface eth0/FA:7D:2F:84:02:4B with driver <veth> (version: 1.0)
Jul 16 18:57:50 HasiMatic daemon.info ifplugd(eth0)[259]: Using detection mode: SIOCETHTOOL
Jul 16 18:57:50 HasiMatic daemon.info ifplugd(eth0)[259]: Initialization complete, link beat detected.
Jul 16 18:57:50 HasiMatic daemon.warn ifplugd(eth0)[259]: Could not open /dev/tty, cannot beep.
Jul 16 18:57:50 HasiMatic daemon.info ifplugd(eth0)[259]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jul 16 18:57:50 HasiMatic daemon.warn ifplugd(eth0)[259]: client: ifup: interface eth0 already configured
Jul 16 18:57:50 HasiMatic daemon.info ifplugd(eth0)[259]: Program executed successfully.
Jul 16 18:57:56 HasiMatic daemon.notice ntpdate[267]: step time server 192.168.176.1 offset -0.000161 sec
Jul 16 18:57:56 HasiMatic daemon.notice ntpd[268]: ntpd [email protected] Tue Apr  2 11:26:20 UTC 2019 (1): Starting
Jul 16 18:57:56 HasiMatic daemon.info ntpd[268]: Command line: /usr/sbin/ntpd -g 192.168.176.1
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: proto: precision = 0.989 usec (-20)
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: Listen and drop on 0 v6wildcard [::]:123
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: Listen normally on 2 lo 127.0.0.1:123
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: Listen normally on 3 eth0 192.168.176.21:123
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: Listen normally on 4 lo [::1]:123
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: Listen normally on 5 eth0 [fe80::f87d:2fff:fe84:24b%4]:123
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: Listening on routing socket on fd #22 for interface updates
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Jul 16 18:57:56 HasiMatic daemon.info ntpd[270]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Jul 16 18:57:56 HasiMatic daemon.err xinetd[288]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Jul 16 18:57:56 HasiMatic daemon.crit xinetd[288]: 288 {init_services} no services. Exiting...
Jul 16 18:57:56 HasiMatic auth.info sshd[313]: Server listening on 0.0.0.0 port 22.
Jul 16 18:57:56 HasiMatic auth.info sshd[313]: Server listening on :: port 22.
Jul 16 18:57:56 HasiMatic user.info root: Updating RF Lan Gateway Coprocessor Firmware
Jul 16 18:57:56 HasiMatic user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Jul 16 18:57:56 HasiMatic user.info root: Updating RF Lan Gateway Firmware
Jul 16 18:57:56 HasiMatic user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Jul 16 18:57:56 HasiMatic user.info kernel: [  237.964165] eq3loop: created slave mmd_hmip
Jul 16 18:57:56 HasiMatic user.info kernel: [  237.964471] eq3loop: created slave mmd_bidcos
Jul 16 18:58:12 HasiMatic user.info kernel: [  253.640286] eq3loop: eq3loop_open_slave() mmd_hmip
Jul 16 18:58:12 HasiMatic user.info kernel: [  253.640537] eq3loop: eq3loop_close_slave() mmd_hmip
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979A9E:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979A9E:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"001558A99C522A:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"001558A99C522A:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979E16:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979E16:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979B14:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979B14:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979E20:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979E20:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979F3F:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979F3F:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979E19:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979E19:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979CCD:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979CCD:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:42 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979AAB:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979AAB:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:42 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:43 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D3C99C7DA3:6","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:43 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0001D3C99C7DA3:6","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:43 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:43 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00155993963154:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:43 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"00155993963154:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:43 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:43 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D3C99C7DA3:6","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:43 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0001D3C99C7DA3:6","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:43 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 18:58:43 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0000D8A9979E39:1","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 18:58:43 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"0000D8A9979E39:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 18:58:43 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:04:57 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000A570998B66C:1","SMOKE_DETECTOR_ALARM_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SMOKE_DETECTOR_ALARM_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000A570998B66C:1","SMOKE_DETECTOR_ALARM_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:04:57 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000A58A991FC03:1","SMOKE_DETECTOR_ALARM_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SMOKE_DETECTOR_ALARM_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000A58A991FC03:1","SMOKE_DETECTOR_ALARM_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:04:57 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000A58A991FC54:1","SMOKE_DETECTOR_ALARM_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SMOKE_DETECTOR_ALARM_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000A58A991FC54:1","SMOKE_DETECTOR_ALARM_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:04:57 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000A58A991FC4E:1","SMOKE_DETECTOR_ALARM_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SMOKE_DETECTOR_ALARM_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000A58A991FC4E:1","SMOKE_DETECTOR_ALARM_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:04:57 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"001898A99271BC:1","WATERLEVEL_DETECTED"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: WATERLEVEL_DETECTED"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"001898A99271BC:1","WATERLEVEL_DETECTED"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:04:57 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"001898A99271BC:1","MOISTURE_DETECTED"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: MOISTURE_DETECTED"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"001898A99271BC:1","MOISTURE_DETECTED"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:04:57 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:08:42 HasiMatic user.debug script: [DutyCycle 4] by_Alchy
Jul 16 19:09:42 HasiMatic user.debug script: [DutyCycleIP 5] by_Alchy
Jul 16 19:11:21 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000393C99B15B7:1","PARTY_TIME_START"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_TIME_START"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:11:21 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000393C99B15B7:1","PARTY_TIME_START"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:11:21 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal =  [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:11:21 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000393C99B15B7:1","PARTY_TIME_END"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_TIME_END"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:11:21 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000393C99B15B7:1","PARTY_TIME_END"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:11:21 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal =  [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:11:21 HasiMatic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000393C99B15B7:1","PARTY_SET_POINT_TEMPERATURE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_SET_POINT_TEMPERATURE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 16 19:11:21 HasiMatic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1011, params: {"000393C99B15B7:1","PARTY_SET_POINT_TEMPERATURE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 16 19:11:21 HasiMatic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 16 19:18:42 HasiMatic user.debug script: [DutyCycle 8] by_Alchy
Jul 16 19:20:42 HasiMatic user.debug script: [DutyCycleIP 9] by_Alchy
Jul 16 19:28:42 HasiMatic user.debug script: [DutyCycle 10] by_Alchy
Jul 16 19:31:42 HasiMatic user.debug script: [DutyCycleIP 10] by_Alchy
Jul 16 19:38:42 HasiMatic user.debug script: [DutyCycle 11] by_Alchy
Jul 16 19:42:42 HasiMatic user.debug script: [DutyCycleIP 11] by_Alchy
Jul 16 19:48:42 HasiMatic user.debug script: [DutyCycle 12] by_Alchy
Jul 16 19:53:42 HasiMatic user.debug script: [DutyCycleIP 12] by_Alchy
Jul 16 19:58:42 HasiMatic user.debug script: [DutyCycle 10] by_Alchy
Jul 16 20:04:42 HasiMatic user.debug script: [DutyCycleIP 11] by_Alchy
Jul 16 20:08:42 HasiMatic user.debug script: [DutyCycle 9] by_Alchy
Jul 16 20:15:42 HasiMatic user.debug script: [DutyCycleIP 8] by_Alchy
Jul 16 20:18:42 HasiMatic user.debug script: [DutyCycle 7] by_Alchy
Jul 16 20:26:42 HasiMatic user.debug script: [DutyCycleIP 8] by_Alchy
Jul 16 20:28:42 HasiMatic user.debug script: [DutyCycle 7] by_Alchy
Jul 16 20:37:42 HasiMatic user.debug script: [DutyCycleIP 8] by_Alchy
Jul 16 20:38:42 HasiMatic user.debug script: [DutyCycle 8] by_Alchy
Jul 16 20:48:42 HasiMatic user.debug script: [DutyCycleIP 8] by_Alchy
Jul 16 20:48:43 HasiMatic user.debug script: [DutyCycle 7] by_Alchy


***** hmserver.log *****
Jul 16 18:58:04 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Jul 16 18:58:04 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
Jul 16 18:58:04 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 32 classes to Vert.x 
Jul 16 18:58:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 32 VertxDeployers initialized 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointElectroCardioGram succeeded (5ec3c816-c8d6-4c7b-bae4-572106ebda20) 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (574ad11d-e519-4b09-9b96-e93c55aee755) 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CheckDeviceExistHandler succeeded (a00519ca-da97-4e4f-a30e-aef8f396abdb) 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of HMIPTRXWriterWorker succeeded (b69afacf-bb26-49bb-973d-1347a3f759cd) 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (9a56860d-566c-4464-b9f1-977dd3b8e669) 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (eb1e1e21-6e31-4754-8028-e0c63b57bfdb) 
Jul 16 18:58:11 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of KeyServerWorker succeeded (03e19f83-68a3-4a71-8e97-8563278791f2) 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of TransactionSubsystemHandler succeeded (50774097-9414-44ed-88b5-2a1c872c0693) 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointKeyServerWorker succeeded (487489bb-e2b7-42d6-b209-a1c98feaee9e) 
Jul 16 18:58:11 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of RouterKeyServerWorker succeeded (06f74d1f-2749-4545-b635-1220ba24b56a) 
Jul 16 18:58:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of KryoPersistenceWorker succeeded (102f832c-804e-4b3b-b92d-4dc6fb4f2286) 
Jul 16 18:58:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LocalServerPersistentDataLoader succeeded (7885f438-f7e3-42fd-8d49-d01c01345c5c) 
Jul 16 18:58:12 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: DeviceLiveUpdateSubsystem started 
Jul 16 18:58:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (ef445a56-0e29-419e-9af8-1c7ee5e1e998) 
Jul 16 18:58:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (a6cef17b-8b5e-4db8-ba3c-58a5fb2d156e) 
Jul 16 18:58:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointWatchdog succeeded (a004527d-4931-4836-9ff9-5dd3930c30bf) 
Jul 16 18:58:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of RemoteCommAdapterInitialization succeeded (384eadee-3d4a-4010-b8a6-9f4fa8ccac0e) 
Jul 16 18:58:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of IncomingHMIPFrameHandler succeeded (35464f0d-72a5-412e-af7f-e7a4d36d9464) 
Jul 16 18:58:12 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerAdapterInitialization succeeded (27eb631d-9e76-420c-82cc-0c1ac79d4b39) 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12126473... 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D709AC79CF to 3 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0 
Jul 16 18:58:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Jul 16 18:58:13 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Jul 16 18:58:13 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 87701505 
Jul 16 18:58:13 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 87712950 
Jul 16 18:58:13 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 35 link partners 
Jul 16 18:58:13 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D709AC79CF initialized 
Jul 16 18:58:13 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Jul 16 18:58:13 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Jul 16 18:58:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of FirmwareLoaderFileSystem succeeded (b6a9e874-c0f9-4539-bf1f-d65c30aa8f56) 
Jul 16 18:58:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (725eb904-6b76-49a5-8ca2-b8e4409098a1) 
Jul 16 18:58:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (58ee8718-d647-4f7e-a944-f9b0c929cef7) 
Jul 16 18:58:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of AccessPointAuthorisationHandler succeeded (5a055d57-f537-439e-88c1-433af3f5dc29) 
Jul 16 18:58:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of WebSocketManager succeeded (7d712878-8606-4b56-ba3f-b4f16896b01c) 
Jul 16 18:58:13 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Checking all devices on all accesspoints for updates 
Jul 16 18:58:13 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (RF) 
Jul 16 18:58:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointMessageDispatcher succeeded (ce332397-53ff-463f-9b76-b27f40335cb5) 
Jul 16 18:58:13 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
Jul 16 18:58:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of BackendCommandHandler succeeded (a4221a2c-704d-4a4c-ba68-f7d111e43eaa) 
Jul 16 18:58:14 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointCommDevice succeeded (b5deff1b-7727-4df1-b174-7dbb3a7cf55d) 
Jul 16 18:58:14 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of RemoteCommAdapterFinalization succeeded (e04f517a-67aa-4c16-bf02-5a483b4b8f49) 
Jul 16 18:58:14 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-1] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 -> 192.168.176.21 
Jul 16 18:58:14 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded (1b2667ef-e36d-4a01-a9dd-2b6fa7266898) 
Jul 16 18:58:14 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyNotificationHandler succeeded (074345b8-efd8-492c-a7f7-3ba68463553e) 
Jul 16 18:58:14 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyAPIWorker succeeded (37daf00f-cc41-4747-8bf9-51b9fa9eeb08) 
Jul 16 18:58:14 de.eq3.cbcs.lib.lanrouting.LanRoutingWorker INFO  [vert.x-worker-thread-1] AP 3014F711A061A7D709AC79CF: Could not initialize routing of access point, version is 2.8.6 
Jul 16 18:58:14 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LanRoutingWorker succeeded (ffca4f07-baef-4b34-bade-5e4601c65759) 
Jul 16 18:58:14 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-0] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168.176.21) 
Jul 16 18:58:14 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-2] UDP Routing multi cast established on network interface eth0 : 192.168.176.21 
Jul 16 18:58:14 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-3] SYSTEM: Started Access Point WebSocket server with port 9293 
Jul 16 18:58:14 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-3] SYSTEM: connector open 
Jul 16 18:58:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (17f3ab4b-c545-454b-946a-18e854f96623) 
Jul 16 18:58:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Jul 16 18:58:15 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
Jul 16 18:58:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
Jul 16 18:58:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
Jul 16 18:58:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
Jul 16 18:58:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized 
Jul 16 18:58:19 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (ff61e879-68d4-42ff-afce-5e4284c2bc40) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of StorageRequestWorker succeeded (7c3dd338-0bcc-4bc0-b557-d44ef119e5ac) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (b5c0a39d-a348-471a-93cb-1139e98d5374) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CouplingRequestWorker succeeded (003b9f2e-0a3d-409f-981b-5525efecd3d5) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of RegaClientWorker succeeded (25a1de20-2377-4af5-9540-e483f80ff322) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of EnergyPriceRequestWorker succeeded (5505dc5b-1239-4faf-9f9d-7109fc4cce80) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupRequestWorker succeeded (57d44c1a-462d-4548-b080-2c2b63c80e20) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DiagramRequestWorker succeeded (f56c19c0-7148-4c58-9ab9-5f196654d97c) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (ca312396-9f7a-48a5-a116-e437aea4db57) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (3c200dc9-5dbd-4f1f-8fc2-7ef0dcf4bd23) 
Jul 16 18:58:20 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
Jul 16 18:58:20 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
Jul 16 18:58:20 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
Jul 16 18:58:20 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
Jul 16 18:58:20 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
Jul 16 18:58:22 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler 
Jul 16 18:58:23 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing... 
Jul 16 18:58:23 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Jul 16 18:58:23 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Jul 16 18:58:23 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device 
Jul 16 18:58:23 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge 
Jul 16 18:58:24 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging 
Jul 16 18:58:24 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService 
Jul 16 18:58:24 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService 
Jul 16 18:58:25 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server 
Jul 16 18:58:25 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler 
Jul 16 18:58:25 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler 
Jul 16 18:58:25 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 
Jul 16 18:58:25 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished 
Jul 16 18:58:25 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: HmIP-RF_java 
Jul 16 18:58:25 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-4] updateDevicesForClient HmIP-RF_java -> 286 device addresses will be added 
Jul 16 18:58:26 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done 
Jul 16 18:58:42 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-4] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999 
Jul 16 18:58:42 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-4] Added InterfaceId: 1007 
Jul 16 18:58:42 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-16] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Jul 16 18:58:42 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-16] updateDevicesForClient -> 21 device addresses will be added 
Jul 16 18:58:54 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-16] set ready config of INT0000001 
Jul 16 18:58:54 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-16] set ready config of INT0000002 
Jul 16 18:58:54 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-16] set ready config of INT0000003 
Jul 16 18:58:54 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999 
Jul 16 18:58:54 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] init finished 
Jul 16 18:58:54 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: 1011 
Jul 16 19:03:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:03:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:03:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:04:48 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 2. Original time: 1563296306962 
Jul 16 19:04:48 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563296306962 
Jul 16 19:04:48 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563296332960 
Jul 16 19:04:48 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563296332960 
Jul 16 19:04:48 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563296386960 
Jul 16 19:08:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:08:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:08:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:08:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 19:12:40 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563296688960 
Jul 16 19:12:40 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563296694960 
Jul 16 19:13:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:13:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:13:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:15:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563296942960 
Jul 16 19:15:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563296942960 
Jul 16 19:15:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563296952960 
Jul 16 19:15:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563296952960 
Jul 16 19:18:10 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563297160961 
Jul 16 19:18:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:18:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:18:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:18:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 19:18:32 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563297192960 
Jul 16 19:18:32 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563297192960 
Jul 16 19:23:10 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563297358960 
Jul 16 19:23:10 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 3. Original time: 1563297408960 
Jul 16 19:23:10 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563297408960 
Jul 16 19:23:10 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563297408960 
Jul 16 19:23:10 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563297444960 
Jul 16 19:23:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:23:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:23:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:23:24 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 2. Original time: 1563297490961 
Jul 16 19:23:24 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563297490961 
Jul 16 19:23:24 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563297490961 
Jul 16 19:24:06 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563297512960 
Jul 16 19:24:06 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563297512960 
Jul 16 19:24:06 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563297540960 
Jul 16 19:25:16 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563297576960 
Jul 16 19:28:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:28:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:28:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:28:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 19:28:22 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563297636960 
Jul 16 19:28:22 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563297656960 
Jul 16 19:28:22 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563297656960 
Jul 16 19:28:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563297804960 
Jul 16 19:33:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:33:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:33:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:33:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563297846961 
Jul 16 19:33:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563297846961 
Jul 16 19:33:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563297846961 
Jul 16 19:33:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563297916960 
Jul 16 19:33:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563298102960 
Jul 16 19:33:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563298108960 
Jul 16 19:33:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563298108960 
Jul 16 19:38:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:38:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:38:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:38:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 19:38:40 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563298408960 
Jul 16 19:43:02 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563298612960 
Jul 16 19:43:02 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563298612960 
Jul 16 19:43:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:43:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:43:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:43:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563298720961 
Jul 16 19:43:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563298728960 
Jul 16 19:43:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563298728960 
Jul 16 19:46:12 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563298828960 
Jul 16 19:46:12 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563298856960 
Jul 16 19:46:12 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563298856960 
Jul 16 19:48:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:48:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:48:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:48:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 19:49:22 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563298982960 
Jul 16 19:49:22 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563299038960 
Jul 16 19:49:22 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 3. Original time: 1563299056960 
Jul 16 19:49:22 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563299056960 
Jul 16 19:49:22 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563299056960 
Jul 16 19:49:53 org.apache.http.impl.client.DefaultHttpClient INFO  [vert.x-worker-thread-1] I/O exception (java.net.SocketException) caught when processing request to {}->http://127.0.0.1:39292: Broken pipe (Write failed) 
Jul 16 19:49:53 org.apache.http.impl.client.DefaultHttpClient INFO  [vert.x-worker-thread-1] Retrying request to {}->http://127.0.0.1:39292 
Jul 16 19:51:34 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 2. Original time: 1563299172960 
Jul 16 19:51:34 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563299172960 
Jul 16 19:51:34 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563299172960 
Jul 16 19:53:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:53:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:53:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:53:48 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563299224960 
Jul 16 19:53:48 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563299278960 
Jul 16 19:58:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 19:58:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 19:58:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 19:58:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563299362960 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563299374960 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563299374960 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563299494960 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563299494960 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563299494960 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563299628960 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 2. Original time: 1563299652960 
Jul 16 19:59:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563299652960 
Jul 16 20:03:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:03:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:03:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:07:08 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563299966960 
Jul 16 20:07:08 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563299982960 
Jul 16 20:07:08 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563299982960 
Jul 16 20:07:08 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563300124960 
Jul 16 20:07:08 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563300124960 
Jul 16 20:08:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:08:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:08:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:08:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 20:10:14 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563300244960 
Jul 16 20:10:14 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563300252960 
Jul 16 20:10:14 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563300252960 
Jul 16 20:12:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563300428960 
Jul 16 20:13:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:13:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:13:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:13:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563300504960 
Jul 16 20:13:58 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563300504960 
Jul 16 20:15:52 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563300614960 
Jul 16 20:15:52 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563300614960 
Jul 16 20:18:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:18:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:18:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:18:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 20:18:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563300700960 
Jul 16 20:18:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563300700960 
Jul 16 20:18:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563300718960 
Jul 16 20:18:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563300748961 
Jul 16 20:18:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 3. Original time: 1563300754960 
Jul 16 20:18:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563300754960 
Jul 16 20:18:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563300754960 
Jul 16 20:19:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 2. Original time: 1563300838960 
Jul 16 20:19:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563300838960 
Jul 16 20:19:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563300838960 
Jul 16 20:20:08 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563300890961 
Jul 16 20:21:30 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563300952960 
Jul 16 20:21:30 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563300966961 
Jul 16 20:23:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:23:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:23:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:25:00 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563301186961 
Jul 16 20:25:00 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563301186961 
Jul 16 20:25:00 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563301186961 
Jul 16 20:27:18 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563301208960 
Jul 16 20:27:18 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563301208960 
Jul 16 20:27:18 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563301290960 
Jul 16 20:27:18 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563301324960 
Jul 16 20:27:18 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563301324960 
Jul 16 20:27:18 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563301324960 
Jul 16 20:28:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:28:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:28:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:28:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 20:30:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563301412960 
Jul 16 20:30:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563301500960 
Jul 16 20:33:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:33:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:33:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:33:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563301638961 
Jul 16 20:33:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563301688960 
Jul 16 20:38:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:38:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:38:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:38:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 20:38:44 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563301828960 
Jul 16 20:38:44 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563301828960 
Jul 16 20:38:44 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563301868960 
Jul 16 20:38:44 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563301874960 
Jul 16 20:38:44 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563301892960 
Jul 16 20:38:44 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563301892960 
Jul 16 20:39:20 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563302036960 
Jul 16 20:43:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:43:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:43:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:43:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563302324960 
Jul 16 20:44:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563302360960 
Jul 16 20:44:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563302360960 
Jul 16 20:44:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 3. Original time: 1563302368960 
Jul 16 20:44:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563302368960 
Jul 16 20:44:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563302368960 
Jul 16 20:45:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563302408960 
Jul 16 20:45:26 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563302408960 
Jul 16 20:48:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:48:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:48:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:48:12 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO  [vert.x-eventloop-thread-6] SYSTEM: Access Point Watchdog running periodic connection check... 
Jul 16 20:49:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 2. Original time: 1563302488961 
Jul 16 20:49:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563302488961 
Jul 16 20:49:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563302488961 
Jul 16 20:49:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563302540960 
Jul 16 20:49:28 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563302636961 
Jul 16 20:49:46 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563302686960 
Jul 16 20:50:12 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563302696961 
Jul 16 20:50:12 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563302696961 
Jul 16 20:52:06 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563302726960 
Jul 16 20:53:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Jul 16 20:53:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Jul 16 20:53:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Jul 16 20:54:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 1. Original time: 1563302968960 
Jul 16 20:54:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563302968960 
Jul 16 20:54:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563302968960 
Jul 16 20:54:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 2. Original time: 1563302974960 
Jul 16 20:54:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 7. Original time: 1563302974960 
Jul 16 20:54:56 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 5. Original time: 1563302986961 
Jul 16 20:55:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 4. Original time: 1563303012960 
Jul 16 20:55:36 de.eq3.lib.measurement.MeasurementService INFO  [Timer-0] Drop unhandled values (timeout) for diagram 6. Original time: 1563303012960 
ich will ja nicht ausschließen, dass im meiner Installation noch irgendwas "grütze" ist ... daher hab ich ja den SDV von @Black installiert und die DatenKonsistenz gecheckt und korrigiert im Test Image 3.47.10 ... bringt jedoch nix bez. DC :(

Und eben im aktiven 3.45.7 hab ich auch Inkonsistenzen lt. SDV, ich habe aber nix korrigiert per SDV, und trotzdem ist der DC hier immer noch < 10 !!
Das verstehe ich eben nicht.
Und wenn Jens irgendwo schreibt (sorry find ich grad net), dass die DC-Anzeige in 3.47.10 mal korrigiert wurde wegen LAN-Gateway ... "hab ich nicht", dann kommt mir glatt der Verdacht, dass die DC-Anzeige doch eben ab und an mal versucht, ein LAN-Gateway zu erreichen, was bei mir definitiv nicht erfolgreich sein kann.

Zudem hab ich der 3.47.10 öfters die Meldung im "messages" :
local0.warn ReGaHss: WARNING: unknown session id = [ExecSystem():iseESPexec.cpp:3709]
eigentlich immer, wenn ich das WebUI verlasse ... ok, getestet ... neue Systemvariablen bleiben bei mir vorhanden.
In der 3.45.7 passiert das nicht..

Summa sumarum : für mich ist die 3.47.10 zur Zeit nicht anwendbar wegen DC. Ich werde meine Konfiguration natürlich weiter checken auch mit SDV, um alle Inkonsistenzen auszubügeln, ich frage mich halt nur, warum bei mir mit 3.45.7 das alles trotzdem funktioniert ?
RPi3 v1.2 mit piVCCU3 v3.47.22-32 (testing), ca. 14 HM- und 56 HMIP-Geräte

deimos
Beiträge: 3162
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Hat sich bedankt: 13 Mal
Danksagung erhalten: 76 Mal
Kontaktdaten:

Re: piVCCU Update 3.47.10 und 2.47.10

Beitrag von deimos » 16.07.2019, 21:49

Hi,

du mischt hier Sachen zusammen, die nichts miteinander zu tun haben.

Das mit der Session Fehlermeldung dürfte ein Bug in der CCU3 Firmware sein, hat mit dem DC aber nichts zu tun. Details gibt es von Jerome in einem Thread zur Original CCU.

Die Anzeige kann den DC auch nicht nach oben treiben, der DC wird vom Funkmodul berechnet und von der Software nur ausgelesen.
Ebenfalls wirst du mit dem SDV keine DC Probleme lösen, das ist für was komplett anderes da.

Ich tippe drauf, dass du irgendein problematisches Skript oder Programm hast, welches durch irgendeine Änderung innerhalb der Rega jetzt Amok läuft.

Viele Grüße
Alex

Antworten

Zurück zu „piVCCU“