Hallo,
ich habe einen neuen Fensterkontakt installiert, der einen alten Drehgriff-Kontakt ersetzen soll, da dieser defekt ist.
Anlernen an der Beere mit Debmatic war kein Problem, ebenso ihn nach fhem zu übernehmen und anzulegen war schnell erletigt.
Wenn ich jetzt das Fenster öffne oder schließe, wird der Status im Device auch sauber angezeigt, jedoch bekomme ich z.B. im Monitor keine events angezeigt, obwohl ich event-on-change-reading angelegt habe.
Die Definition:
define Fenster_Joschua HMCCUCHN 00365F29A55C1C:1
attr Fenster_Joschua DbLogExclude .*
attr Fenster_Joschua devStateIcon closed:fts_window_1w open:fts_window_1w_open
attr Fenster_Joschua event-on-change-reading .*
attr Fenster_Joschua room Joschua
# CFGFN
# DEF 00365F29A55C1C:1
# FUUID 6421a688-f33f-378b-67cb-73fd03d9d8c33500
# IODev d_ccu
# NAME Fenster_Joschua
# NR 29012
# STATE closed
# TYPE HMCCUCHN
# ccuaddr 00365F29A55C1C:1
# ccudevstate active
# ccuif HmIP-RF
# ccuname HmIP-SWDO-2 00365F29A55C1C:1
# ccurolestate SHUTTER_CONTACT
# ccusubtype SWD
# ccutype HmIP-SWDO-2
# eventCount 5
# firmware 1.18.4
# readonly no
# Helper:
# DBLOG:
# STATE:
# logdb:
# TIME 1679926920.60339
# VALUE closed
# activity:
# logdb:
# TIME 1679926920.60339
# VALUE alive
# battery:
# logdb:
# TIME 1679926920.60339
# VALUE ok
# devstate:
# logdb:
# TIME 1679926920.60339
# VALUE ok
# hmstate:
# logdb:
# TIME 1679926920.60339
# VALUE closed
# rssidevice:
# logdb:
# TIME 1679926920.60339
# VALUE -81
# rssipeer:
# logdb:
# TIME 1679926920.60339
# VALUE N/A
# sabotage:
# logdb:
# TIME 1679926920.60339
# VALUE false
# state:
# logdb:
# TIME 1679926920.60339
# VALUE closed
# voltage:
# logdb:
# TIME 1679926920.60339
# VALUE 1.2
# READINGS:
# 2023-03-27 16:22:00 IODev d_ccu
# 2023-03-27 16:23:05 STATE closed
# 2023-03-27 16:23:05 activity alive
# 2023-03-27 16:23:05 battery ok
# 2023-03-27 16:23:05 devstate ok
# 2023-03-27 16:23:05 hmstate closed
# 2023-03-27 16:23:05 rssidevice -80
# 2023-03-27 16:22:00 rssipeer N/A
# 2023-03-27 16:23:05 sabotage false
# 2023-03-27 16:23:05 state closed
# 2023-03-27 16:23:05 voltage 1.2
# hmccu:
# channels 1
# detect 1
# devspec 00365F29A55C1C:1
# nodefaults 0
# role 1:SHUTTER_CONTACT
# setDefaults 0
# cmdlist:
# get
# set
# control:
# dp:
# 0.CONFIG_PENDING:
# VALUES:
# NVAL 0
# ONVAL 0
# OSVAL false
# OVAL 0
# SVAL false
# VAL 0
# 0.DUTY_CYCLE:
# VALUES:
# NVAL 0
# ONVAL 0
# OSVAL false
# OVAL 0
# SVAL false
# VAL 0
# 0.ERROR_CODE:
# VALUES:
# NVAL 0
# ONVAL 0
# OSVAL 0
# OVAL 0
# SVAL 0
# VAL 0
# 0.INSTALL_TEST:
# VALUES:
# NVAL true
# ONVAL true
# OSVAL true
# OVAL true
# SVAL true
# VAL true
# 0.LOW_BAT:
# VALUES:
# NVAL 0
# ONVAL 0
# OSVAL ok
# OVAL 0
# SVAL ok
# VAL 0
# 0.OPERATING_VOLTAGE:
# VALUES:
# NVAL 1.2
# ONVAL 1.2
# OSVAL 1.2
# OVAL 1.2
# SVAL 1.2
# VAL 1.2
# 0.OPERATING_VOLTAGE_STATUS:
# VALUES:
# NVAL 0
# ONVAL 0
# OSVAL NORMAL
# OVAL 0
# SVAL NORMAL
# VAL 0
# 0.RSSI_DEVICE:
# VALUES:
# NVAL -80
# ONVAL -86
# OSVAL -86
# OVAL -86
# SVAL -80
# VAL -80
# 0.RSSI_PEER:
# VALUES:
# NVAL N/A
# ONVAL N/A
# OSVAL N/A
# OVAL 0
# SVAL N/A
# VAL 0
# 0.SABOTAGE:
# VALUES:
# NVAL 0
# ONVAL 0
# OSVAL false
# OVAL 0
# SVAL false
# VAL 0
# 0.UNREACH:
# VALUES:
# NVAL 0
# ONVAL 0
# OSVAL alive
# OVAL 0
# SVAL alive
# VAL 0
# 0.UPDATE_PENDING:
# VALUES:
# NVAL false
# ONVAL false
# OSVAL false
# OVAL false
# SVAL false
# VAL false
# 1.STATE:
# VALUES:
# NVAL 0
# ONVAL 1
# OSVAL open
# OVAL 1
# SVAL closed
# VAL 0
# roleCmds:
# get:
# set:
# state:
# chn 1
# dpt STATE
#
setstate Fenster_Joschua closed
setstate Fenster_Joschua 2023-03-27 16:22:00 IODev d_ccu
setstate Fenster_Joschua 2023-03-27 16:23:05 STATE closed
setstate Fenster_Joschua 2023-03-27 16:23:05 activity alive
setstate Fenster_Joschua 2023-03-27 16:23:05 battery ok
setstate Fenster_Joschua 2023-03-27 16:23:05 devstate ok
setstate Fenster_Joschua 2023-03-27 16:23:05 hmstate closed
setstate Fenster_Joschua 2023-03-27 16:23:05 rssidevice -80
setstate Fenster_Joschua 2023-03-27 16:22:00 rssipeer N/A
setstate Fenster_Joschua 2023-03-27 16:23:05 sabotage false
setstate Fenster_Joschua 2023-03-27 16:23:05 state closed
setstate Fenster_Joschua 2023-03-27 16:23:05 voltage 1.2
Was fehlt jetzt, um die events zu erhalten, damit ich damit arbeiten kann?
Gruß, Christoph
Bei mir kommen Events. Ich musste sonst nichts weiter machen.
Hier ein List von einem meiner Fensterkontakte:
Internals:
DEF 00109A49A51287:1
FUUID 61efd252-f33f-98e0-9f25-733de6146f17e673
IODev ccu
NAME ArbeitszimmerFenster
NR 437
STATE closed um 2023-04-04 17:21:39<br> Bat ok am 2023-04-04 17:21:39
TYPE HMCCUCHN
ccuaddr 00109A49A51287:1
ccudevstate active
ccuif HmIP-RF
ccuname HmIP-SWDO-I 00109A49A51287:1
ccurolestate SHUTTER_CONTACT
ccusubtype SWDO-I
ccutype HmIP-SWDO-I
eventCount 54
firmware 1.16.10
readonly no
receiver ccu:ArbeitszimmerThermostat,ccu:ArbeitszimmerWandThermostat
READINGS:
2023-04-01 01:52:04 IODev ccu
2023-04-04 17:20:13 PRESS_SHORT 1
2023-04-04 17:21:39 STATE closed
2023-04-04 17:21:39 activity alive
2023-04-04 17:21:39 battery ok
2023-04-04 17:21:39 batteryState ok
2023-04-04 17:21:39 devstate ok
2023-04-04 17:21:39 hmstate closed
2023-04-04 17:21:39 rssidevice -59
2023-02-09 10:42:44 rssipeer N/A
2023-04-04 17:21:39 sabotage false
2023-04-04 17:21:39 state closed
2023-04-04 17:21:39 voltage 2.2
hmccu:
channels 1
detect 1
devspec 00109A49A51287:1
nodefaults 1
role 1:SHUTTER_CONTACT
setDefaults 0
cmdlist:
get
set
control:
dp:
0.CONFIG_PENDING:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
0.DUTY_CYCLE:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
0.ERROR_CODE:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
0.LOW_BAT:
VALUES:
NVAL 0
ONVAL 0
OSVAL ok
OVAL 0
SVAL ok
VAL 0
0.OPERATING_VOLTAGE:
VALUES:
NVAL 2.2
ONVAL 2.2
OSVAL 2.2
OVAL 2.2
SVAL 2.2
VAL 2.2
0.OPERATING_VOLTAGE_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
0.RSSI_DEVICE:
VALUES:
NVAL -59
ONVAL -61
OSVAL -61
OVAL -61
SVAL -59
VAL -59
0.SABOTAGE:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
0.UNREACH:
VALUES:
NVAL 0
ONVAL 0
OSVAL alive
OVAL 0
SVAL alive
VAL 0
1.PRESS_SHORT:
VALUES:
NVAL 1
ONVAL 1
OSVAL 1
OVAL 1
SVAL 1
VAL 1
1.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL closed
OVAL 0
SVAL closed
VAL 0
roleCmds:
get:
set:
state:
chn 1
dpt STATE
Attributes:
event-on-change-reading state,hmstate,battery
genericDeviceType ContactSensor
group Heizung,Sensoren
homebridgeMapping ContactSensorState=state,values=closed:CONTACT_DETECTED;open:CONTACT_NOT_DETECTED CurrentDoorState=state,values=closed:CLOSED;open:OPEN
icon fts_window_1w
room Arbeitszimmer,Homekit
stateFormat {ReadingsVal($name,'state',undef)." um ".ReadingsTimestamp($name,'state',undef).'<br> Bat '.ReadingsVal($name,'battery',undef)." am ".ReadingsTimestamp($name,'battery',undef)}
userReadings batteryState {ReadingsVal($NAME,"battery","low")}
Und hier ein passender Rahmen für ein Notify:
defmod ntArbeitszimmerFenster_state notify ArbeitszimmerFenster:[oc].* {\
....
}
Hallo,
ja, inzwischen zeigt er mir auch Events an in den Internals - es war mir nur insofern aufgefallen, daß ich keine Anzeige im Eventmonitor hatte, um daraus mein doif zu basteln. Letztlich habe ich es auch so hinbekommen, und esfunktioniert.
Gruß, Christoph