I have a 3-switch (4-way) configuration for my Entry Lights, and I've labeled my switches as Entry Lightswitch 1-Main (this is the load switch), Entry Lightswitch 2, and Entry Lightswitch 3. I've created (3) MNS Insteon Groups (Entry Lights, Entry Lights 2, and Entry Lights 3), each Group uses one of the switches as a Controller. This 3-Group configuration creates all of the local links required to keep things in sync when physically pressing the switches.
For virtual/remote control, I use the Entry Lights Group, and I review/motor Entry Lightswitch 1-Main to determine if the lights are actually On or Off. I have hidden the other Groups in HS4/HSMobile.
In the Insteon App, this could have been developed with one Scene (with all (3) switches being Both Controller/Responder), but due to the current limitations of MNS Insteon, only one Controller can be assigned per Group.
Pros with this approach -
- Fast/instant response from the switches and the load, especially during local control.
- Only need to manage 3 Groups instead of (6) cross links spread across (3) devices. Individual link management can become a bit cumbersome if you have many devices you're trying to sync.
- Group Controllers have a status in HS4 - you have to kind of ignore this, because depending on which switch was physically pressed last, the GC status will drop out of sync. (Insteon Scenes did not have a status, they only sent commands, so this 'feature' of MNS Groups is different)
- Using one of the HS4 device switches virtually will cause it to fall out of sync with the other switches in the multi-way. It also won't turn off the controlled lights unless it's the switch that's actually on the Load.
- Have to create and manage (3) Groups.
Leave a comment: