Help with Logic to trip Reactor sensor

[delbz]

Hi folks. I have created this reactor sensor to turn on the pool pump (water feature) when I have excess solar power during daytime. It works as needed but it won’t set the overall trip status (even when the export condition is true). Q. Can someone who is good with logic please see where my design is wrong?

[LibraSun]

Since you say everything works as expected, I wonder if you’re not being “tricked” by the speed with which the overall (<root>) group is going TRUE? As has been explained elsewhere in the Reactor forums, the TRUE condition can trip fleetingly fast, so fast indeed that the Vera UI simply doesn’t “go green” long enough for your eyes to witness it.

Suggested workaround (or to test my theory): Click the ▼ drop-down next to each of your two subgroups, and enter a whole number (like 4) in the ‘Follow (default) … delay reset []’ box. This will keep the subgroups(s) ‘green’ long enough for visual confirmation.

Another alternative (which I often use with Reactor routines that don’t fire soon enough to wait around for, like yours) is to include a NOTIFY action in the .true Activity, so you know the <root> group indeed ran.

Hope this helps, and that I haven’t completely missed the point of your post, lol!

• Libra

[rigpapa]

The Events section of the logic summary will also tell you what activities have run and when.

[rigpapa]

@delbz

It works as needed but it won’t set the overall trip status (even when the export condition is true). Q. Can someone who is good with logic please see where my design is wrong?

Also, the overall tripped state of an RS is controlled by the root group. You have an AND there with two subgroups, so both groups have to be true at the same time for the root group to be true/tripped.

[delbz]

Hi Rigpapa. Yes. I found that was the best way to make the routines work.
What else should I have instead of AND? It tried a few condition combinations to make it tripped when the root group was true but it didn’t perform the activity.
The activities are triggered from the sub groups instead. It gets the desired effect, but the root group is never actually triggered.

[delbz]

@LibraSun

Another alternative (which I often use with Reactor routines that don’t fire soon enough to wait around for, like yours) is to include a NOTIFY action in the .true Activity, so you know the group indeed ran.

Clever. Thanks. I tried this and no, it didn’t alert - so mustn’t be triggering at all.