Umzug RaspiMatic -> piVCCU3 - HmIP geht nicht

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

Antworten
Troubadix
Beiträge: 37
Registriert: 19.08.2017, 13:43

Umzug RaspiMatic -> piVCCU3 - HmIP geht nicht

Beitrag von Troubadix » 11.09.2019, 18:36

Hallo,

ich habe heute von RaspberryMatic mit RPi3B+ auf piVCCU3 mit RPi4B umgestellt.
piVCCU3 habe ich manuell installiert auf Raspbian Buster, also nicht das vorkonfigurierte SD-Image verwendet.

Bin begeistert wie problemlos das funktioniert hat. Dickes Lob an Alex und die anderen Entwickler!
Bis auf nachfolgendes kleines Problem:

Das unter RaspiMatic erstellte Backup konnte ich auch problemlos in piVCCU3 einspielen.
Leider sind meine HmIP-Heizungs- und Wandthermostate ohne Funktion. Meine HmIP-Außen-Temperatursensoren HmIP-STHO funktionieren jedoch problemlos (sonst keine HmIP-Geräte im Einsatz).
Ich bekomme keinen Fehler angezeigt, jedoch wird mir als Temperatur 0°C angezeigt (es müssten ca. 20 Grad sein). Auch wenn ich einen Button in der WebUI klicke um z.B. den Boost-Modus des Thermostats zu aktivieren erfolgt am Gerät keine Reaktion. Es kommt aber auch keinerlei Fehlermeldung.

Was kann das sein und wie kann ich es beheben? :)

Danke!

EDIT: Jetzt ist in den Servicemeldungen doch ein Fehler aufgetaucht: "Gerätekommunikation gestört"
Dateianhänge
Bildschirmfoto 2019-09-11 um 18.32.02.png
Bildschirmfoto 2019-09-11 um 18.31.14.png

Troubadix
Beiträge: 37
Registriert: 19.08.2017, 13:43

Re: Umzug RaspiMatic -> piVCCU3 - HmIP geht nicht

Beitrag von Troubadix » 12.09.2019, 17:48

Ich habe jetzt testweise eines der HmIP-WTH-2 aus der VCCU gelöscht und auf Werkseinstellungen zurück gesetzt.
Das Anlernen des Geräts funktioniert aber nicht. Die Geräte finden sich nicht.

Was ist denn da los? :shock:

deimos
Beiträge: 2959
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Hat sich bedankt: 5 Mal
Danksagung erhalten: 33 Mal
Kontaktdaten:

Re: Umzug RaspiMatic -> piVCCU3 - HmIP geht nicht

Beitrag von deimos » 12.09.2019, 18:48

Hi,

bitte mal neu starten, 5-10 Minuten warten und dann die Ausgabe folgender Befehle posten:

Code: Alles auswählen

sudo pivccu-info
sudo pivccu-attach cat /var/hm_mode
sudo pivccu-attach cat /var/log/messages
sudo pivccu-attach cat /var/log/hmserver.log
Hattest du mal YAHM installiert?
Welches Funkmodul hast und hattest du das bereits vorher im Einsatz?

Viele Grüße
Alex

Troubadix
Beiträge: 37
Registriert: 19.08.2017, 13:43

Re: Umzug RaspiMatic -> piVCCU3 - HmIP geht nicht

Beitrag von Troubadix » 12.09.2019, 19:53

Hi,

habe bereits mehrmals neu gestartet mit (unbeabsichtigten) Wartezeiten danach.

Die gewünschten Ausgaben:

Code: Alles auswählen

[email protected]:~# pivccu-info
piVCCU version: 3.47.15-30
Kernel modules: Available
Raw UART dev:   Available
HMRF Hardware:  RPI-RF-MOD
HMIP Hardware:  RPI-RF-MOD
Board serial:   58A992F4DC
Radio MAC:      unknown
SGTIN:          3014F711A0001F58A992F4DC
State:          RUNNING
PID:            799
IP:             192.168.178.59
CPU use:        721.53 seconds
BlkIO use:      55.32 MiB
Memory use:     174.32 MiB
KMem use:       5.91 MiB
Link:           vethpivccu
 TX bytes:      8.04 MiB
 RX bytes:      36.52 MiB
 Total bytes:   44.56 MiB
[email protected]:~# 

Code: Alles auswählen

[email protected]:~# pivccu-attach cat /var/hm_mode
HM_HMIP_ADDRESS=''
HM_HMIP_DEV='RPI-RF-MOD'
HM_HMIP_DEVNODE='/dev/raw-uart'
HM_HMIP_SERIAL='58A992F4DC'
HM_HMIP_SGTIN='3014F711A0001F58A992F4DC'
HM_HMIP_VERSION='4.0.20'
HM_HMRF_ADDRESS=''
HM_HMRF_DEV='RPI-RF-MOD'
HM_HMRF_DEVNODE='/dev/raw-uart'
HM_HMRF_SERIAL='58A992F4DC'
HM_HMRF_VERSION='4.0.20'
HM_HOST='rpi3'
HM_HOST_GPIO_RESET=''
HM_HOST_GPIO_UART='/dev/raw-uart'
HM_LED_GREEN=''
HM_LED_RED=''
HM_LED_YELLOW=''
HM_MODE='NORMAL'
HM_RTC=''
[email protected]:~# 
An dieser Stelle habe ich die MAschine neu gestartet...

Code: Alles auswählen

[email protected]:~# pivccu-attach cat /var/log/messages
Sep 12 19:49:43 piVCCU syslog.info syslogd started: BusyBox v1.29.2
Sep 12 19:49:43 piVCCU user.notice kernel: klogd started: BusyBox v1.29.2 (2019-07-17 08:18:26 CEST)
Sep 12 19:49:44 piVCCU syslog.info syslogd exiting
Sep 12 19:49:44 homematic syslog.info syslogd started: BusyBox v1.29.2
Sep 12 19:49:44 homematic user.notice kernel: klogd started: BusyBox v1.29.2 (2019-07-17 08:18:26 CEST)
Sep 12 19:49:45 homematic daemon.err udhcpc[178]: started, v1.29.2
Sep 12 19:49:45 homematic daemon.err udhcpc[178]: sending discover
Sep 12 19:49:45 homematic daemon.err udhcpc[178]: sending select for 192.168.178.59
Sep 12 19:49:45 homematic daemon.err udhcpc[178]: lease of 192.168.178.59 obtained, lease time 86400
Sep 12 19:49:46 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:46 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:46 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:46 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:46 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:46 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:47 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:47 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:48 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:48 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:48 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:48 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:48 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:48 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:49 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:49 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:49 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:49 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:49 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:49 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:49 homematic user.info firewall: iptables v1.6.2: host/network `fc00::' not found Try `iptables -h' or 'iptables --help' for more information.
Sep 12 19:49:49 homematic user.info firewall: configuration set
Sep 12 19:49:49 homematic daemon.info ifplugd(eth0)[336]: ifplugd 0.28 initializing.
Sep 12 19:49:49 homematic daemon.info ifplugd(eth0)[336]: Using interface eth0/6A:8A:02:98:C1:79 with driver <veth> (version: 1.0)
Sep 12 19:49:49 homematic daemon.info ifplugd(eth0)[336]: Using detection mode: SIOCETHTOOL
Sep 12 19:49:49 homematic daemon.info ifplugd(eth0)[336]: Initialization complete, link beat detected.
Sep 12 19:49:49 homematic daemon.warn ifplugd(eth0)[336]: Could not open /dev/tty, cannot beep.
Sep 12 19:49:49 homematic daemon.info ifplugd(eth0)[336]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Sep 12 19:49:49 homematic daemon.warn ifplugd(eth0)[336]: client: ifup: interface eth0 already configured
Sep 12 19:49:49 homematic daemon.info ifplugd(eth0)[336]: Program executed successfully.
Sep 12 19:50:02 homematic daemon.notice ntpdate[344]: step time server 131.188.3.222 offset 0.000327 sec
Sep 12 19:50:02 homematic daemon.notice ntpd[345]: ntpd [email protected] Wed Jul 17 06:16:52 UTC 2019 (1): Starting
Sep 12 19:50:02 homematic daemon.info ntpd[345]: Command line: /usr/sbin/ntpd -g 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org
Sep 12 19:50:02 homematic daemon.info ntpd[347]: proto: precision = 1.519 usec (-19)
Sep 12 19:50:02 homematic daemon.info ntpd[347]: Listen and drop on 0 v6wildcard [::]:123
Sep 12 19:50:02 homematic daemon.info ntpd[347]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Sep 12 19:50:02 homematic daemon.info ntpd[347]: Listen normally on 2 lo 127.0.0.1:123
Sep 12 19:50:02 homematic daemon.info ntpd[347]: Listen normally on 3 eth0 192.168.178.59:123
Sep 12 19:50:02 homematic daemon.info ntpd[347]: Listen normally on 4 lo [::1]:123
Sep 12 19:50:02 homematic daemon.info ntpd[347]: Listening on routing socket on fd #21 for interface updates
Sep 12 19:50:02 homematic daemon.info ntpd[347]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Sep 12 19:50:02 homematic daemon.info ntpd[347]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Sep 12 19:50:02 homematic daemon.err xinetd[365]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Sep 12 19:50:02 homematic daemon.crit xinetd[365]: 365 {init_services} no services. Exiting...
Sep 12 19:50:02 homematic auth.info sshd[390]: Server listening on 0.0.0.0 port 22.
Sep 12 19:50:02 homematic auth.info sshd[390]: Server listening on :: port 22.
Sep 12 19:50:02 homematic daemon.info cuxd[412]: write_pid /var/run/cuxd.pid [412]
Sep 12 19:50:02 homematic daemon.info cuxd[412]: CUx-Daemon(2.3.3) on CCU(3.47.15) start PID:412
Sep 12 19:50:02 homematic user.info homematic: started cux-daemon
Sep 12 19:50:02 homematic daemon.info cuxd[412]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:2087 update(-73s):Thu Sep 12 19:48:49 2019
Sep 12 19:50:02 homematic daemon.info cuxd[412]: 4 device-paramset(s) loaded ok!
Sep 12 19:50:02 homematic daemon.info cuxd[412]: write_proxy /var/cache/cuxd_proxy.ini (412 /usr/local/addons/cuxd/ 2.3.3 3.47.15 0)
Sep 12 19:50:02 homematic daemon.info cuxd[412]: add interface 'CUxD'
Sep 12 19:50:02 homematic daemon.info cuxd[412]: write interface(1) 'BidCos-RF' to /usr/local/etc/config/InterfacesList.xml
Sep 12 19:50:02 homematic daemon.info cuxd[412]: write interface(2) 'VirtualDevices' to /usr/local/etc/config/InterfacesList.xml
Sep 12 19:50:02 homematic daemon.info cuxd[412]: write interface(3) 'HmIP-RF' to /usr/local/etc/config/InterfacesList.xml
Sep 12 19:50:02 homematic daemon.info cuxd[412]: write interface(4) 'CUxD' to /usr/local/etc/config/InterfacesList.xml
Sep 12 19:50:02 homematic daemon.err cuxd[412]: USB(1-1.4) mknod '/dev/ttyACM1' error!
Sep 12 19:50:02 homematic daemon.info cuxd[412]: USB(1-1.3/ttyACM0) CUL433 connect(9600:8N1)
Sep 12 19:50:02 homematic user.info root: Updating RF Lan Gateway Coprocessor Firmware
Sep 12 19:50:02 homematic user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Sep 12 19:50:02 homematic user.info root: Updating RF Lan Gateway Firmware
Sep 12 19:50:02 homematic user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Sep 12 19:50:02 homematic daemon.info cuxd[412]: USB(1-1.3/ttyACM0) write-retry(1) Resource temporarily unavailable
Sep 12 19:50:02 homematic user.info kernel: [   51.224260] eq3loop: created slave mmd_hmip
Sep 12 19:50:02 homematic user.info kernel: [   51.224700] eq3loop: created slave mmd_bidcos
Sep 12 19:50:17 homematic daemon.err cuxd[412]: USB(1-1.4) mknod '/dev/ttyACM1' error!
Sep 12 19:50:18 homematic daemon.warn cuxd[412]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request
Sep 12 19:50:19 homematic daemon.warn cuxd[412]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request
[email protected]:~# 

Code: Alles auswählen

[email protected]:~# pivccu-attach cat /var/log/hmserver.log
Sep 12 19:50:07 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Sep 12 19:50:07 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
Sep 12 19:50:07 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 32 classes to Vert.x 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (64798bd2-bdb1-4631-9852-deeff46ba0e5) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of AccessPointElectroCardioGram succeeded (b479bed2-a97b-4cbd-8215-5e869c2ef84d) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (917096ca-453a-4f43-b7f6-c3fbaeecdfed) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CheckDeviceExistHandler succeeded (7f928073-f971-4eed-9b56-dfb4b465b5f0) 
Sep 12 19:50:10 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of KeyServerWorker succeeded (b0b78325-2e10-4882-992e-d7863a7f6513) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of TransactionSubsystemHandler succeeded (ab421fb3-51b3-4374-9cc4-262901830f8a) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (d03e7cd1-c7b0-43cb-9619-4202c05c601f) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 32 VertxDeployers initialized 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of AccessPointKeyServerWorker succeeded (11db8122-8ad0-4fb6-9b94-39ffceba3ac5) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (31d6c575-7212-4aff-aa67-d5dbe250dd7f) 
Sep 12 19:50:10 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 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of RouterKeyServerWorker succeeded (2723bf4e-a457-4dd0-b6c3-93956e897865) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KryoPersistenceWorker succeeded (1024c867-d746-4ca2-b489-4c6273dd98ef) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (9897a605-440a-4c56-8726-afccbd627bf7) 
Sep 12 19:50:10 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-6] SYSTEM: DeviceLiveUpdateSubsystem started 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (7bb2738a-e3bd-4ef5-be68-7f342aff8779) 
Sep 12 19:50:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (f3577965-b929-40f8-8080-29a734d8b457) 
Sep 12 19:50:11 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-4] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of FirmwareLoaderFileSystem succeeded (0471d237-51fc-4f09-999a-6305c6e286b4) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of IncomingHMIPFrameHandler succeeded (4f2f61fa-3418-4b82-af92-9aaa88a7acb9) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (6869e65a-4a6c-44d5-a120-3cefeb208d3e) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of BackendCommandHandler succeeded (2b69a0e7-c0d5-43d3-8734-c4c842ccdaaa) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointAuthorisationHandler succeeded (e6e3eca0-782d-4437-802a-a8ebcd1f7320) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of RemoteCommAdapterInitialization succeeded (faa5dc66-131f-4a3d-8df0-e68c56b9515d) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointMessageDispatcher succeeded (aa532d45-2e16-48f5-a447-da8444c1e137) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of WebSocketManager succeeded (c5bc937b-d426-4787-bd34-90de520c8b45) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerAdapterInitialization succeeded (1e3078d4-7655-4750-9f09-a32f37d4df7a) 
Sep 12 19:50:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointWatchdog succeeded (c4c410c1-9db8-4adc-a66a-114e23a334cf) 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 11965672... 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A0001F58A992F4DC to 3 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 4.0.20 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.1 
Sep 12 19:50:11 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.40.1 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: CC1310 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 707888384 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 708169521 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A0001F58A992F4DC initialized 
Sep 12 19:50:12 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Sep 12 19:50:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (63ef251f-7a1d-4647-9bac-d2bba47065cc) 
Sep 12 19:50:13 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Checking all devices on all accesspoints for updates 
Sep 12 19:50:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of AccessPointCommDevice succeeded (0c023a2f-2331-4955-a594-6661485e36af) 
Sep 12 19:50:13 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (RF) 
Sep 12 19:50:13 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
Sep 12 19:50:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBackendNotificationHandler succeeded (e3def70a-f65a-448a-a11b-65ba1837345b) 
Sep 12 19:50:13 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-0] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 -> 192.168.178.59 
Sep 12 19:50:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyNotificationHandler succeeded (8c849776-1893-4ed3-a89d-274909567d0b) 
Sep 12 19:50:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyAPIWorker succeeded (11252c5f-6096-4f32-a46d-f69c1737bb1e) 
Sep 12 19:50:13 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LanRoutingWorker succeeded (eb5737be-fe8e-4677-9ddb-ce4bb5ca9250) 
Sep 12 19:50:13 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-1] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168.178.59) 
Sep 12 19:50:13 de.eq3.cbcs.lib.hmiptrxcommadapter.internal.RoutingSubsystem WARN  [Thread-6] Received routing key 9E7E63DF7966709FAD8E37095069A19D 
Sep 12 19:50:13 de.eq3.cbcs.lib.lanrouting.UdpServer INFO  [vert.x-worker-thread-3] UDP Routing multi cast established on network interface eth0 : 192.168.178.59 
Sep 12 19:50:14 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of RemoteCommAdapterFinalization succeeded (f5e68c2c-d846-4318-93e3-ec4a884dc6f4) 
Sep 12 19:50:15 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-7] SYSTEM: Started Access Point WebSocket server with port 9293 
Sep 12 19:50:15 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO  [vert.x-eventloop-thread-7] SYSTEM: connector open 
Sep 12 19:50:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (980c9fac-34a3-45d5-b406-38c95351f778) 
Sep 12 19:50:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Sep 12 19:50:15 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
Sep 12 19:50:17 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
Sep 12 19:50:17 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
Sep 12 19:50:17 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
Sep 12 19:50:17 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (923f3088-51fb-4348-a591-1a03c86b96ac) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of EnergyPriceRequestWorker succeeded (e65a8da8-0516-4253-b53a-349c7b2a1f5e) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (213109e4-3cef-4e8f-bc3b-47ce4e2b4174) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CouplingRequestWorker succeeded (a9bab08a-d9f9-435d-a4f9-aeaed835f110) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of StorageRequestWorker succeeded (9942396d-49a3-414f-accc-9c67780a0ac5) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of RegaClientWorker succeeded (aca0b85f-5c3f-4432-9592-af10cfe74b83) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupRequestWorker succeeded (a93e2b05-7501-461c-952c-c73f6e29efb5) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DiagramRequestWorker succeeded (8cae28c4-6310-44e1-ad49-ae76eb6c8211) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (a1fa79c1-65d8-4e9f-8d0a-ebf8502b64bd) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (c78142d8-7cbe-48e2-85da-03b8d12a9165) 
Sep 12 19:50:17 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
Sep 12 19:50:17 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
Sep 12 19:50:17 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
Sep 12 19:50:17 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
Sep 12 19:50:17 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler 
Sep 12 19:50:18 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing... 
Sep 12 19:50:18 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Sep 12 19:50:18 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Sep 12 19:50:18 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device 
Sep 12 19:50:18 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge 
Sep 12 19:50:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging 
Sep 12 19:50:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService 
Sep 12 19:50:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService 
Sep 12 19:50:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server 
Sep 12 19:50:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler 
Sep 12 19:50:19 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler 
Sep 12 19:50:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos 
Sep 12 19:50:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished 
Sep 12 19:50:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-1] Added InterfaceId: HmIP-RF_java 
Sep 12 19:50:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-1] updateDevicesForClient HmIP-RF_java -> 152 device addresses will be added 
Sep 12 19:50:20 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done 
Sep 12 19:50:29 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-4] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999 
Sep 12 19:50:29 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-4] Added InterfaceId: 1010 
Sep 12 19:50:29 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-13] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Sep 12 19:50:39 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999 
Sep 12 19:50:39 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Sep 12 19:50:39 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: 1011 
[email protected]:~# 

YAHM war nie installiert (was ist das? sagt mir nichts). Funkmodul ist das RPI-RF-MOD, das ich bisher an der Raspimatic mit 3B+ im Einsatz hatte. Somit eigentlich nur den Pi3 gegen Pi4 getauscht, Rest der Hardware ist gleich.

Antworten

Zurück zu „piVCCU“