Low-priority GUI feedback
-
2021-04-13T14:43:07.943Z <Rule:5:Rule.js:970> Rule#rule-knay6sc6._evaluate() trigger state now false (was false).This is saying the trigger state is false. It says that in both cases. It follows by saying the rule state is false (which is correct if the triggers are false). The constraints are indeed true, but if the triggers are false, the rule state will still be false.
@toggledbits said in Low-priority GUI feedback:
This is saying the trigger state is false.
Much appreciated, and sorry for the n00b question. I've spent the morning chasing down gremlins left and right surrounding this "Alexa Director" endeavor, and I give up. I inadvertently created a thicket of Franken-Rules which deserve to go back into the grave.
Think I'll stick with Virtual Switches after all, as they are far more deterministic, predictable, and UI friendly than any attempt I've made thus far to reinvent them with pure logic.
Ha ha, I was having Triggers accidentally trigger multiple Rules and then, once tightened down even further, NONE of the Rules.
I will henceforth regard the VS as a necessary resource on Vera, especially when used as an adjunct to Alexa Routines.
-
Not a n00b question at all. I'd really like to see for myself what's happening. If you still experiment with it more, crank the rule's log level to 6, and send me the results.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Not a n00b question at all. I'd really like to see for myself what's happening. If you still experiment with it more, crank the rule's log level to 6, and send me the results.
@toggledbits said in Low-priority GUI feedback:
I'd really like to see for myself what's happening. If you still experiment with it more, crank the rule's log level to 6, and send me the results.
I'm sure to fiddle around further, but intend that to happen with inconsequential test Rules rather than some of my most prized "Leaving Home", "Coming Home" level workflows.
Will advise... thx.
P.S. You may legitimately ask, "Why are you trying to avoid Virtual Switches in the first place?" Answer: Because I hate having to create them, configure them, propagate them through the Vera UI (rename, relocate, hard refresh) and again through the Alexa ecosystem (name, discover, configure in Routines, etc.). I've been searching for a quick-to-expand alternative method, one that presents itself in all four UIs (Vera, MSR, Alexa, VeraMobile) with rapid adaptability to new workflows (e.g. "Time for Doing a Puzzle") which I might in turn choose to knock down after a few days.
-
@toggledbits please excuse this umpteenth FEATURE REQUEST, but would it be possible to include "Expressions" among the items listed by the "Insert Entity Attribute Value" button? While I'm not 100% certain you intend for other Rules' variables to be "visible" in the Expressions section, if they are accessible here, then having the ability to "build" such a reference instead of by rote would be helpful.
Example:
varRuleA := 1 + varRuleB[3]
// Insert tool saves having to memorizevarRuleBname and structure -
Just go ahead and open PRs for feature requests. For the benefit of all reading, clear description and use case are a must. I'll add them to the wish list.
-
Not many PRs being opened these days. That's why there aren't many builds. FYI, each morning I plan my work around (a) long-term tasks that are in progress (some of which are PRs that can't be fixed in a day), and (b) new PRs. I do not include discussions here in those plans.
-
I'm not sure I understand your question...
also... this is that thing... topic title is "Low priority GUI feedback", and your question is about lexpjs/expressions?
-
T toggledbits locked this topic on
