support wrote:Unfortunately, this is impossible given how the INSTEON protocol is defined. Indigo cannot simulate or masquerade as another device to send out one of its commands. The PowerLinc V2 can send out group commands (Indigo doesn't do this yet), but they have to be groups defined and linked specifically with the PowerLinc V2. It is impossible to have the PowerLinc send out the same command that a KeypadLinc (or other module) sends out when one of its buttons is pressed.
thanks for replying and clarifying the capabilities of insteon. i understand that it is not kosher/possible to mimic another device at the insteon protocol level.
what i had in mind was that insteon could use the concept of a "smart on" command as a shortcut for saying all the commands you would need to do to achieve the same result as if you'd pressed the on button on a particular device. (note that you could also have "smart" off and dim commands, too). it could be implemented by having indigo send a sequence of individual commands, a group command, or whatever. the user doesn't really need to know or care. however it is implemented, i think it would be a useful feature to have in the program.
so, for example, if i have a "virtual n-way switch", in a script where i currently need to say something like
turn on "dining room light"
turn on "dining room light kitchen entrance slave switch"
turn on "dining room light living room entrance slave switch"
etc...
i could simply say
turn on "dining room light" with paired devices "yes"
or perhaps
simulate on "dining room light"
as another example, you set up a "scene" where one switch turned on a set of multiple units to certain brightness levels. using the "simulate on" command lets me invoke this scene easily from indigo without a lot of extra scripting.
i imagine that the user would just see an extra checkbox in the edit action dialog when the type is set to "send device command" called "also send to paired devices" or something. alternatively, there could be a distinct action type called "simulate insteon device command".
so does this seem feasible? it seems to me as though it would be, since a "simulate on" command could at worst be just a substitute for a sequence of insteon commands sent to the indicated device and it's pairs, and indigo already knows about everyone's pairings.
the only fly i see in the ointment here is that i don't understand why indigo can't change the state of keypadlinc buttons, even though other devices paired with those buttons CAN... what is it about the way indigo pairs with keypadlinc that introduces this limitation? and while we're on this topic... i will say that this issue is the single biggest "kink" in my system right now. i have invested in several keypadlinc II's around my house and while i love the reliable communication, the lack of proper support for the LED's on these things makes it so that using indigo on any devices linked to the keypad buttons mucks things up. needless to say, i hope we see some kind of improvement here soon.
thanks again.