As I mentioned to @Diesel not sure why this has not been added before now other than because we all got used to using them as responders.  I tested out the switches as control in programs & scenes. Try out the generic, dimmers, garage.

I will leave this in beta for a bit to make sure there are not any unintended consequences.  I know many of you have this plugin integral to your home automation, please throw me some feedback.

3.1.14 \
DONE commands for switches, generic, dimmer, garage

3.1.13 \
DONE prevent direct poll from re-running \
DONE add notice if comms check fails \
DONE clean-up & debug

3.1.12 \
DONE rewrite sse events collection

Thanks so much! 

Loaded beta 3.1.14 into another slot.

Created a virtual switch and was able to add it as a scene controller - Awesome!

{"id": "10", "type": "switch", "name": "My vs Name"}

Device type in AC shows as Virtual Switch

 

Created a virtual dimmer but it only allows the option to add it as a scene responder.

{"id": "30", "type": "dimmer", "name": "My vd Name"}

Device type in AC shows as Virtual Generic   

The scene I tried adding it to is a 3-way circuit with 2 dimmers. 

Edited August 24Aug 24 by Diesel

@sjenkins

Is a virtual dimmer not able to used as a scene controller? 

Try it out, I added the commands for tapping up and down on the bright but not for the new value.  Also it currently doesn't have DON or DOFF which are the normal on/off commands.  Could be added though.

Virtual Dimmer only allows adding as a scene responder. Controller/Responder is greyed out. 

5 hours ago, Diesel said:

Virtual Dimmer only allows adding as a scene responder. Controller/Responder is greyed out. 

sorry I should have been clearer as I knew it would NOT work as a scene controller only in a program as controller (versus status)

Scenes prefer DON and DOF.

I can add them but there is a design choice here: Insteon uses DON/DOF as 100% / 0% not brighten / dimming.  Currently the dimmer / generic device does not have those commands.

option 1:  add DON/DOF commands as 100% / 0%, this is most consistent with UD scenes which are aligned with insteon scenes.

option2: use the current brighten / dim which move the percent by 3% I believe.  I would just send the DON / DOF command along with the current command.  This might be more useful considering the device but confusing for scene consistency.

thoughts?

 

IMHO option 2 makes the most sense for a virtual dimmer, otherwise with option 1 it behaves like a switch. 

A virtual dimmer should function in the same way as a physical dimmer or a keypad button added as a scene controller. Holding a Dimmer or Keypad button down brightens or dims a scene. Pressing a keypad button turns a scene ON or OFF. 

One of the most useful applications for a virtual dimmer as a scene controller is for multi-way circuits.

Consider a common 3-way lighting circuit where 2 physical dimmer switches are added to a "3way" scene, both as controllers. BUT in IoX if you control any of the 2 dimmers directly, the other isn't in sync and neither is the scene. The virtual dimmer solves this dysfunctional behaviour where everything remains in sync as it should be.  

 

 

Edited August 26Aug 26 by Diesel

Sorry, I’m just now seeing this update. Virtual is a fabulous plugin. I’ve been using it for great things and it got so much better when you took over development.

Is any additional input or testing needed before you public it to production store?

Thanks @hart2hart for the kind words. As people are using this for lots of different things than I am , I just wanted to make sure the beta had time to soak.  Just make sure it still meets your use case with no unintended consequences. I usually leave beta for a week or two then consider no news as good news and move to production.