Testing Indigo under the Trial License and would like to know the most efficient method for my scenario. I read a similar thread by NicholFD (Frank) but his situation was slightly different and the answers did not address my need.
I have a Master Z-Wave Dimmer switch than operates the recessed LED lights, and two Remote Z-Wave Dimmers (Cooper Aspires, FWIW); these switches have a vertical column of tiny LEDs that animate to show when it's turning on, turning off, as well as it's current brightness level setting. Apparently, each maintains their own status of On/Off and Brightness independently so I need to "script" Indigo to synchronize the Master and Remotes, both at startup and during the course of device operations.
TRIGGERS appear to be the logical method of doing this but I noticed that TRIGGERS do not have an ACTION that allows me to "match" the On/Off status of the "triggering" device; only ON, OFF, or TOGGLE. And since there doesn't appear to be a method to set the CONDITIONS on a per device scenario, what happens is that without building individual triggers for each source/target switch PAIR there will be a lot of unnecessary traffic on the RF network to blindly blanket all "linked" switches to the setting of the source switch, which in turn will result in those devices' triggers being firing by Indigo. Thus it seems I would need to build multiple triggers to handle: 1) An "ON" event for each triggering switch and each individual remote to sync, 2) An "OFF" event for each triggering switch and each individual remote to sync, 3) A "BRIGHTNESS" event for each triggering switch that syncs all other switches. This results in the following synchronization triggers just for the Master Switch:
Master Switch ON then set Remote 1 ON only if OFF
Master Switch ON then set Remote 2 ON only if OFF
Master Switch OFF then set Remote 1 OFF only if ON
Master Switch OFF then set Remote 2 OFF only if on
Master Switch BRIGHTNESS then set all Remotes to Match Brightness
Again, I'm trying to not to flood the RF network with redundant transmissions. Since Indigo doesn't allow CONDITIONS to check if the brightness level is not the same as the source device or against a variable, it appears that each target switch will result in firing off it's own brightness trigger in Indigo.
Is there a better way than the approach I described above (if anyone can understand my logic)?