Trying to grasp the Scenes thing

[rh]

I've read the manual but I'm not sure I understand scenes. They seem like macros. Are they required?

 

Presumably I don't need a scene to have a remote turn on a lamp?

 

But if I wanted to press a button and have it turn on a lamp, turn off a light, and turn on a fan, that would require a scene? But couldn't I do the same thing with a 'program' - if button 1 press received, do this, that, and one other thing?

 

Suppose I have two remotes and I want both to control the same lights. Button 1 on each remote would turn on the bedroom lights. In order to accomplish this would I need to create a scene, then include both remotes and the bedroom light?

 

Are scenes necessary as a basic part of Insteon or just the ISY-99?

[Mark Sanctuary]

rh,

 

ISY scenes are a part of the basic INSTEON network that links together more than one light at one time. In fact the ISY makes managing those scenes much easier than running around and tap programming everything. If you want to get technical there is many write-ups in the forum about how a ISY scene is a wrapper around the INSTEON group but really the most valuable part of that discussion is understanding a ISY scene is doing the same thing as when you tap link switches together.

 

Programs can control many lights at a time just like a scene but this is slower than putting those same lights inside a scene and then controlling it with programs. The real use for programs is for adding functionality beyond the basic linking of devices together. So here is some ideas that programs might be used for...

 

Basic programming ideas

• 
  [*:3rmpw4lf]trigger timers
  [*:3rmpw4lf]shutoff timers
  [*:3rmpw4lf]advanced keypadlinc LED status
  [*:3rmpw4lf]away/vacation buttons
  [*:3rmpw4lf]pool/spa control
  [*:3rmpw4lf]theatrically dim the lights when the TV turns on

Advanced programming ideas

• 
  [*:3rmpw4lf]energy efficiency programming
  [*:3rmpw4lf]power meter reading
  [*:3rmpw4lf]remote access to your home automation
  [*:3rmpw4lf]connecting in smart display panels
  [*:3rmpw4lf]thermostat control, ceiling fan, whole house fan integration
  [*:3rmpw4lf]weather driven irrigation control
  [*:3rmpw4lf]security and emergency integration

And the list goes on, really up to your imagination.

 

Thanks,

[brad77]

To add to marksanctuary, one of the ways scenes are helpful is that they reduce the amount of traffic moving over your INSTEON network. For instance, a program turning on three relay switches could look like this:

 

1. ISY -> Switch A: Turn ON

2. ISY -> Switch B: Turn ON

3. ISY -> Switch C: Turn ON

 

If, however, you link these devices together in a scene, the ISY only needs to do this:

 

ISY -> Scene ABC: Turn ON

 

I'm simplifying a bit, but hopefully you'll get the idea. In both cases, the individual devices will send their status (think "I'm switch A and I turned ON") back to the ISY, but the original request only requires a single "transmission" on your network, and thus less time to execute.

[oberkc]

But if I wanted to press a button and have it turn on a lamp, turn off a light, and turn on a fan, that would require a scene? But couldn't I do the same thing with a 'program' - if button 1 press received, do this, that, and one other thing?

 

Yes, there is potentially some duplication. With programs, you can do much of the same thing as with scenes. Like those before me said, scenes are part of the basic insteon architecture and can be used with, or without, an ISY.

 

To add to the example of of Brad77, scenes are also device-to-device. If switch A and switch B are part of a scene, then they communicate directly with each other and don't even require the ISY to be there. There are benefits to this. First, it is a little faster than programs. Second, if the ISY fails, your basic lighting will continue to work.

 

My suggesting is to use scenes to link devices to each other and use programs for more complicated relationships between and among devices, and for timing-based events.

[LeeG]

A Scene/Group in its simplest form involves two devices. A Controller, such as a KeypadLinc button, and a Responder such as a LampLinc. Pressing the button on the Controller device turns the Responder device On/Off. To accomplish this a link between the Controller and Responder is established. This link consists of a “Controller of†link record in the Controller device and a “Responder to†link record in the Responder device. The link record in the Controller identifies the Insteon address of the Responder device. The link record in the Responder device contains the Insteon address of the Controller device and information such as how Bright should the Responder turn On and how fast (ramp rate) should that Bright level be reached.

 

To create this link the Controller is put into linking mode first (which makes it the Controller) by pressing the button/paddle for a prescribed amount of time. Generally some indication exists that the Controller device has enter linking mode. In this case the KeypadLinc button will blink. Then the Responder device is identified by pressing the Set button on the responder for a prescribed amount of time. This technique involves physical activity at both the Controller device and the Responder device and is often referred to as Set button linking.

 

A much simpler technique is to use the ISY to create the Scene. This involves defining the Scene and adding the Controller and Responder devices to the Scene. The ISY will write the required link records in the Controller and Responder.

 

This may sound complicated but Scenes are the basis for the majority of device to device control. For simple Responder device control there are commands that can be used that do not require a Scene. However, where multiple responder devices are to be controlled a Scene is a far better means of control. All Responder devices react nearly simultaneously to a Scene On or Off command.

 

Some devices, such as a Secondary KeypadLinc button , can only be controlled with a Scene.

 

Take the time to understand what a Scene is and how it works. It is an essential aspect of Insteon communication and the time to learn the workings of a Scene is well worth it.

[rh]

Wow, thanks everyone! That helps allot. I didn't realize the ISY would do the 'linking' for me. That sort of remote management of the devices would certainly simplify setup and help down the road as things change.

[oberkc]

Wow, thanks everyone! That helps allot. I didn't realize the ISY would do the 'linking' for me. That sort of remote management of the devices would certainly simplify setup and help down the road as things change.

 

Exactly! One subtle difference when using the ISY-99 to create your links (scenes): all scenes created with the ISY will include the PLM as a controller, in addition to the other insteon devices. This is done in the background, without user intervention. Remember also that devices added as controllers in the ISY are also responders by default.