@terrydew. Good catch on that bug. I was able to duplicate the problem and found there were actually two issues. First, the variable "Off" processing was due to a bug, and is fixed in 0.9.14. However, the problem with the lights blinking on and then off was due to reversing the logic in the variable settings. In this case, when a zone is faulted, and you want an On action, the variable should be set to True, then set to False when the zone is restored.
After fixing the bug, here is what I did that worked.
First I created triggers to maintain variables that tracked the zone states (True = fault, False = clear).
Next, I created a Group Trigger that looked for ANY of the variables to become true, and if so, had three actions:
1) Turn on a light
2) Change the variable alarmChanged to True
3) after a 0.02 minute delay change alarmChanged to False
EDIT:
Now that I think about it, there is probably no need for steps 2 & 3 here. You only want to test that ALL zones are cleared when one becomes Off. There is no point in testing when a zone becomes faulted.In the same Group Trigger, for the Off trigger I selected the same variables I used for the On trigger, and for the Off Action I selected a Action Group that did the following:
1) Change the variable alarmChanged to True
2) after a 0.02 minute delay change alarmChanged to False
Finally, created a regular Indigo trigger that looked for variable
alarmChanged to become True. The trigger had several conditions ALL of which had to be logically True. Then, I selected each zone tracking variable and set the condition to "is false" (I.e. all variables had to be false as a condition for executing the action. Finally, the Action turned off the light.
Now that we (hopefully) have all of that squared away, I think you can make this a bit easier. I think IanS changed his GE Caddx plugin to be directly compatible with the Group Trigger plugin. So, you should be able to just track the devices directly in the Group Trigger without needing variables (except for
alarmChange, which triggers the ALL condition test). One caveat, there have been some changes in Indigo since IanS made that change and updates to the Group Trigger may have broken the ability to read the Caddx device states. If that his the case, let me know and I will get with IanS to get it fixed.