LeeG

Right click the Program name, select Copy to Clipboard. Post the Program.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Press the Off button a few times with at least 2 seconds between. Post the event trace. It sounds like the PLM is not seeing the device button/paddle press. What else is installed besides the devices mentioned? Also what are they? Do you have Access Points coupling the two 120v legs?

Insteon devices recognize when a button/paddle is quickly pressed twice. It is referred to as Fast Off in this case. Fast Off turns the kitchen lights Off just as a single tap does. In addition an ISY Program can be written to recognize a Fast Off situation and turn Off a Scene of lights that represent the full first floor. If Control 'xxxx' is switched Fast Off Then Set Scene 'yyyy' Off Else Device xxxx is the where a double tap is done. yyyy is a Scene containing the first floor lights. It may take a little practice to create the Fast Off.

The highlighted Program was triggered at 1:15AM with a False status which means the Else clause ran. If you want to pursue an event trace at LEVEL 3 while the KPL button is turned Off would be the next step. No reason to think the Off command was not issued since the Else clause was executed.

The first Program did not participate because the KPL button was On. What does the ISY show for the button Current State now? What does Programs | Summary show for second Program Last Run Time and Status? Was the Program triggered at 1 AM (approx) and does it show a False Status? If so then there is a comm issue as the Program would have issued the Off command. What type load is being controlled as a device that turns On but does not turn Off can be load related.

A few points. Insteon allows one scene (button press message) to run, cancelling others so if the paddles were pressed at the same time results could be different. Second, a Fade Down without a Fade Stop is missing the final message. From a hardware perspective it is not possible to have a Fade Up/Down without a Fade Stop. Devices can produce odd results when a Fade Up/Down is issued without the Fade Stop. Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Reproduce the situation and post the event trace.

Post the actual Program. There are some normal oops, using (same day) instead of (next day), a missed Save, a missing "not", things like that. Also since Scene and Direct commands have not worked an Insteon network issue could be involved.

The 'is responding' tests for a red ! associated with the node being tested. The red ! indicates a problem communicating with the node being checked. I did a Query for each of the Smoke Bridge nodes, none of which actually was sent the Query command. It looks like the nodes are all considered 'Controller Only' nodes where the device does not maintain a Status for any of the nodes. This means there is no mechanism for testing if the device is powered.

Connect Inputs 5 & 6 to the EZIO8SA Gnd. Otherwise these Inputs will cycle On/Off enough to cause problems.

This is the message sequence from a 2441TH running in Auto mode. Set Point was dropped one degree. Mon 12/30/2013 10:17:17 PM : [iNST-SRX ] 02 50 1D.6C.D6 22.80.0B 01 72 3D (3D) Mon 12/30/2013 10:17:17 PM : [std-Direct ] 1D.6C.D6-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Mon 12/30/2013 10:17:17 PM : [ 1D 6C D6 1] CLISPH 122 Mon 12/30/2013 10:17:18 PM : [iNST-SRX ] 02 50 1D.6C.D6 22.80.0B 01 71 51 (51) Mon 12/30/2013 10:17:18 PM : [std-Direct ] 1D.6C.D6-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Mon 12/30/2013 10:17:18 PM : [ 1D 6C D6 1] CLISPC 162

I think I have the sequence. It did not report Set Point changes at the thermostat under ISY. The thermostat was added to HL and it does report Set Point changes. Unfortunately the link table I would want to look at is now gone from the HL activity. The thermostat environment has to be reestablished for the ISY. Was that done?

Unfortunately phrasing does not change the fact that adding the thermostat to HL destroyed the ISY environment. Right click the thermostat node and select Restore Device. Then see what the ISY event viewer at LEVEL 3 indicates. Different PLMs can have different powerline/RF reception. How many nodes are defined for the 2441TH?

For events to show in the HL trace the thermostat must be linked with the HL PLM. This could have erased the links necessary for the ISY PLM to see the events. Run a Show Device Links Table / Compare against the thermostat to see if links are missing. The revision 1.6 is hardware level. The v.0D is the device firmware level.

Cannot speak to Mac. On a Windows system I issued http://192.168.2.3/rest/programs <program id="0001" status="true" folder="true"> My Programs Folder2 Not Saved Folder Test Folder Status Under Programs | Summary the ID of the item is in the right most column although My Programs is not listed as it is an ISY item rather than a user item. EDIT: I assume My Programs will always be 0001

A Program/Folder is accessed by the ID (/rest/programs/). My Programs is accessed with http://192.168.2.3/rest/programs/0001 My Programs Folder2 Not Saved Folder Test Folder Status

Thanks oberkc My assumption to this point is the I/O Linc Relay will operate in any of the Momentary modes to achieve a momentary push button effect by the I/O Linc Relay. In any of the Momentary modes sending a Direct On command turns the Relay On. Momentary mode turns the Relay Off so sending a Direct Off command is effectively a no-op as far as the I/O Linc Relay is concerned. Sending a Direct Off command will cause the ISY to set the Relay “Current State†column to Off which has no affect on how the Relay operates (because Momentary mode has already turned the Relay Off). There are very different results when using a Scene to control the I/O Linc Relay. Again, assuming the I/O Linc Relay is in one of the Momentary modes, the I/O Linc Relay reaction depends on which Momentary mode is being used. There are three Momentary modes with the I/O Linc Relay reacting differently to a Scene command based on which Momentary mode is being used and which Scene command, On or Off, is used. The I/O Linc User Guide details how the I/O Relay works when using a Scene. The I/O Linc User Guide does NOT describe how the I/O Linc Relay reacts to Direct commands because it is impossible for another Insteon device (except the PLM under control of an application) to send a Direct command. Pressing a KPL button to control the I/O Linc Relay is using a Scene.

In a garage application the I/O Linc Relay is physically operating equivalent to a momentary push button. In this configuration the Relay is Off except for the second or two that is used to start the garage door moving. Of course there are combinations of Scene On/Off with Momentary modes where an Off command will turn the Relay On. There has been no discussion by either poster discussing Scenes and how Momentary mode interacts.

Drexx3 The I/O Linc Relay is a Responder Only device. When one of the Momentary modes turns the Relay Off the I/O Linc DOES NOT send message back to the ISY that the Relay is Off. The state of the Relay as understood by the ISY does not make any difference. The Relay turns On when sent an On command even when the ISY believes the Relay is already On. The state of the Relay does not indicate whether the door is open/closed/moving. The I/O Linc Sensor indicates the state of the door. Some users want the Relay to show Off so a Program is used to send an Off command to the Relay. Makes no difference to the operation of the door. The White LED on the side of the I/O Linc next to the Set button indicates whether the Relay is actually On.

The I/O Linc Relay should be put into one of the Momentary (A,B,C) modes. The Relay turns Off automatically after the Momentary timeout. Something on the order of 1-2 seconds normally simulates the press of the door opener manual button.

Controlling an individual device with Direct commands has no affect on any linked device. Turn the Scene On/Off if you want all the Scene devices to stay in sync. Insteon allows an individual device to be controlled with Direct commands which has an effect on that specific device only or control a Scene the device participates in and all the devices in the Scene stay in sync. You can write an ISY Program that monitors what happens to the LampLinc with Direct commands and perform whatever other actions you want to perform. However, this is outside of normal Insteon activity. Direct commands control an individual device, Scene commands affect all the devices in the Scene.

Controlling an individual device with the Admin Console or MobiLinc does not have affect on other devices that may be linked to the device. Turn the Scene that contains the KPL buttons and LampLinc On/Off. Also note that the LampLinc should be a Controller in that Scene. The LampLinc has load sense such that if the lamp is manually controlled the LampLinc will turn On/Off in response. The LampLinc turning On/Off in response to the lamp being manually controlled will turn the KPL buttons On/Off if the LampLinc is a Controller in the Scene.

Secondary KeypadLinc buttons cannot be turned On/Off with Direct commands. Assign the KPL buttons as Responders to an ISY Scene and turn the Scene Off.

ISY Programs run on the ISY.

That option clears the link records only. It does not affect other KPL options. I would use the Admin Console to set the non-toggle modes. It is likely that the entire KPL will have to be set to the default toggle mode. Then set the individual buttons to the desired non-toggle mode. The KPL firmware level is displayed on the second line of the KPL information displayed in the right hand window.

What is the KeypadLinc firmware level? What does Help | About show for Firmware? and UI? The KeypadLinc LEDs are performing opposite to what they should be. Was the toggle mode set with the ISY or done manually?