That's what I do. I use a virtual dimmer and set it's level to the value of a GV in RM. That way it can be displayed on dashboards. That limits it to a value between 0 and 100, but for my use so far that has been OK.
Yes, it seems to work for me. I use "Set color temperature per mode" and insert %variable% in the color temperature field. Using per mode so I can choose different levels. This one's a different variable that uses 2000 as the lowest temperature.
I think something else will have to be written to update the bulbs if they're already on.
All actions are handled sequentially with one notable exception: if a delay is placed on an action, that action, and only that action, happens after that delay.
Global Variables are a creature of Rule Machine, so other apps cannot access a RM Global Variable -- only rules can access them.
No, it is not. However, it is possible to manage a virtual device that reflects the value of the variable. Such a feature will be coming to RM.
Rule Machine just got four-dimensional.
Yes, color temperature can be set by a variable, in just the form you state.
Can variables not currently accept decimals?
errorjava.lang.NumberFormatException: For input string: "321.42" on line 5464 (allHandlerT)
You have to have a decimal variable for decimal value.
I'm wondering if it might be useful to have a global variable for "current time" to reference in rules - trying to think about how to generate it.
Bruce, quick question about how END-REP and Stop Repetition behave. Below are two different repetitions that are supposed to only happen between two different blocks of time based on a condition. I've set END-REP, but I am unsure if it will stop repeating when needed. Will each END-REPs stop upon truth change? Or do I need to manually initiate the stop?
NEVERMIND, I've RTFM and found it right there:
A Repeat Actions, like any action, can have a condition specified. If the condition is false, the Repeat Actions block of actions will not be executed. If the condition becomes false during repetition, the repetition will be stopped (not in the case of Repeat a selected number of times). This provides three features well known to computer programmers; A while-loop, a for-loop and repeat-until loop. The while-loop runs only if the condition is true, and stops if it is false. A for-loop runs for a fixed number of times, but if a condition exists, it will only start that iteration if the condition is true; the condition is not retested during iteration. A repeat-until loop runs until a condition becomes true, running at least once.
Okay it's someone else's turn to ask the stupid questions now
You can put the current time into a String variable, by using %now%. You can also get the hour and minute separately, in Set Variable.
@bravenel I think I found a bug... I hope its a bug.
I changed some trigger values and the actions aren't updating to the new values. I did click on update rule but nothing changed.
I'm not sure they are designed to be updated automatically.
When you first create the rule it puts any triggers you set into the conditions part of the rule for convenience, but if you update the trigger events I'm pretty sure you have to change it manually in conditional actions. I can't think of an example of the top of my head, but I guess there are cases where you may not want it to automatically update the conditions just because you've changed the trigger.
There is no way to edit the triggers.....
That means you have to delete the entire rule just to fix it ? That's insane coding.
Unless something is wrong on your system, you can edit triggers or actions by clicking on the appropriate section of the first page of the rule. That then brings up a the edit screen for that section
I see no way to edit the actions. I even tried opening the hub in a incognito window and same effect.
Try selecting a capability (any) and see if you just have to “finish” the flow once to get your buttons back. I had that once or twice when I started to change something without finishing it