DebMatic - CCU auf Debian Systemen

Begonnen von zap, 12 Februar 2019, 12:01:21

Vorheriges Thema - Nächstes Thema

deimos

Hi,

was liefert debmatic-info? Was steht in der Datei /var/hm_mode?

Die Firmware vom Funkmodul wird automatisch aktualisiert, sofern das notwendig ist.

Viele Grüße
Alex

motopi

/var/HM_mode/

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='HM-MOD-RPI-PCB'
HM_HMIP_DEV='HM-MOD-RPI-PCB'
HM_HMRF_SERIAL='PEQ0532801'
HM_HMRF_VERSION='2.8.6'
HM_HMRF_ADDRESS='0x6a5a8d'
HM_HMIP_SGTIN='3014F711A061A7D8A9918941'
HM_HMIP_SERIAL='PEQ0532801'
HM_HMIP_VERSION='2.8.6'
HM_HMIP_ADDRESS='0x6a5a8d'


$ sudo debmatic-info
debmatic version: 3.47.15-33
Kernel modules: Available
Raw UART dev:   Available
HMRF Hardware:  HM-MOD-RPI-PCB
HMIP Hardware:  HM-MOD-RPI-PCB
Board serial:   PEQ0532801
Radio MAC:      0x6a5a8d
SGTIN:          3014F711A061A7D8A9918941

amenomade

Pi 3B, Alexa, CUL868+Selbstbau 1/2λ-Dipol-Antenne, USB Optolink / Vitotronic, Debmatic und HM / HmIP Komponenten, Rademacher Duofern Jalousien, Fritz!Dect Thermostaten, Proteus

deimos

Hi

@Motopi: Das sieht eigentlich gut aus. Hast du mal einen Neustart gemacht? Es könnte sein, dass da beim ersten Start was durcheinanderging, weil du da noch eine Firmware drauf hattest, welche kein HmIP konnte.
Falls es dann noch nicht läuft, dann bitte mal den Inhalt von /var/log/hmserver.log (ab dem Neustart).

@amenomade
Es gibt eine Möglichkeit über symlinks unter /etc/systemd zusätzliche Abhängigkeiten zu erstellen, ich finde da aber leider grade die Anleitung nicht.

Viele Grüße
Alex

amenomade

Ja, grundsätzlich kann man in systemd Abhängigkeiten haben. Aber die Frage ist: abhängig von welchem debmatic Dienst/Prozess?
Pi 3B, Alexa, CUL868+Selbstbau 1/2λ-Dipol-Antenne, USB Optolink / Vitotronic, Debmatic und HM / HmIP Komponenten, Rademacher Duofern Jalousien, Fritz!Dect Thermostaten, Proteus

deimos

Hi,

debmatic.service wenn debmatic mit dem Start auf einen anderen Service warten soll.

debmatic-startupfinished.service kann verwendet werden, wenn auf den vollständigen Start von debmatic gewartet werden soll.

Viele Grüße
Alex

motopi

#186
schaut leider weiterhin identisch aus. Ich habe 'suchen nach Homematic direkt ' oder 'mit Seriennummern' -- kann es sein, dass das mit der INstallation so gekommen ist? kann ggf. Debmatic neu installieren helfen? 

kt 17 21:08:10 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:08:10 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:08:11 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware
Okt 17 21:08:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of FirmwareLoaderFileSystem succeeded (b9455c49-6cd5-474e-9049-728aad3c9a37)
Okt 17 21:08:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointWatchdog succeeded (77f5f0b9-50c7-4b9b-b001-d2012436c79b)
Okt 17 21:28:13 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Okt 17 21:28:14 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s)
Okt 17 21:28:14 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String]
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1) 
Okt 17 21:28:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1) 
Okt 17 21:28:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 32 classes to Vert.x
Okt 17 21:28:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 32 VertxDeployers initialized
Okt 17 21:28:51 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Okt 17 21:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (6c9a91fe-63b6-45bd-a6e4-dcf46d71015a)
Okt 17 21:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of HMIPTRXWriterWorker succeeded (d418746c-2d95-475f-8378-fa35fcfb9407)
Okt 17 21:28:51 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
Okt 17 21:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of TransactionSubsystemHandler succeeded (32a28bba-1356-498a-b3f3-0c2b6466b0fd)
Okt 17 21:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KeyServerWorker succeeded (99c9bd07-7c3d-4171-b743-348dbcc8dcdd)
Okt 17 21:28:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointKeyServerWorker succeeded (21eb6a6b-4bba-4164-a127-a90322bcfaab)
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of KryoPersistenceWorker still not met - check deployment configuration 
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration 
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of AccessPointMessageDispatcher still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of WebSocketManager still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:28:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterFinalization still not met - check deployment configuration  (still unfulfilled: [connector.ready])
Okt 17 21:28:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LanRoutingWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:28:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:29:01 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem started
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (777935a7-7f4d-47eb-9172-7bbed20eb7dd)
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (8e6e28b8-d516-41be-ab9e-ca608b1cbfc8)
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointElectroCardioGram succeeded (f1608429-a325-4a0a-bffd-5b96032e52ca)
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (0035abbd-81e6-4737-a127-3ac1e53eb76c)
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CheckDeviceExistHandler succeeded (6108ee47-b23a-4555-920d-08c942acf28b)
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of RouterKeyServerWorker succeeded (81fcb34a-3c12-499d-8645-402deccab8cb)
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (771632bd-43e2-4406-94e3-b3287224f4dc)
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (3d06ab20-12a9-430d-a789-8b17dcdd042b)
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerPersistentDataLoader still not met - check deployment configuration 
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointAuthorisationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointWatchdog still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointCommDevice still not met - check deployment configuration  (still unfulfilled: [backend.ready])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [legacy.api.worker][connector.open][persistent.data.loaded])
Okt 17 21:29:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerPersistentDataLoader succeeded (4c01aff3-8dea-4113-869d-abe38ddfe667)
Okt 17 21:29:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:29:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of AccessPointMessageDispatcher still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of WebSocketManager still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:29:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterFinalization still not met - check deployment configuration  (still unfulfilled: [connector.ready])
Okt 17 21:29:04 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-4] SYSTEM: Firmware update directory is set to /etc/config/firmware
Okt 17 21:32:16 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Okt 17 21:32:17 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s)
Okt 17 21:32:17 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String]
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1) 
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Okt 17 21:32:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1) 
Okt 17 21:32:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 32 classes to Vert.x
Okt 17 21:32:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 32 VertxDeployers initialized
Okt 17 21:32:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (5bf952c3-05e4-4b30-8d53-0d9760f0c4b4)
Okt 17 21:32:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointElectroCardioGram succeeded (154dc4a4-e4dd-4c6f-92d8-afada002ef80)
Okt 17 21:32:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CheckDeviceExistHandler succeeded (80e55e10-01c4-4a00-b6ef-0f2a9a515572)
Okt 17 21:32:52 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Okt 17 21:32:52 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Okt 17 21:32:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of RouterKeyServerWorker succeeded (5fe304b0-766d-4d28-be2e-97ffe46be82f)
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerPersistentDataLoader still not met - check deployment configuration 
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration 
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointMessageDispatcher still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointCommDevice still not met - check deployment configuration  (still unfulfilled: [backend.ready])
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterFinalization still not met - check deployment configuration  (still unfulfilled: [connector.ready])
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:32:57 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [legacy.api.worker][connector.open][persistent.data.loaded])
Okt 17 21:33:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (3cde5ba0-eaa1-4ef4-b920-d0640be59a45)
Okt 17 21:33:02 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: DeviceLiveUpdateSubsystem started
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (c9088796-4694-4065-9d0d-3232e1708a50)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of HMIPTRXWriterWorker succeeded (4139495e-943c-4b00-adbc-bd3b14919ddb)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (78f3007d-83cf-42bb-8609-0e2873604a12)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointKeyServerWorker succeeded (571eec7c-fe96-48a9-9a80-10a6d9f0dd12)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of TransactionSubsystemHandler succeeded (d1c45b1e-9118-460b-9231-525bcdd6dfa2)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KeyServerWorker succeeded (d3fefdb4-b21d-426d-8025-05adf38589f7)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (e7ec5b09-c466-4643-a7af-3fa7241226d5)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerPersistentDataLoader succeeded (bb84056e-4136-4568-9b52-e66ce43605f7)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (4aa49414-b012-45ea-85df-e4d05e4e116c)
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of AccessPointAuthorisationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of AccessPointWatchdog still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of WebSocketManager still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LanRoutingWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:33:02 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of WebSocketManager succeeded (e9a23bf0-db1b-482a-b8d5-4fb5c7db2179)
Okt 17 21:33:03 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-3] SYSTEM: Firmware update directory is set to /etc/config/firmware
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of FirmwareLoaderFileSystem succeeded (feae3f14-fe45-4529-bdb9-bb540848ac38)
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (8bb8f934-f81d-4b26-973d-5a7bdd7014c3)
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of IncomingHMIPFrameHandler succeeded (cd1697bf-6449-4d32-828a-6527a00c43d3)
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of RemoteCommAdapterInitialization succeeded (d55c4852-5b70-46dc-9687-f7ccc1527f4c)
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointMessageDispatcher succeeded (2f8008f3-7766-4939-ac06-975a19911bf1)
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointWatchdog succeeded (758b3f4e-e161-4c7b-88d7-98dfbc2ae9c0)
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointAuthorisationHandler succeeded (ceeb561b-92f1-4c01-836f-5efdc0b8435b)
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointCommDevice succeeded (cec77831-8346-4919-833d-13550d44a6be)
Okt 17 21:33:03 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendCommandHandler succeeded (2ab77fa2-4eef-439b-85cd-90513ac69fa3)
Okt 17 21:36:27 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory

motopi

was mir noch aufgefallen ist: wenn ich ne Weile nichts im Webgui mache, dann krieg ich ein Popup mit
Zitat"VirtualDevices
Eine Komponente der Homematic Zentrale reagiert nicht mehr.

Hierfür kann es eine Reihe von Ursachen geben:

    es besteht keine Netzwerk-Verbindung
    die Stromversorung der HomeMatic Zentrale wurde unterbrochen
    mindestens eine Komponente der HomeMatic Zentrale ist abgestürzt

Überprüfen Sie die Netzwerk-Verbindung und die Stromversorgung der HomeMatic Zentrale. Starten Sie ggf. die HomeMatic Zentrale neu."

Danach wieder Popup
ZitatHmIP-RF
Eine Komponente der Homematic Zentrale reagiert nicht mehr.

Hierfür kann es eine Reihe von Ursachen geben:

    es besteht keine Netzwerk-Verbindung
    die Stromversorung der HomeMatic Zentrale wurde unterbrochen
    mindestens eine Komponente der HomeMatic Zentrale ist abgestürzt

Überprüfen Sie die Netzwerk-Verbindung und die Stromversorgung der HomeMatic Zentrale. Starten Sie ggf. die HomeMatic Zentrale neu.

deimos

Hi,

du hast zwar viel aus dem Log gepostet, aber der interessante Teil dürfte vorher passiert sein und fehlt.

Viele Grüße
Alex

motopi

habe es mal oben aktualisiert...  ???

amenomade

Zitat von: deimos am 17 Oktober 2019, 21:33:28
debmatic-startupfinished.service kann verwendet werden, wenn auf den vollständigen Start von debmatic gewartet werden soll.

Viele Grüße
Alex
Genau das meinte ich, danke :)
Pi 3B, Alexa, CUL868+Selbstbau 1/2λ-Dipol-Antenne, USB Optolink / Vitotronic, Debmatic und HM / HmIP Komponenten, Rademacher Duofern Jalousien, Fritz!Dect Thermostaten, Proteus

schwatter

super, dann müsste /etc/systemd/system/fhem.service  so angepasst werden um auf debmatic zu warten?


# $Id: fhem.service 19235 2019-04-21 13:26:17Z betateilchen $

[Unit]
Description=FHEM Home Automation
Wants=network.target
After=network.target
#Requires=postgresql.service
#After=postgresql.service
#Requires=mysql.service
#After=mysql.service

[Service]
Type=forking
User=fhem
Group=dialout
WorkingDirectory=/opt/fhem
ExecStart=/usr/bin/perl fhem.pl fhem.cfg
#ExecStart=/usr/bin/perl fhem.pl configDB
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target
WantedBy=debmatic-startupfinished.service

amenomade

#192
Zitat von: schwatter am 17 Oktober 2019, 22:45:20
super, dann müsste /etc/systemd/system/fhem.service  so angepasst werden um auf debmatic zu warten?


# $Id: fhem.service 19235 2019-04-21 13:26:17Z betateilchen $

[Unit]
Description=FHEM Home Automation
Wants=network.target
After=network.target
#Requires=postgresql.service
#After=postgresql.service
#Requires=mysql.service
#After=mysql.service

[Service]
Type=forking
User=fhem
Group=dialout
WorkingDirectory=/opt/fhem
ExecStart=/usr/bin/perl fhem.pl fhem.cfg
#ExecStart=/usr/bin/perl fhem.pl configDB
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target
WantedBy=debmatic-startupfinished.service

Ne, nicht bei Install und nicht WantedBy. Ich muss die Doku wieder lesen, aber ich tippe eher auf Wants bei Service oder bei Unit

EDIT: sorry, nicht Wants sondern After
Pi 3B, Alexa, CUL868+Selbstbau 1/2λ-Dipol-Antenne, USB Optolink / Vitotronic, Debmatic und HM / HmIP Komponenten, Rademacher Duofern Jalousien, Fritz!Dect Thermostaten, Proteus

amenomade

Hab die Doku wieder gelesen. Wants + After sollte gehen, genauso wie bei network
Pi 3B, Alexa, CUL868+Selbstbau 1/2λ-Dipol-Antenne, USB Optolink / Vitotronic, Debmatic und HM / HmIP Komponenten, Rademacher Duofern Jalousien, Fritz!Dect Thermostaten, Proteus

Wernieman

Aber bei Unit und nicht bei install ... oder?
- Bitte um Input für Output
- When there is a Shell, there is a Way
- Wann war Dein letztes Backup?

Wie man Fragen stellt: https://tty1.net/smart-questions_de.html