LeeG

Do not use Button Grouping. If mutually exclusive KPL buttons (radio buttons) are desired use a Scene to accomplish this. Factory reset will remove all the KPL links including the manual ones. After that a Restore Device must be run to put back the link records the ISY created when the KPL was added to the ISY.

The 2457D2 is listed in the 3.3.4 Device Type pulldown. If it does not add successfully under 3.3.4 run Tools | Diagnostics | Event Viewer at LEVEL 3. Use New INSTEON Device, entering Insteon Address, Name of choice and leave Device Type set to default Auto Discover. Post the event trace.

1. How do I add a button from a keypad to the scene so that it is a controller? Drag the KPL button to the Scene Name and Drop. Note that an Insteon paddle/button can be a Controller of one Scene only. This is the Insteon design point, not an ISY limitation. Need to know why a given KPL button needs to be a Controller of more than one Scene. 2. Do I then have to write to the keypad so that it is updated (and would work if the ISY went down) or is this done automatically The Scene will work even if the ISY is down. The ISY automatically writes the necessary link records to the Controllers and Responders 3. Can I add the A button's from each of the 3 keypads to the same scene? Would one be the controller and the others be responders? Would the LED on the buttons stay in sink? KPL button A from all three KPLs can be added to the same ISY Scene as Controllers. Button LEDs will stay in sync. 4. If one of the lights in the scenes is turned on will the button also turn on? No. Insteon does not work that way. 5. Can I make a Scene of a scene (it doesn't look like it), so that D can be an aggregation of A, B and C? No. Scenes cannot be chained together.

That technique for accessing the Admin Console is fine. That is what I have been using for years. Remember to clear the Java cache after installing 3.3.4. Always a good idea to run Help | About after an upgrade to insure both Firmware and UI lines indicate what was just installed. The device will have to be Deleted and added under 3.3.4.

That is correct; the I/O Linc can be anywhere. I assumed since the kit is a wireless chime the I/O Linc and chime transmitter would be distant. The entire kit, I/O Linc and chime equipment could be inside. Using an ISY Program is one approach with the coding as you describe. The other would be an ISY Scene with the four EZIO6I Inputs as Controllers with the I/O Linc Relay as a Responder. Using a Scene would have the chime come on slightly faster.

Don't know about the range through the walls but conceptually it will work. Some folks have reported using piezo alarms connected to an I/O Linc Relay using the I/O Linc 5V. Would be less than half the cost and the I/O Linc would be inside. See this link for piezo alarm information viewtopic.php?f=27&t=9846&p=75101&hilit=piezo#p75101

It is best to move to 3.3.4 and use one of the Momentary modes. Or use the I/O Linc User Guide and set one of the Momentary modes with the I/O Linc Set button. If there is any comm problem that prevents awareness of the need to send an Off or the I/O Linc from receiving the Off it will leave the Relay On. This will prevent the normal manual garage door button from working. Once the I/O Linc function is understood it is a nice device. Smarthome sells the I/O Linc with some dozen different kits for different applications. Makes the defaults difficult to tailor for so many different uses. Actually there is an industry standard but it is different by industry. Devices sold for Security usage describe NO and NC in the context of switch state when the magnet is next to the reed switch. When used outside the Security environment the switches carry the opposite nomenclature. How much you want to bet both industries consider themselves right.

Check Help | About, verify that Firmware and UI are listed at 3.2.6. If UI not 3.2.6 clear Java cache and be sure to use URL for accessing 3.2.6 Admin Console I agree completely with oberkc, upgrade to 3.3.4.

This means that both MControl buttons have to be On, "Automatic Gutter Deicing" and "Snow On Roof", for deicing to work. Either button being Off defeats deicing. Also means that "Automatic Gutter Deicing" must be turned On first followed by "Snow On Roof"

Using Query is a good test that does not change anything at the device. Right click the I/O Linc Sensor or Relay node, select Query. The following are from a Query of an I/O Linc Sun 11/25/2012 05:57:27 PM : [iNST-TX-I1 ] 02 62 15 BB 5A 0F 19 01 Sun 11/25/2012 05:57:27 PM : [iNST-ACK ] 02 62 15.BB.5A 0F 19 01 06 LTSREQ (01) Sun 11/25/2012 05:57:27 PM : [iNST-SRX ] 02 50 15.BB.5A 19.70.06 2B 00 00 (00) Sun 11/25/2012 05:57:27 PM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 11/25/2012 05:57:27 PM : [iNST-TX-I1 ] 02 62 15 BB 5A 0F 19 00 Sun 11/25/2012 05:57:27 PM : [iNST-ACK ] 02 62 15.BB.5A 0F 19 00 06 LTSREQ (LIGHT) Sun 11/25/2012 05:57:28 PM : [iNST-SRX ] 02 50 15.BB.5A 19.70.06 2B 00 00 (00) Sun 11/25/2012 05:57:28 PM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 11/25/2012 05:57:28 PM : [ 15 BB 5A 2] ST 0 Do a Query of a sample of devices around the house. This might show a pattern where comm is good and where it is bad which may help identify the source.

Thanks. Access Points are not linked together. If referring to the 4 tap Set button test, this test verifies the Access Points are within RF range of each other and on opposite 120v legs. The LED blink pattern and color on the second Access Point provide the feedback as to RF reception and if on opposite 120v legs.

Either Folder or Program, right click on name - select Copy to Clipboard (last option) - paste to forum post. The Folder Variable $Automatic.Gutter.Deicing and Program Variable $Snow.On.Roof, how and when are these State Variables being set?

Release 3.3.5 is the next one available. It has not been released yet.

The Folder provides a set of Conditions that are generally applicable to the group of Programs in the Folder. Makes it easier to define the Conditions once in the Folder rather than replicating the same Conditions into many Programs. The Folder Conditions inhibit the ability for Programs to be triggered (execute/run) or allow Programs to be triggered (execute/run) but do not cause Programs to be triggered. It is the specific Conditions in the Program that determine the Events that will trigger a Program (cause it to execute/run). There is still an open question why the State variable change Anded with the If Status of the EZIO2X4 Input does not trigger the Program. If you can post the Folder those Conditions can be checked against the Program Conditions to see why changing the State variable does not result in the Program being triggered.

The Relay status shown by the Admin Console is not accurate because the I/O Linc does not tell the ISY when it turns the Relay Off automatically with Momentary mode. Since Direct On commands are being used in your implementation the Relay shows On even though the Relay is actually Off 99% of the time. This has no functional effect on the results. The Direct Off commands are not needed and could interfere with Sensor messages being sent from the I/O Linc. A pair of Access Points are the best means of coupling the two 120v legs. The Hops Left=0 indication means that either because of distance or lack of phase coupling or interference the Insteon signals to and from the I/O Linc location are operating at the extreme edge of reliability.

Use Red/Black to produce I/O Linc Sensor On when door is Open (magnet away from reed switch). Just to make things more complex you need to be on 3.3.4 as 3.2.6 has a bug associated with setting the new I2CS I/O Linc options. The confusion about Relay On/Off versus door opener movement is due to the fact that the Smarthome documentation assumes a Scene is used to control the I/O Linc Relay. Since Smarthome devices cannot send Direct On/Off commands (except PLM with HA), only Scene On/Off commands, all the Smarthome doc describes device operation relative to Scene usage. Sending a Direct On command to the Relay ALWAYS turns the Relay On. Being a garage door implementation Momentary mode (any of the three) automatically turns the Relay Off to simulate manual button operation. The Direct Off command serves no functional purpose as the Relay is always automatically turned Off with Momentary mode. When Scene On/Off commands are used to control the I/O Linc Relay it will operate according to the Smarthome documentation for the various Momentary modes. Again, need to be on 3.3.4 for the Set Options to work with the new I2CS I/O Linc.

It is a water proof switch and comes in a housing that can be attached to the floor. However, that does not mean it has to be mounted on the floor. Mount it on the door header if that is the preferred location. Mine is mounted on the header. I used standard security magnetic switches in the beginning. Worked fine initially but as the weather changed I found the door/track relationship would sometimes result in the switch not working. The dual NO/NC magnetic switch Smarthome originally included with the garage door kit (now available separately) comes with a very large magnet allowing the switch to work over a wide range of positions (Wide Gap switch).

If the door is not too loose and the magnet and reed switch are located close together it should work. I was referring to the dual switch with the shielded cable sold by Smarthome as being Wide Gap. It is spec'ed as being Wide Gap. The one from Amazon does not say it is a Wide Gap switch.

The Smarthome magnetic switch with both NO and NC can be mounted above the door just like you have now. Or swap for a NO switch. The advantage of the Smarthome variant that has both NO and NC is it is a Wide Gap switch with a large magnet. Many of the single type switches are not Wide Gap. The Amazon switch should work but it is not labeled Wide Gap. That will make the spacing between the magnet and the reed switch more sensitive.

Using the opposite magnetic switch or the switch with both NO and NC does solve the problem. With the correct magnetic switch the Sensor will be Off when the door is closed. Once the new sensor is installed turn Off Trigger Reverse.

What does it display for UI which is the line below Firmware?

I think the point that is being missed is that a Program is not “running†until it is triggered by an event identified in the IF section. Since the If Status event changes state before the Folder condition is True that did not trigger the Program and will not trigger the Program when the Folder condition is True until the Status changes state again. The If State variable will trigger the Program when the State Variable value is changed assuming the Folder condition is True. Once the Program is triggered by a change in the State Variable value the If Status xxxx is On check will participate in the If evaluation. The question is why a State variable change is not triggering the Program. Either the Folder condition is not True when the State variable value is changed or it is not a State Variable.

I don't use MobiLinc so will not be of much help. There is a MobiLinc category where the question might be better posted. Does Help | About show the right values for Firmware and UI?

Add the new Thermostat. Then use Replace xxxx with .... function against the old thermostat definition. The old Insteon address will not be referenced

The I/O Linc Relay sequence is somewhat unusual. The Relay is turned On, followed 5 seconds later with a Relay Off. Two seconds later there is another Relay On, followed 5 seconds later by a Relay Off. The second Relay On/Off sequence, which simulates a second manual press of the garage door button, could stop door movement before it opens fully. This is followed nearly 1 minute later by another Relay On/Off sequence which is then followed 4 seconds later by an I/O Linc Sensor On. There is no Sensor Off message in the trace. The Sensor must have turned Off when the door opened, otherwise there would not be a Sensor On message when the door closed. Powerline communication with the I/O Linc is poor. All the communication is Max Hops=3 Hops Left=0 which is as bad as it gets and still see communication. Sat 11/24/2012 08:11:03 PM : [std-Direct Ack] 1F.51.67-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sat 11/24/2012 08:11:08 PM : [std-Direct Ack] 1F.51.67-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Also not sure why the Relay Off commands are being sent to the I/O Linc. Normally the I/O Linc Relay is set to one of the Momentary modes so the I/O Linc automatically turns the Relay Off. It is possible the Relay Off is interfering with the Sensor Off message when the door is initially opened. Could also be the Sensor Off message was lost due to the bad comm I would put the Relay into Momentary mode and stop sending the Relay Off commands. Also the issue with communication with the I/O Linc should be cleaned up.