Gradually turn on lights.

[Tarkus]

@librasun Sure I currently have lua that has multiple "if" conditions that is run on the reaction side. Consider these "if" conditions in the lua the secondary conditions.

Usage senario:

Say you have 3 separate expression / variables with varying values of 0-9 lets call them.

Variable_1
Variable_2
Variable_3

On the reaction side

If variable_1 = 2

Send TV IR code for digit 1

If variable_1 = 2

Send TV IR code for digit 2

etc, etc

delay 1 second

If variable_2 = 1

Send TV IR code for digit 1

If variable_2 = 2

Send TV IR code for digit 2

etc, etc

delay 1 second

If variable_3 = 1

Send TV IR code for digit 1

If variable_3 = 2

Send TV IR code for digit 2

etc, etc

[LibraSun]

@tarkus said in Feature request on reactions side.:

@librasun Sure I currently have lua that has multiple "if" conditions

If I'm following your example correctly, each of your three variables can take on integer values from 0-9 inclusive, derived from the status of some device on Vera (I call it tv here for convenience). And you want to send three separate IR codes determined by each variable's value. Here's how I would do that in MSR (in pseudocode, of course):

EXPRESSIONS:

v1 := getEntity( "vera>tv" ).attributes.<attr>.<val1>
v1 := getEntity( "vera>tv" ).attributes.<attr>.<val2>
v1 := getEntity( "vera>tv" ).attributes.<attr>.<val3>
buttonCodes := ["code0","code1","code2", ... ,"code9"]
c1 := buttonCodes[v1]
c2 := buttonCodes[v2]
c3 := buttonCodes[v3]

SET REACTION:

[Entity Action] ["vera>device_<remote#>"] [x_service_name_send_code] [${{ c1 }}]
[Delay] [ 1 ]
[Entity Action] ["vera>device_<remote#>"] [x_service_name_send_code] [${{ c2 }}]
[Delay] [ 1 ]
[Entity Action] ["vera>device_<remote#>"] [x_service_name_send_code] [${{ c3 }}]

What I'm doing is asking MSR to "lookup" the corresponding buttonCode from an array (conveniently indexed 0 through 9), assigning those string values to c1-c3, and making those substitutions in each successive steps of the Set Reaction.

Am I close to your goal?

[Tarkus]

I am afraid the Global Cache IR plugin that Patrick added support for does not seem to work with expressions in the send code field. I tried to add the hex code for a digit to a Global expression and put ${{Digit_1}} in the send code field but it did not work.

[LibraSun]

Can you show me the valid values which the plugin accepts? (After all, they do exist and are transmitted by Lua, and I haven't yet encountered a value which MSR cannot send, so this makes me doubly curious.) Maybe I need to see more of your actual setup, if you don't mind?

FUN READ: https://kinkeadtech.com/control-ir-devices-with-z-wave/

[Tarkus]

@librasun

Patrick did say the Plugin was really barebone's or something to that effect.

-D5;,p-{in[ji1GS

[LibraSun]

@toggledbits can variable substitution be added to the "Code" field shown?

[toggledbits]

Variable substitution works in all action fields.

[LibraSun]

There you go!

[Tarkus]

yes, it just does not fire when putting the code into a variable.

[toggledbits]

Did you look in the MSR logs to see what was being sent? Did you look in the Vera log to see what was being received?

[LibraSun]

@tarkus said in Feature request on reactions side.:

yes, it just does not fire when putting the code into a variable.

Is MSR giving you any feedback in the Log and/or Status screen? I ask because perhaps you haven't used quotes around the hex code strings when defining your variables, for instance?

[Tarkus]

Have not gotten that far. Just was playing around with this, this morning before my workday started. Will dig into logs when I get a chance.

[Tarkus]

@librasun Definitely did not use quotes, will try that.

[Tarkus]

@librasun Ok the quotes did the trick! So I am assuming for

"code0","code1","code2", ... ,"code9"

I am assuming I am making 10 variables. i.e.

code0="0000 0067 0000 000D 0060 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0018 0018 0018 0422"

ect, ect....

[LibraSun]

@tarkus said in Feature request on reactions side.:

@librasun Ok the quotes did the trick! So I am assuming for

"code0","code1","code2", ... ,"code9"

I am assuming I am making 10 variables. i.e.

code0="0000 0067 0000 000D 0060 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0018 0018 0018 0422"

ect, ect....

Okay, not exactly. In my example, above, I had intended for you to paste all 10 codes, with quotes, directly into the array itself. I now see how cumbersome that would look, and not lend itself very well to editing.

So your approach of creating all 10 variables this way makes more sense... BUT you'd have to reference them in the array without quotes, as in:

buttonCodes = [code1, code2, code3, .... , code9]

and be sure to place this Expression definition after all 10 codeN declarations (this is just a best practice, not mandatory).

[Tarkus]

@LibraSun So this is where I am at and I am stuck. The variable Channel gets pulled in from veras multistring and it gets split into the Character variables. That part works, just trying to work thru the rest.

[Tarkus]

I also forgot to mention that I need to work a "." into the array

[LibraSun]

For starters, you've put spaces between buttonCodes and the [ which will not be interpreted correctly.
Look above at my original example: the syntax is buttonCodes[index] with no spaces. (edit: extra spaces should be OK)

Secondly, your definition of buttonCodes itself shows just a long comma-separated list, which cannot work as is. To make it an array, it must start with [ and end with ].

Third, you reference buttonCodes in other variables, but named the expression ButtonCodes which is different. These things must match exactly.

Fourth, some of your CharacterN definitions result in alphanumeric characters which are NOT "just 0 through 9" -- like "x" or "." -- hence they CANNOT serve as the index for an array lookup. Another approach is needed (example: use an Object, per the suggestion below).

This is proving more challenging than expected -- even turning everything into an Object would pose its own hazards at this point -- but getting the syntax right is way more than half the battle!

[toggledbits]

Also note that the data type of most of the index expressions is a string. Use int() to make sure it's a number: C1 = ButtonCodes[ int( Character1 ) ]

Also, it may be useful to break everything out this way while you're testing and figuring it out, but ultimately, you may want to combine them: C1 = ButtonCodes[ int( substr( Channel, 0, 1 ) ) ]

[Tarkus]

The X's are just left over remnants of the lua process I was using. It was just padding and acted a indicator that the channel was at a end and stop the process. So channel 7.1 would come over as 7.1xx. I set 5 characters to accommodate a 5 digit channel i.e. 135.1 I will take a look at your suggestions.