Controlling virtual slider with scene

[rb338 5]

I've connected several third party WiFi RGBW LED controllers to my HC2, using virtual devices. Now I have created a slider, which can be used to set the LED brightness.

I would like to be able to dim the lights the same way as a regular Fibaro dimmer does. This would mean building a couple of Lua pieces:

When button pushed: start sliding.

When button released: stop sliding.

This would probably not be that difficult. However, what a Fibaro dimmer also does is reverse the direction when you release and push again.

How could this be done? I would need to know, when button pushed, how much time has passed since the button was last released. And I would need to know which direction the slider was going when the button was last released.

Is there anyone who made something like this? It could also be used to control your media volume (Sonos, XBMC, etc)

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[A.Socha 133]

rb338, zwave standard not saying about direction of change report. but if you really want you can use scen activation where that information is sending

[rb338 5]

A.Socha, Not sure what you meant. I did get it to work - partly.

I've created a scene with some code:

Please login or register to see this code.

This works. When I hold the button, I can see the slider move.

HOWEVER the action associated to the slider is NOT being executed!

This is what the slider does (apart from setting the variables):

Please login or register to see this code.

When I click the slider or move it about from the web interface or iOS app, it works fine. Just not when the value is changed from a scene.

Is this a known bug? Am I doing something wrong?

[ Added: 2014-03-20, 07:35 ]

Reported bug #1285.

[ Added: 2014-03-21, 07:18 ]

As also noted on the bug report:

The problem seems to be that I should not use:

fibaro:call(deviceId, "setProperty", "ui.SliderDimmer.value", i)

But:

fibaro:call(deviceId, "setSlider", "3", i)

Somehow, setProperty will only change the slider value and not execute the code that's part of the slider, and setSlider (which has to call the slider with a number, instead of the name like with setProperty) will actually execute the code.

So maybe more a feature than a bug, but the inconsistenties are confusing.