Moin zusammen,
ich habe die Tage den 4-fach Schaltaktor HmIP-DRSI4 bei mir verbaut und in Fhem eingebunden (Debmatic + Fhem auf einem PI4; Software aktuell). So weit lassen sich die Eingänge und Relais auch definieren und verwenden, aber es werden bei den Devices dann meist zu viele Readings angezeigt oder Daten mehrfach mit gleichem Timestamp geloggt.
Ein Listing des ersten Relais:
Internals:
DEF 00259F2998AABB sd=5.STATE cd=6.STATE
FUUID 63aecc33-f33f-cc16-1b37-4f0c6236e5225838
IODev sys_Debmatic
NAME cp_hm_ParkSpaceLighting
NR 388
STATE off
TYPE HMCCUDEV
ccuaddr 00259F2998AABB
ccudevstate active
ccuif HmIP-RF
ccuname CP_Schaltaktor_4x:0
ccurolectrl SWITCH_VIRTUAL_RECEIVER
ccurolestate SWITCH_TRANSMITTER
ccusubtype DRSI4
ccutype HmIP-DRSI4
eventCount 80
firmware 1.4.2
readonly no
receiver tr_hm_Leuchten_vchn2
Helper:
DBLOG:
hmstate:
db_DataLog:
TIME 1672728556.94757
VALUE off
rssidevice:
db_DataLog:
TIME 1672598266.32942
VALUE -94
READINGS:
2023-01-03 11:50:12 1.STATE true
2023-01-03 11:50:12 2.STATE false
2023-01-03 11:50:12 3.STATE false
2023-01-03 11:50:12 4.STATE false
2023-01-03 11:50:12 5.PROCESS STABLE
2023-01-03 11:50:12 5.SECTION 0
2023-01-03 11:50:12 5.SECTION_STATUS NORMAL
2023-01-03 11:50:12 5.STATE off
2023-01-03 11:50:12 6.PROCESS STABLE
2023-01-03 11:50:12 6.SECTION 0
2023-01-03 11:50:12 6.SECTION_STATUS NORMAL
2023-01-03 11:50:12 6.STATE off
2023-01-01 14:55:32 IODev sys_Debmatic
2023-01-03 11:50:14 activity alive
2023-01-03 11:50:12 control off
2023-01-03 11:50:14 devstate ok
2023-01-03 11:50:14 hmstate off
2023-01-03 11:50:14 rssidevice -94
2023-01-02 12:36:09 rssipeer -85
2023-01-03 11:50:12 state off
2023-01-02 12:29:13 voltage 0.0
hmccu:
channels 22
defCDP 6.STATE
defSDP 5.STATE
detect 5
devspec 00259F2998AABB
forcedev 0
nodefaults 1
role 0:MAINTENANCE,1:MULTI_MODE_INPUT_TRANSMITTER,2:MULTI_MODE_INPUT_TRANSMITTER,3:MULTI_MODE_INPUT_TRANSMITTER,4:MULTI_MODE_INPUT_TRANSMITTER,5:SWITCH_TRANSMITTER,6:SWITCH_VIRTUAL_RECEIVER,7:SWITCH_VIRTUAL_RECEIVER,8:SWITCH_VIRTUAL_RECEIVER,9:SWITCH_TRANSMITTER,10:SWITCH_VIRTUAL_RECEIVER,11:SWITCH_VIRTUAL_RECEIVER,12:SWITCH_VIRTUAL_RECEIVER,13:SWITCH_TRANSMITTER,14:SWITCH_VIRTUAL_RECEIVER,15:SWITCH_VIRTUAL_RECEIVER,16:SWITCH_VIRTUAL_RECEIVER,17:SWITCH_TRANSMITTER,18:SWITCH_VIRTUAL_RECEIVER,19:SWITCH_VIRTUAL_RECEIVER,20:SWITCH_VIRTUAL_RECEIVER,21:SWITCH_WEEK_PROFILE
setDefaults 0
cmdlist:
get
set off:noArg on-for-timer on:noArg on-till toggle:noArg
control:
chn 6
dpt STATE
dp:
0.ACTUAL_TEMPERATURE:
VALUES:
NVAL 8.0
ONVAL 8.0
OSVAL 8.0
OVAL 8.0
SVAL 8.0
VAL 8.0
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.ERROR_OVERHEAT:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
0.ERROR_POWER_FAILURE:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
0.INSTALL_TEST:
VALUES:
NVAL true
ONVAL true
OSVAL true
OVAL true
SVAL true
VAL true
0.OPERATING_VOLTAGE:
VALUES:
NVAL 0.000000
ONVAL 0.000000
OSVAL 0.0
OVAL 0.000000
SVAL 0.0
VAL 0.000000
0.OPERATING_VOLTAGE_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
0.RSSI_DEVICE:
VALUES:
NVAL -94
ONVAL -94
OSVAL -94
OVAL -94
SVAL -94
VAL -94
0.RSSI_PEER:
VALUES:
NVAL -85
ONVAL -83
OSVAL -83
OVAL -83
SVAL -85
VAL -85
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 1
ONVAL 1
OSVAL true
OVAL 1
SVAL true
VAL 1
10.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
10.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
10.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
10.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
11.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
11.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
11.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
11.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
12.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
12.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
12.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
12.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
13.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
13.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
13.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
13.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
14.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
14.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
14.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
14.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
15.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
15.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
15.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
15.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
16.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
16.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
16.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
16.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
17.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
17.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
17.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
17.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
18.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
18.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
18.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
18.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
19.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
19.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
19.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
19.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
2.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
20.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
20.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
20.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
20.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
21.WEEK_PROGRAM_CHANNEL_LOCKS:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
3.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
4.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
5.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
5.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
5.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
5.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
6.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
6.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
6.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
6.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
7.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
7.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
7.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
7.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
8.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
8.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
8.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
8.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
9.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
9.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
9.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
9.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
roleCmds:
get:
set:
off:
channel 6
role SWITCH_VIRTUAL_RECEIVER
subcount 1
syntax V:STATE:0
usage off
subcmd:
000:
args 0
dpt STATE
fnc
max 1
min 0
parname STATE
partype 3
ps VALUES
scn 000
unit
on:
channel 6
role SWITCH_VIRTUAL_RECEIVER
subcount 1
syntax V:STATE:1
usage on
subcmd:
000:
args 1
dpt STATE
fnc
max 1
min 0
parname STATE
partype 3
ps VALUES
scn 000
unit
on-for-timer:
channel 6
role SWITCH_VIRTUAL_RECEIVER
subcount 2
syntax V:ON_TIME:?duration V:STATE:1
usage on-for-timer duration
subcmd:
000:
args
dpt ON_TIME
fnc
max 8580000.0
min 0.0
parname duration
partype 2
ps VALUES
scn 000
unit s
001:
args 1
dpt STATE
fnc
max 1
min 0
parname STATE
partype 3
ps VALUES
scn 001
unit
on-till:
channel 6
role SWITCH_VIRTUAL_RECEIVER
subcount 2
syntax V:ON_TIME:?time V:STATE:1
usage on-till time
subcmd:
000:
args
dpt ON_TIME
fnc
max 8580000.0
min 0.0
parname time
partype 2
ps VALUES
scn 000
unit s
001:
args 1
dpt STATE
fnc
max 1
min 0
parname STATE
partype 3
ps VALUES
scn 001
unit
state:
chn 5
dpt STATE
Attributes:
ccureadingfilter 1,2,3,4,5,6..*
cmdIcon on:general_an off:general_aus
event-on-change-reading state,hmstate
group Beleuchtung
icon fts_garage
room Carport,Homematic
sortby 2
Ad hoc sind da [1-4].STATE zu viel und beziehen sich auf die Eingänge 1-4 des DRSI4.
Und ein Bespiel der IMHO zu viel geloggten Daten (Timestamp!; hier Eingang 1 wo ein on/off Bewegungsmelder angeschlossen ist) - logging via define FileLog_cp_hm_ParkSpaceMotion FileLog ./log/cp_hm_ParkSpaceMotion-%m-%Y.log cp_hm_ParkSpaceMotion:
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion rssidevice: -58
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion vacant
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion STATE: vacant
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion rssidevice: -58
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:51 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:52 cp_hm_ParkSpaceMotion rssidevice: -58
2023-01-01_00:59:52 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_00:59:52 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:52 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:52 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:52 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion rssidevice: -58
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion rssidevice: -58
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_00:59:53 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_01:14:25 cp_hm_ParkSpaceMotion rssidevice: -59
2023-01-01_01:14:25 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_01:14:25 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_01:14:25 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion rssidevice: -59
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion vacant
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion STATE: vacant
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion rssidevice: -59
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion hmstate: vacant
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion activity: alive
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion rssidevice: -59
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion devstate: ok
2023-01-01_01:35:30 cp_hm_ParkSpaceMotion hmstate: vacant
Zum DRSI4 habe ich hier im Forum nichts gefunden - hat den schon mal wer eingebunden? Oder fehlt da ggf. noch eine spezifische Unterstützung?
Gruß Ralf