Gradually turn on lights.

[cw-kid]

That sl_SceneActivated variable does change OK for the Fibaro Dimmer 2 modules, as I said I have all those scene activations working and setup now in MSR.

But for the Fibaro Roller Shutter 2 modules it only correctly changes that sl_SceneActivated variable for double clicks UP (S1).

For double click down (S2) and triple click down (S2) it doesn't appear to be changing at all. Which is weird.

I wonder what the Fibaro Relay Switch modules do also? I do have some of those, but I am not using them with scene activation. I saw in the vera devices .json you also had a mapping for the Fibaro Relay Switch modules.

[toggledbits]

@cw-kid said in system capability zwave_scene_controller:

I saw in the vera devices .json you also had a mapping for the Fibaro Relay Switch modules.

Yes, but no mapping yet, so when you get around to it....

[cw-kid]

I've done the last test on these Fibaro Roller Shutter 2 modules.

Its as I have said before. The sl_SceneActivated does not change value for S2 Double click or S2 Triple Click it remains as 0 in the Vera web GUI.

This is S1 Double click this does change to 4.

So there's no way this would of worked fully with MSR without also being able to see the Last_Scene_ID numbers.

[cw-kid]

In the new version of MSR this is what I see now:

I think I am going to switch all my rules to use the last_scene_id instead as its these numbers that are in the fibaro user manuals for scene activation.

I guess to reset the rule so I can repeat a double click I will have to reset the last_scene_id if possible ?

Changing this:

To this:

I will test it and see if it works.

EDIT:

Initial tests say everything is working as expected now using the lastsceneID numbers instead of sl_sceneactivated.

Thank you very much for enabling this functionality in MSR.

[LibraSun]

I can't wait to map all my Nodon battery-powered remote buttons to MSR routines once able. Mine can do single-, double- and long-press as well as the "release" action, netting me 16 possible actions. It even has an LED with programmable behavior (which I've never succeeded in altering; it just remains off).

Have you noticed that controlling scenes with MSR is far faster than MFL on Vera?

[toggledbits]

@librasun said in system capability zwave_scene_controller:

Have you noticed that controlling scenes with MSR is far faster than MFL on Vera?

I've noticed that everything is faster. They appear to have considerable overhead in setting up and calling plugin code when it needs to happen. Their job scheduling can also delay the plugin's response when the system is busy doing other things. Luup is trying to be very defensive around plugins, but that comes at a performance cost. They made similar decisions (not surprisingly) in the new firmware that I warned them about early on, in some ways worse. We'll see how that turns out. I've heard they've reversed themselves, but since I'm not playing with that stuff any more, I haven't confirmed it myself.

[cw-kid]

I think these scene activations with my Fibaro modules are slower on MSR running on the Pi, than they were with PLEG running on Vera.

But that is to be expected I guess. I have about a 2 or 3 second delay after doing the clicks on the switch to when the action is run. Sometimes longer delays.

But its working which is the main thing.

[toggledbits]

Can you send me a log? I'd like to see if there's some obvious delay going on in MSR. And just to make sure, you're not using any condition options on the scene variable test, right?

[cw-kid]

I am not using any Constraints if that is what you mean.

Yes I can do some logs at some point.

There was one particular Fibaro Roller Shutter 2 module in the Kitchen, that was being very slow with the action running after the clicks.

I'll test that module again and look at logs.

As for all the others, 2 seconds seemed to be about the time it takes after clicking, for the action to run. Some of my actions are calling existing Vera scene I had in place, I can probably tidy that up a bit and control devices directly via MSR in the action maybe that may help.

[toggledbits]

OK. In case you want to poke at it yourself, and for the benefit of other readers... if you modify the level in logging.yaml for Rule to 6 (that is, find the line in the file that reads Rule: and change the level on the line below that one to 6), you'll get some deeper debug from all rules. Then restart MSR and activate your Fibaro device in whatever way you want to test.

At that level, you should be able to find a logged entry in reactor.log with the string "launching evaluation for" that references your Fibaro device. This is the detection of the change on the Fibaro. That causes the rule to be evaluated, and you'll see that happening shortly after. Follow that along, and you'll see "Enqueueing" followed by the name of the set or reset reaction that is to run based on the rule's result state. That will be followed by the execution of the reaction, which comes mostly from the Engine, so you'll see it report "Starting reaction" (followed by the reaction name), and then the steps. The reaction is finished executing when it logs "all actions completed". If you note the timestamps on all these, you'll get a feel for how fast its responding in the three major phases: detection -> evaluation -> execution.

[Edwin1972]

I want to start moving ReactorOpenLuup to MSR and have the following problem. In Reactor OpenLuup I have set up below. Update does not show in de list in MRS. @cw-kid @ cw-kid What kind of setting do you use to use double click in MRS with roller shutter 2?

[cw-kid]

@edwin1972

I am just using the LastSceneID

Here is an example for S2 Double Click which has a number of "24"

You also need to reset the LastSceneID back to 0 in the "Set Reaction".

The different SceneActivation numbers can be seen from the Fibaro Roller Shutter 2 user manual:

[Edwin1972]

Thanks for the quick response. It works!