LeeG

That is great news! Some devices report I2 but do not function in I2 as expected. The MorningLinc is one of those devices. Best to run in Automatic as the default unless trying to solve some other problem. Even then it should be restored to Automatic. After adding to a Scene check that the MorningLInc On and Off nodes will still cycle the lockset with the On and Off buttons.

The default codes are for the ISY IR feature to receive IR signals directly. Has nothing to do with the 2411R sending Insteon commands in response to it receiving IR signals. You can use the IRLinc with the ISY. There is a link management option "Add button to IRLinc receiver" to add IR codes to the IRLinc and add nodes to the ISY that match the IRLinc codes.

The IR option is additonal hardware. Has to be ordered from UDI. This is needed for the ISY to receive IR signals. It is not needed for the ISY to react to commonads from the 2411R

The ISY did not go back to I1 which it should have. What does Link Management | Advanced Options show for the link option. It should be Automatic.

Your ISY99i does have the IR feature installed?

auger66 Were other RF only devices, such as Motion Sensor and/or RemoteLinc(2), working okay. Only the TriggerLincs were not communicating. There are baby monitors, 900 MHz wireless phones (either could be neighbors) that operate in the same frequency range. Lee

Programs can run at startup because of the "catch up" processing. This attempts to run Programs that may have missed the time based running because the ISY was down. The window of time for "catch up" processing time period is a Configuration option. Run At Startup insures that the Program If will be evaluated at every startup regardless of other factors. Whether the Then or Else clause executes is dependent on what the If is checking. An If section is optional so a Program with Run At Startup with a null If will always run the Then clause at ISY startup.

I understood your previous post. The User Guide indicates the Air Gap switch should remove power from the SwitchLinc and the load. Since it does not on multiple devices I was guessing that might be the reason for the device being discontinued.

Turns out I had archived a copy of the 2476ST User Guide. From the User Guide ... "Pulling the Set button at the bottom of the paddle out as far as it will go (about 1/8 inch) opens mechanical contacts that remove all power from SwitchLinc and its load." Perhaps that is why the product was discontinued.

Don't know. Went to the SH web site to pull down data on the 2476ST. Search no longer finds that type. The very first post on page 1 of this topic has the link to the sales page. That page now says the device has been discontinued. Poor sales or maybe issues with the device. They rarely every indicate a why.

For the benefit of others who may be following this topic, Smarthome has discontinued the 2476ST device.

propman07 The devices can be physically installed before or after the ISY is installed. Note the Insteon address of each device as it is physically installed. Use the ISY to do ALL linking. Do not do any Set button links unless the ISY User Guide or UDI Wiki instructs to do so. This would be done only for special devices. The vast majority of Insteon devices should not have Set button links created. I suggest using New INSTEON Device, entering the Insteon address and a meaningful name. Leave the Device Type set to Auto Discover. This will add the device to the ISY will a meaningful name and the ISY will determine the device type by querying the device. Lee

magvallo Having just done what you are about to do it will work. I would leave the SmartLinc plugged in until all the devices have been added. The SmartLinc will have all the device address where you might miss some if the SmartLinc is not accessed. Plus many of the devices will have the SmartLinc address which will cause device errors when the SmartLinc address is not available. After all devices have been added rename the devices to meaningful names before beginning the Scene definitions. Also delete the SmartLinc device. Scenes where a device will only be a Responder defining it as such is correct. If it is a Scene where mult-way between devices exist and the ISY will control the same Scene defining the devices as Controller is the correct method. That way the devices stay in sync when manually operated with paddle/toggle and allows the ISY to also be a Controller. The ISY assumes a Controller is also a Responder. The ISY will define the KeypadLinc based on its internal device type. A 6 button KeypadLinc and 8 button KeypadLinc have different device types. The only issue will be if you have changed a 6 button to 8 button or vise versa. The base device type will be its original type so a 6 button converted to an 8 button will appear in the ISY as a 6 button KeypadLinc. For these situations the KeypadLinc has to added with New INSTEON Device and the Device Type pulldown used to specify either 6 button or 8 button to match the new converted to configuration. I used option 3 “keep existing links†when I did mine a few weeks ago. I was very comfortable that my device link databases did not have broken links. Using option 2 will insure the devices will start off clean which is a good way to start. Lee EDIT: a KeypadLinc will have a total of 5 (not a finger check) or 8 nodes depending on whether a 6 or 8 button KeypadLinc. Each node represents a button and can be used in different Scenes or the same Scene as the situation requires. This is totally up to you regarding how dependent or independent each button should operate.

Vince The lockset does not communicate to the MorningLinc when the lockset is Locked/Unlocked with the lockset Keypad, key fob or manual knob. This means there is no reliable way of knowing the status of the lockset and MorningLinc at any given time. Thus the Program issues a Lock at 8:00 PM with no other condition. The lockset simply double beeps if it is already Locked or Locks when Unlocked. If Time is 8:00:00PM Then Set 'MormingLinc-On' Lock Door Else - No Actions - (To add one, press 'Action') Lee

Run Help | About and see what is shown for the Firmware Line and the UI line immediately below it, They should both show the level for the ISY Firmware and the UI Admin Console. The missing Variables tab suggests the Admin Console is before 3.1.x where Variables were introduced. Clear the Java cache and be sure the URL for access the Admin Console is the URL which invokes the Admin Console for the ISY firmware level installed.

To copy a Program right click on the Program Name and select Copy to Clipboard. A Paste will then put the Program into the forum post in progress. I agree with oberkc that the posted program, which is apparently not yours, will work. Suggest posting your Program for analysis. Look at the Current State column for the devices involved. Is the On/Off state what you expect. If not then there is a communications problem or link record problem rather the a problem with the Program itself .

A or B or C are all valid solutions. I recommend an Access Point for the other 120V leg. It can be moved around to different outlets until one on the opposite leg is found and also within the Dual Band PLM range. Access Points seem to have slightly better range than other Dual Band devices. EDIT: the down side to depending on the Dual Band PLM for half of the coupling is the PLM is not always in a good central location. I use a pair of Access Points located in good central locations for both coupling and as interfaces for the many RF only devices (motion sensors, triggerlincs, remotelinc, remotelinc2. tstat adaptor, and I'm sure more to come).

If the I/O Linc Sensor does not show the correct status there is a communications issue, a link record problem or the Sensor is running with Trigger Reverse and the device is being queried. The I/O Linc Sensor reports all changes in state which should be reflected in the ISY Admin Console.

Very few home installations work without coupling 120V legs. When a 240V appliance is running, such as an electric clothes dryer, hot water heater, and so on, will provide temporary intermittent coupling. If/when your system shows instability install a pair of Access Points. Comparing the Insteon traffic generated by a SmartLinc to what the ISY generates is night and day. This is due in large part to the great Scene management the ISY has which the SmartLinc does not. Dozens or even hundreds of commands can be issued by the ISY for Scene management which must work. The SmartLinc never issued that level of traffic because it does not support the function. Smarthome gave you some bad advice about not needing coupling. Of course, if it works great, but most homes DO NOT work without positive coupling.

Neither of those devices should be in the My Lighting tree. The wired coupler is passive and Access Points have no configuration or link records.

As a test plug the PLM into an extension cord and plug the extension cord into an outlet in another room. The PC equipment, UPS if any should be on a FilterLinc. How are you going to "link them and include their links as well" if the ISY cannot communication with them. Likely a good question that I just don't understand.

All of what oberkc said. You are in for nothing but trouble creating links outside of the ISY. The ISY is not aware of those links and will eventually overlay or erase them. The powerline path between the switch and KeypadLinc is very different from the powerline path from the ISY PLM to the switch and KeypadLinc. Like comparing Apples to Oranges. Is there other equipment plugged into the same outlet as the PLM such as PC and/or UPS that are not on a FilterLinc. Is the PLM plugged into a surge suppression power strip or perhaps on a UPS outlet. Is there a pair of Access Points that have been verified through the 4 tap Set button method to be on opposite 120V legs. Can the change in configuration be expanded a little. Not sure what is meant by going from a 2412 to an ISY. The ISY uses a 2412 or 2413 rather than replacing a 2412.

A single ISY Scene with the switch and KeypadLinc buttons as Controllers. The ISY assumes a Controller is also a Responder. All switch and button cross linking will be done such that all the devices can control the load and all status LEDs will stay in sync.

Glad to hear it is working. When using Auto Discover the device has to be querried for the Device Type. The device firmware level along with the Device Type comes back in the response.

That is correct. With very few exceptions associated with devices with special needs, no links should be established outside of the ISY. Both switches should be Controllers of the same ISY Scene. The ISY assumes a Controller is also a Responder and establishes the cross links necessary to allow both devices to control the load and keep both in sync with their respective status LEDs.