Why different types of Triggers within openLuup & ALTUI

[akbooer]

[CatmanV2]

Don't beat up over it. Whenever it gets fixed (if it gets fixed) is good.

C

[ArcherS]

I included a ZRC90 remote to Z-way. The inclusion was without problems, and in Z-way you can see what button is pressed.

In OpenLuup I get the same variables as Catman has listed above. I tested and the two variables "zway_61-0-91-DS" and "zway_61-0-91-DS_LastUpdate" on the remote device are updated on key presses.

Depending on what you press "zway_61-0-91-DS" get the following values:
Btn 1 single press: 10
Btn 2 single press: 20
...
Btn 8 single press: 80

Btn 1 double press: 13
Btn 2 double press: 23
...
Btn 8 double press: 83

Btn 1 press&hold: 11
Btn 2 press&hold: 21
...
Btn 8 press&hold: 81

Each time a button is pressed zway_61-0-91-DS_LastUpdate is also updated with a new time.

So far so good, the above two parameters gives the possibility to capture the various key presses on the ZRC90.

What does not work is that I get the same problem as I did for the Zwave.me wall controller, i.e. that the two variable are not updated in Reactor on key presses.
@akbooer is this something that can be fixed?

I am running OL 20.7.4b and Z-way plugin 20.5.12.
(The key presses on the Zwave.me wall controller are still working.)

//ArcherS

[akbooer]

@ArcherS said in Remotec ZRC90:

What does not work is that I get the same problem as I did for the ...

Yes, and it's for the same reason:

@akbooer said in Remotec ZRC90:

The variables that your are describing are really internal to the plugin and only shown for diagnostic purposes (recall that, after all, this is still only a prototype, which needs a degree of re-engineering.)
What you can’t know, is that they are different from regular device variables (for very good reason) in that they do not trigger variable watches when changed, as you have discovered.

What's interesting, is that the variable zway_61-0-91-DS shows that it comes from Command Class #91 which is "Central Scene", something I have not seen [pun intended] before. This should be easy to fix.

@ArcherS said in Remotec ZRC90:

Depending on what you press "zway_61-0-91-DS" get the following values:

Not exactly intuitive, but we can live with that. I'll make a patch for the development version of the plugin...

[CatmanV2]

@akbooer said in Remotec ZRC90:

What's interesting, is that the variable zway_61-0-91-DS shows that it comes from Command Class #91 which is "Central Scene", something I have not seen [pun intended] before. This should be easy to fix.

sl_CentralSceneUpdates was the trigger Reactor used to pick up on that other system

C

[ArcherS]

@akbooer no it is not very intuitive at all, however it is the same as when creating an automation in Z-way:
" The action is described with a two-digit value: The first digit is the button number, the second digit points to the action of this button (0=short press, 1=release, 2=hold, 3=short press two times, 4 = short press three times, and so on. Examples: Double Click button 2 => 23, Single Click button 1 = 10)"

It was a bit different on the Vera, but still equally unintuitive.

When looking in Z-way Expert UI the following command classes are listed for ZRC90:
Basic, ControllerReplication, AssociationGroupInformation, DeviceResetLocally, CentralScene, ZWavePlusInfo, ManufacturerSpecific, PowerLevel, Battery, Wakeup, Association, Version

Let me know if you need more info on this!

[therealdb]

It's not too different from what Fibaro's roller shutter or switch are doing. They support central scene as well.

Vera has the ability to directly map a scene, but a script to monitor the same variable will make migration easier.

[akbooer]

@CatmanV2 said in Remotec ZRC90:

sl_CentralSceneUpdates was the trigger Reactor used

...so now you tell me! OK, I can use this in the same way, I think.

[CatmanV2]

@ArcherS said in Remotec ZRC90:

It was a bit different on the Vera, but still equally unintuitive.

Really? Mine went 1>2>3>4 for button one (single, double, long and release)

@akbooer said in Remotec ZRC90:

...so now you tell me! OK, I can use this in the same way, I think.

You only had to ask!

C

[ArcherS]

As @therealdb says on Vera ZRC90 is supported directly in a scene as a trigger with a scene number, this is how I am using the one ZRC90 that is still on Vera.

On Vera "sl_CentralScene" changes for each button. The variable shows the scene number which is different vs the numbers in Z-way I posted above:
btn 1 single press: 1
btn 2 single press: 3
...
btn 8 single press: 15

btn 1 double press: 2
btn 2 double press: 4
...
btn 8 double press: 16

It also shows unique numbers for press and hold for all buttons.
There is a thread in the Vera forum on this, listing all the scene numbers.

[CatmanV2]

@ArcherS
What Vera firmware are you on? I definitely had 4 for each button (which was the intended operation) and very definitely 1,2,3,4 on button one 5,6,7,8 on button two and so on.

That was on 7.29

C

[sender]

There are "2" versions. Of these wall motes. One sends those scene numbers the other send (I'm not sure ifI say correctly) only one basic command class on very push. The first one works fine with vera, the 2nd one misses a lot of pushes and does always show "waiting for wakeup to configure device". My 2 cents.

[ArcherS]

@CatmanV2 I am still on 7.0.23 (1.7.3232) on my Vera Plus. Too many stories of bricked Veras stopped me from updating every time...
I also have four for each button (once, release, hold and double), sorry if I was unclear on that.

If I remember correctly I saw something on the Vera forum on that one of the later FW updates broke the ZRC90 for some of the four states (I think hold at least).

@sender yes, I think there are different versions. I have two ZRC-90EU, one bough a few years ago and one quite new. Since the older is still on Vera and the new is on Z-way I have not compared them in detail other than that they have different application sw and SDK.

[akbooer]

Can you give the latest development version of the ZWay plugin (v20.7.12) a go?

I've added the command class #91, and hopefully made the device a Scene Controller.

It should create the variables sl_CentralSceneUpdates and LastSceneTime, which are triggerable, but whether it works, or whether it works the way it's supposed to work, I can't say, since I don't have that device.

I leave it as an exercise for the reader...

[ArcherS]

I updated to v20.7.12 and it works partially!

"LastSceneTime" is updated every time you press a key, so that one works.

"sl_CentralSceneUpdates" however stays "null" all the time.

On the ZRC90 that I still have on the Vera there is a variable called "sl_CentralScene" but no variable called "sl_CentralSceneUpdates". I do not know if this could be the reason.

As a side note the variables "zway_61-0-91-DS" and "zway_61-0-91-DS_LastUpdate" are now updated instantly in Reactor.
So a functional workaround could be to use the "zway_61-0-91-DS" and "LastSceneTime" variables for capturing keys pressed in e.g. Reactor. I did a quick test and it seems to work.

[CatmanV2]

Ahh have I thrown a curve ball. Reactor uses sl_CentralScene and reacts to updates :(. I am sorry!

C

[CatmanV2]

@ArcherS said in Remotec ZRC90:

@CatmanV2 I am still on 7.0.23 (1.7.3232) on my Vera Plus.

That would be it. I had to re-number all mine.

C

[akbooer]

@CatmanV2 said in Remotec ZRC90:

I am sorry!

So I should hope.

[CatmanV2]

@akbooer Consider it so!

@ArcherS the workaround seems fine!

C

[akbooer]

@ArcherS said in Remotec ZRC90:

"LastSceneTime" is updated every time you press a key, so that one works.

Thanks... is that, indeed, the correct variable to be using?

@ArcherS said in Remotec ZRC90:

there is a variable called "sl_CentralScene" but no variable called "sl_CentralSceneUpdates"

@CatmanV2 said in Remotec ZRC90:

Reactor uses sl_CentralScene and reacts to updates

So I will change this to sl_CentralScene and try and fix its update.

Would that bring us closer to 'correctness' ?