Insteon scenes are handy, but they won't work with Z-Wave (or any other interfaces we may want to add). If you manage to make Z-Wave scenes work, they won't work with Insteon devices. And many of us will end in a mixed world with multiple interfaces. The result will be some Insteon-specific PowerLinc scenes and some Z-Wave specific whatever-scenes and some other gizmo over to the side - not a terribly scalable mix.
Have you considered making the protocol scene support implicit in Indigo's operation? Let's say I write a humongous action group where I tell all my lights to turn off (except a few to 15% as night lights, and the fans off except a few, and arm the alarm system and stuff). I just did. How cool would it be for Indigo to hand this group to the Insteon interface to pull out all the actions it can bundle up and define as a PowerLinc group; for the Z-Wave interface to do likewise; and all other interface-like plugins getting a shot at pulling out "their" pieces as efficiently as possible? The user would just write action groups in Indigo, and all the heavy lifting and configuring would happen under the hood. And if none of the interfaces has anything to offer, the result is still an action group that works just fine (if slowly).
Okay, I can dream...
Meanwhile, are there any existing Python APIs for plugins to manage PowerLinc scenes?
(Strange how all this suddenly matters when you've got 80+ Insteon switches to manage in your house. )
Cheers
-- perry