Hallo zusammen,
ich habe mehrere Homematic IP Steckdosen (HMIP-PS) im Einsatz.
Ich würde gerne ndie Zustände "Steckdose = on" und "off" an der FTUI Oberfläche anzeigen.
Einen ersten Ansatz habe ich zum Testen wie folgt umgesetzt:
<ftui-grid-tile row="11" col="5" height="2" width="4">
<header>AZ-Dad-Socket</header>
<ftui-label size="2">AZ-Dad-Steckdose</ftui-label>
<ftui-icon
path="../images/fhemSVG" size="5"
class="size-5" [name]="20_DG_AZ_Dad_Stehlampe_HM_IP_2 | map('on: socket_timer, off: socket_timer')"
[color]="20_DG_AZ_Dad_Stehlampe_HM_IP_2 | map('on: green, off: red')"> <!--[color]="dummy1 | map('on: danger, off: medium')"-->
</ftui-icon>
</ftui-grid-tile>
Das Problem ist jetzt, dass ein Wechsel von "on" nach "off" oder "off" nach "on" nur durch aktualisieren der Web-Seite angezeigt werden.
Ein Statuswechsel der Anzeige erfolgt nicht durch das device getriggert.
Wobei es egal ist ob ich <20_DG_AZ_Dad_Stehlampe_HM_IP_2> oder <20_DG_AZ_Dad_Stehlampe_HM_IP_2:state> oder <..:hmstate> oder <..;control> oder <..:3.STATE> oder <..:2.STATE> als Trigger verwende.
Im Event monitor von fhem wird nur nachfolgendes angezeigt:
Events (Filter: 20_DG_AZ_Dad_Stehlampe_HM_IP_2.*) FHEM log
2023-01-16 16:41:47 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16 16:42:38 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16 16:43:03 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16 16:44:11 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16 16:44:53 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16 16:44:53 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16 16:46:41 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
Im Logfile sind allerdings alle Readings geloggt.
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -81
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:41:48 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: off
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 0
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:41:50 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:42:38 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -81
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -79
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:42:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:43:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -81
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 2
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: on
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: on
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:43:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: on
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 2
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: on
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: on
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 2
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:43:07 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -79
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -80
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:11 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 0
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: off
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:14 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:15 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:44:53 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_16:44:53 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -80
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: on
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: on
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 2
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:54 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: on
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 2
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: on
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: on
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 2
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:56 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:44:57 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:57 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:44:57 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:44:57 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:45:39 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -81
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:45:40 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 0
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: off
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:45:43 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_16:46:41 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -80
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_16:46:42 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
Hat jemand eine Idee wie ich den Statuswechsel nach FTUI bekomme?
Müsste ich/kann ich bei [name] und [color] als Quelle das Logfile eintragen? Wenn ja, wie sieht dann die Syntax für die Abfrage aus?
Mache ich das Ganze mit einer Steckdose aus der homematic (classic) Serie (HM-ES-PMSW1-PL) funktioniert [name]/[color] <10_EG_Wohnzimmer_Stehlampe_Sw:state> oder <..:pct> anstandslos, der Wechsel wird durch das Icon sauber angezeigt.
Anbei noch das List der HM-IP Steckdose
Internals:
DEF 00021BE9A2DFC0 sd=2.STATE cd=3.STATE
FUUID 617db4c1-f33f-8c2a-cb09-aab711b62f024bb7
IODev ccu_00
NAME 20_DG_AZ_Dad_Stehlampe_HM_IP_2
NR 3002
STATE off
TYPE HMCCUDEV
ccuaddr 00021BE9A2DFC0
ccudevstate active
ccuif HmIP-RF
ccuname 20_DG_AZ_Dad_Stehlampe_HM_IP
ccurolectrl SWITCH_VIRTUAL_RECEIVER
ccurolestate SWITCH_TRANSMITTER
ccusubtype PS
ccutype HMIP-PS
eventCount 874
firmware 2.6.2
readonly no
READINGS:
2023-01-16 16:45:43 2.PROCESS STABLE
2023-01-16 16:45:43 2.SECTION 0
2023-01-16 16:45:43 2.SECTION_STATUS NORMAL
2023-01-16 16:45:43 2.STATE off
2023-01-16 16:46:42 3.PROCESS STABLE
2023-01-16 16:46:42 3.SECTION 0
2023-01-16 16:46:42 3.SECTION_STATUS NORMAL
2023-01-16 16:46:42 3.STATE off
2023-01-12 21:52:33 IODev ccu_00
2023-01-16 16:46:42 activity alive
2023-01-16 16:46:42 control off
2023-01-16 16:46:42 devstate ok
2023-01-16 16:46:42 hmstate off
2023-01-16 16:46:42 rssidevice -78
2023-01-16 16:46:42 rssipeer -80
2023-01-16 16:45:43 state off
2023-01-12 21:53:30 voltage 0.0
hmccu:
channels 7
defCDP 3.STATE
defSDP 2.STATE
detect 5
devspec 00021BE9A2DFC0
forcedev 0
nodefaults 1
role 0:MAINTENANCE,1:KEY_TRANSCEIVER,2:SWITCH_TRANSMITTER,3:SWITCH_VIRTUAL_RECEIVER,4:SWITCH_VIRTUAL_RECEIVER,5:SWITCH_VIRTUAL_RECEIVER,6:SWITCH_WEEK_PROFILE
setDefaults 0
cmdlist:
get
set on-till on:noArg on-for-timer off:noArg toggle:noArg
control:
chn 3
dpt STATE
dp:
0.ACTUAL_TEMPERATURE:
VALUES:
NVAL 0.000000
ONVAL 0.000000
OSVAL 0.0
OVAL 0.000000
SVAL 0.0
VAL 0.000000
0.ACTUAL_TEMPERATURE_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 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 false
ONVAL false
OSVAL false
OVAL false
SVAL false
VAL false
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 -78
ONVAL -78
OSVAL -78
OVAL -78
SVAL -78
VAL -78
0.RSSI_PEER:
VALUES:
NVAL -80
ONVAL -81
OSVAL -81
OVAL -81
SVAL -80
VAL -80
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
2.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
2.SECTION:
VALUES:
NVAL 0
ONVAL 2
OSVAL 2
OVAL 2
SVAL 0
VAL 0
2.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
2.STATE:
VALUES:
NVAL 0
ONVAL 1
OSVAL on
OVAL 1
SVAL off
VAL 0
3.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
3.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
3.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
3.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
VAL 0
4.PROCESS:
VALUES:
NVAL 0
ONVAL 0
OSVAL STABLE
OVAL 0
SVAL STABLE
VAL 0
4.SECTION:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
4.SECTION_STATUS:
VALUES:
NVAL 0
ONVAL 0
OSVAL NORMAL
OVAL 0
SVAL NORMAL
VAL 0
4.STATE:
VALUES:
NVAL 0
ONVAL 0
OSVAL off
OVAL 0
SVAL off
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.WEEK_PROGRAM_CHANNEL_LOCKS:
VALUES:
NVAL 0
ONVAL 0
OSVAL 0
OVAL 0
SVAL 0
VAL 0
roleCmds:
get:
set:
off:
channel 3
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 3
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 3
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 3
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 2
dpt STATE
Attributes:
alias 20_DG_AZ_Dad_Stehlampe_HM_IP_2
ccureadingfilter 1,2,3..*
group AZ_Dad_Stehlampe
icon light_floor_lamp
room 20_Dachgeschoss->AZ-Dad
Hi,
hast du schon so getestet?:
20_DG_AZ_Dad_Stehlampe_HM_IP_2:state
Im Normalfall wird auf STATE gegangen wenn nix angegeben...
Voraussetzung ist natürlich immer dass ein Event vom Device kommt.
LG
Ja, das ist ja das verwunderliche, egal welches Reading ich nehme, der Status ändert sich nicht.
Zitat
Das Problem ist jetzt, dass ein Wechsel von "on" nach "off" oder "off" nach "on" nur durch aktualisieren der Web-Seite angezeigt werden.
Ein Statuswechsel der Anzeige erfolgt nicht durch das device getriggert.
Wobei es egal ist ob ich <20_DG_AZ_Dad_Stehlampe_HM_IP_2> oder <20_DG_AZ_Dad_Stehlampe_HM_IP_2:state> oder <..:hmstate> oder <..;control> oder <..:3.STATE> oder <..:2.STATE> als Trigger verwende.
Wenn ich mir den Event monitor ansehe ist mir nicht klar welches Reading setzt den Event.
Ich probiere nochmal "STATE" den hatte ich nicht dabei s. o.
Grüße Joachim
Wenn das Problem noch besteht, würde ich mal folgende Ausgabezeilen hinzufügen:
<ftui-label size="2" [text]="20_DG_AZ_Dad_Stehlampe_HM_IP_2"></ftui-label>
<ftui-label size="2" [text]="20_DG_AZ_Dad_Stehlampe_HM_IP_2:state"></ftui-label>
<ftui-label size="2" [text]="20_DG_AZ_Dad_Stehlampe_HM_IP_2:hmstate"></ftui-label>
Zitat von: CottonIJo am 16 Januar 2023, 18:34:06
Wenn ich mir den Event monitor ansehe ist mir nicht klar welches Reading setzt den Event.
Was genau bedeutet das ?
Vielleicht mal einen Ausschnitt aus dem Event-Monitor zeigen ...
P.S.: 2 Nebenbei-HMIP-Zusatzfragen ...
Wurde die Steckdose direkt als HMCCUDEV angelegt, oder war es ursprünglich ein HMCCUCHN ?
Wenn Du die Steckdose umschaltest, wird dies unmittelbar in Event-Monitor und FHEM-Device angezeigt oder verzögert ?
Zur Erklärung: die Steckdose wird über ein DOIF geschaltet.
Um für das FTUI Problem Ergebnisse zu erzeugen mache ich ein set cmd1 (macht ein "on") und ein set cmd2 (macht ein "off")
Auf ein jeweiliges set cmd1 oder set cmd2 folgt eine physische Reaktion der Steckdose, sie wird verzugslos "on" oder "off"
Zitat
Wurde die Steckdose direkt als HMCCUDEV angelegt, oder war es ursprünglich ein HMCCUCHN ?
Gerät wurde über HMCCU 5.0 mit get ccu_00 createDev als HMCCUDEV generiert
Beispiel (Steckdose ist "on"), 2023-01-16_21:34:00, jetzt folgt set cmd2 --> Steckdose schaltet aus aber kein Eintrag im Event Monitor!
Im Log wird das Abschalten protokolliert:
2023-01-16_21:33:59 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -80
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:34:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_21:34:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_21:34:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_21:34:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:34:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: off
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 0
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:34:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
Beispiel (Steckdose ist "off"), 2023-01-16 21:45:00, jetzt folgt set cmd1 --> Steckdose schaltet ein,
nur ein Eintrag im Event Monitor!
2023-01-16 21:45:01 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
dafür im Log-File wieder vollständig:
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -77
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -81
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: on
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: on
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 2
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:45:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: on
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 2
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: on
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: on
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 2
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:45:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
Beispiel (Steckdose ist "on"), 2023-01-16_21:50:00, jetzt folgt set cmd2 --> Steckdose schaltet aus,
ein Eintrag im Event Monitor!
2023-01-16 21:50:00 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
Im Log wird das Abschalten protokolliert:
2023-01-16_21:50:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -77
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -81
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:50:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: off
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 0
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_21:50:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
Danach wie vorgeschlagen die 3 label in FTUI hinzugefügt
Beispiel (Steckdose ist "off"), 2023-01-16 22:06:00, jetzt folgt set cmd1 --> Steckdose schaltet ein,
kein Eintrag im Event Monitor! Auch keine Textänderung bei den 3 Label
dafür im Log-File wieder vollständig:
2023-01-16_22:06:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -77
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -80
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: on
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: on
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 2
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:06:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:06:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -77
2023-01-16_22:06:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_22:06:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:06:03 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 2
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 on
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: on
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: on
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: on
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 2
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:06:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
Ist es der fehlende Event der hier die Anzeige der Änderung in FTUI fehlen läßt?
Grüße Joachim
Zitat von: CottonIJo am 16 Januar 2023, 22:16:54
...
Ist es der fehlende Event der hier die Anzeige der Änderung in FTUI fehlen läßt?
...
Sieht so aus.
Kannst ja mal mit
event-on-change-reading .*
im Device testen.
LG
Nachtrag:
<ftui-label size="2" [text]="20_DG_AZ_Dad_Stehlampe_HM_IP_2"></ftui-label>
<ftui-label size="2" [text]="20_DG_AZ_Dad_Stehlampe_HM_IP_2:state"></ftui-label>
<ftui-label size="2" [text]="20_DG_AZ_Dad_Stehlampe_HM_IP_2:hmstate"></ftui-label>
mein letztes set war "on", irgendwann (hatte ich leider nicht mitgekriegt) ist der Status in FTUI auf "on" gegangen, alle 3 Label standen auf "on".
Das DOIF schaltet die Steckdose um 22:30h ab. (siehe Log), wieder kein Eintrag im Event Monitor.
Dann um 22:35:29h erfolgt (ohne manuelle Aktion) Statuswechsel in FTUI, Label stehen auf "off", icon hat den richtigen Status.
Ist jemandem bekannt ob HM-IP ein timing Problem zwischen CCU3 und fhem hat?
Events (Filter: 20_DG_AZ_Dad_Stehlampe_HM_IP_2.*) FHEM log
2023-01-16 22:35:29 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16 22:35:29 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16 22:35:29 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16 22:35:29 HMCCUDEV 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
Log-File
2023-01-16_22:30:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_22:30:00 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssipeer: -81
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -77
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:30:01 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: on
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: off
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 0
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:30:04 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION_STATUS: NORMAL
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.PROCESS: STABLE
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 off
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.STATE: off
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 2.SECTION: 0
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.PROCESS: STABLE
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION_STATUS: NORMAL
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 control: off
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.STATE: off
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 3.SECTION: 0
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 activity: alive
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 rssidevice: -78
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 devstate: ok
2023-01-16_22:35:29 20_DG_AZ_Dad_Stehlampe_HM_IP_2 hmstate: off
Zitat von: mr_petz am 16 Januar 2023, 22:33:56
Kannst ja mal mit
event-on-change-reading .*
im Device testen.
Ich selbst nutze "event-on-change-reading .*" in vielen Fällen.
Das Attribut dient dazu, "überflüssige" Events (wegen bereits bekanntem Wert) zu unterdrücken.
Da bei Dir Events fehlen, könnte dieses Attribut zwar helfen, den Event-Monitor noch schweigsamer zu machen, aber fehlende Events sollten nicht dazukommen.
In Kombination mit "event-on-change-reading .*" nutze ich auch schon mal "event-on-update-reading irgendeinReading".
Dieses Attribut bewirkt, dass trotz bereits bekanntem Wert auf jeden Fall ein Event generiert wird.
Dies ist z.B. bei reinen Push-Button sinnvoll, da diese nur beim Drücken informieren, nicht aber beim Loslassen.
Bei Dir könnte vielleicht "event-on-update-reading hmstate" helfen.
Da ich (noch) keine HMIP Steckdose habe, aber z.B. einen HMIP-Fensterkontakt, habe ich mal folgenden Test durchgeführt - funktioniert eigentlich wie gewünscht (FHEMWEB,FTUI3).
=== vorhandenes FHEM-Device
defmod HMIP_SWDO_0123456789ABCDEF HMCCUCHN 0123456789ABCDEF:1
attr HMIP_SWDO_0123456789ABCDEF event-on-change-reading .*
=== Neuen FileLog definiert
Event-Monitor
2023-01-17 06:47:46 Global global DEFINED FileLog_HMIP_SWDO_0123456789ABCDEF
2023-01-17 06:47:46 Global global ATTR FileLog_HMIP_SWDO_0123456789ABCDEF logtype text
2023-01-17 06:48:35 Global global ATTR FileLog_HMIP_SWDO_0123456789ABCDEF eventOnThreshold 1
*** Fenster geöffnet
FHEM-Device
setstate HMIP_SWDO_0123456789ABCDEF 2023-01-17 06:51:51 STATE closed
setstate HMIP_SWDO_0123456789ABCDEF 2023-01-17 06:51:51 hmstate closed
setstate HMIP_SWDO_0123456789ABCDEF 2023-01-17 06:51:51 rssidevice -53
setstate HMIP_SWDO_0123456789ABCDEF 2023-01-17 06:51:51 state closed
Event-Monitor
2023-01-17 06:51:51 FileLog FileLog_HMIP_SWDO_0123456789ABCDEF linesInTheFile: 1
2023-01-17 06:51:51 HMCCUCHN HMIP_SWDO_0123456789ABCDEF rssidevice: -58
2023-01-17 06:51:51 FileLog FileLog_HMIP_SWDO_0123456789ABCDEF linesInTheFile: 4
2023-01-17 06:51:51 HMCCUCHN HMIP_SWDO_0123456789ABCDEF open
2023-01-17 06:51:51 HMCCUCHN HMIP_SWDO_0123456789ABCDEF STATE: open
2023-01-17 06:51:51 HMCCUCHN HMIP_SWDO_0123456789ABCDEF hmstate: open
FileLog-Device
2023-01-17_06:51:51 HMIP_SWDO_0123456789ABCDEF rssidevice: -58
2023-01-17_06:51:51 HMIP_SWDO_0123456789ABCDEF open
2023-01-17_06:51:51 HMIP_SWDO_0123456789ABCDEF STATE: open
2023-01-17_06:51:51 HMIP_SWDO_0123456789ABCDEF hmstate: open
*** Fenster geschlossen
FHEM-Device
setstate HMIP_SWDO_0123456789ABCDEF 2023-01-17 06:53:29 STATE closed
setstate HMIP_SWDO_0123456789ABCDEF 2023-01-17 06:53:29 hmstate closed
setstate HMIP_SWDO_0123456789ABCDEF 2023-01-17 06:53:29 rssidevice -53
setstate HMIP_SWDO_0123456789ABCDEF 2023-01-17 06:53:29 state closed
Event-Monitor
2023-01-17 06:53:29 FileLog FileLog_HMIP_SWDO_0123456789ABCDEF linesInTheFile: 5
2023-01-17 06:53:29 HMCCUCHN HMIP_SWDO_0123456789ABCDEF rssidevice: -53
2023-01-17 06:53:30 FileLog FileLog_HMIP_SWDO_0123456789ABCDEF linesInTheFile: 8
2023-01-17 06:53:30 HMCCUCHN HMIP_SWDO_0123456789ABCDEF closed
2023-01-17 06:53:30 HMCCUCHN HMIP_SWDO_0123456789ABCDEF STATE: closed
2023-01-17 06:53:30 HMCCUCHN HMIP_SWDO_0123456789ABCDEF hmstate: closed
FileLog-Device
2023-01-17_06:53:29 HMIP_SWDO_0123456789ABCDEF rssidevice: -53
2023-01-17_06:53:29 HMIP_SWDO_0123456789ABCDEF closed
2023-01-17_06:53:29 HMIP_SWDO_0123456789ABCDEF STATE: closed
2023-01-17_06:53:29 HMIP_SWDO_0123456789ABCDEF hmstate: closed
Ich hatte 3 Desktop-Sitzungen offen und alle reagierten bei jeder Aktion sofort und waren "gefühlt" absolut synchron.
Beim "Schliessen"-Fall fiel mir nur auf, das im FileLog "06:53:29" verwendet wird, im Event-Monitor aber "06:53:29" sowie "06:53:30" .?.
Um sich nicht nur auf das Verhalten eines devices zu stützen habe ich die Versuche mit einer anderen Steckdose (HM-IP) wiederholt.
Das Verhalten war genauso, Steckdose schaltet, FTUI wurde nicht aktualisiert.
Zitat
In Kombination mit "event-on-change-reading .*" nutze ich auch schon mal "event-on-update-reading irgendeinReading".
Zum Schluss der Empfehlung gefolgt, da ich beide Attribute auch verwende, habe ich hier nicht mit einer Verhaltensänderung gerechnet, weit gefehlt.
Versuche die Steckdose zu schalten wiederholt, großes Erstaunen, die Steckdose schaltet und FTUI wird ein paar Sekunden später aktualisiert, widerholbar!
Hatte eigentlich erwartet, dass eine Einschränkung der zu loggenden Readings zu weniger Events führt und nicht zu mehr.
Aber wenn diese Änderung für alle HM-IP Steckdosen als Lösung greift kann ich damit leben.
@OdfFhem,mr_Petz, vielen Dank für die Ideen und Unterstützung.
Event-Monitor
2023-01-17 11:01:00 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP on
2023-01-17 11:10:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17 11:15:47 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP activity: alive
2023-01-17 11:15:47 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -87
2023-01-17 11:15:47 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP devstate: ok
2023-01-17 11:15:47 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP hmstate: off
2023-01-17 11:18:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP on
2023-01-17 11:28:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP on
Event-Monitor
2023-01-17 11:37:21 Global global ATTR 20_DG_Balkonzimmer_SD_aussen_HM_IP event-on-change-reading .*
2023-01-17 11:37:36 Global global ATTR 20_DG_Balkonzimmer_SD_aussen_HM_IP event-on-update-reading .hmstate
2023-01-17 11:39:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17 11:39:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP control: off
2023-01-17 11:39:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.STATE: off
2023-01-17 11:39:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.SECTION: 0
2023-01-17 11:39:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssipeer: -92
2023-01-17 11:39:05 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -85
2023-01-17 11:39:05 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17 11:39:05 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.STATE: off
2023-01-17 11:39:05 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.SECTION: 0
2023-01-17 11:39:05 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP hmstate: off
Event-Monitor
2023-01-17_11:33:33 20_DG_Balkonzimmer_SD_aussen_HM_IP state: on
2023-01-17_11:39:01 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17_11:39:01 20_DG_Balkonzimmer_SD_aussen_HM_IP control: off
2023-01-17_11:39:01 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.STATE: off
2023-01-17_11:39:01 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.SECTION: 0
2023-01-17_11:39:01 20_DG_Balkonzimmer_SD_aussen_HM_IP rssipeer: -92
2023-01-17_11:39:05 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -85
2023-01-17_11:39:05 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17_11:39:05 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.STATE: off
2023-01-17_11:39:05 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.SECTION: 0
2023-01-17_11:39:05 20_DG_Balkonzimmer_SD_aussen_HM_IP hmstate: off
Event-Monitor
2023-01-17 11:42:00 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP on
2023-01-17 11:42:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.SECTION: 2
2023-01-17 11:42:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP control: on
2023-01-17 11:42:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.STATE: on
2023-01-17 11:42:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -86
2023-01-17 11:42:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssipeer: -91
2023-01-17 11:42:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -89
2023-01-17 11:42:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP on
2023-01-17 11:42:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.STATE: on
2023-01-17 11:42:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.SECTION: 2
2023-01-17 11:42:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP hmstate: on
Log-File
2023-01-17_11:42:00 20_DG_Balkonzimmer_SD_aussen_HM_IP on
2023-01-17_11:42:01 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.SECTION: 2
2023-01-17_11:42:01 20_DG_Balkonzimmer_SD_aussen_HM_IP control: on
2023-01-17_11:42:01 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.STATE: on
2023-01-17_11:42:01 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -86
2023-01-17_11:42:01 20_DG_Balkonzimmer_SD_aussen_HM_IP rssipeer: -91
2023-01-17_11:42:04 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -89
2023-01-17_11:42:04 20_DG_Balkonzimmer_SD_aussen_HM_IP on
2023-01-17_11:42:04 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.STATE: on
2023-01-17_11:42:04 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.SECTION: 2
2023-01-17_11:42:04 20_DG_Balkonzimmer_SD_aussen_HM_IP hmstate: on
2023-01-17_11:43:33 20_DG_Balkonzimmer_SD_aussen_HM_IP state: on
2023-01-17_11:43:33 20_DG_Balkonzimmer_SD_aussen_HM_IP devstate: ok
Event-Monitor
2023-01-17 11:47:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17 11:47:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssipeer: -93
2023-01-17 11:47:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -90
2023-01-17 11:47:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.SECTION: 0
2023-01-17 11:47:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP control: off
2023-01-17 11:47:01 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.STATE: off
2023-01-17 11:47:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -81
2023-01-17 11:47:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.SECTION: 0
2023-01-17 11:47:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17 11:47:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.STATE: off
2023-01-17 11:47:04 HMCCUDEV 20_DG_Balkonzimmer_SD_aussen_HM_IP hmstate: off
Log-File
2023-01-17_11:47:01 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17_11:47:01 20_DG_Balkonzimmer_SD_aussen_HM_IP rssipeer: -93
2023-01-17_11:47:01 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -90
2023-01-17_11:47:01 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.SECTION: 0
2023-01-17_11:47:01 20_DG_Balkonzimmer_SD_aussen_HM_IP control: off
2023-01-17_11:47:01 20_DG_Balkonzimmer_SD_aussen_HM_IP 3.STATE: off
2023-01-17_11:47:04 20_DG_Balkonzimmer_SD_aussen_HM_IP rssidevice: -81
2023-01-17_11:47:04 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.SECTION: 0
2023-01-17_11:47:04 20_DG_Balkonzimmer_SD_aussen_HM_IP off
2023-01-17_11:47:04 20_DG_Balkonzimmer_SD_aussen_HM_IP 2.STATE: off
2023-01-17_11:47:04 20_DG_Balkonzimmer_SD_aussen_HM_IP hmstate: off