HM-MOD-RPI-PC pivccu kein anlernen möglich

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

Antworten
enttom
Beiträge: 9
Registriert: 12.12.2013, 12:45

HM-MOD-RPI-PC pivccu kein anlernen möglich

Beitrag von enttom » 19.12.2018, 19:18

EDIT.
Problem gelöst! Mehr oder weniger :D konnte in direkter nähe ne fernbedienung anlernen -daher grundsetzlich geht es :mrgreen:
entweder die antennenleistung ist zu gering oder ich habe die anderen komponenten nicht richtig resetet bzw falsch angelernt!
Hallo,

ich habe folgendes Problem, ich kann an meinen RP2 keine Geräte anlernen.
kury zur vorgeschichte ich habe ein raspimatic mit nem hm-cfg-lan laufen gehabt, von einen tag auf den nächsten hat das dann plötzlich nicht mehr funktioniert - es war zwar im lan auffindbar - man könnte aber weder dir IP Adresse ändern noch ein Firmware Update machen - nicht normal und auch nicht im bootloader - also habe ich mir ein HM-MOD-RPI-Pc besorgt und eine pivccu aufgesetzt

Einen Lichtschalter resetet und versucht anzulernen!

(Wenn ich versuche das Backup einzuspielen funktioniert nachher nichts mehr und wenn ich auf anlernen drücke kommt ne Fehlermeldung das der bris Adapter nicht gefunden wird)
Das HM-MOD-RPI-PC sieht soweit gut aus:

Code: Alles auswählen

 sudo pivccu-info
piVCCU version: 3.41.11-9
Kernel modules: Available
Raw UART dev:   Available
HMRF Hardware:  HM-MOD-RPI-PCB
HMIP Hardware:  HM-MOD-RPI-PCB
Board serial:   PEQ0533218
Radio MAC:      0x6a58e4
SGTIN:          3014F711A061A7D8A9918AE2
State:          RUNNING
PID:            3994
IP:             192.168.178.131
CPU use:        107.55 seconds
BlkIO use:      60.97 MiB
Link:           vethpivccu
 TX bytes:      2.45 MiB
 RX bytes:      2.95 MiB
 Total bytes:   5.40 MiB
Log:

Code: Alles auswählen

***** messages *****
Dec 19 18:17:03 piVCCU syslog.info syslogd started: BusyBox v1.28.4
Dec 19 18:17:03 piVCCU user.notice kernel: klogd started: BusyBox v1.28.4 (2018-11-12 09:49:13 CET)
Dec 19 18:17:04 piVCCU syslog.info syslogd exiting
Dec 19 18:17:04 ccu3-webui syslog.info syslogd started: BusyBox v1.28.4
Dec 19 18:17:04 ccu3-webui user.notice kernel: klogd started: BusyBox v1.28.4 (2018-11-12 09:49:13 CET)
Dec 19 18:17:04 ccu3-webui daemon.err udhcpc[155]: started, v1.28.4
Dec 19 18:17:04 ccu3-webui daemon.err udhcpc[155]: sending discover
Dec 19 18:17:04 ccu3-webui daemon.err udhcpc[155]: sending select for 192.168.178.131
Dec 19 18:17:04 ccu3-webui daemon.err udhcpc[155]: lease of 192.168.178.131 obtained, lease time 86400
Dec 19 18:17:05 ccu3-webui user.info firewall: has ip6 1
Dec 19 18:17:06 ccu3-webui user.info firewall: configuration set
Dec 19 18:17:06 ccu3-webui daemon.info ifplugd(eth0)[224]: ifplugd 0.28 initializing.
Dec 19 18:17:06 ccu3-webui daemon.info ifplugd(eth0)[224]: Using interface eth0/BA:D5:60:51:3D:62 with driver <veth> (version: 1.0)
Dec 19 18:17:06 ccu3-webui daemon.info ifplugd(eth0)[224]: Using detection mode: SIOCETHTOOL
Dec 19 18:17:06 ccu3-webui daemon.info ifplugd(eth0)[224]: Initialization complete, link beat detected.
Dec 19 18:17:06 ccu3-webui daemon.warn ifplugd(eth0)[224]: Could not open /dev/tty, cannot beep.
Dec 19 18:17:06 ccu3-webui daemon.info ifplugd(eth0)[224]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Dec 19 18:17:06 ccu3-webui daemon.warn ifplugd(eth0)[224]: client: ifup: interface eth0 already configured
Dec 19 18:17:06 ccu3-webui daemon.info ifplugd(eth0)[224]: Program executed successfully.
Dec 19 18:17:16 ccu3-webui daemon.notice ntpdate[235]: step time server 193.30.120.245 offset 0.009623 sec
Dec 19 18:17:16 ccu3-webui daemon.notice ntpd[236]: ntpd 4.2.8p11@1.3728-o Mon Nov 12 09:31:16 UTC 2018 (1): Starting
Dec 19 18:17:16 ccu3-webui daemon.info ntpd[236]: Command line: /usr/sbin/ntpd -g 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org
Dec 19 18:17:16 ccu3-webui daemon.info ntpd[238]: proto: precision = 0.833 usec (-20)
Dec 19 18:17:16 ccu3-webui daemon.info ntpd[238]: Listen and drop on 0 v6wildcard [::]:123
Dec 19 18:17:16 ccu3-webui daemon.info ntpd[238]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Dec 19 18:17:16 ccu3-webui daemon.info ntpd[238]: Listen normally on 2 lo 127.0.0.1:123
Dec 19 18:17:16 ccu3-webui daemon.info ntpd[238]: Listen normally on 3 eth0 192.168.178.131:123
Dec 19 18:17:16 ccu3-webui daemon.info ntpd[238]: Listen normally on 4 lo [::1]:123
Dec 19 18:17:16 ccu3-webui daemon.info ntpd[238]: Listening on routing socket on fd #21 for interface updates
Dec 19 18:17:16 ccu3-webui daemon.err xinetd[256]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Dec 19 18:17:16 ccu3-webui daemon.crit xinetd[256]: 256 {init_services} no services. Exiting...
Dec 19 18:17:18 ccu3-webui user.info root: Updating RF Lan Gateway Coprocessor Firmware
Dec 19 18:17:18 ccu3-webui user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Dec 19 18:17:18 ccu3-webui user.debug update-coprocessor: No updatable gateways found in rfd.conf file.
Dec 19 18:17:18 ccu3-webui user.info root: Updating RF Lan Gateway Firmware
Dec 19 18:17:18 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Dec 19 18:17:18 ccu3-webui user.info root: Updating Wired Lan Gateway Firmware
Dec 19 18:17:18 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Dec 19 18:17:18 ccu3-webui daemon.info snmpd[318]: Created directory: /var/lib/snmp
Dec 19 18:17:18 ccu3-webui daemon.info snmpd[318]: Created directory: /var/lib/snmp/cert_indexes
Dec 19 18:17:18 ccu3-webui daemon.info snmpd[318]: Created directory: /var/lib/snmp/mib_indexes
Dec 19 18:17:19 ccu3-webui daemon.info snmpd[318]: Turning on AgentX master support.
Dec 19 18:17:19 ccu3-webui daemon.err snmpd[318]: /etc/config/snmp/snmpd.conf: line 20: Error: Included file '/etc/config/snmp/snmpd-ccu3.conf' not found.
Dec 19 18:17:19 ccu3-webui daemon.info snmpd[320]: NET-SNMP version 5.7.3
Dec 19 18:17:42 ccu3-webui user.info kernel: [  156.213771] eq3loop: eq3loop_open_slave() mmd_hmip
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IseDOM::LoadOM: original file not exists, so try load new file. [iseDOM.cpp:2609]
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IseDOM::LoadOM: new file not exists, so try load bak file. [iseDOM.cpp:2621]
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IsePersist::LoadFromFile-> failed open file= /etc/config/homematic.regadom.bak [iseDOMpersist.cpp:78]
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IseObjectMap::Insert(202) failed! Already in map! [iseDOMobj.cpp:506]
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IseAddFavorite failed! ID=202 [iseDOM.cpp:644]
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IseObjectMap::Insert(203) failed! Already in map! [iseDOMobj.cpp:506]
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IseAddFavorite failed! ID=203 [iseDOM.cpp:644]
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IseObjectMap::Insert(204) failed! Already in map! [iseDOMobj.cpp:506]
Dec 19 18:17:53 ccu3-webui local0.err ReGaHss: Error: IseAddFavorite failed! ID=204 [iseDOM.cpp:644]
Dec 19 18:17:55 ccu3-webui user.info homematic: meine-homematic.de Versions - Upgrade auf 1.503
Dec 19 18:17:55 ccu3-webui user.info homematic: meine-homematic.de VPN Dienst und Autoupdate DEAKTIVIERT
Dec 19 18:25:34 ccu3-webui user.info firewall: has ip6 1


***** hmserver.log *****
Dec 19 18:17:29 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Dec 19 18:17:30 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
Dec 19 18:17:30 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
Dec 19 18:17:38 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_1 subtype=default 
Dec 19 18:17:38 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_2 subtype=default 
Dec 19 18:17:38 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_1 subtype=default 
Dec 19 18:17:38 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_2 subtype=default 
Dec 19 18:17:38 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_BUS_CONFIG_MISMATCH subtype=default 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 21 classes to Vert.x 
Dec 19 18:17:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 21 VertxDeployers initialized 
Dec 19 18:17:39 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of HMIPTRXWriterWorker succeeded (5c85cb62-8ac0-4ac6-9d6b-bb17869a79f1) 
Dec 19 18:17:39 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (62094125-bd59-4424-b47d-405dc589973f) 
Dec 19 18:17:39 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of TransactionSubsystemHandler succeeded (df9aab7e-02b1-4d83-9506-ab76ee5684c1) 
Dec 19 18:17:39 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Dec 19 18:17:39 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (74a1a42e-c8f2-486a-8eb3-f674df7b425d) 
Dec 19 18:17:39 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of KeyServerWorker succeeded (67e7878b-a50b-494d-9dea-6a8d16cae370) 
Dec 19 18:17:39 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (22279c9c-cf78-4705-9517-3b9427d3cac8) 
Dec 19 18:17:40 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: DeviceLiveUpdateSubsystem started 
Dec 19 18:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of CheckDeviceExistHandler succeeded (35b96ced-b45c-4af5-93d3-3ad2d6e5ba87) 
Dec 19 18:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of KryoPersistenceWorker succeeded (b3009e47-d312-43ee-b090-b81e2d64fdc3) 
Dec 19 18:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (c29af415-4382-4629-a087-966329c53d65) 
Dec 19 18:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (a8acb651-89dc-4504-afd5-4300a8d4370f) 
Dec 19 18:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerPersistentDataLoader succeeded (1bed01d7-4410-48dc-a84d-45ea0e661182) 
Dec 19 18:17:41 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Dec 19 18:17:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of FirmwareLoaderFileSystem succeeded (ca36abe6-1872-4683-b30e-23a233456766) 
Dec 19 18:17:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of IncomingHMIPFrameHandler succeeded (8568b5af-0b8f-4a18-a78f-5bc4c17e0fb2) 
Dec 19 18:17:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (c3af225a-b3db-4530-9383-b6c074cf303b) 
Dec 19 18:17:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyNotificationHandler succeeded (a30dce9a-014e-4438-856c-991918beba07) 
Dec 19 18:17:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of BackendCommandHandler succeeded (abdd7dda-eb52-49ff-9a2b-eeac509f948c) 
Dec 19 18:17:41 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [vert.x-eventloop-thread-1] SYSTEM: New random address (0xB8015E) was written to /etc/config/hmip_address.conf 
Dec 19 18:17:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded (4f8e0786-80e8-44d6-a7d3-9378f5a7c7b8) 
Dec 19 18:17:42 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyAPIWorker succeeded (51575c27-d062-46f4-a33d-19522ce3f4d8) 
Dec 19 18:17:42 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerAdapterInitialization succeeded (b4109af8-e064-4ee1-9d42-8b561899c689) 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12058974... 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D8A9918AE2 to 3 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 1.0 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 71680 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D8A9918AE2 initialized 
Dec 19 18:17:42 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Dec 19 18:17:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (949fc583-24d8-4535-a15c-6393ee4ef289) 
Dec 19 18:17:43 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-1] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware 
Dec 19 18:17:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyInitializion succeeded (f23398da-3f21-4a92-b63c-978a58dfb6fa) 
Dec 19 18:17:43 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Checking all devices on all accesspoints for updates 
Dec 19 18:17:43 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: There are 0 APs queued with updatable devices 
Dec 19 18:17:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Dec 19 18:17:44 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
Dec 19 18:17:45 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
Dec 19 18:17:45 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
Dec 19 18:17:45 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
Dec 19 18:17:45 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of BackendWorker succeeded (c4443c82-0dde-484d-8131-3e46a366a035) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (ee5af225-429b-4095-a385-4111c9490913) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of StorageRequestWorker succeeded (fca3b51c-a058-4d81-998f-bea4938fdb1c) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of EnergyPriceRequestWorker succeeded (ca667691-8468-4110-a466-27220394430f) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of RegaClientWorker succeeded (113872e8-1e63-4e00-a0ba-53c64e317345) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CouplingRequestWorker succeeded (4834bef7-94b4-4c01-ac7d-29b378c6ff61) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DiagramRequestWorker succeeded (8bab153d-41cb-4fb7-bc73-9900bb1d084c) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of GroupRequestWorker succeeded (8b9ce17e-86ac-4385-8fab-9dc5cfefe963) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (ef8fde22-6231-439a-ae27-e4dd07c54ed7) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (2e1701df-fa18-4730-af55-a6d822ad41ae) 
Dec 19 18:17:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
Dec 19 18:17:45 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
Dec 19 18:17:45 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
Dec 19 18:17:46 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
Dec 19 18:17:46 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
Dec 19 18:17:48 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler 
Dec 19 18:17:49 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing... 
Dec 19 18:17:49 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Dec 19 18:17:49 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Dec 19 18:17:49 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device 
Dec 19 18:17:49 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge 
Dec 19 18:17:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging 
Dec 19 18:17:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService 
Dec 19 18:17:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService 
Dec 19 18:17:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server 
Dec 19 18:17:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler 
Dec 19 18:17:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler 
Dec 19 18:17:51 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 
Dec 19 18:17:51 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished 
Dec 19 18:17:51 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: HmIP-RF_java 
Dec 19 18:17:52 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done 
Dec 19 18:18:00 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-3] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999 
Dec 19 18:18:00 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-3] Added InterfaceId: 1008 
Dec 19 18:18:00 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-11] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Dec 19 18:18:10 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 
Dec 19 18:18:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-1] Added InterfaceId: 1009 
Dec 19 18:18:10 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished 
Dec 19 18:22:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 18:22:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 18:22:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 18:27:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 18:27:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 18:27:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 18:32:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 18:32:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 18:32:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 18:37:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 18:37:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 18:37:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 18:42:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 18:42:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 18:42:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 18:47:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 18:47:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 18:47:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 18:52:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 18:52:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 18:52:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 18:57:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 18:57:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 18:57:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 19:02:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 19:02:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 19:02:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 19 19:07:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
Dec 19 19:07:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 19 19:07:40 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used
wenn man sich das log file genauer ansieht findet man das:

Code: Alles auswählen

Dec 19 18:17:18 ccu3-webui user.info root: Updating RF Lan Gateway Coprocessor Firmware
Dec 19 18:17:18 ccu3-webui user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Dec 19 18:17:18 ccu3-webui user.debug update-coprocessor: No updatable gateways found in rfd.conf file.
Dec 19 18:17:18 ccu3-webui user.info root: Updating RF Lan Gateway Firmware
Dec 19 18:17:18 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Dec 19 18:17:18 ccu3-webui user.info root: Updating Wired Lan Gateway Firmware
Dec 19 18:17:18 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
jedocht bringt mich das auch nicht weiter - ist das normal?
Hat jemand ahnung woran das liegen könnte? Habe den adapter davor auch schon mit rasberrymatic auf nem RP1 probiert ohne erfolg -_-
Danke!
Zuletzt geändert von enttom am 19.12.2018, 20:21, insgesamt 1-mal geändert.
Nach oben
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:
Kontaktdaten von deimos

Re: HM-MOD-RPI-PC pivccu kein anlernen möglich

Beitrag von deimos » 19.12.2018, 19:58

Hi,

Du kannst den an drei verschiedenen Systemen nicht anlernen, da fallen mir jetzt drei mögliche Sachen ein:

- Gerät defekt
- Gerät nicht korrekt resettet
- eigener Sicherheitsschlüssel vergeben

Viele Grüße
Alex
Nach oben
mczeus
Beiträge: 41
Registriert: 14.01.2019, 20:56
Hat sich bedankt: 4 Mal
Danksagung erhalten: 1 Mal

Re: HM-MOD-RPI-PC pivccu kein anlernen möglich

Beitrag von mczeus » 14.01.2019, 21:10

Hi,

Habe ein All_In_One auf einer Raspberry pi installiert, läuft auch soweit. Habe mir nun ein Atmega mit cc1101 sensor gebaut der auch läuft wie man im serial monitor sieht.
anlernen fehler.jpg
anlernen
habe in der ccu als zusatzsoftware
zusatzsoftware.jpg
zusatz
installiert.
Ich kann den Sensor aber nicht anlernen also ich bekomme keinen Posteingang mit neuem Gerät.

Hier mal noch ne log aus der CCU
homematic-ccu2-2019-01-14-2.log
ccu log
(354.77 KiB) 56-mal heruntergeladen
was mache ich falsch oder was fehlt mir noch?

wäre für jede Hilfe sehr dankbar
Nach oben
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:
Kontaktdaten von deimos

Re: HM-MOD-RPI-PC pivccu kein anlernen möglich

Beitrag von deimos » 15.01.2019, 13:35

Hi,

das hat nichts mit piVCCU zu tun, sondern in irgendeiner Form mit dem Selbstbaugerät, es wäre daher sinnvoller im richtigen Unterforum zu fragen.

Im Log sieht man gut, dass der Anlernversuch bei der CCU ankommt, diese auch antwortet, auf den initialen Config Befehl aber keine Antwort bekommt und daher das Pairing abbricht:

Code: Alles auswählen

Jan 14 20:35:18 homematic-ccu2 user.debug multimac: C<: #111 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 6A 60 15 00 1A 00 00 05 00 00 00 00 00
Jan 14 20:35:18 homematic-ccu2 user.debug multimac: C< @1156699: bin:FD 00 16 03 6F 06 80 00 80 01 A0 01 6A 60 15 00 1A 00 00 05 00 00 00 00 00 EA 60
Jan 14 20:35:18 homematic-ccu2 user.debug multimac: C> @1156728: #111 LLMAC Response ACK @4244: 10 94
Jan 14 20:35:18 homematic-ccu2 user.debug multimac: _txState = TxState_WaitAck
Jan 14 20:35:18 homematic-ccu2 user.debug multimac: No ACK for Bidcos TX: #01[BiDi|Ren] 6A6015->001A00 Configuration: 00 05 00 00 00 00 00
Jan 14 20:35:18 homematic-ccu2 user.info multimac: No ACK received after 3 repetitions: #01[BiDi|Ren] 6A6015->001A00 Configuration: 00 05 00 00 00 00 00
Jan 14 20:35:18 homematic-ccu2 user.debug multimac: A<: #28 HmBidcos Response 04
Jan 14 20:35:18 homematic-ccu2 user.debug multimac: _txState = TxState_Idle
Jan 14 20:35:18 homematic-ccu2 user.debug rfd: (PEQ0531387) Response status: Send failed.
Jan 14 20:35:18 homematic-ccu2 user.debug rfd: SendFrame failed 1 times:  @1306291079 0x6A6015 -> 0x001A00 CONFIG_START [PEQ0531387]:   CNT=1,RPTEN=1,RPTED=0,BIDI=1,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=0,TYPE=0x01   CONFIG_CHANNEL = 0   CONFIG_PEER_ADDRESS = 0x000000   CONFIG_PEE
Jan 14 20:35:18 homematic-ccu2 user.warn rfd: Peering with HMRC001A00 failed
Viele Grüße
Alex
Nach oben
Antworten

Zurück zu „piVCCU“