LeeG

EZIOxx devices do not use the On Level as Smarthome Insteon devices do. The EZIOxx Relays have the capability to respond individually, in patterns, or as if reacting to Input changes. As such the link record data fields have meaning other than the standard On Level and Ramp Rate. The On Level should be returned to 0% On Level. An EZIOxx Relay cannot be turned Off with an On command.

It sounds like the KeypadLinc ON/OFF buttons are controlling main power going to the Fan itself rather than being linked only to the FanLinc for Light control. Explain how the KeypadLinc and FanLinc are wired to the Fan. How many wires going to the Fan (and color) and what they are connected to at the Fan, KeypadLinc and FanLinc.

Glad that worked. Thanks for taking the time to post back the results. It can be helpful info to others who follow.

When KPL button is turned On the thermostat setpoint is changed to away setting, a Wait of 5 hours is established, when Wait expires the thermostat setpoint is changed to home setting. When KPL button is turned off the thermostat setpoint is changed to home setting. If Control ‘kpl button’ is switched On Or Control ‘kpl button’ is not switched Off Then Set ‘thermostat’ setpoint xx Wait 5 hours Set ‘thermostat’ setpoint yy Else Set ‘thermostat’ setpoint yy

Based on what is posted the KPL ON button should not be reacting to the A button being pressed. Suggest doing a Factory Reset of the KPL and Restore Device to rebuild the device configuration. Then see if the A button is affecting the KPL load (ON button). Also the Adjust Scene statement in the Then clause of the Program does not seem useful. What is the purpose of Adjust Scene statement? As written it is setting the Scene Responder On Level in the Responder link record which once changed does not need to be changed again.

barrygordon The Programs | Summary page is a good place to start. It contains the Last Run Time and Status (True/False evaluation of If) for each Program. If the Program did not Run look at the Folder conditions if the Program(s) are in a Folder. If it Ran but has a Status of False the Else was driven which may have prevented commands from being issued. If the Program Ran and the Status is as expected then look at what the Program issued. Scene commands can be less reliable if the Insteon Mesh Network has marginal areas. Although you mentioned not turning On as well, not turning Off can be the type of load the device is controlling. It is not unusual for a device to turn On but not respond to Off because of the interference generated by the load being controlled.

Barrygordon As Michel and hbsh01 have already noted this is an Insteon limitation. Every button on a KPL has a specific Group number. For example, a 6 button KPL Secondary button A = Group 3, B = Group 4, C = Group 5, D = Group 6. For the KPL to know which Secondary button should react to a command it must be told the Group number of the button. Insteon Direct commands do not have a field (placeholder) for a Group number so the Secondary button cannot be identified. Responder link records do have a field for Group number. That is why Secondary buttons on a KPL must be commanded by a Scene that has a Responder link record associated with it. The Primary load control button (Main A on 8 button KPL, ON/OFF on 6 button KPL) is assumed to be the button being controlled by Direct commands. That is why Direct commands can turn the KPL load On/Off but cannot control Secondary KPL buttons. There is a very old document, insteondetails.pdf, on insteon.net web site. The document details the Insteon Direct message field by field. Although an old document the field format of the Direct message has not changed since Insteon was first released.

Elburn Two ISY devices are not configured to talk to each other in the sense you are thinking about. Each ISY could have the Network Module used in conjunction with ISY Programs to send IP messages between the ISYs that contain REST commands to tell the opposite ISY whatever information you want to communicate. You will need to understand how to use the Network Module and how to use REST commands. Keep in mind one ISY knows nothing about the other ISY beyond the fact that it is sending IP messages to some other device on the Network. Those IP messages could just as easily be controlling an IP camera as sending information to another ISY. This is much more complex than just installing two ISYs.

thomas The 'not Off' is used with 'If Control' which is looking at commands flowing from a device. When using 'If Control', a Program is triggered ONLY on the specific commands being tested for. Without the 'not' the Else clause would not be executed (as apostolakisl said) because the If would always evaluate to True. If is also used with ‘If Status’ when checking a Dimmer which can have many Dim values between Off and On (which is 100% On). A single “If Status ‘xxxx’ is not Off†would be True if the Dimmer is anything but Off (5% On, 50% On, 100% On, all result in a True If evaluation with not Off). The examples you are referencing look like If Control ‘xxxx’ is switched On Or Control ‘xxxx’ is not switched Off Then ……. Else …… If Control triggers ONLY when the specific command is received. When an On command is received the Then clause executes. When an Off command is received the Else clause executes because of the ‘not’.

"So the next question is...what happens if the pump turned on at 7:25AM? The program would not be invoked until 7:30AM and, assuming the pump is still on at 7:40AM I would get an SMS at 7:40AM? Or did I "miss" the On event for the pump I was outside my time window?" The Notification message will be sent at 7:40AM assuming the pump sensor is still On. The From time, 7:30 AM, triggers the Program. The If will be True assuming the sensor Status is On. The Sensor turning On also triggered the Program but since the 7:25 AM time is outside the From/To time window the If is False which drives the Else clause. Note the two Sensor Status checks are redundant. Likely the Sensor is either On or Off which makes the not Off Status check unnecessary.

thomas, arw01 When in a Wait or Repeat statement any change to the Status conditions the If is checking causes the Program to be triggered again from the beginning. The only change in Status in this case would be going from On to Off. The ‘If Status On’ would be False which drives the Else clause.

You can also tell by looking at the Show PLM Links Table results. After doing the Restore Modem (PLM) the Show results will generally be in Insteon address order although there may be more than one group of addresses in that order. This is an example of a 6 button KPL. There are 6 link records associated with the 6 button KPL being added to the ISY. There are 5 link records that have the various KPL buttons as Responders which are from using the buttons in ISY Scenes. 0015 : E2 3F 12.B9.0D 01 1B 36 0016 : E2 3E 12.B9.0D 01 1B 36 0017 : E2 3D 12.B9.0D 01 1B 36 0018 : E2 3C 12.B9.0D 01 1B 36 0019 : E2 00 12.B9.0D 01 1B 36 001A : E2 30 12.B9.0D 01 1B 36 001B : A2 01 12.B9.0D 01 1B 36 001C : A2 03 12.B9.0D 01 1B 36 001D : A2 04 12.B9.0D 01 1B 36 001E : A2 05 12.B9.0D 01 1B 36 001F : A2 06 12.B9.0D 01 1B 36

Some basic PLM link record counts: 8 button KPL – 9 link records 6 button KPL - 6 link records SwitchLinc – 2 link records LampLinc – 2 link records ApplianceLinc - 1 link record Motion Sensor – 3 link records Remote Mini 8 Scene – 8 link records Remote Mini 4 Scene – 4 link records Remote Mini – 1 link record Open/Close Sensor (TriggerLinc) – 2 link records Thermostat – 1 link record for each node Leak Sensor – 3 link records Smoke Bridge – 8 link records Generally 1 link record for each node for those not listed ISY Scene – 1 for each device that is reacting as a Responder (includes Controller that is also a Responder)

mmb Go to this link and scroll down to "Program Enabled Checkbox". http://wiki.universal-devices.com/index ... tion_Order "When the Enabled box is not checked, the program will not run in response to an event, but will still run normally when called from another program and when invoked directly from the Program Summary tab, provided any folder conditions in the program's hierarchy are True. "

Try removing power from the ISY to force it to reboot since the router was rebooted. Also unplug the PLM and restore power to it first before powering the ISY.

Sixburg On the front of the ISY, what LEDs are On? It sounds like the ISY might be disconnected from the router, assuming the ISY is configured for DHCP rather than a static IP. On the back where the Internet connection is located, are the two LEDs that are part of the Internet jack On?

Program 2 must be marked Disabled to prevent a change in Sensor Status from triggering the Program. This is the problem with the original implementation, the change in Sensor status was triggering the single Program. By breaking the If section into two Programs Program 2 with the If Status can be Disabled to prevent the change in Sensor Status from driving the process. In this case only the change of the Variable to 1 should trigger the process. The On/Off Status of the Sensor affects the Program flow but should not trigger the process. A Disabled Program can be ‘Run’ from another Program, Program 1 in this example, but it cannot trigger itself. This link into the Wiki might be helpful http://wiki.universal-devices.com/index ... e#Programs ..

mmb Actually I had no idea what the objective was. There are always several ways to implement things in the ISY. One way is to set up two Programs Program 1 If $iPhone_smith is 1 Then Run Program 2 Else Program 2 (this Program is marked Disabled so a change in Sensor status does not trigger program) If Status 'IO Linc Garage Sensor' is On Then Send Notification to 'Default' content 'Garage Door Notification Opening' Set Scene 'Garage Door Relay' On Else Send Notification to 'Default' content 'Garage Door Notification Closed' EDIT: I think the wording in the Else Notification is more accurate to say 'Garage Door Notification - already Open'

Your welcome. Thanks for taking the time to post back the results.

A change in the Variable value (assuming it is a State variable) OR a change in the Sensor state will trigger the Program. The change in Sensor state will trigger the Program so even if the variable is an Integer variable it having a value of 1 makes that part of the If True. When the I/O Linc Sensor turns On which with the current garage kit is when the door closes (unless trigger reverse is in use) the Program executes the Then clause Opening the door after it closes..

NeilP Any Insteon traffic reaching the PLM during the Show PLM Links Table run will produce in invalid link record display and subsequent invalid count. The Show PLM Links Table/Count should be run 3-4 times and only when the same link record count is obtained multiple times should the count be considered valid.

The first thing to do is issue a File | Restore Modem (PLM). PLMs accumulate duplicate and outdated link records which the Restore Modem will eliminate. After the Restore Modem (PLM) completes run the Show PLM Links Table and Count again to see what the new link record count is. The ISY supports only 1 PLM. If the PLM link record count is at the maximum even after the Restore Modem (PLM) the next step to remove/combine ISY Scenes to reduce the PLM link count.

Count the number of links in the PLM using Tools | Diagnostics | Show PLM Links Table followed by Count when the Show display completes. No Insteon traffic can reach the PLM during the Show PLM Links Table as the count will not be accurate. Run the Show PLM Links Table followed by Count 3-4 times to insure the Show/Count sequence results in the same number. The maximum for a 2413 is 992 links. It sounds like the PLM link table is full so the necessary responder links for the Motion Sensor cannot be added to the PLM

Changes cannot be sent to the 2441ZTH as it is asleep.

mmb A change in xxxxx Status causes a Program with If Status xxxxx to trigger. When the If is True the Then clause executes. When the If is False the Else clause executes. Same with a State Variable. Any change in the State Variable value triggers the Program. Suggest posting the Program. Right click Program name, select Copy to Clipboard, paste to forum post.