Hallo Alex,
es hat ein paar Tage gedauert, bis ich die Werte beim Kollegen auslesen konnte:
sudo pivccu-info
Code: Alles auswählen
piVCCU version: 3.47.10-28
Kernel modules: Available
Raw UART dev: Available
Rasp.Pi3 UART: Assigned to GPIO pins
HMRF Hardware: HM-MOD-RPI-PCB
HMIP Hardware: HM-MOD-RPI-PCB
Board serial: OEQ0310457
Radio MAC: 0x584b80
SGTIN: 3014F711A061A7D7098E24B9
State: RUNNING
PID: 749
IP: 192.168.178.50
CPU use: 31.30 seconds
BlkIO use: 77.13 MiB
Memory use: 198.86 MiB
KMem use: 5.55 MiB
Link: vethpivccu
TX bytes: 7.32 KiB
RX bytes: 262.68 KiB
Total bytes: 270.00 KiB
sudo pivccu-attach cat /var/hm_mode
Code: Alles auswählen
HM_HMIP_ADDRESS='0x584b80'
HM_HMIP_DEV='HM-MOD-RPI-PCB'
HM_HMIP_DEVNODE='/dev/raw-uart'
HM_HMIP_SERIAL='OEQ0310457'
HM_HMIP_SGTIN='3014F711A061A7D7098E24B9'
HM_HMIP_VERSION='2.8.6'
HM_HMRF_ADDRESS='0x584b80'
HM_HMRF_DEV='HM-MOD-RPI-PCB'
HM_HMRF_DEVNODE='/dev/raw-uart'
HM_HMRF_SERIAL='OEQ0310457'
HM_HMRF_VERSION='2.8.6'
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=''
sudo pivccu-attach cat /var/log/messages
Code: Alles auswählen
Jul 29 20:23:43 piVCCU syslog.info syslogd started: BusyBox v1.29.2
Jul 29 20:23:43 piVCCU user.notice kernel: klogd started: BusyBox v1.29.2 (2019-06-21 09:16:48 CEST)
Jul 29 20:23:43 piVCCU syslog.info syslogd exiting
Jul 29 20:23:43 ccu3-webui syslog.info syslogd started: BusyBox v1.29.2
Jul 29 20:23:43 ccu3-webui user.notice kernel: klogd started: BusyBox v1.29.2 (2019-06-21 09:16:48 CEST)
Jul 29 20:23:44 ccu3-webui user.info firewall: configuration set
Jul 29 20:23:44 ccu3-webui daemon.info ifplugd(eth0)[223]: ifplugd 0.28 initializing.
Jul 29 20:23:44 ccu3-webui daemon.info ifplugd(eth0)[223]: Using interface eth0/9A:BB:02:32:04:5F with driver <veth> (version: 1.0)
Jul 29 20:23:44 ccu3-webui daemon.info ifplugd(eth0)[223]: Using detection mode: SIOCETHTOOL
Jul 29 20:23:44 ccu3-webui daemon.info ifplugd(eth0)[223]: Initialization complete, link beat detected.
Jul 29 20:23:44 ccu3-webui daemon.warn ifplugd(eth0)[223]: Could not open /dev/tty, cannot beep.
Jul 29 20:23:44 ccu3-webui daemon.info ifplugd(eth0)[223]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jul 29 20:23:44 ccu3-webui daemon.warn ifplugd(eth0)[223]: client: ifup: interface eth0 already configured
Jul 29 20:23:44 ccu3-webui daemon.info ifplugd(eth0)[223]: Program executed successfully.
Jul 29 20:23:50 ccu3-webui daemon.notice ntpdate[231]: step time server 81.14.202.21 offset 0.000340 sec
Jul 29 20:23:50 ccu3-webui daemon.notice ntpd[232]: ntpd 4.2.8p12@1.3728-o Fri Jun 21 07:15:18 UTC 2019 (1): Starting
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[232]: Command line: /usr/sbin/ntpd -g ntp.homematic.com
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: proto: precision = 0.468 usec (-21)
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: Listen and drop on 0 v6wildcard [::]:123
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: Listen normally on 2 lo 127.0.0.1:123
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: Listen normally on 3 eth0 192.168.178.50:123
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: Listen normally on 4 lo [::1]:123
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: Listen normally on 5 eth0 [fe80::98bb:2ff:fe32:45f%5]:123
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: Listening on routing socket on fd #22 for interface updates
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Jul 29 20:23:50 ccu3-webui daemon.info ntpd[234]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Jul 29 20:23:50 ccu3-webui daemon.err xinetd[253]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Jul 29 20:23:50 ccu3-webui daemon.crit xinetd[253]: 253 {init_services} no services. Exiting...
Jul 29 20:23:50 ccu3-webui user.info root: Updating RF Lan Gateway Coprocessor Firmware
Jul 29 20:23:50 ccu3-webui user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Jul 29 20:23:50 ccu3-webui user.info root: Updating RF Lan Gateway Firmware
Jul 29 20:23:50 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Jul 29 20:24:08 ccu3-webui user.info kernel: [ 44.508822] eq3loop: eq3loop_open_slave() mmd_hmip
Jul 29 20:24:10 ccu3-webui user.notice kernel: [ 46.601953] random: crng init done
Jul 29 20:24:10 ccu3-webui user.notice kernel: [ 46.601962] random: 7 urandom warning(s) missed due to ratelimiting
Jul 29 20:24:31 ccu3-webui user.err Sniffing Mode: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Jul 29 20:24:31 ccu3-webui user.err Sniffing Mode: HSSParameter::GetValue() id=STATE failed getting physical value.
Jul 29 20:24:31 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"OEQ0313467:1","STATE"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 29 20:24:31 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1007, params: {"OEQ0313467:1","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 29 20:24:31 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 29 20:24:31 ccu3-webui user.err Sniffing Mode: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Jul 29 20:24:31 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ1849222:3","BRIGHTNESS"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 29 20:24:31 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1007, params: {"MEQ1849222:3","BRIGHTNESS"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 29 20:24:31 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Jul 29 20:24:31 ccu3-webui local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000C170999F94E:1","PRESENCE_DETECTION_STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: PRESENCE_DETECTION_STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Jul 29 20:24:31 ccu3-webui local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000C170999F94E:1","PRESENCE_DETECTION_STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Jul 29 20:24:31 ccu3-webui local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
sudo pivccu-attach cat /var/log/hmserver.log
Code: Alles auswählen
Jul 29 20:23:59 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory
Jul 29 20:23:59 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created instance of HMServerConfiguration with parameter(s)
Jul 29 20:23:59 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 parameter(s), in declarative order [String]
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Jul 29 20:24:04 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 32 classes to Vert.x
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 32 VertxDeployers initialized
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointElectroCardioGram succeeded (c7c69746-bf04-486e-8a94-c40a81f66690)
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (d901c018-4eaf-48a2-b95b-35354f9d4c50)
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (49e61c70-5f16-4508-932f-bf48d2557d99)
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of TransactionSubsystemHandler succeeded (05f92e74-15ad-4376-a286-37565ab4c3d6)
Jul 29 20:24:05 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-4] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of CheckDeviceExistHandler succeeded (bc174237-0043-4e04-93d9-6162f1719370)
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointKeyServerWorker succeeded (15135057-f84d-4f90-a1ae-a5742c11f158)
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of KeyServerWorker succeeded (211ef6d2-c644-4cd3-82c0-e6046d4ee784)
Jul 29 20:24:05 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Jul 29 20:24:05 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of RouterKeyServerWorker succeeded (6628ff98-0109-4215-b360-a367cf1aef1d)
Jul 29 20:24:06 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-2] SYSTEM: DeviceLiveUpdateSubsystem started
Jul 29 20:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (2a913404-0c49-457d-ba7a-b5f35fc62205)
Jul 29 20:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (a05df7cc-780a-4206-8bbe-a595bbef5a4f)
Jul 29 20:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (b4ceca23-ef4e-44b0-b4e4-9dbc9a8a0a79)
Jul 29 20:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of KryoPersistenceWorker succeeded (47e7184c-b29f-41b1-9dc1-6bd923caa4d3)
Jul 29 20:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (41b9ffdd-5548-460f-a513-c3879ac495c1)
Jul 29 20:24:06 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (b84f4806-584d-4022-b57e-691d74e91e16)
Jul 29 20:24:08 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-4] SYSTEM: Firmware update directory is set to /etc/config/firmware
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of FirmwareLoaderFileSystem succeeded (4da3c166-4a13-442c-8d29-69fe32ff1d26)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of RemoteCommAdapterInitialization succeeded (56af7945-92ce-48fb-b5c9-bf7d64961332)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of WebSocketManager succeeded (0efdd1c7-11cf-4894-87c1-79f1be6d0375)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of IncomingHMIPFrameHandler succeeded (5cd521ed-cb5b-4704-bc5e-e2c510735e8a)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointWatchdog succeeded (b9b4e42e-11a4-4141-81e6-23f8389440e7)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of AccessPointMessageDispatcher succeeded (fd2eb66f-aa6b-4433-a723-3b0c1777f3f5)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (3da64a9b-d1da-49e1-a9e7-a11971bee2f1)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of BackendCommandHandler succeeded (3a87bac8-e227-494f-b1ed-04e9dbf345cd)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of AccessPointAuthorisationHandler succeeded (1f13e30d-13be-4590-adbe-05dde5b677fd)
Jul 29 20:24:08 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerAdapterInitialization succeeded (7bd7e9d5-591a-4756-80ab-5a9b730dc141)
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRX_App
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running or started
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ...
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 12561669...
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A061A7D7098E24B9 to 3
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version...
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 2.8.6
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.3
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.20.3
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] MCU type: Si1002_8051
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Duty Cycle: 0.0
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] set DutyCycle limit to ffffffc8
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set Duty Cycle Limit
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Current Security Counter: 353312001
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Update security counter to calculation: 358259862
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter has 1 link partners
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Adapter with Access Point id 3014F711A061A7D7098E24B9 initialized
Jul 29 20:24:08 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Jul 29 20:24:09 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (23c48325-cd16-4286-8365-42b8ea745ceb)
Jul 29 20:24:09 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN [vert.x-worker-thread-3] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware
Jul 29 20:24:09 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of AccessPointCommDevice succeeded (3ee76b75-683d-47f4-99ac-174d70fa5cbf)
Jul 29 20:24:09 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: Checking all devices on all accesspoints for updates
Jul 29 20:24:09 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: There are 0 APs queued with updatable devices (RF)
Jul 29 20:24:09 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO [vert.x-eventloop-thread-4] SYSTEM: There are 0 APs queued with updatable devices (WIRED)
Jul 29 20:24:09 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyBackendNotificationHandler succeeded (ef787386-88c1-42a8-b456-bb2301264ff6)
Jul 29 20:24:09 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.50
Jul 29 20:24:09 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of LegacyNotificationHandler succeeded (18785653-0a1e-4b1f-bf11-ccbb264b141a)
Jul 29 20:24:09 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of LegacyAPIWorker succeeded (8160a516-6274-4e17-865b-aaea21c6a875)
Jul 29 20:24:10 de.eq3.cbcs.lib.lanrouting.LanRoutingWorker INFO [vert.x-worker-thread-0] AP 3014F711A061A7D7098E24B9: Could not initialize routing of access point, version is 2.8.6
Jul 29 20:24:10 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LanRoutingWorker succeeded (5950545a-eb32-4f0c-9c3e-6cd369ef7106)
Jul 29 20:24:10 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.50)
Jul 29 20:24:10 de.eq3.cbcs.lib.lanrouting.UdpServer INFO [vert.x-worker-thread-3] UDP Routing multi cast established on network interface eth0 : 192.168.178.50
Jul 29 20:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of LegacyInitializion succeeded (541c23d4-e31c-4e03-aec3-37bbc08fefb6)
Jul 29 20:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of RemoteCommAdapterFinalization succeeded (537aa5dc-fab3-4589-935f-c4ce732cdb37)
Jul 29 20:24:11 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Jul 29 20:24:11 de.eq3.cbcs.server.local.LocalServer INFO [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
Jul 29 20:24:11 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-7] SYSTEM: Started Access Point WebSocket server with port 9293
Jul 29 20:24:11 de.eq3.cbcs.lib.remotecommadapter.AccessPointCommDevice INFO [vert.x-eventloop-thread-7] SYSTEM: connector open
Jul 29 20:24:14 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
Jul 29 20:24:14 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default BlockedThreadCheckInterval: 1000
Jul 29 20:24:14 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default MaxWorkerExecuteTime: 60000000000
Jul 29 20:24:14 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Default EventLoopPoolSize: 8
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: deploying 10 classes to Vert.x
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: 10 VertxDeployers initialized
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of BackendWorker succeeded (8167c0d0-d7a8-4ce0-b560-ce8d273ed0bf)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (4393f411-b793-46ea-a6d0-3f006534a201)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of StorageRequestWorker succeeded (be76c53d-543b-4282-80ba-68955f236c30)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of CouplingRequestWorker succeeded (edeea845-5ffd-4feb-9bbf-1aaec526dd45)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (0e989988-f877-4e0a-9bb4-214cbe7bfd0f)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of RegaClientWorker succeeded (de5c2651-cb38-4a3e-a4b9-e6b596000818)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of DiagramRequestWorker succeeded (b61776f3-65eb-46ab-abe3-52cdb552fd2a)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of GroupRequestWorker succeeded (7f8cb8ec-c91a-4155-8ee7-2c5bdc0bd891)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (22e07b57-df96-43af-a795-e665422b8f75)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (030aef1d-1f9d-456f-906e-cebdeb3cfd15)
Jul 29 20:24:14 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
Jul 29 20:24:14 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer at 127.0.0.1:39292
Jul 29 20:24:14 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Read Configuration
Jul 29 20:24:15 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create Bidcos Dispatcher
Jul 29 20:24:15 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] InitBidCosCache
Jul 29 20:24:16 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create groupDefinitionProvider
Jul 29 20:24:16 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHolder
Jul 29 20:24:16 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create VirtualDeviceHandlerRega
Jul 29 20:24:16 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupAdministrationService
Jul 29 20:24:16 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceDispatcher
Jul 29 20:24:16 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create GroupDeviceHandler
Jul 29 20:24:16 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] @GroupDeviceHandler - initializing...
Jul 29 20:24:16 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Jul 29 20:24:16 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Jul 29 20:24:16 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO [Thread-1] --> got groupDefinitionProvider
Jul 29 20:24:16 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCosGroupMemberProvider
Jul 29 20:24:17 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init groupAdministrationService
Jul 29 20:24:17 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init Virtual OS Device
Jul 29 20:24:17 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init ESHLight Bridge
Jul 29 20:24:17 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create RrdDatalogging
Jul 29 20:24:17 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create MeasurementService
Jul 29 20:24:17 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Init MeasurementService
Jul 29 20:24:18 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create HTTP Server
Jul 29 20:24:18 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create BidCos context and start handler
Jul 29 20:24:18 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Create group context and start handler
Jul 29 20:24:18 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
Jul 29 20:24:18 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-0] init finished
Jul 29 20:24:18 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-1] Added InterfaceId: HmIP-RF_java
Jul 29 20:24:18 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO [vert.x-worker-thread-1] updateDevicesForClient HmIP-RF_java -> 55 device addresses will be added
Jul 29 20:24:19 de.eq3.ccu.server.BaseHMServer INFO [Thread-1] Starting HMServer done
Jul 29 20:24:28 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999
Jul 29 20:24:28 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO [vert.x-eventloop-thread-5] Added InterfaceId: 1008
Jul 29 20:24:28 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO [vert.x-worker-thread-13] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Jul 29 20:24:38 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999
Jul 29 20:24:38 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO [vert.x-worker-thread-2] init finished
Jul 29 20:24:38 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO [vert.x-worker-thread-0] Added InterfaceId: 1009
Ist dir dort was auffälliges ersichtlich?
Wir haben es mit "Heizkörperthermostat easy connect" versucht. Nach Anleitung.
Ziehen Sie den Isolierstreifen aus dem Batteriefach des Heizkörper-
thermostats heraus. Drücken Sie für mind. 4 s auf die Systemtaste des Heizkörperther- mostats (D), um den Anlernmodus zu aktivieren (s. Abbildung 2). Die Geräte-LED (D) beginnt orange zu blinken. Der Anlernmodus ist für
3 Minuten aktiv.
Auch ein Reset auf Werkseinstellungen brachte keinen Erfolg.