Korrekt, liegt jetzt auch im APT Repository bereit.
Viele Grüße
Alex
piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Moderator: Co-Administratoren
-
deimos
- Beiträge: 5396
- Registriert: 20.06.2017, 10:38
- System: Alternative CCU (auf Basis OCCU)
- Wohnort: Leimersheim
- Hat sich bedankt: 121 Mal
- Danksagung erhalten: 957 Mal
- Kontaktdaten:
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Hi,
Viele Grüße
Alex
Viele Grüße
Alex
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Also Update ist nun drauf, den HAP hat er nun auch gesucht - scheinbar hat der jedoch bereits die aktuellste Firmware drauf.
Ich konnte ich auch nun anlernen - vielen vielen Dank.
Das größere Problem ist jedoch nun, dass sich meine Wandthermostate nicht mehr mit pivccu verbinden...
anderen HM IP geräte habe ich derweil noch nicht eingebunden
EDIT:
Anbei auch ein Screenshot der Thermostate.
Sind in meinen Fall alle.
Auch ein Reboot von PIVCCU als auch der Thermostate durch stromlos - warten - strom dran hat nichts geholfen...
auch den HAP "entlernen" hat nichts geholfen :-/
via sudo dpkg-reconfigure pivccu findet er nun kein installierte pivccu
via sudo dpkg-reconfigure pivccu3 sehr wohl...
kann es sein dass da was neu ist?
bilde mir ein dass es vorher sehrwohl via pivccu und nicht via piccu3 funkte..
kann aber auch einbildung sein
- Dateianhänge
-
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Hast du da vielleicht bereits ne Info wie ich das Problem beheben könnte? oder die vorherige Version installiere?
Ich habe seit in der Früh keinerlei Heizungssteuerung, außer händisch am Thermostat...
Wüsste auch nicht was ich noch machen könnte - außer alleinig den HAP herzunehmen und danach die Thermostate dort neu anzulernen
vielen Dank!
lg
-
deimos
- Beiträge: 5396
- Registriert: 20.06.2017, 10:38
- System: Alternative CCU (auf Basis OCCU)
- Wohnort: Leimersheim
- Hat sich bedankt: 121 Mal
- Danksagung erhalten: 957 Mal
- Kontaktdaten:
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Hi,
versuch mal bei einem der Thermostate einen Werksreset ohne vorheriges Ablernen und dann neu Anlernen.
Viele Grüße
Alex
versuch mal bei einem der Thermostate einen Werksreset ohne vorheriges Ablernen und dann neu Anlernen.
Viele Grüße
Alex
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Leider kein erfolg
EDIT:
Habe nun auch versucht ein Thermostat, der nicht so viele einstellungen hat, komplett zu entfernen, werksreset und dann neu anlernen - leider kein erfolg. es wird nichts im Posteingang gefunden.
Reboot half auch nicht :-/
LG
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
hideimos hat geschrieben: ↑24.02.2022, 20:47Hi,
was liefertViele GrüßeCode: Alles auswählen
sudo pivccu-info /var/log/hmserver.log
Alex
anbei:
Code: Alles auswählen
pi@raspberrypi:~ $ sudo pivccu-info /var/log/hmserver.log
piVCCU version: 3.61.7-69
Kernel modules: Available
Raw UART dev: Available
Rasp.Pi UART: Assigned to GPIO pins
HMRF Hardware: HMIP-RFUSB
Connected via: eQ-3 HmIP-RFUSB@usb-0000:01:00.0-1.3 (/dev/raw-uart1)
Board serial: habe ich für hier entfernt
Radio MAC: 0xFFE9DF
HMIP Hardware: HMIP-RFUSB
Connected via: eQ-3 HmIP-RFUSB@usb-0000:01:00.0-1.3 (/dev/raw-uart1)
SGTIN: habe ich für hier entfernt
Radio MAC: 0xB1EAF0
State: RUNNING
PID: 1936
IP: 192.168.1.98
Link: vethpivccu
TX bytes: 3.04 MiB
RX bytes: 1.61 MiB
Total bytes: 4.65 MiB-
deimos
- Beiträge: 5396
- Registriert: 20.06.2017, 10:38
- System: Alternative CCU (auf Basis OCCU)
- Wohnort: Leimersheim
- Hat sich bedankt: 121 Mal
- Danksagung erhalten: 957 Mal
- Kontaktdaten:
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Hi,
mein Fehler, ich meinte:
Viele Grüße
Alex
mein Fehler, ich meinte:
Code: Alles auswählen
sudo pivccu-attach cat /var/log/hmserver.logAlex
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Kein Problemdeimos hat geschrieben: ↑24.02.2022, 21:29Hi,
mein Fehler, ich meinte:
Viele GrüßeCode: Alles auswählen
sudo pivccu-attach cat /var/log/hmserver.log
Alex
Anbei:
Code: Alles auswählen
pi@raspberrypi:~ $ sudo pivccu-attach cat /var/log/hmserver.log
lxc-attach: lxc: terminal.c: lxc_terminal_create_native: 924 Not a directory - F ailed to open terminal multiplexer device
Feb 24 20:37:51 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFac tory
Feb 24 20:37:51 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created ins tance of HMServerConfiguration with parameter(s)
Feb 24 20:37:51 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 pa rameter(s), in declarative order [String]
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [HMIPTRXWriterWorker] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [KeyServerWorker] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [KryoPersistenceWorker] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [TransactionSubsystemHandler] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [LocalServerPersistentDataLoader] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [LocalServerAdapterInitialization] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [TransactionManagementVerticle] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [BackendCommandHandler] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [DeviceInclusionAcceptHandler] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [CheckDeviceExistHandler] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [IncomingHMIPFrameHandler] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [DeviceLiveUpdateSubsystem] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [DeviceDefaultConfigurationChanger] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [CyclicSmokeDetectorAwakening] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [RoutingNotificationHandler] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [BackboneWorker] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [RouteManagementWorker] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [LegacyNotificationHandler] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [LegacyAPIWorker] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: added for deployment [LegacyInitializion] (1)
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: deploying 25 classes to Vert.x
Feb 24 20:37:55 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: 25 VertxDeployers initialized
Feb 24 20:37:56 de.eq3.cbcs.server.core.vertx.CyclicSmokeDetectorAwakening INFO [vert.x-eventloop-thread-4] SYSTEM: CyclicSmokeDetectorAwakening Verticle or Wo rker started
Feb 24 20:37:56 de.eq3.cbcs.server.core.vertx.DeviceDefaultConfigurationChanger INFO [vert.x-eventloop-thread-2] SYSTEM: DeviceDefaultConfigurationChanger Vert icle or Worker started
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-2] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (44c88073-cf 4d-4d4a-bdc6-5496549e9c0a)
Feb 24 20:37:56 de.eq3.cbcs.server.core.vertx.TransactionSubsystemHandler INFO [vert.x-worker-thread-3] SYSTEM: TransactionSubsystemHandler Verticle or Worker started
Feb 24 20:37:56 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-work er-thread-1] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-4] SYSTEM: start of DeviceDefaultConfigurationChanger succeeded (84a960 ef-c148-4f09-a8be-07f4f8cc0d80)
Feb 24 20:37:56 de.eq3.cbcs.server.core.vertx.HMIPAbstractWriterWorker INFO [ve rt.x-worker-thread-0] SYSTEM: HMIPTRXWriterWorker Verticle or Worker started
Feb 24 20:37:56 de.eq3.cbcs.server.core.vertx.CheckDeviceExistHandler INFO [ver t.x-eventloop-thread-0] SYSTEM: CheckDeviceExistHandler Verticle or Worker start ed
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-6] SYSTEM: start of CheckDeviceExistHandler succeeded (eac17fd9-f463-4b d5-a739-fe9047e54bf8)
Feb 24 20:37:56 de.eq3.cbcs.server.core.vertx.RoutingNotificationHandler INFO [ vert.x-eventloop-thread-1] SYSTEM: RoutingNotificationHandler Verticle or Worker started
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-3] SYSTEM: start of HMIPTRXWriterWorker succeeded (e0b5141b-7e22-4240-a cc4-30e85d77fdcb)
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-0] SYSTEM: start of TransactionSubsystemHandler succeeded (7748a02a-c3f 4-4826-a221-cbe1ee85eb4a)
Feb 24 20:37:56 de.eq3.cbcs.server.core.vertx.KeyServerWorker INFO [vert.x-work er-thread-1] SYSTEM: KeyServerWorker Verticle or Worker started
Feb 24 20:37:56 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBlindLevelCorrectio nHandler INFO [vert.x-worker-thread-2] SYSTEM: LegacyBlindLevelCorrectionHandle r Verticle or Worker started
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-7] SYSTEM: start of RoutingNotificationHandler succeeded (deb4b860-8ffc -4635-85cb-30f949fc7ffc)
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-7] SYSTEM: start of KeyServerWorker succeeded (98849ebb-e22f-4665-bdda- 23ffbbed12d3)
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (7a3d23 66-f71a-4620-8791-52b548dc2073)
Feb 24 20:37:56 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO [vert .x-eventloop-thread-5] SYSTEM: DeviceLiveUpdateSubsystem Verticle or Worker star ted
Feb 24 20:37:56 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-5] SYSTEM: DeviceLiveUpdateSubsystem started
Feb 24 20:37:56 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO [vert .x-eventloop-thread-7] SYSTEM: DeviceBackgroundUpdateSubsystem Verticle or Worke r started
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-4] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (1641ac45 -b417-4cd5-8146-4478d0667e25)
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-2] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (4e2bb5e0-6981- 4186-af9c-2bcf1e512357)
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-5] SYSTEM: start of KryoPersistenceWorker succeeded (217f36e4-309a-428c -80e9-3aa33992056b)
Feb 24 20:37:56 de.eq3.cbcs.server.local.base.internal.LocalServerPersistentData Loader INFO [vert.x-eventloop-thread-1] SYSTEM: LocalServerPersistentDataLoader Verticle or Worker started
Feb 24 20:37:56 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-0] SYSTEM: start of LocalServerPersistentDataLoader succeeded (d11e6ea0 -4e67-42bf-bfba-0a24fc54269b)
Feb 24 20:37:57 de.eq3.cbcs.server.core.vertx.DeviceInclusionAcceptHandler INFO [vert.x-eventloop-thread-3] SYSTEM: DeviceInclusionAcceptHandler Verticle or Wo rker started
Feb 24 20:37:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-2] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (0bdda5ee-c5 9f-4c5f-8fe4-772f458b0f84)
Feb 24 20:37:57 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-1] SYSTEM: Firmware update directory is set to /etc/confi g/firmware
Feb 24 20:37:57 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-1] SYSTEM: FirmwareLoaderFileSystem Verticle or Worker st arted
Feb 24 20:37:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-4] SYSTEM: start of FirmwareLoaderFileSystem succeeded (b1f7d55d-ea30-4 ffd-adea-9c4022b7ad65)
Feb 24 20:37:57 de.eq3.cbcs.server.core.vertx.IncomingHMIPFrameHandler INFO [ve rt.x-eventloop-thread-7] SYSTEM: IncomingHMIPFrameHandler Verticle or Worker sta rted
Feb 24 20:37:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-6] SYSTEM: start of IncomingHMIPFrameHandler succeeded (091be3ef-5c46-4 0c0-b65c-af200e97bd9f)
Feb 24 20:37:57 de.eq3.cbcs.server.core.transaction.TransactionManagementVerticl e INFO [vert.x-eventloop-thread-1] SYSTEM: TransactionManagementVerticle Vertic le or Worker started
Feb 24 20:37:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-0] SYSTEM: start of TransactionManagementVerticle succeeded (057ebeda-6 7ae-4309-ad3d-2f0c1343c378)
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitial ization INFO [vert.x-eventloop-thread-3] SYSTEM: LocalServerAdapterInitializati on Verticle or Worker started
Feb 24 20:37:57 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-2] SYSTEM: start of LocalServerAdapterInitialization succeeded (50bbe72 e-5c18-4f7f-9da7-c8107d5567f3)
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] TRX adapter state 1: HMIP_TRX_App
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] TRX adapter application is already running or started
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] No NWK, try to set address ...
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Try to set radio address 11660016.. .
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Set max send attempts for 3014F711A 000041D89971651 to 3
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Try to get application version...
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Application version 4.4.16
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Bootloader version 1.0.24
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] hmos version 1.64.0
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] MCU type: EFM32G200F64_CM3
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Duty Cycle: 0.0
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] set DutyCycle limit to ffffffc8
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Set Duty Cycle Limit
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Current Security Counter: 6283008
Feb 24 20:37:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Update security counter to calculat ion: 6348475
Feb 24 20:37:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] TRX adapter has no linkpartner
Feb 24 20:37:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseLis tener INFO [RXTXPortMonitor(/dev/mmd_hmip)] Adapter with Access Point id 3014F7 11A000041D89971651 initialized
Feb 24 20:37:58 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitial ization INFO [RXTXPortMonitor(/dev/mmd_hmip)] HMIPTRXInitialResponseListener sa id that Adapter was initialized
Feb 24 20:37:58 de.eq3.cbcs.server.core.vertx.BackendCommandHandler INFO [vert. x-eventloop-thread-4] SYSTEM: BackendCommandHandler Verticle or Worker started
Feb 24 20:37:58 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-3] SYSTEM: start of BackendCommandHandler succeeded (0a0bc6c0-a059-4aaf -a0fc-fad949cb0f12)
Feb 24 20:37:58 de.eq3.cbcs.server.local.base.internal.LocalServerFirmwareUpdate Initialization INFO [vert.x-eventloop-thread-2] SYSTEM: LocalServerFirmwareUpda teInitialization Verticle or Worker started
Feb 24 20:37:58 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-1] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded ( 7dcd56e5-d059-4c81-bc21-08f36c78507b)
Feb 24 20:37:58 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN [vert.x-worker-thread-4] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware
Feb 24 20:37:58 de.eq3.cbcs.lib.backbone.lanrouting.RouteManagementWorker INFO [vert.x-worker-thread-2] SYSTEM: RouteManagementWorker Verticle or Worker starte d
Feb 24 20:37:58 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates
Feb 24 20:37:58 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-7] SYSTEM: start of RouteManagementWorker succeeded (16777dbc-afd6-4da7 -9451-f32608e3c631)
Feb 24 20:37:58 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyNotificationHandler INFO [vert.x-worker-thread-1] SYSTEM: LegacyNotificationHandler Verticle or Wo rker started
Feb 24 20:37:58 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-5] SYSTEM: start of LegacyNotificationHandler succeeded (778dddf5-728f- 41aa-8536-3caaf5959edd)
Feb 24 20:37:58 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-work er-thread-3] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0. 0 -> 192.168.1.98
Feb 24 20:37:59 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotification Handler INFO [vert.x-worker-thread-4] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started
Feb 24 20:37:59 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotification Handler INFO [vert.x-worker-thread-4] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started
Feb 24 20:37:59 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotification Handler INFO [vert.x-worker-thread-4] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started
Feb 24 20:37:59 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-7] SYSTEM: start of LegacyBackendNotificationHandler succeeded (5381e5c 5-206b-45d3-86ab-512bca9a489d)
Feb 24 20:37:59 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker INFO [ve rt.x-worker-thread-0] SYSTEM: LegacyAPIWorker Verticle or Worker started
Feb 24 20:37:59 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-5] SYSTEM: start of LegacyAPIWorker succeeded (3dab3ff0-ceb9-43d8-8593- 1afd178399f9)
Feb 24 20:37:59 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker INFO [vert.x -worker-thread-3] SYSTEM: BackboneWorker Verticle or Worker started
Feb 24 20:37:59 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-3] SYSTEM: start of BackboneWorker succeeded (5e5d9d39-3faa-4f09-a155-1 175ecb23dc7)
Feb 24 20:37:59 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-work er-thread-2] UDP Routing established on network interface eth0 : 0.0.0.0 (192.16 8.1.98)
Feb 24 20:37:59 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO [vert.x-work er-thread-1] UDP Routing multi cast 'DEFAULT_MULTICAST_ADDRESS' established on n etwork interface eth0 : 192.168.1.98
Feb 24 20:38:00 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyInitializion INFO [vert.x-eventloop-thread-4] SYSTEM: LegacyInitializion Verticle or Worker starte d
Feb 24 20:38:00 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-3] SYSTEM: start of LegacyInitializion succeeded (61cbd951-e2b6-477e-a9 51-f8567eab070f)
Feb 24 20:38:00 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTE M: initial deployment complete _________________________________________________ ____
Feb 24 20:38:01 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bi nd XML-RPC api to port 32010
Feb 24 20:38:01 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxEvent LoopExecuteTime: 2000000000
Feb 24 20:38:01 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default BlockedT hreadCheckInterval: 1000
Feb 24 20:38:01 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxWorke rExecuteTime: 60000000000
Feb 24 20:38:01 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default EventLoo pPoolSize: 8
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [BackendWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [GroupRequestWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [DiagramRequestWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [StorageRequestWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [EnergyPriceRequestWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [CouplingRequestWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [RegaClientWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [AccessPointUpdateServerWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: added for deployment [AccessPointUpdateLoaderWorker] (1) *worker
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: deploying 12 classes to Vert.x
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-4] SYSTEM: start of BackendWorker succeeded (f3ea0ffd-049f-466c-a55b-ae 19ce1c2648)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: 12 VertxDeployers initialized
Feb 24 20:38:01 de.eq3.ccu.hmip.accesspoint.update.AccessPointUpdateLoaderWorker INFO [vert.x-worker-thread-7] SYSTEM: Firmware update directory is set to /etc /config/firmware
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-1] SYSTEM: start of AccessPointUpdateLoaderWorker succeeded (2d3240dc-2 add-4bf4-af10-84dcae7e23de)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (6ca47be9-2e62-4 eb6-b511-4e49aed024d4)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-1] SYSTEM: start of CouplingRequestWorker succeeded (dcdbb828-382a-4e76 -a675-15393e6ab2dc)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-1] SYSTEM: start of StorageRequestWorker succeeded (cf2a965b-0a16-4bac- baa8-69c2c88d9161)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded ( 55641f38-f842-4df6-8049-11f7bb376fc1)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-0] SYSTEM: start of RegaClientWorker succeeded (e42e66c7-20ee-4f4e-8447 -b1032616d034)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-4] SYSTEM: start of AccessPointUpdateServerWorker succeeded (a5503ca3-e 4dc-483e-95a8-099a54565454)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-5] SYSTEM: start of GroupRequestWorker succeeded (81ad5ffe-c1cc-425a-af e7-65afe0902dd4)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (ea3c3a37-cea 6-4dd6-afda-b61ddb751cb4)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-3] SYSTEM: start of DiagramRequestWorker succeeded (13876dca-cc46-4274- 8665-98bb6d601654)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloo p-thread-3] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (5806f 6ee-72b0-4995-8937-30eb978c5861)
Feb 24 20:38:01 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTE M: initial deployment complete _________________________________________________ ____
Feb 24 20:38:01 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServe r at 127.0.0.1:39292
Feb 24 20:38:01 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Read Configurati on
Feb 24 20:38:01 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Bidcos Di spatcher
Feb 24 20:38:01 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] InitBidCosCache
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create groupDefi nitionProvider
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDe viceHolder
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDe viceHandlerRega
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupAdmi nistrationService
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDevi ceDispatcher
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDevi ceHandler
Feb 24 20:38:02 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread- 1] @GroupDeviceHandler - initializing...
Feb 24 20:38:02 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread- 1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatch er))
Feb 24 20:38:02 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread- 1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Feb 24 20:38:02 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread- 1] --> got groupDefinitionProvider
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCosGro upMemberProvider
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init groupAdmini strationService
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Virtual OS Device
Feb 24 20:38:02 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init ESHLight Br idge
Feb 24 20:38:03 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create RrdDatalo gging
Feb 24 20:38:03 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Measureme ntService
Feb 24 20:38:03 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Measurement Service
Feb 24 20:38:03 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create HTTP Serv er
Feb 24 20:38:03 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCos co ntext and start handler
Feb 24 20:38:03 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group con text and start handler
Feb 24 20:38:03 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos
Feb 24 20:38:03 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotification Handler INFO [HmIP-RF_java_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandl er Verticle or Worker started
Feb 24 20:38:03 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-4] init finished
Feb 24 20:38:03 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-1] Added InterfaceId: HmIP-RF_java
Feb 24 20:38:03 de.eq3.ccu.hmip.accesspoint.update.AccessPointUpdateLoaderWorker WARN [vert.x-worker-thread-13] SYSTEM: Firmware update directory in config fil e is no valid directory: /etc/config/firmware
Feb 24 20:38:03 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x- worker-thread-1] updateDevicesForClient HmIP-RF_java -> 110 device addresses wil l be added
Feb 24 20:38:03 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates
Feb 24 20:38:04 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServe r done
Feb 24 20:38:12 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHand lerRega INFO [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceH andlerRega called from url: xmlrpc_bin://127.0.0.1:31999
Feb 24 20:38:12 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHand lerRega INFO [vert.x-eventloop-thread-5] Added InterfaceId: 1008
Feb 24 20:38:12 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INF O [vert.x-worker-thread-14] Execute BackendCommand: de.eq3.ccu.virtualdevice.se rvice.internal.rega.BackendUpdateDevicesCommand
Feb 24 20:38:16 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.1.99:42010
Feb 24 20:38:16 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotification Handler INFO [raspberrypi:hm-rpc.0_WorkerPool-0] SYSTEM: LegacyBackendNotificat ionHandler Verticle or Worker started
Feb 24 20:38:16 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-1] init finished
Feb 24 20:38:16 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-4] Added InterfaceId: raspberrypi:hm-rpc.0
Feb 24 20:38:16 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.1.99:42010
Feb 24 20:38:16 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-3] Removed InterfaceId: raspberrypi:hm-rpc.0
Feb 24 20:38:16 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x- worker-thread-4] updateDevicesForClient raspberrypi:hm-rpc.0 -> 110 device addre sses will be added
Feb 24 20:38:22 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999
Feb 24 20:38:22 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotification Handler INFO [1009_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandler Verti cle or Worker started
Feb 24 20:38:22 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-3] init finished
Feb 24 20:38:22 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-3] Added InterfaceId: 1009
Feb 24 20:39:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.1.99:42010
Feb 24 20:39:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotification Handler INFO [raspberrypi:hm-rpc.0_WorkerPool-0] SYSTEM: LegacyBackendNotificat ionHandler Verticle or Worker started
Feb 24 20:39:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x -worker-thread-2] init finished
Feb 24 20:39:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-1] Added InterfaceId: raspberrypi:hm-rpc.0
Feb 24 20:39:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x- worker-thread-1] updateDevicesForClient raspberrypi:hm-rpc.0 -> 96 device addres ses will be added
Feb 24 20:42:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 20:42:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 20:42:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 20:47:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 20:47:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 20:47:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 20:52:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 20:52:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 20:52:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 20:57:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 20:57:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 20:57:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 21:02:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 21:02:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 21:02:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 21:06:36 org.apache.http.impl.client.DefaultHttpClient INFO [HmIP-RF_jav a_WorkerPool-0] I/O exception (java.net.SocketException) caught when processing request to {}->http://127.0.0.1:39292: Broken pipe (Write failed)
Feb 24 21:06:36 org.apache.http.impl.client.DefaultHttpClient INFO [HmIP-RF_jav a_WorkerPool-0] Retrying request to {}->http://127.0.0.1:39292
Feb 24 21:07:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 21:07:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 21:07:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 21:12:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 21:12:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 21:12:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 21:17:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 21:17:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 21:17:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 21:22:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 21:22:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 21:22:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 21:27:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 21:27:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 21:27:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
Feb 24 21:31:20 de.eq3.cbcs.server.core.internal.InclusionHandling INFO [vert.x -eventloop-thread-7] AP 3014F711A000041D89971651: Device included 3014F711A00003 DA498C378B
Feb 24 21:32:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue
Feb 24 21:32:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilizat ion: 0/50 used
Feb 24 21:32:56 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INF O [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 u sed
EDIT:
Zur Info was ich noch getestet hatte:
Einmal HAP raus, dann einen Thermostat reseten, löschen und neu anlernen bzw. einen anderen lt. deiner vorgangsweise (reset, neu anlernen, ohne vorher löschen) - hat nix geholfen
versucht HAP anzulernen um zu sehen ob überhaupt der stick noch funkt > ist sofort ohne probleme gegangen.
-
deimos
- Beiträge: 5396
- Registriert: 20.06.2017, 10:38
- System: Alternative CCU (auf Basis OCCU)
- Wohnort: Leimersheim
- Hat sich bedankt: 121 Mal
- Danksagung erhalten: 957 Mal
- Kontaktdaten:
Re: piVCCU3 Unterstützung für BidCos/HmIP Dualbetrieb mit HmIP-RFUSB
Hi,
Das Log sieht absolut unauffällig aus, da der eigentliche HMIPServer Closed Source ist, ist das ganze aber leider eine Blackbox für mich, so dass ich da nicht wirklich weiter Ideen habe, woran das liegen könnte.
Viele Grüße
Alex
Das Log sieht absolut unauffällig aus, da der eigentliche HMIPServer Closed Source ist, ist das ganze aber leider eine Blackbox für mich, so dass ich da nicht wirklich weiter Ideen habe, woran das liegen könnte.
Das ist kein valider Funk-Test. Die Kommunikation zwischen CCU und HAP erfolgt nicht per Funk, sondern per Netzwerk.
Viele Grüße
Alex