[Solved] FGFS-101 Flood Sensor with multiple Flood Alarm Channels --> multiple rule executions

I just added a FIbaro FGFS101 to my system and it shows 2 Flood Alarm channels. If I link it to an item on one channel it shows up linked to both.

And when I run a rule against that item, the rule is actually executing three times (I’m assuming they are related but can’t verify):

rule "Flood Sensors"
	Item Sensor_GF_Kitchen_Flood_Dishwasher received update ON
	logInfo("Water Alarm","Sensor Changed" + Sensor_GF_Kitchen_Flood_Dishwasher.state)
	sendBroadcastNotification("Water Detected:  Dishwasher")
	logInfo("Water Alarm","Alarm State")

Resulting in this in my logs:

2017-02-20 21:14:19.917 [INFO ] [e.smarthome.model.script.Water Alarm] - Sensor ChangedON
2017-02-20 21:14:19.920 [INFO ] [e.smarthome.model.script.Water Alarm] - Sensor ChangedON
2017-02-20 21:14:19.931 [INFO ] [e.smarthome.model.script.Water Alarm] - Sensor ChangedON
2017-02-20 21:14:21.217 [INFO ] [e.smarthome.model.script.Water Alarm] - Alarm State
2017-02-20 21:14:21.531 [INFO ] [e.smarthome.model.script.Water Alarm] - Alarm State
2017-02-20 21:14:21.888 [INFO ] [e.smarthome.model.script.Water Alarm] - Alarm State

This is likely caused by the binding receiving the message from the device 3 times. This can happen for many reasons - retries from the device, or if the device is configured with multiple association groups for the same request. One common reason is if you add the controller into more than one association group - normally for Fibaro devices you only need to use the lifeline group.

@Chris That makes sense and is the mistake I made. When I was first struggling to get it to report, I added the additional associations. Thanks as always for setting me down the right path.

1 Like