zunächst erst einmal: Vielen Dank an Alex für deine Mühe, das ist wirklich toll, was du hier auf die Beine stellst.
Ich möchte jetzt auch von piVCCU auf Debmatic umsteigen.
Dazu habe ich mir einen NUC mit Proxmox eingerichtet auf dem auch schon ein paar virtuelle Maschinen laufen.
Soweit so gut...
Nun habe ich mir eine Debian 9.8. VM erstellt, darauf Debmatic installiert und das Backup eingespielt.
Auch das lief ohne Probleme und HM-Geräte lassen sich ohne Probleme schalten.
Leider hakt es bei den IP Geräten:
Diese werden zwar in der Geräte-Liste angezeigt, reagieren im WebUI aber überhaupt nicht.
Außerdem blinkt mein Funkmodul langsam blau / gelb im Wechsel.
Service Meldungen gibt es aktuell aber keine und auch meine debmatic Version ist akutell.
Debmatic-info gibt das hier zurück:
Code: Alles auswählen
debmatic version: 3.45.7-25
Kernel modules: Available
Raw UART dev: Available
HMRF Hardware: RPI-RF-MOD
HMIP Hardware: RPI-RF-MOD
Board serial: 58a9a71e02
Radio MAC: 0xB44882
SGTIN: 3014f711a0001f58a9a71e02
Im hmserver.log steht das hier:
Code: Alles auswählen
Jun 8 15:34:20 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory
Jun 8 15:34:20 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created instance of HMServerConfiguration with parameter(s)
Jun 8 15:34:20 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 parameter(s), in declarative order [String]
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 32 classes to Vert.x
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of TransactionSubsystemHandler succeeded (f56683f4-501b-499e-bc2d-6be403983d6e)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of CheckDeviceExistHandler succeeded (3728319c-176a-4582-97a0-d4c7e88a34cb)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of HMIPTRXWriterWorker succeeded (8247640a-89d2-4210-a88b-81a6d0add19b)
Jun 8 15:34:21 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of KeyServerWorker succeeded (67af6acd-676b-4c08-9713-99dc671bb4f5)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (a55f8504-cf8a-4900-9d21-64938cbdd4cb)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointElectroCardioGram succeeded (c38ac700-a3ad-4597-b87b-58bb0ed36751)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (05211b05-3788-4586-8a8e-7811fe03ffa7)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 32 VertxDeployers initialized
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of AccessPointKeyServerWorker succeeded (687c6997-57cb-4e0c-abb5-fb957601e151)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (8f80d3e5-ab9c-412b-ae79-0838bfa6ca70)
Jun 8 15:34:21 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
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of RouterKeyServerWorker succeeded (ca520836-1c4e-4736-8fd5-6c0e161457f9)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of KryoPersistenceWorker succeeded (35766f38-4e14-43a8-904e-190d9cbbc280)
Jun 8 15:34:21 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem started
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (bebbb078-6462-4d58-90b2-d8fddb82d165)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (8bdf8da1-70ae-4b6d-aae6-a7f2913e2579)
Jun 8 15:34:21 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (6501dc45-6d35-4b33-a09c-37df48a38504)
Jun 8 15:34:23 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-4] SYSTEM: Firmware update directory is set to /etc/config/firmware
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of FirmwareLoaderFileSystem succeeded (0065c253-e445-45a4-a7b6-e4a2bf3b4f3c)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (05f29131-0f5a-4b7e-a5db-c20efdb8c42b)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of BackendCommandHandler succeeded (fb89a4cd-7a4b-4e3d-8794-5a616a93a485)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of IncomingHMIPFrameHandler succeeded (1e6f9dad-af21-4c64-86d6-ea0cb3147cb4)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointAuthorisationHandler succeeded (145b5cab-fc08-4040-a5c4-bb951c0c263c)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of WebSocketManager succeeded (e080f873-4529-414c-8d73-d791c6f204db)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerAdapterInitialization succeeded (e30df6c0-abe9-49d0-bbbb-48b2c821342b)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointMessageDispatcher succeeded (cb98a0fa-1e02-4384-b061-5e5506f8dbf1)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointWatchdog succeeded (ffb74554-4c96-4135-8328-9b4a3f75318a)
Jun 8 15:34:23 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of RemoteCommAdapterInitialization succeeded (ffb1269c-5bff-4ab8-8c54-25bf7460970b)
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRX_App
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running or started
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ...
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 11815042...
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A0001F58A9A71E02 to 3
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version...
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 4.0.16
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.1
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.40.0
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] MCU type: CC1310
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Duty Cycle: 0.0
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] set DutyCycle limit to ffffffc8
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set Duty Cycle Limit
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Current Security Counter: 324523776
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter has no linkpartner
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Adapter with Access Point id 3014F711A0001F58A9A71E02 initialized
Jun 8 15:34:23 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Jun 8 15:34:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (8aa249f7-8142-4911-92cd-305d0b134238)
Jun 8 15:34:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointCommDevice succeeded (00057529-dbc9-43ef-a863-e6110ed48a82)
Jun 8 15:34:24 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-2] UDP Routing configuration: trying to bind port 43438 on ens18 0.0.0.0 -> 192.168.10.112
Jun 8 15:34:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded (75870b1b-4aaf-451d-b508-df842fb951c8)
Jun 8 15:34:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LegacyNotificationHandler succeeded (15a4f805-3134-4546-bf6c-3498132dc36c)
Jun 8 15:34:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of RemoteCommAdapterFinalization succeeded (3220a182-f3b0-4c09-beec-f5d058803501)
Jun 8 15:34:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyAPIWorker succeeded (5758ea40-f0db-45b2-9def-c6a2e1517277)
Jun 8 15:34:24 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LanRoutingWorker succeeded (c8f51001-59ba-411b-98c3-f2cec131f147)
Jun 8 15:34:25 de.eq3.cbcs.lib.hmiptrxcommadapter.internal.RoutingSubsystem WARN [Thread-6] Received routing key 2599EC6E7A9B1397C90A7CEA28CD4CE6
Jun 8 15:34:25 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-1] SYSTEM: Started Access Point WebSocket server with port 9293
Jun 8 15:34:25 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-1] SYSTEM: connector open
Jun 8 15:34:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Checking all devices on all accesspoints for updates
Jun 8 15:34:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updatable devices (RF)
Jun 8 15:34:25 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
Jun 8 15:34:25 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-1] UDP Routing established on network interface ens18 : 0.0.0.0 (192.168.10.112)
Jun 8 15:34:25 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-4] UDP Routing multi cast established on network interface ens18 : 192.168.10.112
Jun 8 15:34:26 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyInitializion succeeded (48ab4561-00c2-424e-87af-df5383fd3d19)
Jun 8 15:34:26 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Jun 8 15:34:26 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
Jun 8 15:34:26 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-0] IO Exception: Could not reinitialize interface: 2140. Remove interface from list.
de.eq3.cbcs.legacy.communication.rpc.RpcIOException: java.net.ConnectException: Verbindungsaufbau abgelehnt (Connection refused)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:85)
at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.sendRequest(RpcClient.java:94)
at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.invoke(RpcClient.java:82)
at com.sun.proxy.$Proxy13.listDevices(Unknown Source)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendClient.listDevices(LegacyBackendClient.java:135)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.synchronizedBackendDevices(DeviceUtil.java:144)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.loadClients(InterfaceInitializer.java:207)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:132)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:26)
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)
Caused by: java.net.ConnectException: Verbindungsaufbau abgelehnt (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:120)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:179)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:612)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:884)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:81)
... 16 more
Jun 8 15:34:26 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-0] IO Exception: Could not reinitialize interface: HmIP-RF_java. Remove interface from list.
de.eq3.cbcs.legacy.communication.rpc.RpcIOException: java.net.ConnectException: Verbindungsaufbau abgelehnt (Connection refused)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:85)
at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.sendRequest(RpcClient.java:94)
at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.invoke(RpcClient.java:82)
at com.sun.proxy.$Proxy13.listDevices(Unknown Source)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendClient.listDevices(LegacyBackendClient.java:135)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.synchronizedBackendDevices(DeviceUtil.java:144)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.loadClients(InterfaceInitializer.java:207)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:132)
at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:26)
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)
Caused by: java.net.ConnectException: Verbindungsaufbau abgelehnt (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:120)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:179)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:612)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:884)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:81)
... 16 more
Jun 8 15:34:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
Jun 8 15:34:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default BlockedThreadCheckInterval: 1000
Jun 8 15:34:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxWorkerExecuteTime: 60000000000
Jun 8 15:34:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default EventLoopPoolSize: 4
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: deploying 10 classes to Vert.x
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: 10 VertxDeployers initialized
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (b0b68fe8-e852-4481-8449-850c4b861a91)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of StorageRequestWorker succeeded (dc4a1d5e-f7b4-4910-b76f-f84500247d3e)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of BackendWorker succeeded (f5e3c621-9021-491f-82ea-012aad885e72)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of RegaClientWorker succeeded (b4bd89c7-2e11-4ee1-8274-2927760be36d)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of CouplingRequestWorker succeeded (9107c308-933a-43dd-906c-4f674eb0ffc8)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (c23a598b-6ded-4b9d-bbf1-a6bebcb5eeaf)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (0c605332-9763-401d-b280-ca9544f923dc)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of GroupRequestWorker succeeded (c7236d2e-f1a9-4907-9d70-b81a3cafdecf)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of DiagramRequestWorker succeeded (31e531e4-2743-44be-9fad-ae4757cf123f)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (1c4c79cd-07a6-49e5-b48f-aea29c6d4fc6)
Jun 8 15:34:30 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
Jun 8 15:34:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer at 127.0.0.1:39292
Jun 8 15:34:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Read Configuration
Jun 8 15:34:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Bidcos Dispatcher
Jun 8 15:34:30 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] InitBidCosCache
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create groupDefinitionProvider
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHolder
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHandlerRega
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupAdministrationService
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceDispatcher
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceHandler
Jun 8 15:34:31 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] @GroupDeviceHandler - initializing...
Jun 8 15:34:31 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Jun 8 15:34:31 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Jun 8 15:34:31 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> got groupDefinitionProvider
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCosGroupMemberProvider
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init groupAdministrationService
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Virtual OS Device
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init ESHLight Bridge
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create RrdDatalogging
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create MeasurementService
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init MeasurementService
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create HTTP Server
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCos context and start handler
Jun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group context and start handler
Jun 8 15:34:31 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [Thread-1] Add Interfaces from handler list
Jun 8 15:34:31 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [Thread-1] Added from HandleFile: InterfaceId= 1236
Jun 8 15:34:31 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-10] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUJun 8 15:34:31 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group context and start handler
Jun 8 15:34:31 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [Thread-1] Add Interfaces from handler list
Jun 8 15:34:31 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [Thread-1] Added from HandleFile: InterfaceId= 1236
Jun 8 15:34:31 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-10] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Jun 8 15:34:41 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos
Jun 8 15:34:41 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-3] init finished
Jun 8 15:34:41 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-3] Added InterfaceId: HmIP-RF_java
Jun 8 15:34:41 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-3] updateDevicesForClient HmIP-RF_java -> 114 device addresses will be added
Jun 8 15:34:42 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer done
Jun 8 15:34:49 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
Jun 8 15:34:49 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] Added InterfaceId: 1236
Jun 8 15:34:49 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-13] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Jun 8 15:35:00 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999
Jun 8 15:35:00 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] init finished
Jun 8 15:35:00 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-4] Added InterfaceId: 2140
Jun 8 15:39:21 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue
Jun 8 15:39:21 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jun 8 15:39:21 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used
Kann das mit meinem Problem zusammenhängen?
Hm-Mode zeigt das hier:
Code: Alles auswählen
HM_HOST='DEBMATIC'
HM_HOST_RAW_UART='raw-uart'
HM_HOST_GPIO_UART='/dev/raw-uart'
HM_HOST_GPIO_RESET=''
HM_LED_GREEN=''
HM_LED_RED=''
HM_LED_YELLOW=''
HM_RTC=''
HM_MODE='NORMAL'
HM_HMRF_DEVNODE='/dev/mmd_bidcos'
HM_HMIP_DEVNODE='/dev/mmd_hmip'
HM_HMRF_DEV='RPI-RF-MOD'
HM_HMIP_DEV='RPI-RF-MOD'
HM_HMRF_SERIAL='58a9a71e02'
HM_HMRF_VERSION='4.0.16'
HM_HMRF_ADDRESS='0xB44882'
HM_HMIP_SGTIN='3014f711a0001f58a9a71e02'
HM_HMIP_SERIAL='58a9a71e02'
HM_HMIP_VERSION='4.0.16'
HM_HMIP_ADDRESS='0xB44882'
Braucht ihr noch andere Logs?
Ich bin hier echt gerade ratlos und für jede Idee dankbar.
Danke und viele Grüße
Markus