yep, i got that first time! 
i reckon for this situation, you'll probably just find it easier to use an enum attribute, which'll allow you to excluserfy the different setups. attach an expression to that attribute, which cases up the situations, and (if you are having the master attacthed to it dominions in a connection based manner) sets the states on some dummy, hidden, attributes that you can wire into the controlled attributes ...
it starts to gets messy otheriwse. if you want to be changing/enabling rafts of attributes for different global conditions (like on the light nodes), then you've got to start adding and removing the attributes on the fly (you cant enable/disable the actual AE interface elements/items that carry/house the attributes unless you schming with the AETemplates, which arent the best thing to mess with unless you know what your doing).
let me know if above works for ya!