Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: More than 4 triggers
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
What can be done if you have more than 4 possible triggers?

I have 5 doors to the deck.  If any one of them is opened I want the deck lights to turn on.  Today using ISY I can have as many devices as I want in the trigger with an OR statement.
(01-08-2020, 08:17 PM)simplextech Wrote: [ -> ]What can be done if you have more than 4 possible triggers?

I have 5 doors to the deck.  If any one of them is opened I want the deck lights to turn on.  Today using ISY I can have as many devices as I want in the trigger with an OR statement.

You might look at the logic server.  You could have one variable that is always true if one of the 5 doors to the deck is true.  Then you could set a trigger on that and turn the lights on.
(01-09-2020, 12:18 AM)kblagron Wrote: [ -> ]
(01-08-2020, 08:17 PM)simplextech Wrote: [ -> ]What can be done if you have more than 4 possible triggers?

I have 5 doors to the deck.  If any one of them is opened I want the deck lights to turn on.  Today using ISY I can have as many devices as I want in the trigger with an OR statement.

You might look at the logic server.  You could have one variable that is always true if one of the 5 doors to the deck is true.  Then you could set a trigger on that and turn the lights on.
I haven't looked at Logic Server yet so I will.  thanks
Another option is to just trigger on any field from that driver that matches some pattern (though be careful so that you don't react to too many things that you don't need to), and then check the doors within the action. If it's something that's not going to happen often, that's lower overhead than the logic server, which will constantly be monitoring them. For something that happens a lot, then the logic server is more efficient since it always has the info.
(01-09-2020, 09:21 AM)Dean Roddey Wrote: [ -> ]Another option is to just trigger on any field from that driver that matches some pattern (though be careful so that you don't react to too many things that you don't need to), and then check the doors within the action. If it's something that's not going to happen often, that's lower overhead than the logic server, which will constantly be monitoring them. For something that happens a lot, then the logic server is more efficient since it always has the info.

I think the RegEx option will work.  I plan on replacing the Insteon contact sensors someday with ELK but until then I can rename those sensors with <room>-<door>-Ext and RegEx against that to only capture the Exterior doors to the deck.  I only have exterior doors to the deck... I have no "front door".  Confuses guests and pizza delivery people Smile