8 hours ago8 hr Hi guys - I searched for other threads in the forum re turning every device off using a single button. It seems the prevailing recommendation is to use a scene, which I agree. I also like someone's idea of a program to indicate the status of the "All Off" lights by checking if the status is "not off."I made an "All Off" scene and added all of the items I want to turn off as responders. Added a keypad button (set to toggle off) as the controller. Then Set those devices to 0% for that button within the scene.Two things:I have some other keypad buttons that do not turn off when the "All Off" scene is triggered. This is mainly because those buttons are in a different scene and trigger microcontrollers. One simple example is I have a light scene called "Garage Hall Accent Light Scene." This scene has one keypad button and one microcontroller that's tied to under cabinet lighting. If I add the microcontroller to my "All Off" scene it will turn off the microcontroller but the button on that keypad remains lit. Do I need to keep adding those additional trigger buttons as responders to my "All Off" scene and set them to "Off"? My concern is that it's creating a super-bloated scene. Is there performance issues to consider? A better way?I want to have multiple "All Off" buttons throughout the house (eg. one at each door, a remote for the car, etc.). Is there a way to add another controller to my "All Off" scene without having to re-do all of the "Insteon -> 0%" settings for each device within that scene for the new controller? (Like... copy default settings from controller A to controller B within this scene.)Thank you!Peter. Edited 8 hours ago8 hr by PeterP Clarifying
6 hours ago6 hr 1 hour ago, PeterP said:Do I need to keep adding those additional trigger buttons as responders to my "All Off" scene and set them to "Off"? My concern is that it's creating a super-bloated scene. Is there performance issues to consider? A better way?No better way. The performance might be felt only when managing the scene.. adding, modifying or removing scene members. Especially if any of them are wireless sensors, which doesn't sound like the case. The scene itself is a single group # programmed into all the scene members. They all wait for that one group number so, no, run time performance is not a factor.What can be a factor is that the PLM can handle 1000 links and large scenes can affect the approaching or exceeding that.1 hour ago, PeterP said:I want to have multiple "All Off" buttons throughout the house (eg. one at each door, a remote for the car, etc.). Is there a way to add another controller to my "All Off" scene without having to re-do all of the "Insteon -> 0%" settings for each device within that scene for the new controller? (Like... copy default settings from controller A to controller B within this scene.)No sure I'm following. Each new controller in a scene activates the scene... that's it. A controller activating the scene tells each group member to do whatever it's been told to do for that scene. A follow up is that scenes are a one time, fire-and-forget Insteon moment. Large scenes increase the odds that one or more member doesn't hear it.
3 hours ago3 hr Insteon scenes are one of it's biggest features. Turning off a bunch of lights is just one wonderful application for a scene. I have scenes like that which are only used for turning off devices (those scenes are never "turned on"). And you can have multiple controllers for the same scene, or use programs.
Create an account or sign in to comment