Ich habe gestern meinen ersten HmIP-SRH bekommen und an der CCU3 angelernt.
Um zu prüfen, ob das Device irgendwann im Reading activity von alive auf dead wechselt habe ich die Batterie entfernt.
Meine CCU3 zeigt unter Servicemeldungen an "Sabotage" und nach langem Warten zusätzlich "Gerätekommunikation gestört" an.
Soweit so gut...
In fhem können die Servicemeldungen auch abgerufen werden:
get CCU3 ccuMsg service
24.05.22 17:14;24.05.22 17:16;12345678901234;HmIP-SRH-Esszimmer-Tuer-Ost;SABOTAGE
24.05.22 20:29;25.05.22 11:22;12345678901234;HmIP-SRH-Esszimmer-Tuer-Ost;UNREACH
2
Das Reading bleibt aber auf "alive"
READINGS:
2022-05-24 16:41:13 IODev CCU3
2022-05-24 16:55:20 activity alive
Internals:
CFGFN
DEF 12345678901234:1
FUUID 628cee89-f33f-324f-c987-0299e72328253954
IODev CCU3
NAME HmIP_SRH_Esszimmer_Tuer_Ost
NR 223
STATE alive
ok
open
TYPE HMCCUCHN
ccuaddr 12345678901234:1
ccudevstate active
ccuif HmIP-RF
ccuname HmIP-SRH 12345678901234:1
ccurolestate ROTARY_HANDLE_TRANSCEIVER
ccusubtype SRH
ccutype HmIP-SRH
firmware 1.2.10
readonly no
Helper:
DBLOG:
STATE:
logdb:
TIME 1653403275.1402
VALUE open
activity:
logdb:
TIME 1653403275.1402
VALUE dead
battery:
logdb:
TIME 1653403275.1402
VALUE ok
devstate:
logdb:
TIME 1653403275.1402
VALUE sabotage,unreach
hmstate:
logdb:
TIME 1653403275.1402
VALUE unreachable
rssidevice:
logdb:
TIME 1653403275.1402
VALUE -90
rssipeer:
logdb:
TIME 1653403275.1402
VALUE N/A
sabotage:
logdb:
TIME 1653403275.1402
VALUE true
state:
logdb:
TIME 1653403275.1402
VALUE open
voltage:
logdb:
TIME 1653403275.1402
VALUE 1.4
READINGS:
2022-05-24 16:41:13 IODev CCU3
2022-05-24 16:55:19 STATE open
2022-05-24 16:55:20 activity alive
2022-05-24 16:55:20 battery ok
2022-05-25 11:12:39 devstate sabotage
2022-05-25 11:12:39 hmstate open
2022-05-24 16:55:20 rssidevice -92
2022-05-24 16:41:15 rssipeer N/A
2022-05-24 16:55:20 sabotage true
2022-05-24 16:55:19 state open
2022-05-24 16:55:20 voltage 1.4
hmccu:
channels 1
detect 1
devspec 12345678901234:1
nodefaults 0
role 1:ROTARY_HANDLE_TRANSCEIVER
setDefaults 0
cmdlist:
get
set
control:
dp:
0.ARR_TIMEOUT:
MASTER:
NVAL 10
ONVAL 10
OSVAL 10
OVAL 10
SVAL 10
VAL 10
VALUES:
0.CONFIG_PENDING:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
0.CYCLIC_INFO_MSG:
MASTER:
NVAL 1
ONVAL 1
OSVAL 1
OVAL 1
SVAL 1
VAL 1
VALUES:
0.CYCLIC_INFO_MSG_DIS:
MASTER:
NVAL 20
ONVAL 20
OSVAL 20
OVAL 20
SVAL 20
VAL 20
VALUES:
0.CYCLIC_INFO_MSG_DIS_UNCHANGED:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
0.CYCLIC_INFO_MSG_OVERDUE_THRESHOLD:
MASTER:
NVAL 2
ONVAL 2
OSVAL 2
OVAL 2
SVAL 2
VAL 2
VALUES:
0.DISABLE_MSG_TO_AC:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
0.DUTYCYCLE_LIMIT:
MASTER:
NVAL 180
ONVAL 180
OSVAL 180
OVAL 180
SVAL 180
VAL 180
VALUES:
0.DUTY_CYCLE:
VALUES:
NVAL 0
ONVAL 0
OSVAL false
OVAL 0
SVAL false
VAL 0
0.ENABLE_ROUTING:
MASTER:
NVAL 1
ONVAL 1
OSVAL 1
OVAL 1
SVAL 1
VAL 1
VALUES:
0.ERROR_CODE:
VALUES:
NVAL 1
ONVAL 1
OSVAL 1
OVAL 1
SVAL 1
VAL 1
0.INSTALL_TEST:
VALUES:
NVAL true
ONVAL true
OSVAL true
OVAL true
SVAL true
VAL true
0.LOCAL_RESET_DISABLED:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
0.LOW_BAT:
VALUES:
NVAL 0
ONVAL 0
OSVAL ok
OVAL 0
SVAL ok
VAL 0
0.LOW_BAT_LIMIT:
MASTER:
NVAL 1.1
ONVAL 1.1
OSVAL 1.1
OVAL 1.1
SVAL 1.1
VAL 1.1
VALUES:
0.OPERATING_VOLTAGE:
VALUES:
NVAL 1.4
ONVAL 1.3
OSVAL 1.3
OVAL 1.3
SVAL 1.4
VAL 1.4
0.OPERATING_VOLTAGE_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
0.RSSI_DEVICE:
VALUES:
NVAL -92
ONVAL -88
OSVAL -88
OVAL -88
SVAL -92
VAL -92
0.RSSI_PEER:
VALUES:
NVAL N/A
ONVAL N/A
OSVAL N/A
OVAL 0
SVAL N/A
VAL 0
0.SABOTAGE:
VALUES:
NVAL 1
ONVAL 1
OSVAL true
OVAL 1
SVAL true
VAL 1
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.ALARM_MODE_TYPE:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_1:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_2:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_3:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_4:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_5:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_6:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_7:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.EVENT_DELAY_UNIT:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.EVENT_DELAY_VALUE:
MASTER:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
VALUES:
1.MSG_FOR_POS_A:
MASTER:
NVAL 2
ONVAL 2
OSVAL 2
OVAL 2
SVAL 2
VAL 2
VALUES:
1.MSG_FOR_POS_B:
MASTER:
NVAL 1
ONVAL 1
OSVAL 1
OVAL 1
SVAL 1
VAL 1
VALUES:
1.MSG_FOR_POS_C:
MASTER:
NVAL 3
ONVAL 3
OSVAL 3
OVAL 3
SVAL 3
VAL 3
VALUES:
1.STATE:
VALUES:
NVAL 2
ONVAL 0
OSVAL closed
OVAL 0
SVAL open
VAL 2
roleCmds:
get:
set:
state:
chn 1
dpt STATE
Attributes:
DbLogExclude .*
DbLogInclude devstate|activity|battery|hmstate
alias Esszimmer: Tür Terrasse
devStateIcon alive:10px-kreis-gruen
open:fts_window_2w_open_l@red closed:fts_window_2w@green tilted:fts_window_2w_tilt_l@orange
low:measure_battery_0@red ok:measure_battery_100@green
event-on-change-reading .*
group Homematic-IP
icon fts_door_slide_2w
room Homematic
stateFormat activity
battery
state
Hat jemand eine Idee, wie ich einen plötzlichen Ausfall feststellen kann?
Manfred