I understand that once defined in the plugin, scenes can be triggered from any Insteon controller including motion sensors which is a great idea You mentioned your "circadian" scene which basically adjusts the color temp/color to correspond with the time of day. I like that a lot, but, unfortunately, it got my mind engaged as I thought it through.
In addition to Osram, I have Hue lights and Insteon bulbs. I originally assumed I'd simply individually control each type of bulb in Indigo with the specific plugin for each one. Like me, many people may have a mixture of bulbs, if only because some brands have bulbs others don't (e.g. Hue has GU10, but Osram has MR16) and the prices of comparable bubs are sometimes much lower for particular brands. While I was thinking about how cool your circadian scene would be as I walked into each room, I also got a big dose of reality. In my house most rooms have a mixture of lights and it would be a total nightmare if the only way to keep multiple brands of bulbs in sync is to manually enter--and update--changes to the same complicated combinations of settings in every place they are used: multiple plugins, actions, device settings, etc., One of Indigo's great strengths is the ability to combine multiple protocols in one interface, but in situations like this, that strength becomes a two-edged sword.
That scenario got me to thinking about the possibility of a "master lighting settings" plugin affording the option to store definitions common to all lighting applications in one place. Color values and scene parameters are obvious candidates because I assume they are composed of standard parameters, such as RGB, color temp, level, etc. It could also allow definitions of even more useful things as well. For example, devices from multiple manufacturers could be assigned to any number of "groups". When Indigo commands are sent to that group, the master plugin would direct the command to the appropriate plugin for each device, along with the common data to execute the command. If the definition of the scene "Party TIme" and the members of the "Living Room" group were defined in the master plugin, the values would be applied to every light in that group regardless of the manufacturer. An analogy is the official Hue app restricts a light to one "Room", but a third-party iPhone app called "Hue Lights" allows the assignment of lights to multiple different groups.
At this early stage of development of lighting plugins, it shouldn't be hard for the developers to agree on the format for different kinds of data. Each plugin already includes functions to generate lists of devices and available actions for each device, so the master plugin could easily assemble a comprehensive list, The master plugin wouldn't incorporate and specific functionality itself, but would serve as a single source of data forIndigo to process actions for multiple lighting devices. It wouldn't replace local definitions as the plugins currently function, but would be an option to facilitate integration of more than one type of lights. To me, that would be a major plus for Indigo and would avoid what is likely to be chaos as more and more lighting systems gain market share. Is this a crazy idea?
So many possibilities, so little time.