Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation

[therealdb]

Hi @toggledbits ,
I'm slowly moving my ZWave network from Vera to ZWaveJS. I successfully cloned my ZWave network using a spare Vera Edge (a new post for the community later when I'll be fully back from vacation) and I'm testing a couple of things before moving everything to ZWaveJS.

In the meanwhile, I have a couple of venetian blinds connected to Fibaro Roller Shutters 2 (FGR222) and I'm using some proprietary ZWave commands to control the tilt position, that right now I'm sending via Vera (with some code from the old place, messing with this):

The ZWaveJS values are reported via this:

x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=0
x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsTilt=0

I hope there's a way to expose a separate device to control the tilt position directly, without doing the mess I'm doing now. Let me know if you need some files. Thanks.

[toggledbits]

I'm on my way to a conference but will look at this when I get back (Sunday)

[therealdb]

Thanks. It's public holiday tomorrow and then I'm out to watch a soccer match. It's perfectly fine. I've also managed to import device names into Zwavejs via mqtt. On my way to do the same for the endpoints on the controller side.

[therealdb]

In the meanwhile, I found a way to call it from Reactor:

zwavedata is just the requested position, 0...99

[toggledbits]

For tilt, the ZWave standard command class (which Fibaro does not implement) uses 50 to represent open (the slats of the blind are flat/horizontal), and values 0 and 99 to indicate the two versions of closed (fully tilted up, or fully tilted down). What do the tilt values 0-99 represent on this device?

[therealdb]

0 closed, 99 open (so, horizontal). 50 is 50% open. But maybe my device is specific, I've never been able to open more than flat/horizontal.