Dear Community,
I’m experiencing some strange behavior with one of my KNX block objects. Here is the setup. I’ve configured a contact item that is used to represent my rain alert.
The item is linked to two thing channels. The first channel is an MQTT channel that receives rain alert messages as values 0
if no rain is falling and 1
if rain is falling. The values are mapped to the corresponding values CLOSED
and OPEN
on the channel configuration.
The other thing channel is a KNX channel configured as a contact-control
channel with the matching group address. On the KNX side the GA is connected to the block object of an actor (in this case a MDT Jalousie actor) that drives my roof top windows.
The use case intended is to close the roof top window if it starts raining and go to the previous position if the rain stops.
So far this setup is working. At least for a while. When the alarm flag is received by the MQTT channel, it is forwarded to the KNX side and blocks the actor. When the alarm flag reset is received, it is also forwarded to the actor and unblocks it.
Now, if there is no alarm received for about 30 minutes, the roof top window is suddenly blocked. No message was received on MQTT and no message was forwarded to KNX. It seems like the actor forgot about the last state of the block object and thinks he is blocked now.
The actor stays in this state until it receives another write to the block object of 1
followed by a 0
which in fact toggles the alarm. The same can be achieved if I write to the alarm GA with ETS. Reading the GA is resulting in a refresh event on openHAB, upon openHAB writes back the old value. But this does not unblock the actor.
Has anyone seen a similar behavior or can give advice, what is wrong here? I’ve added the configuration of the item and the connected thing channels below.
Configuration of the rain alarm item
UID: mqtt:topic:4b925e7086:5a969c13f1
label: Regensensor Dach
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:4b925e7086
location: Dach
channels:
- id: regenalarm
channelTypeUID: mqtt:contact
label: Regenalarm
description: ""
configuration:
stateTopic: regensensor/regenalarm/state
closed: "0"
open: "1"
Configuration of the MQTT channel
UID: knx:device:bridge:6570664e
label: Extern
thingTypeUID: knx:device
configuration:
pingInterval: 600
readInterval: 0
fetch: false
bridgeUID: knx:ip:bridge
location: Technikraum
channels:
- id: C
channelTypeUID: knx:contact-control
label: Regenalarm
description: null
configuration:
ga: 0/2/1
Configuration of the KNX channel
Configuration of the GA for the rain alarm