Local notification methods?

[toggledbits]

@cw-kid said in system capability zwave_scene_controller:

Not sure what's going on but it's a problem somewhere.

No, it's a Vera thing. There are three things going on that make their implementation choices for scene controllers really sticky...

1. When Vera reloads/reboots, it sets a timestamp on every state variable on every device to the startup timestamp. Timestamps are not stored in the persistent user_data, so any previous timestamp is lost. Every time Vera starts, every state variable get a new timestamp.
2. Not only do the timestamps not appear in user_data for the states, they are not exported with the user_data or status queries. In other words, the timestamps are locked inside Vera's head and not available outside.
3. When you set a state variable on Vera, if and only if the value changes is the new value set and the timestamp updated. And in turn, for any plugins that are running on Vera and have watches on those state variables, their callbacks get called. If you attempt to set a state variable to the same value it already has, the timestamp and value and not modified, and the watch callbacks are not called. But there's an exception. Probably to support their crazy way to handling scene controllers, any state variable that starts with sl_ will update its timestamp even if you rewrite it with the same value it already has.

On the Vera, it works out that any plugins that handle the scene controller state variables, like Reactor or PLEG, or my SceneSlayer plugin, or the other scene controller plugin whose name escapes me at the moment, handle all this OK because, principally, the watch callback doesn't get called at system boot, and does get called otherwise. So it's pretty easy to detect repeat activations of the same scene, although it still takes some effort, as seen in the approaches one must use in both Reactor for Vera and PLEG.

Off the Vera, however, the combination of the above three choices are just a near-fatal limitation. Without a stable timestamp that comes from the Vera itself, there's just no way to tell if you're looking at an original value or a repeated value.

Anyway, there's still one good alternative, and it's simple: after you act on the scene activation (i.e. in the Set reaction), set the source state variable to 0 or some other value outside the range of normal (-1 or -999 or whatever). I've referred to this in the notes for your PR, so check there for more specifics.

I've tested it with my scene controllers in MSR and it works fine.

[Edwin1972]

It works in Reactor on Vera and Openluup
maybe this is the solution

Nov 22, 2019

Double click/triple click is detected with reactor

I have a number of fibaro roller shutter 2 with which you can also control scene by means of 2x click down/ up button. I use PLEG to arrange this. I found the example on a website. See the example below. Is it also possible to do that with reactor?

[cw-kid]

I think its working OK now:

Trigger:

Reaction:

I can double click the wall switch and each time the Reaction runs and my HTTP request is sent to Node-Red which in turn sends a TTS announcement to a Google Home speaker saying "This is a Test".

If I reload the Luup engine on Vera the rule no longer fires.

I then configured this rules Set Reaction to its actual purpose of turning on or off another light using the toggle.toggle.

This also works and now when I double click the Lounge light switch it turns on the kitchen ceiling light.

I will transfer all my rules for this from PLEG to MSR.

One thing I need to check however, I also use Fibaro Roller Shutter 2 modules for this same purpose as well. So they might need mapping. I will create a device dump for one of these modules.

Thank you very much.

EDIT: I've setup all the MSR rules now for the various Fibaro Dimmer 2 modules. Everything is working. However it does seem a little slow to run the action than what PLEG was.

I guess this is the price to pay for having MSR not running locally on Vera and on the Raspberry Pi instead.

[cw-kid]

I've just tried a Fibaro Roller Shutter 2 module and as suspected it says: zwave_scene_controller.scene_activated? (missing)

So cannot setup these wall switches for double and triple click events till its mapped.

Thanks

For future reference, this is the Scene Activation information for the Fibaro Roller Shutter 2 module.

[cw-kid]

Something strange with these Fibaro Roller Shutter 2 modules.

I've updated the vera_devices.json file for the mapping and restarted MSR.

When I Double Click UP (S1) the sl_SceneActivated changes to 4, so that is OK and works.

However when I double click DOWN (S2) sl_SceneActivated remains at 0 its value doesn't change to anything. (Note I am setting them to 0 as part of the Set Reaction)

Same when I triple click DOWN (S2) sl_SceneActivated remains at 0.

PLEG is really using LastSceneID instead of sl_SceneActivated and they are the numbers above in that screen shot 14, 24 and 25 etc They are the numbers in PLEG I monitor for.

However we cannot see LastSceneID in MSR so I cannot use those numbers in my rules.

I have tried two different wall switches that are Roller Shutter 2 modules and they both behave exactly the same as I just described.

Which is somewhat confusing. So as it stands I can't use these Fibaro Roller Shutter 2 modules in MSR with scene activation.

I will test some more and maybe check their user manual and parameter settings or something.

The Fibaro Dimmer 2 modules on the other hand they are all working great with MSR no issues with any different types of clicks.

EDIT:

It says 0 in Vera GUI as well after just doing a double click down.

[toggledbits]

Can you confirm that the value of sl_SceneActivated behaves the same way on the Vera alone, without looking at MSR? Look at the state variables in Advanced > Variables for the device. Turn off your MSR rules or stop MSR to keep it from doing anything while you're testing, so the test is clean. To see changes accurately on Vera, you'll need to hard-refresh your browser after every test attempt, or alternately, click the "Edit" link on the state variables (you don't need to change them, just bring them into the editor, as this populates the correct current value when it opens; confirm the value and then just close the editor and move on to the next variable).

[toggledbits]

FYI, I threw in the towel last night and admitted defeat. Fibaro has once again claimed a victim. There's a new extended capability that has the last_scene_id and last_scene_time values.

I have a dozen scene controllers in my house. Leviton, EnerWave, ZRC-90s, and Hank. Not a one of them defines those two variables, and they're not declared in the service (and as I said, the service isn't even declared on the device type -- Fibaro support is kludged, apparently). I hope the new dev team over there, for everyone's sanity, takes a strict approach to consistency in handling devices. Between scene controllers and thermostats, this is a horrible legacy in current Vera firmware.

[cw-kid]

@toggledbits

Sorry for the late reply I've been feeling unwell today.

I've not done the last test yet, where I disable the MSR rules and then look to see if the sl_SceneActivated value changes from 0 in the Vera web GUI ? When doing double and triple clicks on the switch etc.

I've not installed any new version of MSR either today. So we can now see the last_scene_id values now instead in MSR ?

Thanks for your efforts on this.

[toggledbits]

@cw-kid said in system capability zwave_scene_controller:

So we can now see the last_scene_id values now instead in MSR ?
Thanks for your efforts on this.

Yes. I tried to stick to standards, but since Vera really didn't, there's nothing I can do if I want it to work at all. I think we did a good job of pursuing every avenue before taking that step, but at the end of the day, we can't make something out of nothing, and have to use what we have available.

P.S. Sorry to hear you're not well. Rest up; hope you're on the mend soon.

[cw-kid]

Yeah I hear what you are saying. I'll do that last test anyway a some point, be interesting to see actually what does happen with that sl_SceneActivated variable in Vera.

Might be a few days, gonna take things easy for a while.

[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.