LeeG

Add a Wait 2 Seconds before the Set Scene Off in both Programs. Test again. Be sure to Save Changes.

You indicate that KPL A remains On. Which is KPL A? Backdoor Porch - A Front Entryway - A Master Bedroom Switch - A

The device must be a dimmer. The Action Insteon pulldown for a dimmer, along with On, Off, etc, there are % On levels that should be listed. What does the Admin Console show for the device type? The line below the device name in the right pane. The Bright/Dim change the On Level a set amount. About 3% for each Bright/Dim statement if memory is correct.

I don't know what the tstat sends when. If Status was not working and a command is sent when the heat comes On it is because there was no corresponding heat Off. The Status MUST change for an If Status to trigger a Program. The Event Viewer will show what commands are flowing from the tstat. That will show what the tstat sends when the heat cycles.

Use If Control rather than If Status. If Control triggers every time the command is received. If Status triggers only when a change in Status occurs.

If Control 'KeypadLinc Dimmer 6 Button / KeypadLinc 1 Dimmer 6 Button A' is switched On Or Control 'KeypadLinc Dimmer 6 Button / KeypadLinc 2 Dimmer 6 Button A' is switched On Then Set Scene 'SceneCButttons' Off Else - No Actions - (To add one, press 'Action') If Control 'KeypadLinc Dimmer 6 Button / KeypadLinc 1 Dimmer 6 Button C' is switched On Or Control 'KeypadLinc Dimmer 6 Button / KeypadLinc 2 Dimmer 6 Button C' is switched On Then Set Scene 'SceneAButttons' Off Else - No Actions - (To add one, press 'Action')

Define two ISY Scenes. One ISY Scene xxxx has both KPL button As as responders. The other ISY Scene yyyy has both KPL button Cs as responders. Define an ISY Program that triggers from button A press on either KPL and have the Then clause Set Scene yyyy Off which will turn Off the C buttons. Define another ISY Program that triggers from button C press on either KPL and the Then clause Set Scene xxxx Off which will turn Off the A buttons.

Assuming the Current State column is not all blank and many devices are not indicating state changes a File | Restore Modem (PLM) is the place to start. There could be other causes. All the devices not reporting state changes are on the opposite 120V leg to the ISY PLM and something has happened to the Access Points that are coupling the two 120V legs. PLMs have been known to lose link records. Sometimes means the PLM is approaching failure but not always.

Either the link records in the device and/or PLM have been lost or there is a comm problem. In this case it is more likely a link record problem since the device can be controlled through the Admin Console. Controlling the device through the Admin Console uses Insteon Direct commands which are not dependent on link records for their operation. Pressing a button/paddle requires link records in both the device and the PLM for the ISY to be aware of the button/paddle press. The device does not send any commands if its link records have been erased. The PLM does not receive commands if its link records have been erased.

A change in Status triggers the Program. The evaluation of the If for True or False determines whether the Then or Else clause runs.

The SwitchLinc Current State as On could have been from a previous command. Run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Watch for Insteon traffic from the SwitchLinc when the On paddle is pressed. If the On command is received and Program Last Run Time does not indicate the Program was triggered be sure the Program was Saved. If the Program was Saved likely there is intermittent comm with the SwitchLinc.

The Status has to change for Status to trigger a program. Repetitive Heat-Control Ons do not trigger with Status as there is no change in Status.

If Control 'KeypadLinc 8 Button / KeypadLinc 8 Button - B' is switched On Then Set 'KeypadLinc 8 Button' Off Else - No Actions - (To add one, press 'Action') The ISY User Guide and the ISY Wiki have good information on the various Program elements.

The EZIO2X4 link database in the device itself has been corrupted. You can try a Restore Device and then another Show Device Links Table (event viewer not needed). Was the EZIO2X4 upgraded by SHN?

The ISY is not receiving the EZIO2X4 Input state change messages. This can be caused by a number of things. The EZIO2X4 configuration data has been lost or corrupted. The link records in the EZIO2X4 have been lost or corrupted. Both the configuration data and link records are established when the EZIO2X4 is added to the ISY. Could also be a communication problem between the EZIO2X4 location and the ISY PLM. I’m leaning away from this for now. If the link records are correct then either the configuration data will have to be verified with the SHN Utility or the EZIO2X4 deleted and added back to the ISY so it can be rewritten from scratch. There was a series of EZIOxx devices that were shipped with an internal PLM that had a combination of memory and firmware that are not compatible with the ISY. I believe these were before the time when your EZIO2X4 was purchased. It may be necessary to verify this EZIO2X4 is not in that group of devices. However, the configuration data and link records are higher on the list of possibilities for now. The Event Viewer trace will show what link records are in the EZIO2X4 and where they were written. If they are correct then the configuration data will be the next thing to look at. Because both are established during device add anything that affects their integrity will prevent the EZIO2X4 state change messages from being generated or received.

First run Help | About and verify the Firmware line and the UI line just below Firmware are both there and both indicate 3.1.17. If this is not true then clear the Java cache and be sure the URL for accessing the Admin Console is the correct URL. There have been a few problems reported where Java did not report the movement of a slider. Try moving the slider to a different position and release the cursor. A progress bar should appear when Java notifies the Admin Console of the slider move. If the Progress bar does not appear what level Java is being used?

Check the Help | About when under the Admin Console. The URL for 3.1.17 Admin Console is different from the URL to access the 2.8.16 Admin Console. The Help | About for 3.1.17 will have two lines, Firmware which shows the ISY firmware and UI just below Firmware which shows the Admin Console level. On 3.1.17 both these lines must be there and must show 3.1.17. On 2.8.16 the UI line is not there and 2.8.16 appears on a different line. I think the Java cache will have to be cleared each time you switch between the two Admin Console versions. The proof of that will be what the Help | About shows. I run two ISYs but they are both at 3.1.17 so no need to clear the Java cache. I always cleared the Java cache when I switched between the two systems until they were both on 3.1.17. I'm not absolutely sure about the need to clear the Java cache but think the Admin Console code names did not change so the wrong level will be pulled from the cache.

What ISY firmware is installed? 3.1.17 is the latest official release. Earlier versions will say Device communications events in the Level pulldown (no 3-). The Event Viewer is invoked. The Event Viewer popup has a Level pulldown that has the Device communication events

That purchase date should eliminate a potential problem with internal PLM configuration, Invoke Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Then run Tools | Diagnostics | Show Device Links Table for the EZIO2X4 and send me the event trace file at lwgwork@embarqmail.com. I think the trace file will be too big to post In the link record display produced by the Show Device Links Table verify there are E2 09 xx.yy.zz where xx.yy.zz is the ISY PLM address E2 0A xx.yy.zz Was the EZIO2X4 Input information accessed through the SHN Utility? What ISY firmware is being used?

The ISY User Guide and the ISY Wiki have some good information on ISY Programs. Also many examples on this forum itself.

I spoke to quickly. With ISY function there are generally multiple ways of implementing something. In this case an ISY Program can trigger on the Secondary button press and issue a device Off for the KeypadLinc primary button.

Without the Query the Admin Console does not show changes in state of nodea 9 & A? How old is the EZIO2X4?

Sorry, I have no suggestion. I tested the configuration on a v.36 KeypadLinc. A Secondary KeypadLinc button does in fact turn Off the Primary load button when the On Level is 0%. Of course I had to use alternative methods (different product) to set the On Level to 0%. Perhaps this was a limitation that did exist on older KeypadLincs.

The Replace xxxx with ..... function is there in 3.1.17. Right click on the old node and Select Replace xxxx with ... Note that there has to be a functionally equivalent device already defined for that function to show for any given node.

To question 1, what is the KeypadLinc firmware level? KeypadLinc buttons operate in one of three modes; toggle On/Off, non-toggle On, non-toggle Off. In the non-toggle modes only On or Off commands are issued. Use the Buttons Toggle Mode button to set individual KeypadLinc buttons to the desired toggle, non-toggle mode.