In OH2.2 with KNX1, openHAB gets information about moving or stopping rollershutters by “received command”.
haus.item
Rollershutter EG_Wohnzimmer_Rollladen_Terrasse_Rechts "Terrasse rechts [%.0f %%]" <rollershutter> (gEG) { autoupdate="false", knx="1.008:4/1/7, 1.010:4/1/8, 5.001:4/4/33+<5.001:9/3/7" }
When I press DOWN followed by STOP on a KNX-switch, these are the results in OH2.2:
ETS monitor
|#|Zeit|Dienst|Flags |Prio|Quell-Adresse|Quell-Name|Ziel-Adresse|Ziel-Name|Rout|Typ|DPT|Info|
|6783|04.06.2018 14:30:44,572|vom Bus||Low|1.1.39|6324 5f-triton-Taster,UP|4/1/7|R104 Wohnzimmer Terassentür rechts Rolladen auf/ab|6|GroupValueWrite| 1.008 Auf/Ab|$01 | Ab|
|6785|04.06.2018 14:30:48,224|vom Bus||Low|1.1.39|6324 5f-triton-Taster,UP|4/1/8|R104 Wohnzimmer Terassentür rechts Rolladen stop|6|GroupValueWrite| 1.010 Start/Stop|$00 | Stop|
OH2.2 Log
2018-06-04 14:30:42.691 [ome.event.ItemCommandEvent] - Item 'EG_Wohnzimmer_Rollladen_Terrasse_Rechts' received command DOWN
2018-06-04 14:30:46.343 [ome.event.ItemCommandEvent] - Item 'EG_Wohnzimmer_Rollladen_Terrasse_Rechts' received command STOP
2018-06-04 14:30:48.404 [vent.ItemStateChangedEvent] - EG_Wohnzimmer_Rollladen_Terrasse_Rechts changed from 0 to 10
The “received command DOWN”- and “received command STOP”-events are important for me, as they are used in serveral rules.
After updating to OH2.3 with KNX2 the behavior chances.
knx.things
Bridge knx:ip:knx-ip-gateway "KNX/IP Gateway" @ "EG Vorzimmer" [
ipAddress="192.168.1.55",
portNumber=3671,
localIp="192.168.1.44",
type="TUNNEL",
readingPause=50,
responseTimeout=10,
readRetriesLimit=3,
autoReconnectPeriod=1,
localSourceAddr="0.0.0"
] {
Thing device knx "KNX dummy for openHAB" [
address="1.1.2",
fetch=false,
pingInterval=300,
readInterval=0
] {
Type rollershutter : EG_Wohnzimmer_Rollladen_Terrasse_Rechts "EG_Wohnzimmer_Rollladen_Terrasse_Rechts" [ upDown="4/1/7", stopMove="4/1/8", position="4/4/33+<9/3/7" ]
}
haus.item (2.3)
Rollershutter EG_Wohnzimmer_Rollladen_Terrasse_Rechts "Terrasse rechts [%.0f %%]" <rollershutter> (gEG) { channel="knx:device:knx-ip-gateway:knx:EG_Wohnzimmer_Rollladen_Terrasse_Rechts" }
haus.sitemap (2.2 and 2.3)
Switch item=EG_Wohnzimmer_Rollladen_Terrasse_Rechts label="Terrasse rechts [%.0f %%]"
When I press DOWN followed by STOP on a KNX-switch, these are the results in OH2.3:
ETS monitor
|#|Zeit|Dienst|Flags |Prio|Quell-Adresse|Quell-Name|Ziel-Adresse|Ziel-Name|Rout|Typ|DPT|Info|
|6688|04.06.2018 14:25:21,432|vom Bus||Low|1.1.39|6324 5f-triton-Taster,UP|4/1/7|R104 Wohnzimmer Terassentür rechts Rolladen auf/ab|6|GroupValueWrite| 1.008 Auf/Ab|$01 | Ab|
|6690|04.06.2018 14:25:24,161|vom Bus||Low|1.1.39|6324 5f-triton-Taster,UP|4/1/8|R104 Wohnzimmer Terassentür rechts Rolladen stop|6|GroupValueWrite| 1.010 Start/Stop|$00 | Stop|
OH2.3 Log
2018-06-04 14:25:19.600 [vent.ItemStateChangedEvent] - EG_Wohnzimmer_Rollladen_Terrasse_Rechts changed from 0 to 100
2018-06-04 14:25:19.659 [ome.event.ItemCommandEvent] - Item 'EG_Wohnzimmer_Rollladen_Terrasse_Rechts' received command 100
2018-06-04 14:25:24.396 [vent.ItemStateChangedEvent] - EG_Wohnzimmer_Rollladen_Terrasse_Rechts changed from 100 to 10
As one can see there is no “received command DOWN” or “received command STOP” anymore. How can I get them back?
Greetings from Vienna, Austria
Peter