Seite drucken - HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen

Titel: HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: lewej am 30 Januar 2020, 20:12:11

Hallo zusammen,

ich versuche einen HM-SEC-MDIR-2 von meinem homematic Stick abzulernen, leider funktioniert es und ich weiß nicht warum.
Ich habe bereits folgendes probiert:

Code Auswählen

 CUL_HM set HM_3E355B reset
2020.01.30 20:03:16.763 5: CUL_HM HM_3E355B protEvent:CMDs_pending pending:2
2020.01.30 20:03:16.763 5: CUL_HM HM_3E355B protEvent:CMDs_pending pending:3
2020.01.30 20:03:16.763 5: CUL_HM HM_3E355B protEvent:CMDs_pending pending:4
2020.01.30 20:03:16.764 3: CUL_HM set HM_3E355B unpair
2020.01.30 20:03:42.528 5: CUL_HM HM_3E355B protEvent:CMDs_pending pending:5
2020.01.30 20:03:42.528 5: CUL_HM HM_3E355B protEvent:CMDs_pending pending:6
2020.01.30 20:03:42.528 5: CUL_HM HM_3E355B protEvent:CMDs_pending pending:7
2020.01.30 20:03:42.528 3: CUL_HM set HM_3E355B getConfig
2020.01.30 20:03:42.624 5: CUL_HM HM_3E355B protEvent:CMDs_processing... pending:6

==> /opt/fhem/log/HM_3E355B-2020.log <==
2020-01-30_20:03:42 HM_3E355B battery: ok
2020-01-30_20:03:42 HM_3E355B brightness: 38
2020-01-30_20:03:42 HM_3E355B sabotageError: off

==> /opt/fhem/log/fhem-2020-01.log <==
2020.01.30 20:03:42.908 4: CUL_HM HM_3E355B dupe: dont process
2020.01.30 20:03:48.196 4: CUL_HM_Resend: HM_3E355B nr 2
2020.01.30 20:03:48.196 5: CUL_HM HM_3E355B protEvent:CMDs_pending pending:7

==> /opt/fhem/log/HM_3E355B-2020.log <==
2020-01-30_20:05:44 HM_3E355B motion: off
2020-01-30_20:05:44 HM_3E355B motionDuration: 242
2020-01-30_20:05:44 HM_3E355B noMotion

Code Auswählen

Internals:
   DEF        3E355B
   FUUID      5e32c420-f33f-daf7-6f34-5f48db4448c598b8
   HMLAN1_MSGCNT 339
   HMLAN1_RAWMSG E3E355B,0000,01483C34,FF,FFC6,70A6103E355B00FFFF06012600
   HMLAN1_RSSI -58
   HMLAN1_TIME 2020-01-30 20:03:42
   IODev      HMLAN1
   LASTInputDev HMLAN1
   MSGCNT     339
   NAME       HM_3E355B
   NOTIFYDEV  global
   NR         1199
   NTFY_ORDER 50-HM_3E355B
   STATE      set_reset
   TYPE       CUL_HM
   chanNo     01
   lastMsg    No:70 - t:10 s:3E355B d:00FFFF 06012600
   protCmdDel 40
   protCmdPend 6 CMDs pending
   protErrIoAttack 58 last_at:2020-01-30 14:08:49
   protErrIoId_00FFFF 58 last_at:2020-01-30 14:08:49
   protLastRcv 2020-01-30 20:03:42
   protRcv    115 last_at:2020-01-30 20:03:42
   protResnd  10 last_at:2020-01-30 20:03:48
   protResndFail 3 last_at:2020-01-30 14:22:02
   protSnd    13 last_at:2020-01-30 20:03:42
   protState  CMDs_pending
   rssi_at_HMLAN1 cnt:316 min:-81 max:-48 avg:-60.99 lst:-58 
   READINGS:
     2020-01-30 14:18:38   Activity        alive
     2020-01-30 14:18:38   D-firmware      1.6
     2020-01-30 14:18:38   D-serialNr      SEARIALGELOESCHT
     2020-01-30 13:00:08   R-pairCentral   set_0x000000
     2020-01-30 20:03:42   battery         ok
     2020-01-30 20:03:42   brightness      38
     2020-01-30 20:01:42   motion          on (to 00FFFF)
     2020-01-30 20:01:42   motionCount     31_next:240s
     2020-01-30 20:00:18   motionDuration  242
     2020-01-30 12:55:12   powerOn         2020-01-30 12:55:12
     2020-01-30 20:03:42   recentStateType info
     2020-01-30 14:09:37   sabotageAttackId_ErrIoId_00FFFF  cnt:58
     2020-01-30 14:09:37   sabotageAttack_ErrIoAttack cnt 58
     2020-01-30 20:03:42   sabotageError   off
     2020-01-30 20:02:26   state           set_reset
     2020-01-30 20:01:42   trigDst_00FFFF  noConfig
     2020-01-30 20:01:42   trigger_cnt     31
   cmdStack:
     ++A011137ADF3E355B0400
     ++A001137ADF3E355B00050000000000
     ++A001137ADF3E355B00080A000B000C00
     ++A001137ADF3E355B0006
     ++A001137ADF3E355B00040000000000
     ++A001137ADF3E355B01040000000001
     ++A001137ADF3E355B0103
   helper:
     HM_CMDNR   113
     cSnd       01137ADF3E355B00050000000000,11137ADF3E355B0400
     getCfgList all
     getCfgListNo ,4
     mId        004A
     moStart    1580410902.23968
     peerFriend peerAct,peerVirt
     peerOpt    4:motionDetector
     regLst     0,1,4p
     rxType     28
     supp_Pair_Rep 0
     expert:
       def        1
       det        0
       raw        1
       tpl        0
     io:
       newChn     +3E355B,02,00,00
       nextSend   1580411023.00776
       prefIO     
       rxt        2
       vccu       
       p:
         3E355B
         00
         00
         00
     mRssi:
       mNo        70
       io:
         HMLAN1:
           -52
           -52
     prt:
       bErr       0
       sProc      2
       sleeping   0
       wuReSent   2
     q:
       qReqConf   
       qReqStat   
     role:
       chn        1
       dev        1
     rssi:
       at_HMLAN1:
         avg        -60.9968354430379
         cnt        316
         lst        -58
         max        -48
         min        -81
     shadowReg:
       RegL_00.    0A:00 0B:00 0C:00
Attributes:
   IODev      HMLAN1
   actCycle   000:20
   actStatus  alive
   autoReadReg 4_reqStatus
   expert     2_raw
   firmware   1.6
   model      HM-SEC-MDIR-2
   room       CUL_HM
   serialNr   SEARIALGELOESCHT
   subType    motionDetector
   verbose    5

Hat jemand eine Idee warum das nicht funktioniert?

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: frank am 30 Januar 2020, 20:30:18

wieso meinst du, dass es nicht funktioniert hat?

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: lewej am 30 Januar 2020, 20:54:42

Ich bekomme das Teil an der neuen CCU3 Raspberrymatic nicht angelernt. An dem Stick mit fhem, lässt sich das Teil immer wieder verbinden.

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: frank am 30 Januar 2020, 21:45:12

ZitatIch bekomme das Teil an der neuen CCU3 Raspberrymatic nicht angelernt.

1. was sagt die ccu?

2. zeig mal ein vollständiges list ohne manuelle veränderungen, wenn das device in fhem wieder angelernt ist.

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: lewej am 31 Januar 2020, 10:55:08

Hi,

Die CCU loggt nicht wirklich, hab schon in der CCU auf Levellog alles gestellt und unter /var/log/hmserver.log wird nichts dazu geloggt. Oder gibt es noch eine andere Datei.

Im ersten Thread ist das List vollständig , ich habe nur die Seriennummer editiert, alles andere ist orginal list output.

Oder welches Log wird noch benötigt?

Gruss

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: frank am 31 Januar 2020, 12:46:18

ich wollte kein log, sondern von dir die info, woran du erkennst, dass die ccu nicht pairen will oder kann.
wie äussert sich das nicht pairen können?

das erste list ist bereits nach dem reset.

ein reset über knöpfchen drücken geht immer, wenn das device keinen eigenen aes key von dir bekommen hat.
ich sehe jedenfals keine aes hinweise. das würde die ccu sicher auch anmeckern.

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: lewej am 01 Februar 2020, 14:52:41

Also das reseten scheint wohl geklappt zu haben. Jedoch bekomme ich den nicht angelernt.
Hat jemand eine IDee?

Code Auswählen

Device firmware version is 1.6
Feb  1 14:51:33 homematic-raspi user.debug rfd: TX:  @17128604 0x00FFFF -> 0x3E355B CONFIG_START [PEQ0627013]:   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_PEER_CHANNEL = 0   CONFIG_PARAM_LIST = 0
Feb  1 14:51:33 homematic-raspi user.debug multimac: A>: #201 HmBidcos TxTelegram [] #01[BiDi|Ren] 00FFFF->3E355B Configuration: 00 05 00 00 00 00 00
Feb  1 14:51:33 homematic-raspi user.debug multimac: SubsystemBidcos::ProcessTxQueue() size=1
Feb  1 14:51:33 homematic-raspi user.debug multimac: MacController::OnDownstreamFrame(#255 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00)
Feb  1 14:51:33 homematic-raspi user.debug multimac: _txState = TxState_WaitCoproResponse
Feb  1 14:51:33 homematic-raspi user.debug multimac: C<: #66 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00
Feb  1 14:51:33 homematic-raspi user.debug multimac: C< @175585677: bin:FD 00 16 03 42 06 80 00 80 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00 32 2D
Feb  1 14:51:33 homematic-raspi user.debug multimac: C> @175585708: #66 LLMAC Response ACK @30924: 78 CC
Feb  1 14:51:33 homematic-raspi user.debug multimac: _txState = TxState_WaitAck
Feb  1 14:51:33 homematic-raspi user.debug multimac: No ACK for Bidcos TX: #01[BiDi|Ren] 00FFFF->3E355B Configuration: 00 05 00 00 00 00 00
Feb  1 14:51:33 homematic-raspi user.debug multimac: MacController::OnDownstreamFrame(#255 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00)
Feb  1 14:51:33 homematic-raspi user.debug multimac: _txState = TxState_WaitCoproResponse
Feb  1 14:51:33 homematic-raspi user.debug multimac: C<: #67 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00
Feb  1 14:51:33 homematic-raspi user.debug multimac: C< @175585959: bin:FD 00 16 03 43 06 80 00 80 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00 CB 3E
Feb  1 14:51:33 homematic-raspi user.debug multimac: C> @175585990: #67 LLMAC Response ACK @31206: 79 E6
Feb  1 14:51:33 homematic-raspi user.debug multimac: _txState = TxState_WaitAck
Feb  1 14:51:34 homematic-raspi user.debug multimac: No ACK for Bidcos TX: #01[BiDi|Ren] 00FFFF->3E355B Configuration: 00 05 00 00 00 00 00
Feb  1 14:51:34 homematic-raspi user.debug multimac: MacController::OnDownstreamFrame(#255 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00)
Feb  1 14:51:34 homematic-raspi user.debug multimac: _txState = TxState_WaitCoproResponse
Feb  1 14:51:34 homematic-raspi user.debug multimac: C<: #68 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00
Feb  1 14:51:34 homematic-raspi user.debug multimac: C< @175586241: bin:FD 00 16 03 44 06 80 00 80 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00 A4 48
Feb  1 14:51:34 homematic-raspi user.debug multimac: C> @175586272: #68 LLMAC Response ACK @31488: 7B 00
Feb  1 14:51:34 homematic-raspi user.debug multimac: _txState = TxState_WaitAck
Feb  1 14:51:34 homematic-raspi user.debug multimac: No ACK for Bidcos TX: #01[BiDi|Ren] 00FFFF->3E355B Configuration: 00 05 00 00 00 00 00
Feb  1 14:51:34 homematic-raspi user.debug multimac: MacController::OnDownstreamFrame(#255 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00)
Feb  1 14:51:34 homematic-raspi user.debug multimac: _txState = TxState_WaitCoproResponse
Feb  1 14:51:34 homematic-raspi user.debug multimac: C<: #69 LLMAC TX @32768ms [10k,NoCCA] 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00
Feb  1 14:51:34 homematic-raspi user.debug multimac: C< @175586523: bin:FD 00 16 03 45 06 80 00 80 01 A0 01 00 FF FF 3E 35 5B 00 05 00 00 00 00 00 5D 5B
Feb  1 14:51:34 homematic-raspi user.debug multimac: C> @175586553: #69 LLMAC Response ACK @31769: 7C 19
Feb  1 14:51:34 homematic-raspi user.debug multimac: _txState = TxState_WaitAck
Feb  1 14:51:34 homematic-raspi user.debug multimac: No ACK for Bidcos TX: #01[BiDi|Ren] 00FFFF->3E355B Configuration: 00 05 00 00 00 00 00
Feb  1 14:51:34 homematic-raspi user.info multimac: No ACK received after 3 repetitions: #01[BiDi|Ren] 00FFFF->3E355B Configuration: 00 05 00 00 00 00 00
Feb  1 14:51:34 homematic-raspi user.debug multimac: A<: #201 HmBidcos Response 04
Feb  1 14:51:34 homematic-raspi user.debug multimac: _txState = TxState_Idle
Feb  1 14:51:34 homematic-raspi user.debug rfd: (PEQ0627013) Response status: Send failed.
Feb  1 14:51:34 homematic-raspi user.debug rfd: SendFrame failed 1 times:  @17128604 0x00FFFF -> 0x3E355B CONFIG_START [PEQ0627013]:   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_PEER_CHANNEL = 0   CONFIG_PARAM_LIST = 0
Feb  1 14:51:34 homematic-raspi user.warn rfd: Peering with MEQ0688603 failed
Feb  1 14:51:34 homematic-raspi user.debug multimac: A>: #202 HmBidcos PeerRemove 3E355B
Feb  1 14:51:34 homematic-raspi user.debug multimac: A<: #202 HmBidcos Response 07 00 01 00 01
Feb  1 14:51:34 homematic-raspi user.debug rfd: (PEQ0627013) Response status: OK, Data.
Feb  1 14:51:34 homematic-raspi user.debug rfd: Deleting persistent data for device MEQ0688603
Feb  1 14:51:37 homematic-raspi user.debug multimac: C<: #70 TRX GetDutyCycle
Feb  1 14:51:37 homematic-raspi user.debug multimac: C< @175589981: bin:FD 00 03 01 46 03 0C 1B
Feb  1 14:51:37 homematic-raspi user.debug multimac: C> @175590085: #70 TRX Response Ack 11
Feb  1 14:51:37 homematic-raspi user.debug multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 8.0, 8.5 ) = 0

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: frank am 01 Februar 2020, 15:11:04

du drückst wahrscheinlich nicht das knöpfchen vom mdir, da er sich nicht meldet.
steht doch sicherlich alles in der bedienungsanleitung.

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: lewej am 01 Februar 2020, 15:14:18

Den Knopf drücke. Auch den Werksreset habe ich gefühlte 100mal probiert.

Titel: Antw:HM-SEC-MDIR-2 lässt sich nicht reseten und auch nicht unpairen
Beitrag von: lewej am 01 Februar 2020, 15:18:41

Ein erneuter Verbindungsversuch scheitert:

Code Auswählen


Feb  1 15:16:45 homematic-raspi local0.err ReGaHss: ERROR: ScriptRuntimeError: string channels = "";string timestamps = ""; [ExecError():iseESPexec.cpp:12798]
Feb  1 15:16:46 homematic-raspi user.debug rfd: TX:  @18641738 0x00FFFF -> 0x3E355B Generic [PEQ0627013]:   CNT=40,RPTEN=1,RPTED=0,BIDI=1,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=0,TYPE=0x11   DATA = 04 00
Feb  1 15:16:47 homematic-raspi user.debug rfd: (PEQ0627013) Response status: Send failed.
Feb  1 15:16:47 homematic-raspi user.debug rfd: SendFrame failed 1 times:  @18641739 0x00FFFF -> 0x3E355B Generic [PEQ0627013]:   CNT=40,RPTEN=1,RPTED=0,BIDI=1,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=0,TYPE=0x11   DATA = 04 00
Feb  1 15:16:48 homematic-raspi local0.err ReGaHss: ERROR: ScriptRuntimeError: string channels = "";string timestamps = ""; [ExecError():iseESPexec.cpp:12798]
Feb  1 15:16:51 homematic-raspi local0.err ReGaHss: ERROR: ScriptRuntimeError: string channels = "";string timestamps = ""; [ExecError():iseESPexec.cpp:12798]
Feb  1 15:16:52 homematic-raspi user.debug rfd: TX:  @18647137 0x00FFFF -> 0x3E355B Generic [PEQ0627013]:   CNT=41,RPTEN=1,RPTED=0,BIDI=1,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=0,TYPE=0x11   DATA = 04 00
Feb  1 15:16:53 homematic-raspi user.debug rfd: (PEQ0627013) Response status: Send failed.
Feb  1 15:16:53 homematic-raspi user.debug rfd: SendFrame failed 1 times:  @18647137 0x00FFFF -> 0x3E355B Generic [PEQ0627013]:   CNT=41,RPTEN=1,RPTED=0,BIDI=1,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=0,TYPE=0x11   DATA = 04 00
Feb  1 15:16:53 homematic-raspi user.debug rfd: (PEQ0627013) Response status: OK, Data.
Feb  1 15:16:53 homematic-raspi user.debug rfd: Deleting persistent data for device MEQ0688603
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:1","MOTION",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:1","MOTION",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1652 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:1","INSTALL_TEST",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:1","INSTALL_TEST",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1651 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:1","ERROR",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:1","ERROR",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1629 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:1","BRIGHTNESS",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:1","BRIGHTNESS",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1628 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","UPDATE_PENDING",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","UPDATE_PENDING",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1623 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","UNREACH",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","UNREACH",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1619 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","STICKY_UNREACH",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","STICKY_UNREACH",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1615 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","RSSI_PEER",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","RSSI_PEER",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1614 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","RSSI_DEVICE",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","RSSI_DEVICE",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1613 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","LOWBAT",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","LOWBAT",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1609 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","ENTER_BOOTLOADER",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","ENTER_BOOTLOADER",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1608 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","DEVICE_IN_BOOTLOADER",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","DEVICE_IN_BOOTLOADER",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1604 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","CONFIG_PENDING",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","CONFIG_PENDING",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1600 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'reportValueUsage': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"MEQ0688603:0","AES_KEY",0}, result: [faultCode:-2,faultString:"Unknown instance"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'reportValueUsage' call failed (interface: 1007, params: {"MEQ0688603:0","AES_KEY",0}) [CallReportValueUsage():iseXmlRpc.cpp:1676]
Feb  1 15:16:53 homematic-raspi local0.err ReGaHss: ERROR: rpc.CallReportValueUsage failed dp id = 1599 [RemoveDPFromCollections():iseManageDP.cpp:439]
Feb  1 15:16:53 homematic-raspi user.debug hm_deldev: event fired (delete MEQ0688603)
Feb  1 15:17:05 homematic-raspi user.debug rfd: Entering install mode for 60 s
Feb  1 15:17:08 homematic-raspi user.debug rfd: MEQ0688603's type is HM-Sec-MDIR-2
Feb  1 15:17:08 homematic-raspi user.debug rfd: (PEQ0627013) Response status: OK, Data.
Feb  1 15:17:08 homematic-raspi user.debug rfd: (PEQ0627013) Response status: OK.
Feb  1 15:17:08 homematic-raspi user.debug rfd: (PEQ0627013) Response status: OK, Data.
Feb  1 15:17:08 homematic-raspi user.debug rfd: (PEQ0627013) Response status: OK.
Feb  1 15:17:08 homematic-raspi user.debug rfd: Device firmware version is 1.6
Feb  1 15:17:08 homematic-raspi user.debug rfd: TX:  @18663218 0x00FFFF -> 0x3E355B CONFIG_START [PEQ0627013]:   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_PEER_CHANNEL = 0   CONFIG_PARAM_LIST = 0
Feb  1 15:17:09 homematic-raspi user.debug rfd: (PEQ0627013) Response status: Send failed.
Feb  1 15:17:09 homematic-raspi user.debug rfd: SendFrame failed 1 times:  @18663218 0x00FFFF -> 0x3E355B CONFIG_START [PEQ0627013]:   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_PEER_CHANNEL = 0   CONFIG_PARAM_LIST = 0
Feb  1 15:17:09 homematic-raspi user.warn rfd: Peering with MEQ0688603 failed
Feb  1 15:17:09 homematic-raspi user.debug rfd: (PEQ0627013) Response status: OK, Data.
Feb  1 15:17:09 homematic-raspi user.debug rfd: Deleting persistent data for device MEQ0688603

FHEM Forum

FHEM - Hausautomations-Systeme => Homematic => Thema gestartet von: lewej am 30 Januar 2020, 20:12:11