Arming Envisalink panel from MSR

[cw-kid]

Don't think my LUA code is running anymore:

Has something changed?

[cw-kid]

I can select x_vera_sys.runlua OK on my Vera Edge controller.

However on my Vera Plus controller I see as in the above screen shot.

Maybe I broke something when I tried to rename the Vera Plus controller the other day ?

I also added the Vera Edge as a second controller the other day, so maybe related to that?

[Crille]

@cw-kid Are you using this to run an existing scene on Vera?

[cw-kid]

@crille

Yes in this example I am using some LUA code to randomly run various existing scenes on the Vera.

I also have other MSR rules that either reference LUA code directly in that box in the Reaction or call LUA code stored in the VeraScenes.lua file on the Vera.

All the MSR rules that were using runlua are now all saying "missing".

[Crille]

@cw-kid Ah, ok. I missed the random part and wondered why you didn’t just selected the scene in the entity list
I agree, something looks broken and unfortunately I have no solution for you.

[cw-kid]

Yeah I have some scenes in Vera that will just set my Fibaro RGBW module / garden lights to different colours.

This LUA code will randomly run one of those Vera scenes. And the MSR rule pulses every 15 minutes, so the colour of the LED strip will change randomly every 15 minutes etc.

I think I will remove the "lab" Vera Edge controller from MSR and just have my production Vera Plus controller connected again on its own.

See if that fixes this "missing" runlua function.

[cw-kid]

I've removed the second Vera Edge from the reactor.yaml file and restarted MSR and the x_vera_sys.runlua is now back again and working for my production Vera Plus (first controller).

So this appears to be a bug.

Logged:

https://reactor.toggledbits.com/mantisbt/view.php?id=155

[toggledbits]

@cw-kid Found it, will have it fixed.

Did I ever bother to ask why you just don't run the scene entity using its native run action?

[cw-kid]

@toggledbits said in Vera Run LUA Missing:

Did I ever bother to ask why you just don't run the scene entity using its native run action?

I am aware I can call Vera scenes directly using the scene entity and I do have some other rules that do that.

However for this particular rule as I already explained I am running this LUA code to have various Vera scenes run randomly.

local scenes = {"172", "173", "174", "175", "176", "271", "272"}
local tmp_random_number = math.random(1,7)
local  scene_id_to_launch = scenes[tmp_random_number]
luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = scene_id_to_launch}, 0)

[cw-kid]

Appears to be fixed in version 21090. I can now see and select x_vera_sys.runlua on both Vera controllers.

Thanks