Reconfig of Driver Causes Built In Triggers to Fire

[gReatAutomation]

I have the RadioRA2 driver and am using a triggered event (Is Load Change For) to do some things. The triggered event is specific to a load change from a specific switch and a load state (on).

When I reconfig the RadioRA2 driver, this triggered event fires off.

Is this normal behavior?

[Dean Roddey]

Yeh, it's very hard to avoid. It is a legitimate change to a valid state, so it gets reported. It would require getting some info down way into the driver architecture and each driver to explicitly try to not do this, which would be really messy. So it's one of those where we know it's not optimal, but it's hard to avoid.

[gReatAutomation]

thanks for the context.