Slider Control to shift between scenes

[wayneph]

I have a FanLinc with KeyPadLinc buttons linked via scenes. If I just use the normal slider on the fan device, the buttons don’t turn on (or off) to stay in sync with the Fan.

 

Is there a way i can have the “Fan Device†with “Fan Offâ€, “Fan Lowâ€, “Fan Medâ€, and “Fan High†as an array of associated scenes. Instead of just updating the Fan, it would fire the scene at the appropriate level to keep all related buttons tied together.

 

Thanks!

 

----

wayne

[PurdueGuy]

I have 4 programs and 4 scenes for each fan.

Scene - sets fan speed and any associated KPL button(s), with the correct KPL button being a Controller, and others Responders

Program examples - Fan High:

If
       Status  'Devices / Downstairs / Downstairs Fan-Motor' is High

Then
       Wait  1 second
       Set Scene 'Scenes / Downstairs / Fan High' On

Else
  - No Actions - (To add one, press 'Action')

 

The scene "Fan High" sets the fan speed and any associated KPL buttons. If I change the fan to high from an app or other program, the scene will fire, wait 1 second, and set the scene. The fan is already in the right state, but KPLs will follow in a moment. If I press a button on a KPL, the fan immediately gets set to the right scene, and when the program runs a scene later, everything is already in the correct state, so it doesn't look like anything happened.

 

There might be other ways, but for my 4 fans, this have been fine.

[bmercier]

I have a FanLinc with KeyPadLinc buttons linked via scenes. If I just use the normal slider on the fan device, the buttons don’t turn on (or off) to stay in sync with the Fan.

 

Is there a way i can have the “Fan Device†with “Fan Offâ€, “Fan Lowâ€, “Fan Medâ€, and “Fan High†as an array of associated scenes. Instead of just updating the Fan, it would fire the scene at the appropriate level to keep all related buttons tied together.

 

Hello Wayne,

 

Not directly, but there is a work around.

 

HAD features a variable slider you can leverage for this. So the general idea is to use a state variable with 4 possible values that would trigger ISY programs, which in turn would activate your scenes based on the value.

 

So in HAD, to control a variable this way, you would need to set a line like this in a custom device table:

{ name : "Scene Slider", labelOn:"Slower", labelOff:"Faster", typeControl:"Var", refreshOpt:"Var", varType:"2", varId:"", varSliderSnap:"1", varMax:"3" }

 

That would give you a "device" that controls fan speed. The status displayed would be the actual variable (0 to 3).

 

As an alternative, you could set your var slider on the same line as your fan.

The syntax would be:

{ name : "", labelOn:"Slower", labelOff:"Faster", typeControl:"Var", refreshOpt:"Yes", varType:"2", varId:"", varSliderSnap:"1", varMax:"3" }

 

That would then display the exact status of you fanlinc, but giving you control over the variable. A var change would start your program which would activate the scene and the devices, and the device refresh would show the change. In the present version, the device will not get refreshed on a change, as I have not implemented it. I could not think of a use case where one would want to display a device when controlling a var. But that is a good example.

 

I will code that this week-end and it will appear in the next version. But in the mean time, the first option will work.

 

Benoit.