Wechsel von externem LAN-Gateway auf das neue Funkmodul

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

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: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von deimos » 07.08.2018, 18:20

Hi,

Code: Alles auswählen

rfd: No BidCoS-Interface available
Das sieht schwer danach aus, dass dein rfd.conf fehlerhaft ist, daher bitte mal:

Code: Alles auswählen

cat /var/lib/piVCCU/userfs/etc/config/rfd.conf
Was hattest du vor piVCCU im Einsatz? Das dürfte nämlich schon vor deinem Wechsel auf das neue Funkmodul fehlerhaft gewesen sein, nur ist es dir da vermutlich nicht aufgefallen, weil du das LAN GW hattest. Ich würde aus dem Bauch raus ja tippen, dass du YAHM hattest und die Migrationschritte auf meiner Github Seite nicht durchgeführt hast.

Viele Grüße
Alex

schlusi
Beiträge: 25
Registriert: 17.11.2015, 12:23
Hat sich bedankt: 1 Mal

Re: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von schlusi » 08.08.2018, 07:44

Hi Alex,

deine Vermutung ist richtig, yahm habe ich davor genutzt und die Migrationsschritte hatte ich nicht auf dem Schirm.
Ich bin einfach davon ausgegangen, dass ich bei einem neuen System einfach nur das backup von der ccu einspielen muss, war wohl zu einfach gedacht :?

cat /var/lib/piVCCU/userfs/etc/config/rfd.conf

Code: Alles auswählen

# TCP Port for XmlRpc connections
Listen Port = 2001

Log Destination = Syslog
Log Identifier = rfd
Log Level = 1

Persist Keys = 1

# PID File = /var/rfd.pid
# UDS File = /var/socket_rfd

Device Description Dir = /firmware/rftypes
Device Files Dir = /etc/config/rfd
Key File = /etc/config/keys
Address File = /etc/config/ids
Firmware Dir = /firmware
Replacemap File = /firmware/rftypes/replaceMap/rfReplaceMap.xml
Fire NACK Error Events = true
Improved Coprocessor Initialization = true

#[Interface 0]
#Type = CCU2
#ComPortFile = /dev/mmd_bidcos
#AccessFile = /dev/null
#ResetFile = /dev/ccu2-ic200
Ist das einfach zu fixen?

Danke & lg
Joerg


schlusi
Beiträge: 25
Registriert: 17.11.2015, 12:23
Hat sich bedankt: 1 Mal

Re: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von schlusi » 08.08.2018, 08:41

Moin,

das hat schon mal geholfen.

Jetzt kommt in den Servicemeldungen beim Schaltaktor "Gerätekommunikation gestört".
Fernbedienung reagiert auch nicht.

Raspi zur Sicherheit einmal durchgestartet, aber keine Aenduerung.

lg
Joerg

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: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von deimos » 08.08.2018, 08:48

Hi,

dann nochmal zurück zu den Fragen, welche du teilweise noch nicht beantwortet hast:

- Wie sieht die Zuordnung der Geräte zu den Gateways aus?
- Fernbedienung zu Kaffeemaschiene: Zentralenprogramm oder Direktverknüpfung?
- Sieht man in der Weboberfläche bei der Fernbedienung, dass eine Taste gedrückt wurde (Timestamp verändert sich)?
- Idealweise bitte nochmal die Logs.

Viele Grüße
Alex

schlusi
Beiträge: 25
Registriert: 17.11.2015, 12:23
Hat sich bedankt: 1 Mal

Re: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von schlusi » 08.08.2018, 09:25

Hi,

- Zuordnung der Geraete zu den Gateways: Stehen alle auf (Standard)
- Fernbedienung zu Kaffeemaschine: Zentralenprogramm (steuert eine Systemvariable, die die Kaffeemaschine ein-/ausschaltet, soll spaeter ueber Homekit bedient werden)
- Tastendruck auf der Fernbedienung erscheint auf der Weboberflaeche mit neuem Timestamp.
- Schaltaktor fuer die Kaffeemaschine laesst sich auch nicht direkt ueber das Webui bedienen

sudo pivccu-info

Code: Alles auswählen

piVCCU version: 2.35.16-35
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi3 UART:  Assigned to GPIO pins
HMRF Hardware:  RPI-RF-MOD
HMIP Hardware:  RPI-RF-MOD
Board serial:   58a992f2f8
Radio MAC:      0xB555F4
SGTIN:          3014f711a0001f58a992f2f8
State:          RUNNING
PID:            792
IP:             192.168.2.6
CPU use:        27.70 seconds
BlkIO use:      32.91 MiB
Link:           vethpivccu
 TX bytes:      1.11 MiB
 RX bytes:      688.57 KiB
 Total bytes:   1.79 MiB
sudo pivccu-attach cat /var/log/messages

Code: Alles auswählen

Aug  8 09:08:56 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Aug  8 09:08:56 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2018-07-03 14:19:59 CEST)
Aug  8 07:08:58 homematic-ccu2 daemon.info ifplugd(eth0)[144]: ifplugd 0.28 initializing.
Aug  8 07:08:58 homematic-ccu2 daemon.info ifplugd(eth0)[144]: Using interface eth0/2A:3C:3D:B8:35:40 with driver <veth> (version: 1.0)
Aug  8 07:08:58 homematic-ccu2 daemon.info ifplugd(eth0)[144]: Using detection mode: SIOCETHTOOL
Aug  8 07:08:58 homematic-ccu2 daemon.info ifplugd(eth0)[144]: Initialization complete, link beat detected.
Aug  8 07:08:58 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: Could not open /dev/tty, cannot beep.
Aug  8 07:08:58 homematic-ccu2 daemon.info ifplugd(eth0)[144]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Aug  8 07:08:58 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: net.ipv4.tcp_timestamps = 0
Aug  8 07:08:58 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: udhcpc (v1.20.2) started
Aug  8 09:08:58 homematic-ccu2 user.debug setclock: Try to get time from 0.de.pool.ntp.org
Aug  8 09:08:58 homematic-ccu2 user.debug setclock: Wed Aug 8 09:08:58 CEST 2018
Aug  8 07:08:58 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: Sending discover...
Aug  8 07:08:58 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: Sending select for 192.168.2.6...
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: Lease of 192.168.2.6 obtained, lease time 86400
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: netconfigcmd [-i ip-address] [-g gateway] [-n netmask] [-d1 dns-server] [-d2 dns-server]
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:   Sets the networkinformation
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:   Options:
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -i: current ip address
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -g: current gateway
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -n: current (sub) netmask
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -d1: current primary dns server
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -d2: current secondary dns server
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: netconfigcmd [-i ip-address] [-g gateway] [-n netmask] [-d1 dns-server] [-d2 dns-server]
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:   Sets the networkinformation
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:   Options:
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -i: current ip address
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -g: current gateway
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -n: current (sub) netmask
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -d1: current primary dns server
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -d2: current secondary dns server
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: rm: can't remove '/var/etc/resolv.conf': No such file or directory
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: udhcpc (v1.20.2) started
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: Sending discover...
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: Sending select for 192.168.2.6...
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: Lease of 192.168.2.6 obtained, lease time 86400
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: netconfigcmd [-i ip-address] [-g gateway] [-n netmask] [-d1 dns-server] [-d2 dns-server]
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:   Sets the networkinformation
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:   Options:
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -i: current ip address
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -g: current gateway
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -n: current (sub) netmask
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -d1: current primary dns server
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -d2: current secondary dns server
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client: netconfigcmd [-i ip-address] [-g gateway] [-n netmask] [-d1 dns-server] [-d2 dns-server]
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:   Sets the networkinformation
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:   Options:
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -i: current ip address
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -g: current gateway
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -n: current (sub) netmask
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -d1: current primary dns server
Aug  8 07:08:59 homematic-ccu2 daemon.warn ifplugd(eth0)[144]: client:     -d2: current secondary dns server
Aug  8 07:08:59 homematic-ccu2 daemon.info ifplugd(eth0)[144]: Program executed successfully.
Aug  8 07:10:41 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Aug  8 07:10:41 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Aug  8 07:10:41 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Aug  8 07:10:41 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Aug  8 07:10:41 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Aug  8 07:10:41 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Aug  8 07:10:41 homematic-ccu2 user.info logger: Checking if firmware Update is needed for RPI-RF-MOD
Aug  8 07:10:42 homematic-ccu2 user.info logger: [DEBUG] Start bootloader ...
Aug  8 07:10:42 homematic-ccu2 user.info logger: [DEBUG] Bootloader running
Aug  8 07:10:42 homematic-ccu2 user.info logger: [DEBUG] Request bootloader version ...
Aug  8 07:10:42 homematic-ccu2 user.info logger: [INFO] SGTIN = 3014f711a0001f58a992f2f8
Aug  8 07:10:42 homematic-ccu2 user.info logger: [INFO] Performing update with firmware file '/firmware/RPI-RF-MOD/dualcopro_update_blhmip-3.4.2.eq3' ...
Aug  8 07:10:42 homematic-ccu2 user.info logger: [DEBUG] Start application ...
Aug  8 07:10:42 homematic-ccu2 user.info logger: [DEBUG] Application 'DualCoPro_App' running
Aug  8 07:10:42 homematic-ccu2 user.info logger: [DEBUG] Request application version ...
Aug  8 07:10:42 homematic-ccu2 user.info logger: [DEBUG] Request application version ...
Aug  8 07:10:42 homematic-ccu2 user.info logger: [WARN] The coprocessor already has the desired version 3.4.2
Aug  8 07:10:42 homematic-ccu2 user.info logger: [ERROR] No update performed.
Aug  8 07:10:42 homematic-ccu2 user.info logger: [INFO] Exiting update tool.
Aug  8 09:10:57 homematic-ccu2 user.info kernel: [   51.247826] eq3loop: eq3loop_close_slave() ttyS0
Aug  8 09:10:57 homematic-ccu2 user.notice kernel: [   51.266666] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
Aug  8 09:11:17 homematic-ccu2 user.err rfd: HSSParameter::SetValue() true Put failed
Aug  8 09:11:17 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"NEQ1502095:1","STATE",true} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Aug  8 09:11:17 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Aug  8 09:11:17 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = NEQ1502095:1 [iseDOMdpHSS.cpp:77]
Aug  8 09:11:17 homematic-ccu2 local0.err ReGaHss: Error: IseESP::ScriptRuntimeError: var x = dom.GetObject("Kaffeemaschine"); if ( x.Variable() == true )  { x.Variable(false); }  else  { x.Variable(true); } [iseESPexec.cpp:12500]
Aug  8 09:11:36 homematic-ccu2 user.debug setclock: Try to get time from 0.de.pool.ntp.org
Aug  8 09:11:36 homematic-ccu2 user.debug setclock: Wed Aug 8 09:11:36 CEST 2018
Aug  8 09:16:08 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug  8 09:16:08 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=WORKING failed getting physical value.
Aug  8 09:16:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"NEQ1502095:1","WORKING"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Aug  8 09:16:08 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Aug  8 09:16:08 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Aug  8 09:16:09 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug  8 09:16:09 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug  8 09:16:09 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"NEQ1502095:1","STATE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Aug  8 09:16:09 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Aug  8 09:16:09 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Aug  8 09:16:21 homematic-ccu2 user.err rfd: HSSParameter::SetValue() true Put failed
Aug  8 09:16:21 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"NEQ1502095:1","STATE",true} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Aug  8 09:16:21 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Aug  8 09:16:21 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = NEQ1502095:1 [iseDOMdpHSS.cpp:77]
sudo pivccu-attach cat /var/log/hmserver.log

Code: Alles auswählen

Aug 8 09:10:50 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Aug 8 09:10:50 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Aug 8 09:10:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 20 classes to Vert.x 
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 20 VertxDeployers initialized 
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (81c71490-8c46-4582-b57b-245e5cc9b033) 
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of CheckDeviceExistHandler succeeded (7a78477a-9e99-44ef-a157-9b97720d7453) 
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of HMIPTRXWriterWorker succeeded (1048d69e-423c-46e1-8c4d-943f19bfced3) 
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (e559e48d-20eb-48f4-bdd8-e6f78014e476) 
Aug 8 09:10:56 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of TransactionSubsystemHandler succeeded (30644ebf-4d5d-4f5b-a962-7cc92e5a06d1) 
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (46f6fc56-e650-45d9-abb2-4d0aa6c934a9) 
Aug 8 09:10:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of KeyServerWorker succeeded (a31d475c-ff34-49f5-9c68-8cc3801a6e34) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of KryoPersistenceWorker succeeded (36d407d1-3be1-4bb1-8630-fac3a0dbda61) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerPersistentDataLoader succeeded (1ba9d0e6-b5f3-4ba1-b419-3aac98bf6374) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (6fa941d4-d811-46ba-9be8-a53eb83884c7) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (d5342990-f259-4fda-a114-d532e53a9267) 
Aug 8 09:10:57 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of FirmwareLoaderFileSystem succeeded (5e5cf988-5e43-4ad1-9f22-dead33d89b39) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of IncomingHMIPFrameHandler succeeded (f9bec9e6-5d46-427d-aa9c-be7db94bc162) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LegacyNotificationHandler succeeded (ce5063dc-a961-449b-8762-21ffd6c25f15) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyBackendNotificationHandler succeeded (d675f8f2-a414-41ca-a8b9-91782749200b) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of BackendCommandHandler succeeded (e260e700-06fd-4146-b0c8-f22d0b0b4752) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LegacyAPIWorker succeeded (0361f7a1-a89e-464c-b50d-09640450da05) 
Aug 8 09:10:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerAdapterInitialization succeeded (aad4aad7-91e9-48df-a730-bd60e7ee7cb6) 
Aug 8 09:10:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Aug 8 09:10:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running 
Aug 8 09:10:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Aug 8 09:10:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 11884020... 
Aug 8 09:10:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A0001F58A992F2F8 to 3 
Aug 8 09:10:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 3.4.2 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.1 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.28.0 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: CC1310 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 245250304 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 245256830 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 1 link partners 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A0001F58A992F2F8 initialized 
Aug 8 09:10:58 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Aug 8 09:10:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (4bd2c584-c11c-41a8-875e-449972d1deb7) 
Aug 8 09:10:59 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-4] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware 
Aug 8 09:10:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyInitializion succeeded (66554f8f-3835-43b9-9f3a-a828a3e07818) 
Aug 8 09:10:59 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Checking all devices on all accesspoints for updates 
Aug 8 09:10:59 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: There are 0 APs queued with updatable devices 
Aug 8 09:10:59 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Aug 8 09:11:00 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 2010 
Aug 8 09:11:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxEventLoopExecuteTime: 2000000000 
Aug 8 09:11:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default BlockedThreadCheckInterval: 1000 
Aug 8 09:11:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default MaxWorkerExecuteTime: 60000000000 
Aug 8 09:11:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Default EventLoopPoolSize: 8 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: deploying 9 classes to Vert.x 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: 9 VertxDeployers initialized 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of BackendWorker succeeded (768a9c75-01e7-496c-bc2e-de3902d75587) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (a31ceb29-286c-4727-bc70-c2e7effcc7ca) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CouplingRequestWorker succeeded (139bf9d1-4988-4125-af67-a60e851fac82) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (be0ae276-a7d7-4edc-b157-16c949358453) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of StorageRequestWorker succeeded (f1c4f343-a35a-414e-80b8-0062c657da54) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of RegaClientWorker succeeded (fc38ce51-c086-48f6-9950-b5cb25d8bba1) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DiagramRequestWorker succeeded (79f71d24-8cad-4be6-a2a4-6c416e01252b) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of GroupRequestWorker succeeded (9ab8d804-fc38-42d1-a7ee-9c5767729153) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (0f36a16d-477d-4d1f-beeb-50e9ec432020) 
Aug 8 09:11:01 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: initial deployment complete _____________________________________________________ 
Aug 8 09:11:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Starting HMServer at 127.0.0.1:9292 
Aug 8 09:11:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Read Configuration 
Aug 8 09:11:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create Bidcos Dispatcher 
Aug 8 09:11:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] InitBidCosCache 
Aug 8 09:11:02 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create groupDefinitionProvider 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create VirtualDeviceHolder 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create VirtualDeviceHandlerRega 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupAdministrationService 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupDeviceDispatcher 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create GroupDeviceHandler 
Aug 8 09:11:03 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] @GroupDeviceHandler - initializing... 
Aug 8 09:11:03 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Aug 8 09:11:03 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Aug 8 09:11:03 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> got groupDefinitionProvider 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create BidCosGroupMemberProvider 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init groupAdministrationService 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init Virtual OS Device 
Aug 8 09:11:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init ESHLight Bridge 
Aug 8 09:11:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create RrdDatalogging 
Aug 8 09:11:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create MeasurementService 
Aug 8 09:11:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Init MeasurementService 
Aug 8 09:11:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create HTTP Server 
Aug 8 09:11:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create BidCos context and start handler 
Aug 8 09:11:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Create group context and start handler 
Aug 8 09:11:04 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:9292/bidcos 
Aug 8 09:11:04 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished 
Aug 8 09:11:04 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: HmIP-RF_java 
Aug 8 09:11:05 de.eq3.ccu.server.BaseHMServer INFO  [Thread-2] Starting HMServer done 
Aug 8 09:11:16 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999 
Aug 8 09:11:16 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] Added InterfaceId: 1008 
Aug 8 09:11:16 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-9] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Aug 8 09:11:26 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:1999 
Aug 8 09:11:26 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Aug 8 09:11:26 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-4] Added InterfaceId: 1009 
Aug 8 09:15:57 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: 0 Accesspoints in Queue 
Aug 8 09:15:57 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Aug 8 09:15:57 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Aug 8 09:20:57 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: 0 Accesspoints in Queue 
Aug 8 09:20:57 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Aug 8 09:20:57 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-5] SYSTEM: Eventlistener Handler utilization: 0/50 used 
sudo ps aux

Code: Alles auswählen

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.2  0.6  28036  6076 ?        Ss   09:10   0:01 /sbin/init
root         2  0.0  0.0      0     0 ?        S    09:10   0:00 [kthreadd]
root         4  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/0:0H]
root         5  0.0  0.0      0     0 ?        I    09:10   0:00 [kworker/u8:0]
root         6  0.0  0.0      0     0 ?        I<   09:10   0:00 [mm_percpu_wq]
root         7  0.0  0.0      0     0 ?        S    09:10   0:00 [ksoftirqd/0]
root         8  0.0  0.0      0     0 ?        I    09:10   0:00 [rcu_sched]
root         9  0.0  0.0      0     0 ?        I    09:10   0:00 [rcu_bh]
root        10  0.0  0.0      0     0 ?        S    09:10   0:00 [migration/0]
root        11  0.0  0.0      0     0 ?        S    09:10   0:00 [cpuhp/0]
root        12  0.0  0.0      0     0 ?        S    09:10   0:00 [cpuhp/1]
root        13  0.0  0.0      0     0 ?        S    09:10   0:00 [migration/1]
root        14  0.0  0.0      0     0 ?        S    09:10   0:00 [ksoftirqd/1]
root        15  0.0  0.0      0     0 ?        I    09:10   0:00 [kworker/1:0]
root        16  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/1:0H]
root        17  0.0  0.0      0     0 ?        S    09:10   0:00 [cpuhp/2]
root        18  0.0  0.0      0     0 ?        S    09:10   0:00 [migration/2]
root        19  0.0  0.0      0     0 ?        S    09:10   0:00 [ksoftirqd/2]
root        21  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/2:0H]
root        22  0.0  0.0      0     0 ?        S    09:10   0:00 [cpuhp/3]
root        23  0.0  0.0      0     0 ?        S    09:10   0:00 [migration/3]
root        24  0.0  0.0      0     0 ?        S    09:10   0:00 [ksoftirqd/3]
root        26  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/3:0H]
root        27  0.0  0.0      0     0 ?        S    09:10   0:00 [kdevtmpfs]
root        28  0.0  0.0      0     0 ?        I<   09:10   0:00 [netns]
root        30  0.0  0.0      0     0 ?        I    09:10   0:00 [kworker/1:1]
root        31  0.0  0.0      0     0 ?        I    09:10   0:00 [kworker/2:1]
root        32  0.0  0.0      0     0 ?        I    09:10   0:00 [kworker/3:1]
root        33  0.0  0.0      0     0 ?        S    09:10   0:00 [khungtaskd]
root        34  0.0  0.0      0     0 ?        S    09:10   0:00 [oom_reaper]
root        35  0.0  0.0      0     0 ?        I<   09:10   0:00 [writeback]
root        36  0.0  0.0      0     0 ?        S    09:10   0:00 [kcompactd0]
root        37  0.0  0.0      0     0 ?        I<   09:10   0:00 [crypto]
root        38  0.0  0.0      0     0 ?        I<   09:10   0:00 [kblockd]
root        39  0.0  0.0      0     0 ?        I<   09:10   0:00 [watchdogd]
root        40  0.0  0.0      0     0 ?        I<   09:10   0:00 [rpciod]
root        41  0.0  0.0      0     0 ?        I<   09:10   0:00 [xprtiod]
root        42  0.0  0.0      0     0 ?        I    09:10   0:00 [kworker/u8:1]
root        44  0.0  0.0      0     0 ?        S    09:10   0:00 [kswapd0]
root        45  0.0  0.0      0     0 ?        I<   09:10   0:00 [nfsiod]
root        55  0.0  0.0      0     0 ?        I<   09:10   0:00 [kthrotld]
root        56  0.0  0.0      0     0 ?        I<   09:10   0:00 [iscsi_eh]
root        57  0.0  0.0      0     0 ?        I<   09:10   0:00 [dwc_otg]
root        58  0.0  0.0      0     0 ?        I<   09:10   0:00 [DWC Notificati
root        59  0.0  0.0      0     0 ?        S<   09:10   0:00 [vchiq-slot/0]
root        60  0.0  0.0      0     0 ?        S<   09:10   0:00 [vchiq-recy/0]
root        61  0.0  0.0      0     0 ?        S<   09:10   0:00 [vchiq-sync/0]
root        62  0.0  0.0      0     0 ?        S    09:10   0:00 [vchiq-keep/0]
root        63  0.0  0.0      0     0 ?        S<   09:10   0:00 [SMIO]
root        65  0.0  0.0      0     0 ?        S    09:10   0:00 [irq/92-mmc1]
root        67  0.0  0.0      0     0 ?        S    09:10   0:00 [mmcqd/0]
root        68  0.0  0.0      0     0 ?        S    09:10   0:00 [jbd2/mmcblk0p2
root        69  0.0  0.0      0     0 ?        I<   09:10   0:00 [ext4-rsv-conve
root        70  0.0  0.0      0     0 ?        I<   09:10   0:00 [ipv6_addrconf]
root        84  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/2:1H]
root        97  0.0  0.4  26924  4620 ?        Ss   09:10   0:00 /lib/systemd/sy
root       124  0.0  0.0      0     0 ?        I    09:10   0:00 [kworker/0:2]
root       128  0.0  0.3  14468  3360 ?        Ss   09:10   0:00 /lib/systemd/sy
root       159  0.0  0.0      0     0 ?        I    09:10   0:00 [kworker/3:2]
root       195  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/0:1H]
root       199  0.0  0.0      0     0 ?        I<   09:10   0:00 [cfg80211]
root       203  0.0  0.0      0     0 ?        S    09:10   0:00 [scsi_eh_0]
root       204  0.0  0.0      0     0 ?        I<   09:10   0:00 [scsi_tmf_0]
root       205  0.0  0.0      0     0 ?        I<   09:10   0:00 [brcmf_wq/mmc1:
root       206  0.0  0.0      0     0 ?        S    09:10   0:00 [usb-storage]
root       207  0.0  0.0      0     0 ?        S    09:10   0:00 [brcmf_wdog/mmc
systemd+   235  0.0  0.3  17280  3484 ?        Ssl  09:10   0:00 /lib/systemd/sy
root       325  0.0  0.0      0     0 ?        S    09:10   0:00 [irq/169-usb-00
root       335  0.0  0.2   5700  2428 ?        Ss   09:10   0:00 /usr/sbin/cron 
root       337  0.0  0.4   7380  4340 ?        Ss   09:10   0:00 /lib/systemd/sy
nobody     338  0.0  0.2   5296  2400 ?        Ss   09:10   0:00 /usr/sbin/thd -
message+   345  0.0  0.3   6516  3328 ?        Ss   09:10   0:00 /usr/bin/dbus-d
root       370  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/3:1H]
avahi      400  0.0  0.2   6536  2836 ?        Ss   09:10   0:00 avahi-daemon: r
root       402  0.0  0.2  23748  2404 ?        Ssl  09:10   0:00 /usr/sbin/rsysl
avahi      407  0.0  0.0   6404   324 ?        S    09:10   0:00 avahi-daemon: c
root       455  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/1:1H]
root       467  0.0  0.2   6644  1976 ?        Ss   09:10   0:00 /sbin/dhclient 
root       528  0.0  0.1   4600  1392 tty1     Ss+  09:10   0:00 /sbin/agetty --
root       551  0.0  0.4  10208  4660 ?        Ss   09:10   0:00 /usr/sbin/sshd 
redis      573  0.3  0.3  30088  3092 ?        Ssl  09:10   0:02 /usr/bin/redis-
root       584  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/u9:0]
root       588  0.0  0.0   2096   152 ?        S    09:10   0:00 /usr/bin/hciatt
root       590  0.0  0.0      0     0 ?        I<   09:10   0:00 [kworker/u9:2]
root       592  0.0  0.3   7076  3472 ?        Ss   09:10   0:00 /usr/lib/blueto
pi         593  0.0  0.5   9664  4976 ?        Ss   09:10   0:00 /lib/systemd/sy
pi         596  0.0  0.1  11268  1332 ?        S    09:10   0:00 (sd-pam)
pi         694  1.4  5.5 132612 52680 ?        Sl   09:10   0:11 homebridge
root       719  1.2  6.1 152420 58432 ?        Ssl  09:10   0:10 iobroker.js-con
root       784  0.0  0.3   8200  3404 ?        Ss   09:10   0:00 /usr/bin/lxc-st
root       792  0.0  0.1   2388  1424 ?        Ss   09:10   0:00 init
root       828  0.9  4.5 139340 43648 ?        Sl   09:10   0:07 io.admin.0
root       907  0.0  0.1   2472  1552 ?        Ss   09:10   0:00 /usr/sbin/crond
root       911  0.0  0.0   2388    52 ?        Ss   09:10   0:00 /sbin/syslogd -
root       913  0.0  0.0   2388    48 ?        Ss   09:10   0:00 /sbin/klogd
root       980  0.0  0.0   1988    68 ?        S    09:10   0:00 /usr/sbin/ifplu
root      1070  0.0  0.0   2388    60 ?        Ss   09:10   0:00 udhcpc -x hostn
root      1071  0.2  3.4 127936 33156 ?        Sl   09:10   0:02 io.discovery.0
root      1099  0.0  0.0   3744   940 ?        S    09:10   0:00 /bin/eq3configd
root      1100  0.0  0.0   3720   916 ?        S    09:10   0:00 /bin/ssdpd
root      1105  0.0  0.3   5048  2876 ?        S    09:10   0:00 /usr/sbin/light
root      1139  0.3  3.7 128708 35280 ?        Sl   09:10   0:02 io.web.0
root      1158  0.0  0.1   5428   952 ?        Sl   09:10   0:00 /bin/multimacd 
root      1188  0.3  1.2  15648 11732 ?        Sl   09:10   0:02 /bin/rfd -f /et
root      1212  2.4  7.0 158536 67192 ?        Sl   09:10   0:18 java -Xmx64m -D
root      1222  0.2  3.4 127892 32624 ?        Sl   09:10   0:02 io.history.0
root      1236  0.9  6.2 154532 59288 ?        Sl   09:10   0:06 io.javascript.0
root      1276  0.5  3.7 129992 35488 ?        Sl   09:10   0:04 io.rpi2.0
root      1354  0.3  3.7 122088 35744 ?        Sl   09:11   0:02 io.socketio.0
root      1379  0.1  0.9  16272  8576 ?        Sl   09:11   0:00 /bin/ReGaHss.no
root      1427  0.0  0.2   3832  2092 ?        S    09:11   0:00 ntpclient -h 0.
root      1549  0.0  0.6  11528  5736 ?        Ss   09:13   0:00 sshd: pi [priv]
pi        1559  0.0  0.3  11528  3752 ?        S    09:13   0:00 sshd: pi@pts/1
pi        1562  0.0  0.4   6608  4196 pts/1    Ss   09:13   0:00 -bash
root      1707  0.0  0.0      0     0 ?        I    09:15   0:00 [kworker/0:0]
root      1822  0.0  0.0      0     0 ?        I    09:17   0:00 [kworker/2:2]
root      1974  0.0  0.0      0     0 ?        I    09:19   0:00 [kworker/u8:2]
root      2019  0.0  0.0      0     0 ?        I    09:20   0:00 [kworker/3:0]
root      2024  0.0  0.0      0     0 ?        I    09:20   0:00 [kworker/1:2]
root      2166  0.0  0.0      0     0 ?        I    09:23   0:00 [kworker/2:0]
root      2172  0.0  0.3   7632  3344 pts/1    S+   09:23   0:00 sudo ps aux
root      2176  0.0  0.3   8116  2904 pts/1    R+   09:23   0:00 ps aux
lg
Joerg

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: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von deimos » 08.08.2018, 09:39

Hi,

Das sich der Timestamp bei der Fernbedienung aktualisiert, zeigt jetzt schonmal, dass der RFD korrekt läuft. Im Log sieht man aber auch gut, dass der Aktor der Kaffeemaschine nicht erreichbar ist, allerdings nicht weil der vom Funk nicht erreichr wird, sondern weil der Befehl schon gar nicht an das Funkmodul übergeben werden kann ("RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET"). Das klingt also schwer danach, dass die Zuordnung zum richtigen Gateway nicht gegeben ist.

Kannst du daher bitte testhalber die Zuordnung des Aktors von der Kaffeemaschine mal editieren, dort Standard auswählen und dann mit OK bestätigen?
Und dann über die Weboberfläche direkt schalten?

Viele Grüße
Alex

schlusi
Beiträge: 25
Registriert: 17.11.2015, 12:23
Hat sich bedankt: 1 Mal

Re: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von schlusi » 08.08.2018, 09:49

Hi Alex,

habe ich gemacht, Standard ausgewaehlt (andere Optionen gibt es nicht), mit OK bestaetigt.
Aktor laesst sich weiterhin nicht ueber das Webui schalten.

lg
Joerg

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: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von deimos » 08.08.2018, 09:54

Hi,

dann fällt mir jetzt nur noch ein, den Aktor mal drüber zu lernen, also Aktor in Werkszustand versetzten (am Aktor, nicht über WebUI) und dann neu in der CCU anlernen. Dabei erhält er dann alle (bisherigen) Einstellungen von der CCU neu gesendet.

Bzw: Eine Idee habe doch noch: Dein Backup einspielen (das mit LAN GW), die Migrationsschritte durchführen, dann die Zuordnung der Geräte prüfen bzw. korrigieren und erst dann das LAN GW löschen.

Viele Grüße
Alex

schlusi
Beiträge: 25
Registriert: 17.11.2015, 12:23
Hat sich bedankt: 1 Mal

Re: Wechsel von externem LAN-Gateway auf das neue Funkmodul

Beitrag von schlusi » 08.08.2018, 15:23

Hi,

habe den Vorschlag mit dem Backup umgesetzt.
(Das alte LAN-Gateway war waerend der Prozedur nicht angeschlossen)

Jetzt funktioniert wieder alles wie vorher :)

Vielen Dank!!!
Joerg

Antworten

Zurück zu „piVCCU“