Condition must occur after -restriction
-
@toggledbits noticed that in MSR you can define "only after" restrictions within the same rule, but not within the same rule set as is the case for RfV (one RS being similar to a rule set).
Is this intentional or have I misunderstood something?
-
Rule Sets in Multi-hub Reactor (aka Multi-system Reactor/MSR) are an organizational construct only and have no contribution to logic. ReactorSensors in Reactor for Vera (R4V) necessarily contributed to functionality at one time in the early days of Reactor, when it was strictly a rules engine and relied on Vera scenes for execution of actions (prior to version 2). It was also a manifestation of the requirement that all plugins are implemented as devices in Vera/Luup (and sensor seemed to be the right choice as a scene trigger). After R4V got its own activities, it maintained its sensor behavior and device structure for compatibility with the prior version, and that never changed.
It was never my intention to create full parity between Reactor for Vera and Multi-hub Reactor, although clearly they share a lot. Notwithstanding that, it is explicitly not true that Rule Sets and ReactorSensors are equivalent structures. They may share some attributes or uses for some people, but it was never my intention to have one be the replacement or analogue for the other.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Rule Sets in Multi-hub Reactor (aka Multi-system Reactor/MSR) are an organizational construct only and have no contribution to logic. ReactorSensors in Reactor for Vera (R4V) necessarily contributed to functionality at one time in the early days of Reactor, when it was strictly a rules engine and relied on Vera scenes for execution of actions (prior to version 2). It was also a manifestation of the requirement that all plugins are implemented as devices in Vera/Luup (and sensor seemed to be the right choice as a scene trigger). After R4V got its own activities, it maintained its sensor behavior and device structure for compatibility with the prior version, and that never changed.
It was never my intention to create full parity between Reactor for Vera and Multi-hub Reactor, although clearly they share a lot. Notwithstanding that, it is explicitly not true that Rule Sets and ReactorSensors are equivalent structures. They may share some attributes or uses for some people, but it was never my intention to have one be the replacement or analogue for the other.
@toggledbits okay, that was a bit badly formed that R4V RS = MSR rule set. Also, don't get me wrong that I would be driving a full parity of these two products.
I raised this up because I think in this case R4V implementation provides more value for the user, and one (at least me
) could create more flexible automations if this "only after" restriction could reference other rules at least in the same rule set, if not even broader scale. -
You can use a Rule State condition in the current rule, though, and reference that condition. While it's not as direct as picking a rule outside of the current rule, the effect is the same. If you want, though, you're welcome to open a feature request PR for direct selection of another rule.
-
T toggledbits locked this topic on
