LeeG

That is a good start. The Program is changing the Responder On Levels for the two SwitchLincs when the Scene is used in a Program or controlled through the Admin Console. You need a few additional statements in each clause. These are for the Then clause In Scene ‘After Hours Hallway’ Set ‘Hallway main’ 25% (On Level) – existing In Scene ‘After Hours Hallway’ Set ‘Hallway’ 25% (On Level) - existing In Scene ‘Hallway’ Set ‘Hallway main’ 25% (On Level) - new In Scene ‘Hallway main’ Set ‘Hallway’ 25% (On Level) - new In Scene ‘Hallway main’ Set Hallway main’ 25% (On Level) - new I made an assumption ‘Hallway main’ is the SwitchLinc that has the Red wire connected to the load. If ‘Hallway’ is the SwitchLinc that has the Red wire connected to the load then the last statement should be In Scene ‘Hallway’ Set ‘Hallway’ 25% (On Level) The three additional statements are required the Else clause with 100% On Level. The first two additional statements in the Then clause above set the cross-link relationship between the two SwitchLincs to 25% On Level. These will keep the status LEDs in sync. The third statement sets the Local On Level to 25% On Level.

Run an additional pair of wires between the manual switch location and the I/O Linc Relay. Any home improvement store carries 2-conductor thermostat wire which is rated for in-wall installation. Remove one wire from the mechanical switch, attaching it to one of the new wires. Connect the other new wire to the mechanical switch where the wire was just removed. Connect the 2 wires at the I/O Linc Relay, one to Com and one to NO. With this wiring the mechanical switch has to be On and the I/O Linc Relay has to be On for the fireplace to turn On. That is what is referred to as a serial connection between the mechanical switch and I/O Linc Relay. The circuit has to be complete through both the mechanical switch and the I/O Linc Relay for the fireplace to work. Turning either Off will shut Off the fireplace. That makes the mechanical switch the failsafe. Turning if Off when leaving the house or going to bed insures the fireplace cannot accidentally start from an I/O Linc malfunction. With the mechanical switch On a RemoteLinc or RemoteLinc2 or KPL mounted in a table top enclosure can be linked to the I/O Linc Relay for remote fireplace control.

Vyrolan The Dual Band KeypadLinc Relay 2.44 [02.2C] is in the New INSTEON Device Device Type pulldown on 3.3.5 (RC2).

No battery powered Relay device. Battery would not last long enough to be useful. An I/O Linc can be positioned any where there is power with a pair of low voltage wires running from mechanical wall switch (or fireplace which ever is easier to access) to I/O Linc relay contacts. If the mechanical switch and I/O Linc relay are wired in parallel either can turn on the fireplace. If the mechanical switch and I/O Linc relay are wired in series both have to be on (either would turn fireplace off) for the fireplace to work. I prefer the series wiring approach which insures the fireplace cannot be turned on by accident by the I/O Linc relay if the mechanical switch is Off.

The Program is triggered at each From time and each To Time. Normally the If evaluates to True at the From time and False at the To time. The True/False evaluation is affected by the Variable value. The affect of the variable on Program triggering depends on whether an Integer Variable (does not trigger Program on value change) or State Variable (does trigger Program on value change). Regardless of type of Variable the value will always affect the If evaluation as far as True/False is concerned. Because of the Repeat and Wait statements the trigger points (From and To time and Variable value change if State Variable) will interrupt Program execution and reevaluate the IF. The Programs | Summary tab will show when the Program is executing even when waiting in the Repeat or Wait statements. Should the If turn False at any point (To time or State Variable ? value change) the Program stops execution because nothing is in the Else clause. It would not run again until another trigger point (From time or State Variable ? value change). Because there is nothing in the Else clause the Fan may not return to Auto because the Repeat/Wait sequence is interrupted in the middle of processing which is normal. Put final state processing in the Else clause.

gviliunas After clearing Java cache and using URL for 3.3.5 (RC2) run Help | About. Verify Firmware and UI both show 3.3.5.

I suggest posting the Program(s) and the Scene information (which switch physically controls the load, which switch is the linked slave in the 3-way, which switch paddle is being used). When using the RemoteLinc both switches are Responders, reacting to the Responder On Level for the RemoteLinc as Controller. When the paddle of the slave switch is pressed the switch controlling the physical load is reacting to the Responder On Level for the slave switch as Controller. When the paddle on the switch physically controlling the load is pressed the Local On Level is controlling. When a SwitchLinc is reacting using the Responder On Level (RemoteLinc as Controller or slave switch as Controller) the response is the same each time no matter how many times the Controller paddle is pressed (not counting Fast On double tap). When a SwitchLinc is reacting to the Local On Level the first press goes to the Local On Level, the 2nd press goes to 100% On. That is the nature of SwitchLinc operation. A Program making changes based on time of day not only has to change the Responder On Level for each Controller, the Local On Level also has to be adjusted to handle the paddle press on the SwitchLinc that is physically controlling the load.

Also keep in mind 3.2.6 was released the beginning of May 2012. That is 7 months ago. The amount of I2CS device evolution alone that has occurred over those 7 months is huge.

Release 3.3.4 provides support for setting the options of an I2CS I/O Linc. Release 3.2.6 does not have that capability. 3.2.6 correctly handles pre I2CS I/O Lincs. If that is your only problem 3.3.4 will solve it. The I/O Linc has a variety of features that support nearly a dozen different I/O Linc kits. Even the garage kit can be implemented in various ways depending on how you want the door controlled, how the status of the door should be presented, and so on. I would not be surprised if you have additional questions once the I2CS I/O Linc options can be configured.

Thanks Brian.

The information the Admin Console is displaying is the Motion Sensor Firmware level. The information on the sticker is the hardware Revision level. Rev 1 Motion Sensors cannot be configured programmatically as the documentation that came with the Rev 1 motion sensors indicates. Jumper 5 has no function at hardware Rev 1

Also sounds like you are running 3.2.6 which cannot set the new I2CS I/O Linc options. Have to move to 3.3.4 to get that support.

The Err and Mem LEDs blinking indicates the ISY no longer has Ethernet access.

So what is the data in the initial post that says they are V2 motion sensor? "My sensors are older and listed as 2420M v.24."

My bad. That is how it is done where the address is not known.

What ISY firmware is being used? What is the Motion Sensor firmware level? Sensing Mode (also known as Occupancy mode) causes the Motion Sensor to send Motion On commands for every motion detected. Without Sensing Mode the Motion Sensor must timeout before issuing an Off command or the next On command. Check that Jumper 5 is positioned on both pins. It acts as though it is not set up for programmatic configuration.

Remove the bottom battery. On the long side vertical wall of the battery compartment normally covered by the bottom battery is the Insteon Address label.

If those were the words, button already a Controller, it was referring to the KeypadLinc button. A node can be a Controller in one Scene only. This is an Insteon design point rather than an ISY limitation. Dropping the KPL button on another Scene would produce the question should the button be added as a Responder as that is the only option available. I just check and the ISY will not allow the I/O Linc Sensor node to be added as anything but a Controller and if an attempt to add to another Scene an error popup displays indicating the Sensor is already a Controller and cannot be added to another Scene (running 3.3.4). When you get home click the Scene name and look at the color of the nodes below the Scene name. Anything in Red is a Controller; anything in Blue is a Responder. Many devices can function as both Controller and Responder, such as a KeypadLinc button and SwitchLinc. Some devices can only be Responders such as an ApplianceLinc or I/O Linc Relay and some can only be Controllers such as the I/O Linc Sensor or RemoteLinc button. I think the Scenes will actually be correct.

"I had the Door Sensor as the Responder and the Relay as the controller." That is backward. The I/O Linc Sensor can only be a Controller and the I/O Linc Relay can only be a Responder. The ISY does not allow the Sensor to be added to a Scene as a Responder nor does it allow the Relay to be added as a Controller so I suspect you are just remembering the definitions incorrectly.

That will not happen if all things are correct. Be sure there was a Save on the Variable screen and Save Changes was done on Program Details screen. Keep in mind that like Status, variables have to change value for a Program to trigger, regardless of which clause will execute. Change the variable value to 2 or 3 and see what happens. Look at the Last Run Time on the Programs Summary tab to insure Program is actually being triggered.

"Is it possible with the Insteon Lights to send an ALL OFF command say to all lights?" No. Insteon devices have a unique hex address. This allows a Controller to send a command to a device and expect the device to ACK the command. This allows a Controller to retry a failing command. Something X10 never heard of. A Scene can be created with whatever lights should be turned Off and turn the Scene Off. As was discussed elsewhere there is no automatic blink and sending repeated Insteon commands to turn a light(s) On and Off can interfere with other Insteon traffic. Can be done, just know that the action can interfere with other Insteon traffic.

As TJF1960 has already noted the Variable must be a State variable for a change in value to trigger program execution. It means the posted Program was never triggered, Then or Else clause. There is a forum Category dedicated to Variables which has some good information on how Variables work. Also be sure the Folder condition is still True when the State variable changes to 0. Otherwise the Program will not be triggered even when using a State variable.

Is the Program in a Folder? Is the Variable a State or Integer?

What is Sensing Mode option?

Programs in the ISY are event driven. The light was told to turn On to 60% at Sunset. If something changes the light On Level after that nothing brings if back to 60%. Insteon has no function to "restore to a previous setting". Nothing tells the 60% On Program to run again so the light does not get set to 60% again. Think about ISY Programs as event driven. Something has to tell a Program to run each time.