Hey Leute, bin nicht sicher ob ich hier oder im HomeMaticForum besser aufgehoben bin, daher poste ichs auch hier nochmal und entschuldige mich falls ich falsch bin.
Ich bin vom RPi3 auf den 4 umgestiegen und kann seither in piVCCU meinen HM-MOD-RPI-PCB nicht mehr nutzen. Eigentlich sieht alles ok aus:
/dev/ttyUSB0 (FTDI_FT232R_USB_UART_AL008LZI)
pi@SmartHome:~ $ sudo pivccu-info
piVCCU version: 3.51.6-36
Kernel modules: Available
Raw UART dev: Available
Rasp.Pi UART: Assigned to GPIO pins
HMRF Hardware: HM-MOD-RPI-PCB
HMIP Hardware: HM-MOD-RPI-PCB
Board serial: OEQ061xxxx
Radio MAC: 0x5c7f50
SGTIN: 3014F711A061A7D7xxxxxx
State: RUNNING
PID: 1171
IP: 192.168.178.137
CPU use: 16.25 seconds
BlkIO use: 59.37 MiB
Memory use: 158.79 MiB
KMem use: 5.26 MiB
Link: vethpivccu
TX bytes: 32.90 KiB
RX bytes: 287.20 KiB
Total bytes: 320.10 KiB
Ein Interface vom HM-MOD-RPI-PCB sehe ich allerdings nicht:
pi@SmartHome:~ $ sudo pivccu-attach cat /etc/config/rfd.conf
# TCP Port for XmlRpc connections
Listen Port = 32001
Log Destination = Syslog
Log Identifier = rfd
Log Level = 1
Persist Keys = 1
# PID File = /var/rfd.pid
# UDS File = /var/socket_rfd
Device Description Dir = /firmware/rftypes
Device Files Dir = /etc/config/rfd
Key File = /etc/config/keys
Address File = /etc/config/ids
Firmware Dir = /firmware
Replacemap File = /firmware/rftypes/replaceMap/rfReplaceMap.xml
Fire NACK Error Events = true
Improved Coprocessor Initialization = true
[Interface 0]
Type = CCU2
ComPortFile = /dev/mmd_bidcos
#AccessFile = /dev/null
#ResetFile = /dev/ccu2-ic200
[Interface 1]
Type = Lan Interface
Name = HML
Serial Number = LEQ04xxxx
Encryption Key = xxxxxxxx
IP Address = 192.168.178.21
Im Log finde ich nichts auffälliges
pi@SmartHome:~ $ sudo pivccu-attach cat /var/log/hmserver.log
Feb 23 11:43:40 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory
Feb 23 11:43:40 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created instance of HMServerConfiguration with parameter(s)
Feb 23 11:43:40 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 parameter(s), in declarative order [String]
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 32 classes to Vert.x
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (7347497e-09c6-42ea-b9a4-de4bbf069a73)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of CheckDeviceExistHandler succeeded (6f1d1c25-4c4c-45ea-84b2-cb7a6b1f839a)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (e4991ddf-9faa-4c14-80dc-88fe6ab3d838)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of TransactionSubsystemHandler succeeded (caeda577-d393-439d-86a4-a0a5b3cfb7ab)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointElectroCardioGram succeeded (0aee28c1-d892-43fa-9013-97f062f4687f)
Feb 23 11:43:44 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of HMIPTRXWriterWorker succeeded (816e2804-c40b-4b4d-adb5-2aa2029ac7c2)
Feb 23 11:43:44 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of RouterKeyServerWorker succeeded (0a428022-6869-4c9d-b36b-3b8c3f81ca24)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 32 VertxDeployers initialized
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (69bc0900-f5dc-4006-bde6-f885f7e95c23)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of AccessPointKeyServerWorker succeeded (f806cd06-e9ab-493b-a9ee-e6f9ade739b8)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of KryoPersistenceWorker succeeded (8c0d2a29-6025-4012-af34-5faf990945fd)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (f562247c-ff20-4cb7-9953-a867664e7bd3)
Feb 23 11:43:44 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: DeviceLiveUpdateSubsystem started
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of KeyServerWorker succeeded (da56fb1f-7e59-4185-816a-ceec4bb91e68)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (d65ac205-2d56-4dad-b76c-7f91dcbb0843)
Feb 23 11:43:44 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (57340441-86af-4dbb-ac51-d700b2ae439a)
Feb 23 11:43:45 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of FirmwareLoaderFileSystem succeeded (95c58aa1-6d62-43b5-bae2-840fbd058340)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (7cd5a745-43d2-41fa-bb0c-861bb5dc7d8a)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of BackendCommandHandler succeeded (f9fc6556-57f0-498c-a313-8bf211863a87)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of IncomingHMIPFrameHandler succeeded (298d3737-374a-4cc0-8f84-0637672f0e7d)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointWatchdog succeeded (c0b81baa-fea7-455c-b8e2-0fdfeda72172)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of RemoteCommAdapterInitialization succeeded (fba4d225-b835-40c4-b0c2-74b1dce00179)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of WebSocketManager succeeded (c10ebd67-ae45-4d89-9580-f134d42b7e0e)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointCommDevice succeeded (7cf64154-f336-4785-96bd-cec6fe6327ed)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of RemoteCommAdapterFinalization succeeded (479ee313-ed8d-4ffa-9c01-0e20e170ff1e)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointAuthorisationHandler succeeded (f95640d8-ddc5-4e05-bdc2-49f69318dcbc)
Feb 23 11:43:45 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointMessageDispatcher succeeded (151dcdd4-1e52-4735-a7f0-9258c0da362b)
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRX_App
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running or started
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ...
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 12066613...
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A061A7D70992BA98 to 3
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version...
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 2.8.6
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.3
Feb 23 11:43:45 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.20.3
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] MCU type: Si1002_8051
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Duty Cycle: 0.0
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] set DutyCycle limit to ffffffc8
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set Duty Cycle Limit
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Current Security Counter: 116834304
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Update security counter to calculation: 116834956
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter has 3 link partners
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Adapter with Access Point id 3014F711A061A7D70992BA98 initialized
Feb 23 11:43:46 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Feb 23 11:43:46 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-1] SYSTEM: Started Access Point WebSocket server with port 9293
Feb 23 11:43:46 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-1] SYSTEM: connector open
Feb 23 11:43:46 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerAdapterInitialization succeeded (484747d9-748e-4cf7-b639-656cef35c424)
Feb 23 11:43:47 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (c3258ed1-f685-450b-86c7-f41aa3a0e985)
Feb 23 11:43:47 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Checking all devices on all accesspoints for updates
Feb 23 11:43:47 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updatable devices (RF)
Feb 23 11:43:47 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
Feb 23 11:43:47 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-0] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 -> 192.168.178.137
Feb 23 11:43:47 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded (1f88d345-7005-4bcf-8d00-f5a72fc842bb)
Feb 23 11:43:47 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of LegacyNotificationHandler succeeded (21ae520f-d8da-4f07-913f-90bb0b262ec8)
Feb 23 11:43:47 de.eq3.cbcs.lib.lanrouting.LanRoutingWorker INFO [vert.x-worker-thread-0] AP 3014F711A061A7D70992BA98: Could not initialize routing of access point, version is 2.8.6
Feb 23 11:43:47 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LanRoutingWorker succeeded (f7dae6de-8e61-4c8e-8a20-7644daa8157c)
Feb 23 11:43:47 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-1] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168.178.137)
Feb 23 11:43:47 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-2] UDP Routing multi cast established on network interface eth0 : 192.168.178.137
Feb 23 11:43:47 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LegacyAPIWorker succeeded (b1409d80-8c0f-47fa-93fe-f652b4ce1f67)
Feb 23 11:43:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (5b766b5a-c404-40e1-9ac8-ea19161a5464)
Feb 23 11:43:48 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Feb 23 11:43:48 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
Feb 23 11:43:50 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
Feb 23 11:43:50 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default BlockedThreadCheckInterval: 1000
Feb 23 11:43:50 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxWorkerExecuteTime: 60000000000
Feb 23 11:43:50 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default EventLoopPoolSize: 8
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: deploying 10 classes to Vert.x
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: 10 VertxDeployers initialized
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of BackendWorker succeeded (4573fa33-c2b9-4c3e-8755-a570f846d977)
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of StorageRequestWorker succeeded (9c8828e2-a657-458d-bb07-f2530db2670e)
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of RegaClientWorker succeeded (9ef0843b-6d73-43b4-9951-469c6e30b967)
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of EnergyPriceRequestWorker succeeded (de8aff1c-219e-4ea6-a4e4-3068f7a1d87a)
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (f562c7f0-c12b-461c-9771-1fd2dc57ea29)
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of CouplingRequestWorker succeeded (65c15f33-df10-4831-ac47-5e3082863606)
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DiagramRequestWorker succeeded (4280c02a-56ab-48df-a43e-62a3d31a7aa5)
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of GroupRequestWorker succeeded (42856fd3-8501-4eee-8e2f-7f41b1855985)
Feb 23 11:43:50 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (286d7efc-83d4-4aea-bb76-5a77072b6ffc)
Feb 23 11:43:51 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (75da316b-cce0-4d39-97f9-be44d78766f6)
Feb 23 11:43:51 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
Feb 23 11:43:51 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer at 127.0.0.1:39292
Feb 23 11:43:51 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Read Configuration
Feb 23 11:43:51 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Bidcos Dispatcher
Feb 23 11:43:51 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] InitBidCosCache
Feb 23 11:43:51 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create groupDefinitionProvider
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHolder
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHandlerRega
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupAdministrationService
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceDispatcher
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceHandler
Feb 23 11:43:52 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] @GroupDeviceHandler - initializing...
Feb 23 11:43:52 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Feb 23 11:43:52 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Feb 23 11:43:52 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> got groupDefinitionProvider
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCosGroupMemberProvider
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init groupAdministrationService
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Virtual OS Device
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init ESHLight Bridge
Feb 23 11:43:52 org.eclipse.smarthome.binding.hue.handler.HueBridgeHandler INFO [safeCall-2] Polling interval not configured for this hue bridge. Using default value: 10s
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create RrdDatalogging
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create MeasurementService
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init MeasurementService
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create HTTP Server
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCos context and start handler
Feb 23 11:43:52 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group context and start handler
Feb 23 11:43:52 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
Feb 23 11:43:52 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] init finished
Feb 23 11:43:52 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-4] Added InterfaceId: HmIP-RF_java
Feb 23 11:43:52 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-4] updateDevicesForClient HmIP-RF_java -> 64 device addresses will be added
Feb 23 11:43:53 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer done
Feb 23 11:44:04 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999
Feb 23 11:44:04 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] Added InterfaceId: 1008
Feb 23 11:44:04 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-13] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Feb 23 11:44:04 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] updateDevicesForClient -> 9 device addresses will be added
Feb 23 11:44:14 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
Feb 23 11:44:14 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-1] init finished
Feb 23 11:44:14 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-1] Added InterfaceId: 1009
Feb 23 11:44:14 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-Philips hue
Feb 23 11:44:14 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-Kellerlicht
Feb 23 11:44:14 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO [vert.x-worker-thread-13] set ready config of HU-On/Off plug
Hat jemand eine Idee wie ich weiter komme? Wie müsste der HM-MOD-RPI-PCB eigentlich in der CCU3 zu sehen sein? In der LAN Konfiguration seh ich nur den HMLan.
1000 Dank in jedem Fall schon einmal
ciao Carlo
Alex hat grad schon im HomeMaticForum geantwortet, daher wars da wohl richtiger :).
https://homematic-forum.de/forum/viewtopic.php?f=69&t=57010&p=565575#p565575
Der Post hier könnte daher auch gelöscht oder geschlossen werden. Alternativ poste ich gern die Lösung später (wenn ich sie mal hab).
ciao Carlo