C Martin Posted June 1, 2016 Posted June 1, 2016 I know that this was a request from long ago. I would like to see a "Virtual Device". This is one that only exist in the ISY but can be used to program events with. An example would be when using a motion detector and when you create a scene in conjunction with the motion detector the action is immediate because of the scene.Right now, if I create a scene with a device that is connected to a working switchlinc, when the motion detector turns off, the switchlinc turns off. The use of Virtual Devices brings a whole new realm of programming possibilities.
Xathros Posted June 1, 2016 Posted June 1, 2016 I know that this was a request from long ago. I would like to see a "Virtual Device". This is one that only exist in the ISY but can be used to program events with. An example would be when using a motion detector and when you create a scene in conjunction with the motion detector the action is immediate because of the scene.Right now, if I create a scene with a device that is connected to a working switchlinc, when the motion detector turns off, the switchlinc turns off. The use of Virtual Devices brings a whole new realm of programming possibilities. With 5.X and the ability to set variables based on device status and vice versa, is this not already possible? Maybe I'm not understanding your requirement. -Xathros
paulbates Posted June 1, 2016 Posted June 1, 2016 Programs can be used as virtual devices. In the case of the insteon motion sensor, you can configure it to "send on commands only". When its set that way, it will turn the switchlinc on right away via a scene and can also run a program. Because there are no "off" commands, the MS will not turn the lights back off. The program will be 'True', while its running, and can be evaluated as a virtual device condition. The program(s) can decide when to turn the switchlinc off. Paul
Recommended Posts
Archived
This topic is now archived and is closed to further replies.