Update RM rules via another RM rule action

[SmartHomePrimer]

Thanks!

@bravenel

@HAL9000

Under what scenario would you NOT want a required expression to work correctly?

Under the scenario that none of the Required Expressions need to be evaluated at System Start, and there being no point in doing that at start up. None of mine require this. Why would I want to run a bunch of pointless condition evaluations at startup?

@HAL9000

But since it is just iterating through rules that have required expressions and looking at device and variable states (i.e., not having to poll devices or anything like that), it wouldn't seem like it would be a significant hit. I stipulate that I'm speculating. I don't know.

I just happen to believe that doing something pointless is worth not doing. It has nothing to do with "excessive load" or anything like that. I do believe that most Required Expressions don't need this to happen. Restarting a hub is an isolated event, and only a Required Expression that might have changed during the reboot cycle is implicated by this.

Now, if you think every Required Expression should be evaluated on every hub startup, go for it.

With that said, I’d personally would rather have it default to being evaluated on startup anytime I use a required expression, and then if I don’t want it to be evaluated, I turn that option off. Or, the option instead says “Do not evaluate required expression at start up” and it remains disabled by default until I enable it. To me, it seems this would be a lot more user friendly to those that didn’t notice or forgot about that option, like I did.