debmatic Update auf 3.53.34
Moderator: Co-Administratoren
- deimos
- Beiträge: 5383
- Registriert: 20.06.2017, 10:38
- System: Alternative CCU (auf Basis OCCU)
- Wohnort: Leimersheim
- Hat sich bedankt: 121 Mal
- Danksagung erhalten: 950 Mal
- Kontaktdaten:
debmatic Update auf 3.53.34
Hi,
ich habe grade das Update auf die Firmware 3.53.34 im testing APT Repository bereitgestellt. Falls keine Probleme auftauchen, werde ich das Update wie gehabt in ca. 2 Wochen auch ins stable APT Repository übernehmen.
Viele Grüße
Alex
ich habe grade das Update auf die Firmware 3.53.34 im testing APT Repository bereitgestellt. Falls keine Probleme auftauchen, werde ich das Update wie gehabt in ca. 2 Wochen auch ins stable APT Repository übernehmen.
Viele Grüße
Alex
Re: debmatic Update auf 3.53.34
Moin
habe sudo apt update && sudo apt upgrade ausgeführt.
Ergebnis siehe:
viewtopic.php?f=76&t=60150&p=614574#p614574
habe sudo apt update && sudo apt upgrade ausgeführt.
Ergebnis siehe:
viewtopic.php?f=76&t=60150&p=614574#p614574
-
- Beiträge: 33
- Registriert: 20.04.2016, 13:41
- Wohnort: Ruhrgebiet
- Hat sich bedankt: 53 Mal
- Danksagung erhalten: 2 Mal
Re: debmatic Update auf 3.53.34
Update ist glatt durchgelaufen und die debmatic verhält sich unauffällig.
Danke für die schnelle Bereitstellung des Updates und viele Grüße
Marco
Danke für die schnelle Bereitstellung des Updates und viele Grüße
Marco
debmatic in VM (debian Buster) unter proxmox 7.2 mit HB-RF-USB und RPI-RF-MOD
iobroker im Container unter proxmox 7.2
knapp 40 HomeMatic Geräte, Phillips Hue, Ikea Tradfri, Logitech Harmony Hub, Botvac Connected, Robonect
iobroker im Container unter proxmox 7.2
knapp 40 HomeMatic Geräte, Phillips Hue, Ikea Tradfri, Logitech Harmony Hub, Botvac Connected, Robonect
-
- Beiträge: 131
- Registriert: 28.12.2019, 18:57
- System: Alternative CCU (auf Basis OCCU)
- Hat sich bedankt: 4 Mal
- Danksagung erhalten: 3 Mal
Re: debmatic Update auf 3.53.34
Bei mir zeigt debmatic ein Update zur Version „ 3.53.30.53“ an wieder was ganz neues?
- deimos
- Beiträge: 5383
- Registriert: 20.06.2017, 10:38
- System: Alternative CCU (auf Basis OCCU)
- Wohnort: Leimersheim
- Hat sich bedankt: 121 Mal
- Danksagung erhalten: 950 Mal
- Kontaktdaten:
Re: debmatic Update auf 3.53.34
Hi,
Viele Grüße
Alex
Die 3.53.30-53 ist die aktuellste stable Version. Die 3.53.34-55 ist die aktuellste testing Version.eviltrooper hat geschrieben: ↑04.11.2020, 15:23Bei mir zeigt debmatic ein Update zur Version „ 3.53.30.53“ an wieder was ganz neues?
Viele Grüße
Alex
-
- Beiträge: 131
- Registriert: 28.12.2019, 18:57
- System: Alternative CCU (auf Basis OCCU)
- Hat sich bedankt: 4 Mal
- Danksagung erhalten: 3 Mal
- deimos
- Beiträge: 5383
- Registriert: 20.06.2017, 10:38
- System: Alternative CCU (auf Basis OCCU)
- Wohnort: Leimersheim
- Hat sich bedankt: 121 Mal
- Danksagung erhalten: 950 Mal
- Kontaktdaten:
Re: debmatic Update auf 3.53.34
Hi,
ich habe die Version vorhin auch in das stable APT Repository übernommen.
Viele Grüße
Alex
ich habe die Version vorhin auch in das stable APT Repository übernommen.
Viele Grüße
Alex
Re: debmatic Update auf 3.53.34
Kurze Rückinfo: Die neue Version läuft wie sie soll, keine Fehlermeldungen beim Update. Ich habe allerdings auch nur wenig Hardware am RasPi4: HmIP-SWO-B und HmIP-SWD, bedient durch den HM-MOD-RPI-PCB. Den Rest macht FHEM, gekoppelt mit HMCCU.
-
- Beiträge: 131
- Registriert: 28.12.2019, 18:57
- System: Alternative CCU (auf Basis OCCU)
- Hat sich bedankt: 4 Mal
- Danksagung erhalten: 3 Mal
Re: debmatic Update auf 3.53.34
hat bei mir auch funktioniert..
allerdings mit Schock.. aber der Raspi hatte auch ein Kernel Update.. nach einem Neustart ging alles.
allerdings mit Schock.. aber der Raspi hatte auch ein Kernel Update.. nach einem Neustart ging alles.
Re: debmatic Update auf 3.53.34
Hallo,
nach dem Update auf die Version 3.53.34 und nachdem sich die Vorgängerversion erneut aufgehangen hatte (die HomeMatic-Programme reagierten nicht mehr) bekomme ich jetzt alle circa 30 Sekunden folgende Einträge in die hmserver.log protokolliert:
Infos zum System:
Das Ganze ist eine VM, die auf einem Intel NUC mit Proxmox VE läuft.
Sonst ist soweit alles unauffällig aber die Log-Einträge geben mir schon zu denken.
Zumal davor sonst nur alle 5 Minuten etwas protokolliert wurde und das über "Wochen" hinweg, soweit ich das aus den Logs nachvollziehen kann. Nach dem Update ging es dann mit den Fehlern los.
Alle Einträge seit dem Update:
Eventuell hat ja jemand eine Idee, was das sein könnte und wie ich es wegbekomme.
Ich habe übrigens keine HM-Wired oder HM-IP-Wired Geräte. Ist alles Funk.
Schöne Grüße
nach dem Update auf die Version 3.53.34 und nachdem sich die Vorgängerversion erneut aufgehangen hatte (die HomeMatic-Programme reagierten nicht mehr) bekomme ich jetzt alle circa 30 Sekunden folgende Einträge in die hmserver.log protokolliert:
Code: Alles auswählen
Dec 6 09:36:56 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-0] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:36:56 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-2] AP 3014F711A061A7DA498F9F88: Could not parse routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendFrameToBackbone(BackboneWorker.java:677)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$15(BackboneWorker.java:121)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Infos zum System:
Code: Alles auswählen
debmatic-info
debmatic version: 3.53.34-55
Kernel modules: Available
Raw UART dev: Available
HMRF Hardware: HM-MOD-RPI-PCB
Connected via: HB-RF-USB@usb-0000:00:1d.0-1 (/dev/raw-uart)
Board serial: QEQ0407432
Radio MAC: 0x6D0171
HMIP Hardware: HM-MOD-RPI-PCB
SGTIN: 3014F711A061A7DA498F9F88
Radio MAC: 0xB96500
java -version
openjdk version "1.8.0_275"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_275-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.275-b01, mixed mode)
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
cat /proc/version
Linux version 4.19.0-13-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28)
Sonst ist soweit alles unauffällig aber die Log-Einträge geben mir schon zu denken.
Zumal davor sonst nur alle 5 Minuten etwas protokolliert wurde und das über "Wochen" hinweg, soweit ich das aus den Logs nachvollziehen kann. Nach dem Update ging es dann mit den Fehlern los.
Code: Alles auswählen
Dec 6 09:00:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: 0 Accesspoints in Queue
Dec 6 09:00:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Dec 6 09:00:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: Eventlistener Handler utilization: 0/50 used
Dec 6 09:05:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: 0 Accesspoints in Queue
Dec 6 09:05:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Dec 6 09:05:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: Eventlistener Handler utilization: 0/50 used
Dec 6 09:05:14 de.eq3.cbcs.lib.remotecommadapter.device.service.AccessPointWatchdog INFO [vert.x-eventloop-thread-1] SYSTEM: Access Point Watchdog running periodic connection check...
Dec 6 09:10:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: 0 Accesspoints in Queue
Dec 6 09:10:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Dec 6 09:10:12 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: Eventlistener Handler utilization: 0/50 used
Alle Einträge seit dem Update:
Code: Alles auswählen
Dec 6 09:36:47 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory
Dec 6 09:36:47 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created instance of HMServerConfiguration with parameter(s)
Dec 6 09:36:47 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 parameter(s), in declarative order [String]
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionManagementVerticle] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RoutingNotificationHandler] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackboneWorker] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RouteManagementWorker] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 25 classes to Vert.x
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of CheckDeviceExistHandler succeeded (1df24f2c-4495-4a04-b163-950ea8882ec4)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (d8a51324-f1a5-41af-963a-dbdcf0bc941e)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of RoutingNotificationHandler succeeded (b3610b4e-7094-4779-8c6b-3e97a73b096c)
Dec 6 09:36:48 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (e1aa743d-4e89-45c4-8929-fc8d8859f100)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of TransactionSubsystemHandler succeeded (388405f5-389a-4e11-86a9-5cb437b7b845)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 25 VertxDeployers initialized
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (d540912a-80be-4d4c-a3d3-2449b97fa203)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (d40caecb-1571-459d-aa36-5fca48c8e786)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (6404b780-120f-4179-a41f-0cccef465271)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerPersistentDataLoader succeeded (c2ba5d1f-8a91-4a07-8ec3-72d203c8760a)
Dec 6 09:36:48 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: DeviceLiveUpdateSubsystem started
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (a8020133-55c5-4d25-8ac7-fce2c56dafdc)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (f6f23d9f-11fc-46f1-b8a8-8bad4bba339d)
Dec 6 09:36:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of KeyServerWorker succeeded (aadd7e6c-774d-4639-8eec-7748288f39b6)
Dec 6 09:36:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (886871b1-ddba-40c6-88d6-f71d97ea35ee)
Dec 6 09:36:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of TransactionManagementVerticle succeeded (b580c06d-84bc-4923-b09b-928b08dd2f74)
Dec 6 09:36:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of IncomingHMIPFrameHandler succeeded (7b127e53-c238-479d-b24b-4ef30aa326f9)
Dec 6 09:36:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of BackendCommandHandler succeeded (0d642400-e9e5-4c26-ac62-e3867fdf5bcf)
Dec 6 09:36:49 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware
Dec 6 09:36:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of FirmwareLoaderFileSystem succeeded (66583985-ddf9-470b-87bd-5445da8edea5)
Dec 6 09:36:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of LocalServerAdapterInitialization succeeded (5640fd22-cf0d-421b-af5d-2d7eb3e51a13)
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRX_App
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running or started
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ...
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 12150016...
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A061A7DA498F9F88 to 3
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version...
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 2.8.6
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.3
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.20.3
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] MCU type: Si1002_8051
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Duty Cycle: 0.0
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] set DutyCycle limit to ffffffc8
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set Duty Cycle Limit
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Current Security Counter: 396428800
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Update security counter to calculation: 406494251
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener WARN [Thread-6] Routing was enabled in configuration but cannot be initialized
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter has 2 link partners
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Adapter with Access Point id 3014F711A061A7DA498F9F88 initialized
Dec 6 09:36:50 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Dec 6 09:36:51 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of RouteManagementWorker succeeded (45fc94f6-8c97-4cba-8e5d-f944e431efd0)
Dec 6 09:36:51 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (86d4560b-8a69-494c-a27c-4627ea3d591a)
Dec 6 09:36:51 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-worker-thread-1] UDP Routing configuration: trying to bind port 43438 on ens18 0.0.0.0 -> 10.5.5.200
Dec 6 09:36:51 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LegacyNotificationHandler succeeded (b3efe08f-cda6-4239-a8ce-1c0510b392fc)
Dec 6 09:36:51 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LegacyAPIWorker succeeded (922cfdee-7115-4bc3-97ad-926779dcbf40)
Dec 6 09:36:51 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of LegacyBackendNotificationHandler succeeded (d5298c9a-73c4-4245-9163-a45be3806dcb)
Dec 6 09:36:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates
Dec 6 09:36:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (RF)
Dec 6 09:36:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
Dec 6 09:36:51 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of BackboneWorker succeeded (40d462d7-c26e-4205-bc7f-4512a70e2a3c)
Dec 6 09:36:51 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-worker-thread-0] UDP Routing established on network interface ens18 : 0.0.0.0 (10.5.5.200)
Dec 6 09:36:51 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-worker-thread-2] UDP Routing multi cast 'DEFAULT_MULTICAST_ADDRESS' established on network interface ens18 : 10.5.5.200
Dec 6 09:36:52 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LegacyInitializion succeeded (6eae2db6-4957-4f28-844f-ad07e5b18500)
Dec 6 09:36:53 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Dec 6 09:36:53 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
Dec 6 09:36:56 de.eq3.cbcs.server.core.transaction.TransactionManagementVerticle ERROR [vert.x-eventloop-thread-5] AP 3014F711A061A7DA498F9F88: Error while queueing transaction:
java.lang.NullPointerException
at de.eq3.cbcs.server.core.task.protocol.SendFrameTask.determineActualTargetInterface(SendFrameTask.java:420)
at de.eq3.cbcs.server.core.task.protocol.SendFrameTask.getTargetIdentifier(SendFrameTask.java:191)
at de.eq3.cbcs.server.core.task.constraint.TargetInterfaceTaskConstraint.evaluateExecution(TargetInterfaceTaskConstraint.java:42)
at de.eq3.cbcs.transaction.management.TransactionManager.isExecutionPossible(TransactionManager.java:577)
at de.eq3.cbcs.transaction.management.TransactionManager.executeNextTasks(TransactionManager.java:501)
at de.eq3.cbcs.transaction.management.TransactionManager.queueTransaction(TransactionManager.java:219)
at de.eq3.cbcs.transaction.hmip.management.HmipTransactionManager.queueTransaction(HmipTransactionManager.java:102)
at de.eq3.cbcs.server.core.transaction.TransactionManagementVerticle$4.handle(TransactionManagementVerticle.java:246)
at de.eq3.cbcs.server.core.transaction.TransactionManagementVerticle$4.handle(TransactionManagementVerticle.java:216)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:445)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:36:56 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-0] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:36:56 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-2] AP 3014F711A061A7DA498F9F88: Could not parse routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendFrameToBackbone(BackboneWorker.java:677)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$15(BackboneWorker.java:121)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:36:56 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-3] AP 3014F711A061A7DA498F9F88: Could not parse routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendFrameToBackbone(BackboneWorker.java:677)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$15(BackboneWorker.java:121)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default BlockedThreadCheckInterval: 1000
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxWorkerExecuteTime: 60000000000
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default EventLoopPoolSize: 8
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [AccessPointUpdateServerWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [AccessPointUpdateLoaderWorker] (1) *worker
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: deploying 12 classes to Vert.x
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: 12 VertxDeployers initialized
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (a75b7b6b-3f2f-4f02-ad1b-6087e356badf)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (7c288b19-ed7a-4d6b-9751-635e8555c54e)
Dec 6 09:36:57 de.eq3.ccu.hmip.accesspoint.update.AccessPointUpdateLoaderWorker INFO [vert.x-worker-thread-4] SYSTEM: Firmware update directory is set to /etc/config/firmware
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of AccessPointUpdateLoaderWorker succeeded (7ec1a9f7-0ed3-4552-8110-762e23de47a1)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointUpdateServerWorker succeeded (67e578f0-98e7-4cb6-a283-2351e8abf4ba)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of CouplingRequestWorker succeeded (0c4833dd-2d83-44b9-a8bf-723af8fa6612)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of StorageRequestWorker succeeded (bd300fe8-5059-475c-bf1d-7182c15289b3)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of RegaClientWorker succeeded (fa4953c0-4ce9-4b0c-a958-cea5acdc92d7)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (e3b15e15-a7f2-4a76-ad31-53ca6a93a92b)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of GroupRequestWorker succeeded (75292d7f-df9d-4ba1-881a-5187933f28fe)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DiagramRequestWorker succeeded (f4582265-5499-446e-adb9-2a001469c87a)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (2e14c29a-d1b8-4d7b-9edd-74e5c48d4aec)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (20ef77f7-d2ff-41e0-adc8-6d77f1d04423)
Dec 6 09:36:57 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer at 127.0.0.1:39292
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Read Configuration
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Bidcos Dispatcher
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] InitBidCosCache
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create groupDefinitionProvider
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHolder
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHandlerRega
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupAdministrationService
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceDispatcher
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceHandler
Dec 6 09:36:57 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] @GroupDeviceHandler - initializing...
Dec 6 09:36:57 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Dec 6 09:36:57 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Dec 6 09:36:57 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> got groupDefinitionProvider
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCosGroupMemberProvider
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init groupAdministrationService
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Virtual OS Device
Dec 6 09:36:57 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init ESHLight Bridge
Dec 6 09:36:58 org.eclipse.smarthome.binding.hue.handler.HueBridgeHandler INFO [safeCall-4] Polling interval not configured for this hue bridge. Using default value: 10s
Dec 6 09:36:58 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create RrdDatalogging
Dec 6 09:36:58 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create MeasurementService
Dec 6 09:36:58 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init MeasurementService
Dec 6 09:36:58 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create HTTP Server
Dec 6 09:36:58 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCos context and start handler
Dec 6 09:36:58 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group context and start handler
Dec 6 09:36:58 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
Dec 6 09:36:58 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-3] init finished
Dec 6 09:36:58 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-4] Added InterfaceId: HmIP-RF_java
Dec 6 09:36:58 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-4] updateDevicesForClient HmIP-RF_java -> 66 device addresses will be added
Dec 6 09:36:58 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates
Dec 6 09:36:58 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (RF)
Dec 6 09:36:58 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
Dec 6 09:36:59 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer done
Dec 6 09:37:21 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-4] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:37:51 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-4] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:38:21 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-4] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:40:35 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory
Dec 6 09:40:35 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created instance of HMServerConfiguration with parameter(s)
Dec 6 09:40:35 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 parameter(s), in declarative order [String]
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionManagementVerticle] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RoutingNotificationHandler] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackboneWorker] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RouteManagementWorker] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 25 classes to Vert.x
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (dae1aad0-3dae-4449-8d12-286598fc6970)
Dec 6 09:40:36 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of TransactionSubsystemHandler succeeded (3079567c-9efd-4e67-b242-717aaa7871f5)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of CheckDeviceExistHandler succeeded (d949efe5-8ad1-43fe-bf59-6043774426eb)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of HMIPTRXWriterWorker succeeded (268b3e04-b5d1-4a2c-881f-b2d226b64fe8)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of KeyServerWorker succeeded (3ea95a80-2248-4ca4-aedd-6a775e226025)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (ef030c4d-ad57-4dab-a96a-44f5ebf6c950)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of RoutingNotificationHandler succeeded (259024e3-8e08-407f-a3a3-2827b39303e6)
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 25 VertxDeployers initialized
Dec 6 09:40:36 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (bd339811-3f41-46fb-b58e-39d4d801322f)
Dec 6 09:40:37 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-5] SYSTEM: DeviceLiveUpdateSubsystem started
Dec 6 09:40:37 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of KryoPersistenceWorker succeeded (d5b863b8-7c5b-4a5c-948f-4f8e55a79c43)
Dec 6 09:40:37 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (3ca1a671-0792-4519-8830-c1568533e11d)
Dec 6 09:40:37 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (6aeeacfb-56d0-4171-aaec-555d15d35931)
Dec 6 09:40:37 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerPersistentDataLoader succeeded (69e365c0-fd25-44e3-81d6-a27ccb3ff706)
Dec 6 09:40:38 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of TransactionManagementVerticle succeeded (7ab5816e-5017-426f-b91b-b44e46a98acf)
Dec 6 09:40:38 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (956f6f96-d809-4077-bd48-5a3b3f7c8c85)
Dec 6 09:40:38 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of BackendCommandHandler succeeded (84e7bbe8-e5ac-4aec-8640-e44838b7940d)
Dec 6 09:40:38 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of IncomingHMIPFrameHandler succeeded (d51e1429-a771-476d-a642-933ae731b45d)
Dec 6 09:40:38 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware
Dec 6 09:40:38 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of FirmwareLoaderFileSystem succeeded (72b6a649-fe28-481e-84e3-e27cc0ef391c)
Dec 6 09:40:38 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerAdapterInitialization succeeded (d85ee9d9-b9e4-4b0a-95f2-c5c5ebeadc64)
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRX_App
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running or started
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ...
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 12150016...
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A061A7DA498F9F88 to 3
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version...
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 2.8.6
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.3
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.20.3
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] MCU type: Si1002_8051
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Duty Cycle: 0.0
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] set DutyCycle limit to ffffffc8
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set Duty Cycle Limit
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Current Security Counter: 406494464
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Update security counter to calculation: 406495013
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener WARN [Thread-6] Routing was enabled in configuration but cannot be initialized
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter has 2 link partners
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Adapter with Access Point id 3014F711A061A7DA498F9F88 initialized
Dec 6 09:40:38 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Dec 6 09:40:39 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of RouteManagementWorker succeeded (ac41bc03-646a-4eb7-82cc-ec94e4d98a72)
Dec 6 09:40:39 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (43f63101-a6af-490d-aebd-6362e6c8b7fa)
Dec 6 09:40:39 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-worker-thread-3] UDP Routing configuration: trying to bind port 43438 on ens18 0.0.0.0 -> 10.5.5.200
Dec 6 09:40:39 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyBackendNotificationHandler succeeded (fc1e782b-784f-43fd-94fa-22401abfd67e)
Dec 6 09:40:39 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates
Dec 6 09:40:39 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of LegacyNotificationHandler succeeded (b0516058-98a5-43db-bf23-3d109c6c1b1d)
Dec 6 09:40:39 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (RF)
Dec 6 09:40:39 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
Dec 6 09:40:39 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyAPIWorker succeeded (9210cf52-61ef-4afa-b500-2d9560624f3c)
Dec 6 09:40:40 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of BackboneWorker succeeded (15d21af7-d630-4482-a1b3-a3aba85888ff)
Dec 6 09:40:40 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-worker-thread-0] UDP Routing established on network interface ens18 : 0.0.0.0 (10.5.5.200)
Dec 6 09:40:40 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-worker-thread-4] UDP Routing multi cast 'DEFAULT_MULTICAST_ADDRESS' established on network interface ens18 : 10.5.5.200
Dec 6 09:40:41 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LegacyInitializion succeeded (81eed161-e24f-4893-aa05-16a535b36006)
Dec 6 09:40:41 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Dec 6 09:40:41 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
Dec 6 09:40:44 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-1] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:40:44 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-1] AP 3014F711A061A7DA498F9F88: Could not parse routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendFrameToBackbone(BackboneWorker.java:677)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$15(BackboneWorker.java:121)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:40:44 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-0] AP 3014F711A061A7DA498F9F88: Could not parse routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendFrameToBackbone(BackboneWorker.java:677)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$15(BackboneWorker.java:121)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:40:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
Dec 6 09:40:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default BlockedThreadCheckInterval: 1000
Dec 6 09:40:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxWorkerExecuteTime: 60000000000
Dec 6 09:40:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default EventLoopPoolSize: 8
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [AccessPointUpdateServerWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [AccessPointUpdateLoaderWorker] (1) *worker
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: deploying 12 classes to Vert.x
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: 12 VertxDeployers initialized
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (685ec2c3-f09e-470d-8713-b72c26a98ef9)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (b54a250f-1206-4f45-9432-d5467af2d134)
Dec 6 09:40:45 de.eq3.ccu.hmip.accesspoint.update.AccessPointUpdateLoaderWorker INFO [vert.x-worker-thread-7] SYSTEM: Firmware update directory is set to /etc/config/firmware
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of AccessPointUpdateLoaderWorker succeeded (729e0490-f930-4124-8c85-6ef5a80afde3)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (5e6b2c50-2ef1-4bdb-b629-fc6a89f8a6b1)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of RegaClientWorker succeeded (a2b859b5-1cae-4332-934e-c94ff03fe2fa)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of CouplingRequestWorker succeeded (6937b0f6-8207-4a94-b279-072ffee7590a)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of StorageRequestWorker succeeded (31cdce7d-86bc-4309-9a4b-5cf9034734a3)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointUpdateServerWorker succeeded (0b0f60d3-f899-4d9f-9a53-2bf332594299)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of DiagramRequestWorker succeeded (760f609e-f7e7-4f46-966b-1b99f1acdc7f)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of GroupRequestWorker succeeded (5b824bc5-5872-47d2-94af-eb327efa0235)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (4e7673b4-bf5f-4f3a-b73f-f936b5d2e7ba)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (9633517c-046e-4b5a-86b4-9a3ff4106a99)
Dec 6 09:40:45 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
Dec 6 09:40:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer at 127.0.0.1:39292
Dec 6 09:40:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Read Configuration
Dec 6 09:40:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Bidcos Dispatcher
Dec 6 09:40:45 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] InitBidCosCache
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create groupDefinitionProvider
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHolder
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHandlerRega
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupAdministrationService
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceDispatcher
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceHandler
Dec 6 09:40:46 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] @GroupDeviceHandler - initializing...
Dec 6 09:40:46 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Dec 6 09:40:46 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Dec 6 09:40:46 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> got groupDefinitionProvider
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCosGroupMemberProvider
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init groupAdministrationService
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Virtual OS Device
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init ESHLight Bridge
Dec 6 09:40:46 org.eclipse.smarthome.binding.hue.handler.HueBridgeHandler INFO [safeCall-2] Polling interval not configured for this hue bridge. Using default value: 10s
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create RrdDatalogging
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create MeasurementService
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init MeasurementService
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create HTTP Server
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCos context and start handler
Dec 6 09:40:46 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group context and start handler
Dec 6 09:40:46 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos
Dec 6 09:40:46 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-0] init finished
Dec 6 09:40:46 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-4] Added InterfaceId: HmIP-RF_java
Dec 6 09:40:46 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-4] updateDevicesForClient HmIP-RF_java -> 66 device addresses will be added
Dec 6 09:40:46 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates
Dec 6 09:40:46 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (RF)
Dec 6 09:40:46 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
Dec 6 09:40:47 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer done
Dec 6 09:40:56 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-3] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999
Dec 6 09:40:56 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-3] Added InterfaceId: 28221
Dec 6 09:40:56 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-13] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Dec 6 09:40:56 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] updateDevicesForClient -> 18 device addresses will be added
Dec 6 09:41:06 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999
Dec 6 09:41:06 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-4] init finished
Dec 6 09:41:06 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-4] Added InterfaceId: 30731
Dec 6 09:41:06 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-Indirekte B
Dec 6 09:41:06 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-TV Licht
Dec 6 09:41:06 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-Philips hue
Dec 6 09:41:06 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-Fenster
Dec 6 09:41:07 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-Balkon
Dec 6 09:41:07 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-Deckenlampe
Dec 6 09:41:09 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-0] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:41:14 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-0] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Dec 6 09:41:39 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker ERROR [vert.x-worker-thread-1] AP 3014F711A061A7DA498F9F88: Could not parse outgoing routing frame
de.eq3.cbcs.util.core.InvalidParameterLengthException: The parameter key must be 16 byte long
at de.eq3.cbcs.util.core.ByteArrayUtils.validateParameterLength(ByteArrayUtils.java:200)
at de.eq3.cbcs.util.core.CbcMacAes.calculateMIC(CbcMacAes.java:423)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.sendBackboneFrameToBackbone(BackboneWorker.java:773)
at de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker.lambda$start$16(BackboneWorker.java:132)
at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Ich habe übrigens keine HM-Wired oder HM-IP-Wired Geräte. Ist alles Funk.
Schöne Grüße