LeeG

To the first question, the Program will trigger at Sunrise. Setting the Enable Run At Startup option from the Summary page or using Enable Run At Startup from a Program accomplishes the same thing.

Define an ISY Scene with KeypadLinc Secondary buttons A,B,C as Controllers and whatever device is physically controlling the load as Responder. The KeypadLinc Secondary nodes will be listed below the ISY Scene name. Select button A setting the responder On Level associated with button A. Repeat for buttons B & C. Button Grouping is used to establish A,B,C as mutually exclusive buttons so only one of the Secondary buttons is On at a time.

Is this an 8 button KeypadLinc or a 6 button KeypadLinc? If a 6 button KeypadLinc where the 3 buttons are Secondary buttons a single Scene can be used. If an 8 button KeypadLinc where button A is Main/A physically controlling the load then probably not.

The Program should not be changing the backlight level. Backlight level applies to ALL the KeypadLinc buttons not just button F and does not result in an On button look like it is Off. Secondary KeypadLinc buttons cannot be turned On or Off directly. The KeypadLinc does not support a Direct command to do that. Define an ISY Scene with KeypadLinc button F as a Responder. In the Program Then clause set this new Scene Off to turn Off button F.

Did you clear the Java cache and perhaps went back to the 2.8.16 URL if you switched to something new to get to 3.1.17. For sure the Java cache has to be cleared. If you did not clear the Java cache going into 3.1.17 that would also be a problem at 3.1.17.

One easy test is use an extension cord. Plug the PLM into the extension cord and plug the extension cord into a different circuit in another room. Then run the Program driving the Scenes. The surge suppressor and associated equipment should be isolated with a FilterLinc.

A successful Scene Test indicates the link records that support the Scene are correct in both the devices and the PLM. When some devices fail to respond to a Scene when the Scene Test is successful indicates either a comm problem or some interference with a Program that is triggered by the devices in the Scene changing state. The Program interference question is easily eliminated by Disabling all other Programs and running only the one that is driving the Scenes that are failing. If the devices continue not to respond with the Programs Disabled then some interference is indicated. Could be the load(s) that are being turned On by the Scene such as CFLs or Fluorescents. Could be something else that is generating interference or attenuating the Insteon Scene message such that it does not reach all the devices. Verify the Access Points are installed on opposite 120V legs and are receiving each other’s RF signals. Is the ISY PLM plugged into an outlet that is being shared by UPS/PC equipment? The power supplies in these devices can attenuate an Insteon signal to the point that it may not reach all devices. A FilterLinc should be used with UPS/PC. Look for a pattern. Are the devices that are not responding on the same circuit? What else is on that circuit? Finding comm problems can be a long frustrating process and often have more than one cause.

With the I/O Linc working plugged in at the PLM it does sound like a comm problem. There could be something in the garage such as florescent lighting for example that is generating noise on that circuit. The garage may be susceptible to noise if that circuit is on the opposite 120V leg as the ISY PLM. The hardwired Insteon coupler is passive, not repeating the message at maximum amplitude as Access Points do. First thing would be to look for something that is generating interference. I would normally suggest adding an Access Point to the garage but this is useful only if you have Access Points or other Dual Band devices in RF range of the garage. EDIT: reading your last post again I am confused. Moving the I/O Linc and using jumpers to test the Sensor things work Okay. But then nothing works regardless of where plugged. Can you clarify.

Yes, that is exactly right.

Factory reset the SwitchLinc and then Restore Device for the SwitchLinc. Right click the SwitchLinc node and select Restore Device. If could be a half link in the KPL. The simple solution to that possibility is to add the SwitchLinc to the Scene that has KPL button C as Controller. Then Delete the SwitchLinc from Scene.

Disable the two Programs that are sending X10 signals and see if the SwitchLinc continues to follow KPL button C. The SwitchLinc could have an X10 code assigned and it is following the X10 messages.

That is very unlikely. Insteon messages are complex with a validation character (CRC) making it almost impossible for noise to be interpreted as a valid Insteon message. Noise can prevent a valid Insteon message from being recognized but never generating a false Insteon message. More likely candidates are loose wiring in the magnetic switch connection, magnet is not close enough to the switch, or the "Trigger Reverse" option is being used and the I/O Linc was Queried. Trigger Reverse option reverses the commands sent, On command for Sensor Off, Off command for Sensor On, but it has no affect on the Query response. A Query will change the status to the true Sensor state rather than the reversed state.

If the light is physically controlled by the FanLinc the FanLinc Responder Ramp Rate for the light is the place to set the 2 second ramp rate. Outside the ISY world the FanLinc Light Ramp Rate is established with the Set button on the FanLinc, locked in and then the FanLinc is linked as a Responder to whatever Controller device is controlling the side of the FanLinc that is controlling the Light. Both the On Level and the Ramp Rate values are stored in the Responder link record in the FanLinc.

When I touch the Sensor to GND (a few hundred mili-seconds at most) the I/O Linc generates a full Group On message sequence followed by a full Group Off message sequence. Each Group sequence consists of a Group Broadcast, Group Cleanup Direct and ACK back from PLM to the I/O Linc. I had no problem seeing the Admin Console change the Current State column from Off to On to Off. This does not answer the question of minimum pulse width but it does seem to show if the probe had taken the Sense input to GND even for a short time there would have been Insteon message generated. There are always thresholds so a few mili-seconds might not cause the I/O Linc to generate a Group message.

"I guess the problem here is I’m trying to start a scene with an OFF command." The only thing an Off command can do is turn the Scene Off (without an ISY).

Skripo If the Green Sensor LED is correctly tracking the door state then either there is a comm problem between the I/O Linc and the ISY PLM or there is a link record problem in either the I/O Linc or the PLM. The simplest way to determine which is to move the I/O Linc to the same plug point as the ISY PLM. Two short wires connected to the GND and Sensor connections. Strip a little insulation off the free ends so that the wires can be touched together. There is no issue with shocks as this is very low voltage controlling a digital circuit. If the Sensor node tracks as the wires are shorted and opened with the I/O Linc plugged into the PLM plug point there is a comm problem between the garage and the ISY PLM. If the Sensor node does not change state as the wires are shorted and opened there is a link record problem either in the I/O Linc or the PLM. You can Restore Device for the I/O Linc first. If that does not resolve the problem then Restore Modem (PLM). An alternative is to Delete the I/O Linc and add it back to the ISY which will create the links again in both devices.

If Time is 5:30:00PM Then Set Scene 'SceneKitchenLights' On Wait 40 minutes Set Scene 'SceneFamilyRoomLights' On Wait 5 minutes Set Scene 'SceneKitchenLights' Off Else - No Actions - (To add one, press 'Action') The Program can be Disabled when not needed. Some folks use a KeypadLinc button On when away. The KeypadLinc button On would trigger a program to Enable the above Program.

Have you looked at the Green LED on the I/O Linc itself? Is the Green LED normally On when the door is open or On when the door is closed? Does the Green LED change as the door is opened and closed?

Mark Program B Disabled. It can still be called from another Program but will not trigger the If on its own.

Radio Shack carries a simple 24VAC relay ($11.64). Connect the coil in parallel with the door bell, just as the probe was connected, and the Com and N/O contacts to the I/O Linc GND/Sensor connections respectively. NTE R14-11A10-24 10Amp 24VAC Relay Model R14-11A10-24 Catalog #: 55048264 Tests show it takes less than a second of GND to Sensor to cause the I/O Linc Sensor to send the On command. Any press of the door bell button that rings the door bell will trigger the I/O Linc Sensor.

ELA Latching mode applies to the I/O Linc Relay. The I/O Linc Sensor has no optional modes. There is an I/O Linc option for the Relay to follow the Sensor but this overrides the Relay Latching mode. The Relay does not Latch up if the Sensor is pulsed.

I would need to know exactly what you were reading that discussed Groups to answer that. There are other subjects that use the term Group. KeypadLinc Button Grouping for example. That discussion would have nothing to do with a collection of devices (Scene).

Can you identify the specific area you are reading about Groups. From an Insteon perspective, Group and Scene is the same thing. The term Scene is used in external end user material such as the Quick Start Guides, User Guides and sales pages on the Smarthome site. The term Group is used in the internal hardware reference material. Again, they mean exactly the same thing. Just depends on which document is being used. However, I don't know what you were reading where Groups were being discussed so Groups may mean something different. Need to know in what context Group is being used. .

cats First, from the posts on Smarthome forum and here I'm not sure the InLineLinc w/sense is wired as it should. The Sense wire on the InLineLinc should be connected to the motion head sense line. The motion head sense wire that turns On when motion is sensed. It may have just been the working on the other forum that made me think it was wired wrong. If this is the way it is wired, good. The function of the InLineLinc w/sense, to turn On when the motion head detects motion and turn Off when the motion head times out, can be overriden with a Fast On and a Fast Off. A Fast On command will turn the InLineLinc On and it will stay On regardless of the Sense line. A Fast Off command will turn the InLineLinc Off and it will stay Off regardless of the Sense line.

John Thanks for the update. As an FYI for others, battery RF devices in general require the Device Type field pulldown be used to indicate the device type being added. Auto Discover does not work with battery RF devices.