LeeG

"Just to clarify that: If a trigger condition changes and logic becomes negative, resulting in the "else" clause being invoked, the "then" clause wait timers (and following lines of code) get cancelled right where they are?" The above is correct but not limited to If becoming False. A change in the trigger conditions cause the If to be reevaluated (while in Wait or Repeat statement) which may drive Then or Else clause.

The Leak Sensor nodes are Controller Only nodes. The nodes have no function to Query so a Is Not Responding is not condition that will exist past getting the device installed. Heartbeat On and Off are the two conditions to be checked.

A functioning Insteon Mesh Network is often not as easy as plugging a device in at the desired location. A pair of Access Points to couple the two 120v legs, isolating noise/attenuation sources at the PLM location are a few items that have to happen. Plugging the ApplianceLinc into the PLM location avoids the need for the above. Of course it is not a solution but does verify the PLM and ApplianceLinc function together. Now the other requirements can be implemented to get started on creating a good Insteon network.

The last link being discussed is a deleted link record. The device containing this link should not functionally be reacting to this link record as it logically does not exist. As with the first deleted link discussed earlier, if the device is reacting to a deleted link record the device is defective. My normal direction about deleted link records is to do a Restore Device to physically eliminate the record. Unless the device is defective a deleted link record has no affect on the device. I would guess that most of the installed devices have deleted link records.

I do not use Mac but there have been various posts about the OS/browser unzipping the download file. The ISY expects the file to be ZIPed as it was before the download.

Do a Show Device Links Table and then Compare when the display completes. What does the ISY think that link record should look like?

It took a long time to go through each entry converting the values back to hex. I do not know why the ISY Restore Device would write a deleted link record. It looks like a Scene was adjusted after the Restore Device. Like the other deleted record it should not affect what happens when button H is pressed.

There may be an issue with how the LED works on that level of KPL. The ISY marks the node Off because in non-toggle Off mode the button issues an Off command only.

The two Black nodes are the two EZIO2X4 relays. The Red nodes are the 4 Inputs. The 9,A,B,C are assigned by the ISY as Scene (Group) numbers of Inputs 1,2,3,4.

"To anyone who owns a EZIO2X4 module, how good is it? Is it easy to get the status of the inputs? Are its nodes updated automatically when the inputs are triggered?" The EZIO2X4 Input nodes update automatically just like KPL buttons. I have been using 2 EZIO2X4s in a detached garage for monitoring and controlling the bay doors for years. Note that Inputs 3&4 need to be connected to EZIO2X4 Gnd until they are connected to an actual Input control. These Inputs can support Analog so have no built-in pull up resisters. These are two EZIO2X4s in my test bed. Just like KPLs the nodes can be grouped or ungrouped. First EZIO2X4 is ungrouped, second is Grouped.

Try plugging the Dual Band ApplianceLinc into the same outlet as the PLM. What are the symptoms?

That is another deleted link, this one for button H. It should not be there after a Restore Device. Can you post the Show Device Links Table display?

Deleted links are not rewritten by Restore Device. An active link that the ISY thinks should be there will be written but not a deleted link.

That line is a Deleted link record and should have no affect. If the Cabinet Lights are reacting to that link record the device is defective. Do a Restore Device for Cabinet Lights device which will eliminate deleted link records.

The SwitchLinc has to be a Controller of a Scene for it to be available for the 'In Scene' parameter of an Adjust Scene statement.

When the new PLM was added were the steps in the Wiki followed for replacing a PLM? http://wiki.universal-devices.com/index ... _.28PLM.29

The fact that the event viewer is displaying messages from 24.02.43 indicates the PLM has a link record for that device. Otherwise the PLM would not pass the message on to the ISY. What does Help | About show on the Firmware line and the UI Line?

According to Summary display the Program has never been invoked (nothing in Last Run Time). Are there conditions in My Programs Folder?

The Program did not issue the statement in the Then clause. Go to Programs | Summary display and check the Last Run Time and Status for the Program. Does it match the last double tap time? Also is there a Save pending for the Program?

Andreas Fast On is not dependent on the device already being On. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Watch the messages sent to the PLM when the paddle is double tapped. I suspect you are getting two On commands rather than one Fast On. The speed of a double tap can take some practice. Watch the event viewer output until the correct speed of the double tap is obtained. You can also check that the 'Garage' switch is On when an On is received and execute the Then If ( Control 'Garage' is switched On And Status ' Garage' is On ) Or Control 'Garage' is switched Fast On Then turn on device

Or move the function into the Controller. Use a KPL button, something to indicate the normal ISY changes should not occur. Would be nice to trigger that with the HOLD button but since the thermostat did not implement it that way it has to be a different Insteon device.

From the User Guide ... Hold overrides a preprogrammed mode to stay in the current settings mode. While Hold is enabled, the next preprogrammed time that comes in Time of Day Mode will be ignored. It appears HOLD keeps the thermostat from changing to the next programmed setting. Heat/Cool modes have no 'next' as far as the thermostat is concerned. That would be my guess. A question that would have to be addressed by SmartLabs for the actual why.

What Mode is the thermostat when HOLD is pressed? Mine indicates HOLD only when using in Auto/Return.

Locate the issue first, then work on how it happened. Once the issue is found there may not be another question. Go to the Programs | Summary display. Right click the first Program name, select Find/Replace looking for the Insteon devices.

It sounds like an ISY Program is being triggered and turning the devices back On.