Triggered Event and Standard Triggers

[gReatAutomation]

Wanting to know if there is a way to add latching to the standard set of triggers in CQC. Specifically the alarm related ones. For my alarm driver (v2 compatible) I can see, for example, the motion sensors firing off in System -> Monitor -> Event Triggers.

If I add latching to the zone in the driver config will the latching work?

[Dean Roddey]

You can't latch those. It's OK that they are firing. That's normal. In some drivers that have a lot of things that could send triggers, they will let you configure whether it should be sent on any given light, zone, etc...

[gReatAutomation]

So how do we manage or create triggered events when a "notready" is constantly firing? I am trying to create some triggered events that take place when certain doors open but I only need it to happen once and not constantly until the door is back in a Secure state.

[Dean Roddey]

They shouldn't be constantly firing. They should only fire when a zone transitions into not ready state (or any other state), i.e. only when there's a change. You would see other zones firing of course. If that's what you mean, just filter for the specific zone you want the trigger to respond to.

[gReatAutomation]

The standard alarm triggers do in fact fire every second until state=secure see below output from System->Monitor->Event Triggers








This is why I am asking how to create a triggered event on a zone when it is "notready" when that trigger will fire every  second and if we cannot add latching to them

[Dean Roddey]

What driver is that? It absolutely should not be sending out continuous triggers like that. It should only send them if the value changes. The correct thing to do here is to fix the driver.