mark_anderson_us wrote:...There wouldn't be any point in me creating virtual devices for my project. Basically, when I turn on the TV or press play on DVR, AppleTV, Blu-ray, etc. it dims the lights. All it does is send a message to Homeseer saying "Movie". This triggers the movie event, which is used from many other triggers. This event sets the lighting levels of several z-wave switches (real devices). When the movie/TV is paused or TV is turned off, it raises the light level in the living room. Resuming again dims them. Way cool....
It sounds like you've thought this through pretty well. As you describe the functionality, I'd agree, a plugin probably wouldn't add a lot. Maybe make the setup interface a bit more seamless, but no real benefit.
BTW, in Indigo terms, the HS
movie event would be an
Action Group.. Each Action Group contains one or more actions for Indigo to take. These actions can be device changes, scripts executed, log entries, emails, etc. The other half of the equation is the
Trigger. A Trigger "looks" for a specific event to take pace: a light turns on, a plugin indicates a pattern has been matched, an X10 signal is received, etc. The Trigger can contain an action to execute, or it can execute an Action Group. Thus, in your model, several Triggers might exist each looking for specific conditions to take place (RS232 message, Light switch dimmed, room occupied, etc.) but, regardless of the event that set the Trigger, the same set of actions would be executed.