Problem bei der Umstellung von CCU2 auf pivccu

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

Pitter4
Beiträge: 67
Registriert: 08.10.2016, 20:13
Danksagung erhalten: 1 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von Pitter4 » 15.11.2018, 15:30

Code: Alles auswählen

pi@All-In-One_RasPi:~ $ sudo pivccu-attach cat /var/log/messages
Nov 15 15:27:11 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Nov 15 15:27:11 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2018-07-03 14:19:59 CEST)
Nov 15 14:27:16 homematic-ccu2 daemon.info ifplugd(eth0)[131]: ifplugd 0.28 initializing.
Nov 15 14:27:16 homematic-ccu2 daemon.info ifplugd(eth0)[131]: Using interface eth0/FA:D4:17:DF:D1:69 with driver <veth> (version: 1.0)
Nov 15 14:27:16 homematic-ccu2 daemon.info ifplugd(eth0)[131]: Using detection mode: SIOCETHTOOL
Nov 15 14:27:16 homematic-ccu2 daemon.info ifplugd(eth0)[131]: Initialization complete, link beat detected.
Nov 15 14:27:16 homematic-ccu2 daemon.warn ifplugd(eth0)[131]: Could not open /dev/tty, cannot beep.
Nov 15 14:27:16 homematic-ccu2 daemon.info ifplugd(eth0)[131]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Nov 15 14:27:16 homematic-ccu2 daemon.warn ifplugd(eth0)[131]: client: net.ipv4.tcp_timestamps = 0
Nov 15 14:27:16 homematic-ccu2 daemon.warn ifplugd(eth0)[131]: client: eth0 carrier detected
Nov 15 15:27:18 homematic-ccu2 user.debug setclock: Try to get time from 87.230.102.12
Nov 15 15:27:19 homematic-ccu2 user.debug setclock: Try to get time from 192.168.178.1
Nov 15 15:27:19 homematic-ccu2 user.debug setclock: Thu Nov 15 15:27:19 CET 2018
Nov 15 14:27:21 homematic-ccu2 daemon.info ifplugd(eth0)[131]: Program executed successfully.
Nov 15 14:27:26 homematic-ccu2 auth.info sshd[211]: Server listening on 0.0.0.0 port 22.
Nov 15 14:27:26 homematic-ccu2 auth.info sshd[211]: Server listening on :: port 22.
Nov 15 15:27:26 homematic-ccu2 daemon.info cuxd[223]: write_pid /var/run/cuxd.pid [223]
Nov 15 15:27:26 homematic-ccu2 user.info homematic: started cux-daemon
Nov 15 15:27:26 homematic-ccu2 daemon.info cuxd[223]: CUx-Daemon(1.12) on CCU(2.35.16) start PID:223
Nov 15 14:27:26 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Nov 15 14:27:26 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Nov 15 15:27:26 homematic-ccu2 daemon.info cuxd[223]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:2914 update(-430s):Thu Nov 15 15:20:16 2018
Nov 15 14:27:26 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Nov 15 14:27:26 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Nov 15 14:27:26 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Nov 15 14:27:26 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Nov 15 15:27:26 homematic-ccu2 daemon.info cuxd[223]: 5 device-paramset(s) loaded ok!
Nov 15 15:27:26 homematic-ccu2 daemon.info cuxd[223]: write_proxy /var/cache/cuxd_proxy.ini (223 /usr/local/addons/cuxd/ 1.12 2.35.16 0)
Nov 15 15:27:26 homematic-ccu2 daemon.info cuxd[223]: add interface 'CUxD'
Nov 15 14:27:26 homematic-ccu2 user.info logger: Checking if firmware Update is needed for HM-MOD-RPI-PCB
Nov 15 15:27:27 homematic-ccu2 daemon.info cuxd[223]: write 4 interfaces to /usr/local/etc/config/InterfacesList.xml
Nov 15 14:27:30 homematic-ccu2 user.info update-coprocessor: Version: 2.8.6
Nov 15 14:27:30 homematic-ccu2 user.info update-coprocessor: No update necessary
Nov 15 15:27:59 homematic-ccu2 user.info kernel: [   72.601614] eq3loop: eq3loop_open_slave() ttyS0
Nov 15 15:27:59 homematic-ccu2 user.notice kernel: [   72.603845] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
Nov 15 15:27:59 homematic-ccu2 user.notice kernel: [   72.603857] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
pi@All-In-One_RasPi:~ $

Pitter4
Beiträge: 67
Registriert: 08.10.2016, 20:13
Danksagung erhalten: 1 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von Pitter4 » 15.11.2018, 15:32

Code: Alles auswählen

pi@All-In-One_RasPi:~ $ sudo pivccu-attach cat /var/log/hmserver.log
Nov 15 15:27:52 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Nov 15 15:27:52 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 20 classes to Vert.x
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 20 VertxDeployers initialized
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (ffe2f154-da8c-470b-9f29-f0298200ce2b)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CheckDeviceExistHandler succeeded (925eb4c6-9ad7-4a03-810c-27d8d6a63a0b)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (9f18e533-ecac-4311-92e7-6efc19305a14)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of HMIPTRXWriterWorker succeeded (cbadfb3b-a4df-42ab-ad39-f50d3ede2e4b)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of TransactionSubsystemHandler succeeded (55610734-511d-4318-9945-c95053749910)
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (88e48371-f60f-4e87-9fe3-8c6fe1351f15)
Nov 15 15:27:57 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Nov 15 15:27:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KeyServerWorker succeeded (100ffec8-6f86-4ad9-8ce5-a1b1f7294916)
Nov 15 15:27:58 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of KryoPersistenceWorker succeeded (8e687667-6bbf-4790-b365-70cc25d4a7c3)
Nov 15 15:27:58 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerPersistentDataLoader succeeded (93304027-4dc4-43ea-bbb8-c30357075bda)
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (b66469bf-ab52-4ae5-be17-b578f53a397d)
Nov 15 15:27:59 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of FirmwareLoaderFileSystem succeeded (4e8e9a07-1ae0-45e6-a2d3-26133510cfd3)
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (657e4ec6-81d6-4d79-b38c-3ae7df562d67)
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of IncomingHMIPFrameHandler succeeded (d41252be-6ff5-493f-a9a4-38f773b0f39a)
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of BackendCommandHandler succeeded (e56a51db-aa40-4856-9566-f9d50e6e5819)
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyBackendNotificationHandler succeeded (ab73a238-2c21-4c3d-b54e-bfd619d31e89)
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyNotificationHandler succeeded (5f3a9da5-0d61-486a-b738-616ef1a8a00e)
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyAPIWorker succeeded (dc237feb-fce8-49ef-91eb-eeac351dae96)
Nov 15 15:27:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerAdapterInitialization succeeded (69217363-bdd7-45d9-804f-f29cb2446400)
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ...
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12512326...
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D70992AA39 to 3
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version...
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3
Nov 15 15:27:59 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Exchanging adapter from 3014F711A00003522998D4CA to 3014F711A061A7D70992AA39 ...
Nov 15 15:28:04 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:04 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:11 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:28:11 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:11 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:18 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:18 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:25 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:28:25 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:25 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:32 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:32 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:39 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:28:39 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:39 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:46 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:46 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:53 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:28:53 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:28:53 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:00 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:00 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:07 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:29:07 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:07 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:14 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:14 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:21 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:29:21 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:21 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:28 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:28 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:35 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:29:35 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:35 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:42 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:42 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:49 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:29:49 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:49 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:29:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:30:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:03 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:10 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:10 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:17 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:30:17 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:17 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:24 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:24 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:30:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:31 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:30:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:45 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:52 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:52 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:59 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 18 out of 20
Nov 15 15:30:59 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:30:59 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:31:06 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Nov 15 15:31:06 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
pi@All-In-One_RasPi:~ $

Pitter4
Beiträge: 67
Registriert: 08.10.2016, 20:13
Danksagung erhalten: 1 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von Pitter4 » 15.11.2018, 15:34

Hallo Alex,
jetzt habe ich gewartet bis der PI wieder ansprechbar war ca. 6 Minuten ich hoffe das ich es jetzt richtig gemacht habe. nochmals Danke für deine Geduld und deine Unterstützung.
Grüße
Peter

Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von deimos » 15.11.2018, 15:40

Hi,

das sieht doch jetzt schonmal etwas aussagekräftiger aus.

Beim Wechsel der Schlüssel für HmIP läuft irgendwas schief, dass müssen wir jetzt rausbekommen.

Falls du bisher keine HmIP Geräte angelernt hast (und nur dann), können wir das abkürzen, indem du alle HmIP Konfiguration löscht, dann werden die frisch neu angelegt:

Code: Alles auswählen

sudo systemctl stop pivccu
rm -rf /var/lib/piVCCU/userfs/etc/config/crRFD/data/*
sudo systemctl start pivccu
Ansonsten bitte mal die Ausgabe von folgendem Befehl:

Code: Alles auswählen

sudo ls -la /var/lib/piVCCU/userfs/etc/config/crRFD/data/*
Viele Grüße
Alex

Pitter4
Beiträge: 67
Registriert: 08.10.2016, 20:13
Danksagung erhalten: 1 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von Pitter4 » 15.11.2018, 15:53

Jetzt fällt mir aber ein Stein von Herzen. Nur kann ich auch keine neuen ip Geräte anlernen weil in der Webui nur die Möglichkeit von reinen ccu2. Geräten gegeben ist es fehlen die Maken für wired Un auch homematic ip.
Aber ich werde jetzt einmal deinen Rat befolgen und die entsprechen Kommandos absetzen

Pitter4
Beiträge: 67
Registriert: 08.10.2016, 20:13
Danksagung erhalten: 1 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von Pitter4 » 15.11.2018, 15:57

Noch eine Verständnisfrage mit angelernt meinst du sicher hier auf dem System nicht früher auf der CCU2
Sorry ist wahrscheinlich eine Dumme Frage

Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von deimos » 15.11.2018, 16:01

Hi,

Nein, ich meine generell angelernete HmIP Geräte, egal ob das auf der CCU2 war und dann über das Backup übernommen wurde, oder direkt jetzt an piVCCU.

Der Button für Wired fehlt seit einigen CCU2 Versionen, sofern kein Wired Gateway eingebunden ist. Das der Button für HmIP fehlt, ist direkte Folge des Problems mit dem Fehler vom Schlüsselaustausch. Sobald der Fehler behoben ist, wird der Button mit ziemlicher Sicherheit sofort wieder auftauchen, wenn nicht, können wir das dann angehen.

Viele Grüße
Alex

Pitter4
Beiträge: 67
Registriert: 08.10.2016, 20:13
Danksagung erhalten: 1 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von Pitter4 » 15.11.2018, 16:01

So hab jetzt die folgenden Befehle abgesetzt
sudo systemctl stop pivccu
sudo rm -rf /var/lib/piVCCU/userfs/etc/config/crRFD/data/*
sudo systemctl start pivccu

Pitter4
Beiträge: 67
Registriert: 08.10.2016, 20:13
Danksagung erhalten: 1 Mal

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von Pitter4 » 15.11.2018, 16:03

Jetzt war ich zu schnell, auf der ccu2 hatte ich die IP Geräte über die mitgelieferten KEYs angelernt, ich glaube ich habe jetzt ein Problem, oder?

Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:

Re: Problem bei der Umstellung von CCU2 auf pivccu

Beitrag von deimos » 15.11.2018, 16:06

Hi,

ja, das ist jetzt ein Problem. Zwei mögliche Lösungen: Alle bisherigen HmIP Geräte aus der CCU löschen, am Gerät lokal einen Werksreset durchführen und frisch anlernen.
Oder: Letztes Backup einspielen und hoffen, dass du nicht zu viel Änderungen seit dem gemacht hast.

Viele Grüße
Alex

Antworten

Zurück zu „piVCCU“