HmIP-RF VirtualDevice Komponente reagiert ....

Einrichtung, Nutzung und Hilfe zu YAHM

Moderator: Co-Administratoren

Darth.Weber
Beiträge: 55
Registriert: 14.12.2014, 13:07
Hat sich bedankt: 1 Mal

Re: HmIP-RF VirtualDevice Komponente reagiert ....

Beitrag von Darth.Weber » 11.04.2018, 19:29

Ich habe gar keine homematic-ip Geräte - bin ich da mit deinem pivccu nicht viel besser dran ? Werde ich morgen mal probieren. Recht herzlichen Dank schon mal so weit.

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

Re: HmIP-RF VirtualDevice Komponente reagiert ....

Beitrag von deimos » 11.04.2018, 19:39

Hi,

bei piVCCU ist HmIP Support immer drin, weil die CCU dort so weit wie möglich emuliert wird.

Ob du damit besser dran bist, müssen andere beurteilen. :wink:

Viele Grüße
Alex

Darth.Weber
Beiträge: 55
Registriert: 14.12.2014, 13:07
Hat sich bedankt: 1 Mal

Re: HmIP-RF VirtualDevice Komponente reagiert ....

Beitrag von Darth.Weber » 12.04.2018, 06:33

Test mir Raspianmatic ist durch: Einmal damit durchgestartet, danach wieder yahm in Betrieb genommen - der im ersten Post beschriebene Fehler ist noch genau so da (inkl. der log-Meldungen)

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

Re: HmIP-RF VirtualDevice Komponente reagiert ....

Beitrag von deimos » 12.04.2018, 07:36

Hi,

dann bin ich leider raus, bei YAHM kenn ich mich nur beschränkt aus. Der Fehler liegt aber grundsätzlich daran, dass der HmServer nicht mit dem Funkmodul kommunizieren kann, das kann an fehlenden Kernel-Modules, fehlenden Device Tree Overlays oder falschen Device Nodes liegen.

Viele Grüße
Alex

Darth.Weber
Beiträge: 55
Registriert: 14.12.2014, 13:07
Hat sich bedankt: 1 Mal

Re: HmIP-RF VirtualDevice Komponente reagiert ....

Beitrag von Darth.Weber » 12.04.2018, 07:58

hab jetzt noch mal mit deinem PiVCCU getestet - läuft ja auf Anhieb !

Code: Alles auswählen

***** messages *****
Apr 12 07:23:40 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Apr 12 07:23:40 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2018-01-15 15:55:20 CET)
Apr 12 05:23:41 homematic-ccu2 daemon.info ifplugd(eth0)[138]: ifplugd 0.28 initializing.
Apr 12 05:23:41 homematic-ccu2 daemon.info ifplugd(eth0)[138]: Using interface eth0/0A:CF:BB:CB:B6:3E with driver <veth> (version: 1.0)
Apr 12 05:23:41 homematic-ccu2 daemon.info ifplugd(eth0)[138]: Using detection mode: SIOCETHTOOL
Apr 12 05:23:41 homematic-ccu2 daemon.info ifplugd(eth0)[138]: Initialization complete, link beat detected.
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: Could not open /dev/tty, cannot beep.
Apr 12 05:23:41 homematic-ccu2 daemon.info ifplugd(eth0)[138]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: net.ipv4.tcp_timestamps = 0
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: udhcpc (v1.20.2) started
Apr 12 07:23:41 homematic-ccu2 user.debug setclock: Try to get time from 0.de.pool.ntp.org
Apr 12 07:23:41 homematic-ccu2 user.debug setclock: Thu Apr 12 07:23:41 CEST 2018
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: Sending discover...
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: Sending select for 192.168.178.65...
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: Lease of 192.168.178.65 obtained, lease time 864000
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: rm: can't remove '/var/etc/resolv.conf': No such file or directory
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: udhcpc (v1.20.2) started
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: Sending discover...
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: Sending select for 192.168.178.65...
Apr 12 05:23:41 homematic-ccu2 daemon.warn ifplugd(eth0)[138]: client: Lease of 192.168.178.65 obtained, lease time 864000
Apr 12 05:23:42 homematic-ccu2 daemon.info ifplugd(eth0)[138]: Program executed successfully.
Apr 12 05:23:46 homematic-ccu2 auth.info sshd[236]: Server listening on 0.0.0.0 port 22.
Apr 12 05:23:46 homematic-ccu2 auth.info sshd[236]: Server listening on :: port 22.
Apr 12 07:23:46 homematic-ccu2 user.info homematic: started cux-daemon
Apr 12 05:23:46 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Apr 12 05:23:46 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Apr 12 05:23:46 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Apr 12 05:23:46 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Apr 12 05:23:46 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Apr 12 05:23:46 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Apr 12 07:23:49 homematic-ccu2 user.info update-coprocessor: Version: 2.8.6
Apr 12 07:23:49 homematic-ccu2 user.info update-coprocessor: No update necessary
Apr 12 07:23:55 homematic-ccu2 user.warn rfd: opendir(/etc/config/firmware//) failed
Apr 12 07:23:55 homematic-ccu2 user.err rfd: HEQ0400002: Could not determine IP
Apr 12 07:23:55 homematic-ccu2 user.err rfd: IEQ0245542: Could not determine IP
Apr 12 07:24:06 homematic-ccu2 user.notice kernel: [   45.352372] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
Apr 12 07:24:10 homematic-ccu2 user.err rfd: HEQ0400002: Could not determine IP
Apr 12 07:24:10 homematic-ccu2 user.err rfd: Invalid Message received: \xc7\xc1\x15XD\x01t\xfeM\xaed-\xf7\xe2d\xf3\xbd\x05\x8a\x12\xf5U\xdcWZ[\x02U\xa5\xc4\xe1*\xfc,I\xec\xad
Apr 12 07:24:10 homematic-ccu2 user.warn rfd: IEQ0245542: Invalid hello message received: 
Apr 12 07:24:19 homematic-ccu2 user.info homematic: started cux-daemon
Apr 12 07:24:27 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= IEQ0245542 [iseXmlRpc.cpp:2144]
Apr 12 07:24:28 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr 12 07:24:28 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=ENERGY_COUNTER failed getting physical value.
Apr 12 07:24:28 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"LEQ0529456:2","ENERGY_COUNTER"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Apr 12 07:24:28 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Apr 12 07:24:28 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Apr 12 07:24:30 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr 12 07:24:30 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=ENERGY_COUNTER failed getting physical value.
Apr 12 07:24:30 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"LEQ0534434:2","ENERGY_COUNTER"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Apr 12 07:24:30 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Apr 12 07:24:30 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Apr 12 07:24:32 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr 12 07:24:32 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Apr 12 07:24:32 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"LEQ0534434:1","STATE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Apr 12 07:24:32 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Apr 12 07:24:32 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Apr 12 07:24:32 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Apr 12 07:24:32 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=ENERGY_COUNTER failed getting physical value.
Apr 12 07:24:32 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"LEQ0534434:2","ENERGY_COUNTER"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Apr 12 07:24:32 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Apr 12 07:24:32 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Apr 12 07:24:35 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= HEQ0400002 [iseXmlRpc.cpp:2144]
Apr 12 07:24:36 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [iseXmlRpc.h:281]
Apr 12 07:24:36 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","2760"} result= nil [iseXmlRpc.cpp:2599]
Apr 12 07:24:36 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [iseXmlRpc.cpp:1204]
Apr 12 07:24:36 homematic-ccu2 local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=CUxD [iseRTHss.cpp:163]
Apr 12 07:24:41 homematic-ccu2 user.debug setclock: Try to get time from 0.de.pool.ntp.org
Apr 12 07:24:41 homematic-ccu2 user.debug setclock: Thu Apr 12 07:24:41 CEST 2018
Apr 12 07:30:01 homematic-ccu2 cron.info crond[68]: crond: USER root pid 543 cmd /bin/SetInterfaceClock 127.0.0.1:2001
Apr 12 07:56:03 homematic-ccu2 user.warn rfd: XmlRpc transport failed (first try), retrying...


***** hmserver.log *****
Apr 12 07:24:00 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Apr 12 07:24:00 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Apr 12 07:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 19 classes to Vert.x 
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 19 VertxDeployers initialized 
Apr 12 07:24:05 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of HMIPTRXWriterWorker succeeded (03b587c3-bc30-4a8a-86e8-595c931a7365) 
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of TransactionSubsystemHandler succeeded (06ed1340-5e77-44d8-8bf5-c6d7e321b84e) 
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (195d6526-0d95-4f5d-bbc4-926b4506bf7a) 
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (478ad997-c082-420e-b7ba-d91921843d46) 
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of KeyServerWorker succeeded (d359c341-eead-449a-920e-e3d8730dbaa0) 
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (30f7f3b4-8946-4edc-a66b-7a504387a346) 
Apr 12 07:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (d035488c-06b4-4b46-98d0-ad68cb33c7b8) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KryoPersistenceWorker succeeded (fff32fce-5b32-4456-807f-e69e29a000b8) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LocalServerPersistentDataLoader succeeded (7ac85a40-8a03-493f-bd7c-4bb1aa635c33) 
Apr 12 07:24:06 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of FirmwareLoaderFileSystem succeeded (540b54f4-f624-4981-a5e4-ddae7ef409b5) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (dc8ba943-0d22-41a6-a107-332f24c1371b) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of IncomingHMIPFrameHandler succeeded (c924ab2c-9e8a-4671-a7d5-18835094ea9b) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyNotificationHandler succeeded (77b008a0-0e27-4cca-a6b1-a15e2be7627f) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of BackendCommandHandler succeeded (a9cad14e-0434-42f0-9974-7a239e005cd5) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyBackendNotificationHandler succeeded (3a0788b8-73f0-4e3c-9ef8-0daf8eaca863) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyAPIWorker succeeded (31e2e61f-cea9-49d2-9159-19671318f559) 
Apr 12 07:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerAdapterInitialization succeeded (8b8c16de-ceb8-46c3-b54a-a3eb589dfafd) 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12549111... 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D70992B057 to 3 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3 
Apr 12 07:24:06 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 0.0 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 37060608 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 37067840 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D70992B057 initialized 
Apr 12 07:24:07 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Apr 12 07:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LegacyInitializion succeeded (324ff642-3b75-45a0-9252-52dfef2cf1bd) 
Apr 12 07:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (9b83cfb9-81fc-4aa0-b8a9-51b2b8b29bc3) 
Apr 12 07:24:08 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-0] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware 
Apr 12 07:24:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-3] SYSTEM: Checking all devices on all accesspoints for updates 
Apr 12 07:24:08 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-3] SYSTEM: There are 0 APs queued with updatable devices 
Apr 12 07:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Apr 12 07:24:10 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default MaxEventLoopExecuteTime: 2000000000 
Apr 12 07:24:10 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default BlockedThreadCheckInterval: 1000 
Apr 12 07:24:10 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default MaxWorkerExecuteTime: 60000000000 
Apr 12 07:24:10 de.eq3.ccu.server.HMServer INFO  [Thread-2] Default EventLoopPoolSize: 8 
Apr 12 07:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Apr 12 07:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Apr 12 07:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Apr 12 07:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Apr 12 07:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Apr 12 07:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Apr 12 07:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Apr 12 07:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: deploying 7 classes to Vert.x 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: 7 VertxDeployers initialized 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of BackendWorker succeeded (8320882a-9641-421c-98f0-ea823570709a) 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of EnergyPriceRequestWorker succeeded (650fb1dd-5ef7-434f-befd-f922d33833ae) 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of StorageRequestWorker succeeded (b06b5a2d-2145-4661-b747-6841a40cc5b3) 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of CouplingRequestWorker succeeded (5e1e9381-eaa2-44e0-b5f4-6f7487539c9d) 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of GroupRequestWorker succeeded (d8ae10d0-a5b4-4a2f-b6d7-0d2cfef593fa) 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DiagramRequestWorker succeeded (d0fb0be3-8841-4bdc-ae05-897e53e2f310) 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (a76043c5-ce5b-4e1c-9150-8feba3f0646b) 
Apr 12 07:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-2] SYSTEM: initial deployment complete _____________________________________________________ 
Apr 12 07:24:11 de.eq3.ccu.server.HMServer INFO  [Thread-2] Starting HMServer at 127.0.0.1:9292 
Apr 12 07:24:11 de.eq3.ccu.server.HMServer INFO  [Thread-2] Read Configuration 
Apr 12 07:24:11 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create Bidcos Dispatcher 
Apr 12 07:24:11 de.eq3.ccu.server.HMServer INFO  [Thread-2] InitBidCosCache 
Apr 12 07:24:12 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create groupDefinitionProvider 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create VirtualDeviceHolder 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create VirtualDeviceHandlerRega 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupAdministrationService 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupDeviceDispatcher 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create GroupDeviceHandler 
Apr 12 07:24:13 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] @GroupDeviceHandler - initializing... 
Apr 12 07:24:13 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Apr 12 07:24:13 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Apr 12 07:24:13 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-2] --> got groupDefinitionProvider 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create BidCosGroupMemberProvider 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init groupAdministrationService 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init Virtual OS Device 
Apr 12 07:24:13 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init ESHLight Bridge 
Apr 12 07:24:14 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create RrdDatalogging 
Apr 12 07:24:14 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create MeasurementService 
Apr 12 07:24:14 de.eq3.ccu.server.HMServer INFO  [Thread-2] Init MeasurementService 
Apr 12 07:24:14 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create HTTP Server 
Apr 12 07:24:14 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create BidCos context and start handler 
Apr 12 07:24:14 de.eq3.ccu.server.HMServer INFO  [Thread-2] Create group context and start handler 
Apr 12 07:24:14 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 
Apr 12 07:24:14 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished 
Apr 12 07:24:14 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: HmIP-RF_java 
Apr 12 07:24:15 de.eq3.ccu.server.HMServer INFO  [Thread-2] Starting HMServer done 
Apr 12 07:24:26 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 
Apr 12 07:24:26 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] Added InterfaceId: 1008 
Apr 12 07:24:26 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-7] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Apr 12 07:24:36 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:1999 
Apr 12 07:24:36 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] init finished 
Apr 12 07:24:36 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: 2589 

woran erkenne ich denn, dass das Funkmodul läuft und welche fw nun drauf ist ?

*UPDATE* wer lesen kann ... steht ja drin, sieht ja echt okay aus

Antworten

Zurück zu „YAHM“