Moin,
ich habe gesetern einen HM-SEC-SCo in Betrieb genommen und mit meiner vccu gepaired. Seit dem habe ich im Log (dbLog) periodische Close-Events, obwohl der Sensor nicht ausgelöst hat. Im log der DB diehst das so aus:
2019-02-04 00:36:38 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 00:36:39 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 00:36:40 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 00:36:42 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 01:30:33 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 01:30:34 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 01:30:35 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 01:30:36 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 01:30:37 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 02:32:16 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 02:32:18 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 02:32:19 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 02:32:21 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 03:25:14 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 03:25:15 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 03:25:17 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 03:25:18 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 04:21:49 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 04:21:51 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 04:21:52 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 04:21:53 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 05:22:34 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 05:22:36 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 05:22:37 Tuerkontakt_Haustuer CUL_HM state: closed state closed
2019-02-04 05:22:38 Tuerkontakt_Haustuer CUL_HM state: closed state closed
Diese Events triggern dann auch ein paar Notifies, welches auf das Close-Event reagieren. Das List des Devices sieht aktuell so aus:
list Tuerkontakt_Haustuer
Internals:
.triggerUsed 1
DEF 613629
FUUID 5c572f46-f33f-437e-4d3f-9b0ef13373689a6d
HMLAN1_MSGCNT 128
HMLAN1_RAWMSG E613629,0000,08070442,FF,FFC1,E8A61061362929A07E06010000
HMLAN1_RSSI -63
HMLAN1_TIME 2019-02-04 05:22:38
IODev RM_HmUART_EG
LASTInputDev HMLAN1
MSGCNT 261
NAME Tuerkontakt_Haustuer
NOTIFYDEV global
NR 5041
RM_HmUART_EG_MSGCNT 133
RM_HmUART_EG_RAWMSG 05010145E8A61061362929A07E06010000
RM_HmUART_EG_RSSI -69
RM_HmUART_EG_TIME 2019-02-04 05:22:38
STATE closed
TYPE CUL_HM
lastMsg No:E8 - t:10 s:613629 d:29A07E 06010000
peerList Heizung_Flur_EG_WindowRec,
protCmdDel 5
protEvt_AESCom-ok 7 last_at:2019-02-03 19:34:35
protLastRcv 2019-02-04 05:22:38
protNack 3 last_at:2019-02-03 19:23:17
protRcv 129 last_at:2019-02-04 05:22:38
protRcvB 19 last_at:2019-02-03 19:39:38
protResnd 1 last_at:2019-02-03 19:13:42
protSnd 113 last_at:2019-02-04 05:22:38
protState CMDs_done
rssi_at_HMLAN1 cnt:128 min:-77 max:-44 avg:-56.69 lst:-63
rssi_at_RM_HmUART_EG cnt:126 min:-79 max:-45 avg:-66.19 lst:-69
.attraggr:
.attrminint:
Helper:
DBLOG:
Activity:
sensorsDblog:
TIME 1549218872.34254
VALUE alive
D-firmware:
sensorsDblog:
TIME 1549218872.34254
VALUE 1.0
D-serialNr:
sensorsDblog:
TIME 1549218872.34254
VALUE OEQ1555807
R-Heizung_Flur_EG_WindowRec-expectAES:
sensorsDblog:
TIME 1549218876.88043
VALUE off
R-Heizung_Flur_EG_WindowRec-peerNeedsBurst:
sensorsDblog:
TIME 1549218876.88043
VALUE on
R-eventDlyTime:
sensorsDblog:
TIME 1549218876.0245
VALUE 0 s
R-sign:
sensorsDblog:
TIME 1549218876.0245
VALUE on
aesCommToDev:
sensorsDblog:
TIME 1549218875.34115
VALUE ok
aesKeyNbr:
sensorsDblog:
TIME 1549218875.31551
VALUE 00
alive:
sensorsDblog:
TIME 1549254158.62066
VALUE yes
battery:
sensorsDblog:
TIME 1549254158.62066
VALUE ok
contact:
sensorsDblog:
TIME 1549254158.62066
VALUE closed (to vccu)
powerOn:
sensorsDblog:
TIME 1549218164.53228
VALUE 2019-02-03 19:22:44
sabotageError:
sensorsDblog:
TIME 1549254158.62066
VALUE off
state:
sensorsDblog:
TIME 1549254158.62066
VALUE closed
trigger_cnt:
sensorsDblog:
TIME 1549219179.37624
VALUE 32
READINGS:
2019-02-03 19:34:32 .D-devInfo 810101
2019-02-03 19:34:32 .D-stc 80
2019-02-03 19:34:36 .R-msgScPosA open
2019-02-03 19:34:36 .R-msgScPosB closed
2019-02-03 19:13:43 .R-transmDevTryMax 6
2019-02-03 19:34:36 .R-transmitTryMax 6
2019-02-03 19:34:36 .peerListRDate 2019-02-03 19:34:36
2019-02-04 05:22:38 .protLastRcv 2019-02-04 05:22:38
2019-02-03 19:34:32 Activity alive
2019-02-03 19:34:35 CommandAccepted yes
2019-02-03 19:34:32 D-firmware 1.0
2019-02-03 19:34:32 D-serialNr OEQ1555807
2019-02-03 19:34:35 PairedTo 0x29A07E
2019-02-03 19:34:36 R-Heizung_Flur_EG_WindowRec-expectAES off
2019-02-03 19:34:36 R-Heizung_Flur_EG_WindowRec-peerNeedsBurst on
2019-02-03 19:13:43 R-cyclicInfoMsg on
2019-02-03 19:34:36 R-eventDlyTime 0 s
2019-02-03 19:13:43 R-pairCentral 0x29A07E
2019-02-03 19:13:43 R-sabotageMsg on
2019-02-03 19:34:36 R-sign on
2019-02-03 19:34:35 RegL_00. 00:00 02:01 09:01 0A:29 0B:A0 0C:7E 10:01 14:06
2019-02-03 19:34:36 RegL_01. 00:00 08:01 20:9C 21:00 30:06
2019-02-03 19:34:36 RegL_04.Heizung_Flur_EG_WindowRec 00:00 01:01
2019-02-03 19:34:35 aesCommToDev ok
2019-02-03 19:34:35 aesKeyNbr 00
2019-02-04 05:22:38 alive yes
2019-02-04 05:22:38 battery ok
2019-02-04 05:22:38 contact closed (to vccu)
2019-02-03 19:34:36 peerList Heizung_Flur_EG_WindowRec,
2019-02-03 19:22:44 powerOn 2019-02-03 19:22:44
2019-02-04 05:22:38 recentStateType info
2019-02-04 05:22:38 sabotageError off
2019-02-04 05:22:38 state closed
2019-02-03 19:39:39 trigger_cnt 32
helper:
HM_CMDNR 232
PONtest 0
cSnd 0129A07E6136290103,0129A07E61362901042E7B4E0304
mId 00C7
peerIDsRaw ,2E7B4E03,00000000
regLst ,0,1,4p
rxType 28
supp_Pair_Rep 0
ack:
expert:
def 1
det 0
raw 1
tpl 0
io:
newCh 1
newChn +613629,00,02,00
nextSend 1549254158.82657
prefIO
rxt 2
vccu
p:
613629
00
02
00
mRssi:
mNo E8
io:
HMLAN1:
-63
-63
RM_HmUART_EG:
-65
-65
prt:
bErr 0
sProc 0
sleeping 0
rspWait:
q:
qReqConf
qReqStat
regCollect:
role:
chn 1
dev 1
rpt:
IO RM_HmUART_EG
flg A
ts 1549254158.53141
ack:
HASH(0x5569940c0920)
E8800229A07E61362900
rssi:
at_HMLAN1:
avg -56.6953125
cnt 128
lst -63
max -44
min -77
at_RM_HmUART_EG:
avg -66.1904761904762
cnt 126
lst -69
max -45
min -79
shadowReg:
RegL_04.Heizung_Flur_EG_WindowRec 00:00 01:01
tmpl:
Attributes:
IODev RM_HmUART_EG
IOgrp vccu:RM_HmUART_EG
actCycle 002:50
actStatus alive
alias Haustür
autoReadReg 4_reqStatus
devStateIcon closed:fts_door@blue open:fts_door_open@red
expert 2_raw
firmware 1.0
group Sensoren
model HM-SEC-SCo
peerIDs 00000000,2E7B4E03,
room Flur EG
serialNr OEQ1555807
subType threeStateSensor
Hat jemand eine Idee, was das sein könnte?
Gruß,
budy
Moin,
ehrlich gesagt sehen die Events komisch aus, zweimal state closed hintereinander habe ich noch nicht gesehen.
Solange Du event-on-change-reading nicht gesetzt hast, ist es normal, dass immer mal (aber nicht jede Minute) ein Feuer an Events kommt. Aber ein solcher Event ist bei mir nicht dabei!
Da hast Du irgendwas anderes gemacht. :o
Gruß Otto
Moin Otto,
stimmt... ich hatte event-on-change-reading noch nicht gesetzt...
Danke,
budy