Hallo,
über daas Verhalten der Keymatic haben schon andere berichtet und die Lösung hieß dann:
"event-on-change-reading auf .*" setzen.
Das führt bei mir leider nicht zum gewünschtem Ergebnis!
Hier mal das List meines Keymatic-Devices:
Internals:
.triggerUsed 1
DEF 23D8F6
HMLAN1_MSGCNT 101
HMLAN1_RAWMSG R99C71FD9,0021,3D62A179,01,FFBD,CC800223D8F6123ABC01010100403009D1E3
HMLAN1_RSSI -67
HMLAN1_TIME 2016-03-21 16:24:37
IODev HMLAN1
LASTInputDev hmusb
MSGCNT 184
NAME EG.FL.KEYM
NR 339
NTFY_ORDER 50-EG.FL.KEYM
STATE unlocked
TYPE CUL_HM
hmusb_MSGCNT 83
hmusb_RAWMSG E23D8F6,0000,2DC0BE3E,FF,FFD5,CC800223D8F6123ABC01010100403009D1E3
hmusb_RSSI -43
hmusb_TIME 2016-03-21 16:24:37
lastMsg No:CC - t:02 s:23D8F6 d:123ABC 01010100403009D1E3
peerList RC.Key3,RC.Key2_unlock,RC.Key2_lock,RC.Key2_open,RC.Key1_unlock,RC.Key1_lock,RC.Key1_open,
protEvt_AESCom-ok 10 last_at:2016-03-21 16:24:37
protLastRcv 2016-03-21 16:24:37
protResnd 2 last_at:2016-03-21 16:24:36
protSnd 52 last_at:2016-03-21 16:24:37
protState CMDs_done
rssi_HMLAN1 avg:-63.95 min:-65 max:-61 lst:-64 cnt:24
rssi_RC.Key1 avg:-51.8 min:-86 max:-37 lst:-81 cnt:21
rssi_RC.Key3 avg:-41 min:-41 max:-41 lst:-41 cnt:2
rssi_at_HMLAN1 avg:-69.77 min:-95 max:-62 lst:-67 cnt:81
rssi_at_hmusb avg:-44.27 min:-58 max:-41 lst:-43 cnt:83
Helper:
Dblog:
Aescommtodev:
Mydblog:
TIME 1458573877.79288
VALUE ok
Aeskeynbr:
Mydblog:
TIME 1458423002.64907
VALUE 02
Battery:
Mydblog:
TIME 1458462466.1249
VALUE ok
Direction:
Mydblog:
TIME 1458509408.01983
VALUE none
Error:
Mydblog:
TIME 1458462466.1249
VALUE none
Lock:
Mydblog:
TIME 1458573877.79288
VALUE unlocked
State:
Mydblog:
TIME 1458573877.16826
VALUE unlocked
Triglast:
Mydblog:
TIME 1458499567.72487
VALUE RC.Key1_open:short
Trig_rc.key1_unlock:
Mydblog:
TIME 1458570585.03053
VALUE short
Uncertain:
Mydblog:
TIME 1458573877.79288
VALUE no
Readings:
2016-03-21 16:24:37 .protLastRcv 2016-03-21 16:24:37
2016-03-21 16:24:37 CommandAccepted yes
2016-02-03 21:57:12 D-firmware 2.5
2016-02-03 21:57:12 D-serialNr KEQ0858861
2016-03-21 16:24:37 aesCommToDev ok
2016-03-21 16:24:37 aesKeyNbr 02
2016-03-21 16:24:37 battery ok
2016-03-21 16:24:37 direction none
2016-03-21 16:24:37 error none
2016-03-21 16:24:37 lock unlocked
2016-03-19 21:36:31 peerList RC.Key3,RC.Key2_unlock,RC.Key2_lock,RC.Key2_open,RC.Key1_unlock,RC.Key1_lock,RC.Key1_open,
2016-03-14 18:00:26 powerOn 2016-03-14 18:00:26
2016-03-21 16:24:37 recentStateType ack
2016-03-21 16:24:37 state unlocked
2016-03-21 15:29:44 trigLast RC.Key1_unlock:short
2016-03-20 18:25:32 trig_RC.Key1_lock short
2016-03-21 12:30:17 trig_RC.Key1_open short
2016-03-21 15:29:44 trig_RC.Key1_unlock short
2016-03-20 18:22:46 trig_RC.Key3 long
2016-03-21 16:24:37 uncertain no
Helper:
HM_CMDNR 204
cSnd 01123ABC23D8F6010E,11123ABC23D8F6800101FF
mId 0026
rxType 2
Expert:
def 1
det 0
raw 0
tpl 0
Io:
newChn +23D8F6,00,01,00
nextSend 1458573877.49299
rxt 0
vccu vccu
p:
23D8F6
00
01
00
prefIO:
HMLAN1
Mrssi:
mNo CC
Io:
HMLAN1 -65
hmusb -43
Prt:
bErr 0
sProc 0
Rspwait:
Q:
qReqConf
qReqStat
Role:
chn 1
dev 1
Rssi:
Hmlan1:
avg -63.9583333333333
cnt 24
lst -64
max -61
min -65
Rc.key1:
avg -51.8095238095238
cnt 21
lst -81
max -37
min -86
Rc.key3:
avg -41
cnt 2
lst -41
max -41
min -41
At_hmlan1:
avg -69.7777777777778
cnt 81
lst -67
max -62
min -95
At_hmusb:
avg -44.277108433735
cnt 83
lst -43
max -41
min -58
Shadowreg:
Attributes:
IODev HMLAN1
IOgrp vccu:HMLAN1
autoReadReg 0_off
event-on-change-reading .*
event-on-update-reading uncertain,lock
expert 0_defReg
firmware 2.5
group Türen
hmProtocolEvents 0_off
icon hm_keymatic
model HM-SEC-KEY-S
msgRepeat 1
peerIDs 00000000,1DF0C101,227B9601,227B9602,227B9604,24702901,24702902,24702904,
room Flur
serialNr KEQ0858861
subType keyMatic
verbose 0
webCmd lock:inhibit on:inhibit off:unlock:open
und hier daie Events nach einem "set EG.FL.KEYM unlock":
2016-03-21 16:24:34 CUL_HM EG.FL.KEYM set_unlock
2016-03-21 16:24:34 CUL_HM EG.FL.KEYM state: set_unlock
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM aesCommToDev: pending
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM aesCommToDev: ok
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM lock: unlocked
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM unlocked
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM uncertain: no
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM state: unlocked
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM lock: unlocked
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM uncertain: no
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM aesCommToDev: pending
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM aesCommToDev: ok
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM lock: unlocked
2016-03-21 16:24:37 CUL_HM EG.FL.KEYM uncertain: no
Was mache ich falsch?
ZitatKeymatic sendet immer alle Events zweimal
das sehe ich nicht in deinen events.
es werden nur die events "doppelt" generiert, für die du es explizit erlaubst:
event-on-update-reading uncertain,lockim state: finde ich nur set_unlock und dann unlocked.
Ja, danke da hast du natürlich recht. :)
Ich war einfach auf der falschen Fährte.
Gruß
Thomas