LeeG

Put the TriggerLinc into link mode by holding the TriggerLinc Set button until Green LED is blinking. Then proceed with the New INSTEON Device process. Actually all the fields in New INSTEON Device can be filled in, put the TriggerLinc into linking mode, then click Ok

Select the KeypadLinc button below the Scene name. Set the Responder device(s) On Level and Ramp Rate when the KeypadLinc button is selected as the Controller.

garybixler What OS, what browser

Brian I see the same thing, .. because the default column width is not wide enough to display Thur 2011/12/29 xx.xx.xx PM. When I widen the column the PM displays.

garybixler What size is the downloaded file? I think this was noted by someone else on an earlier image and it was a router/AV blocking the ISY access to the downloaded image. Or maybe now that I think about it one of the browsers was automatically unzipping the file which the ISY is not expecting. Is there still one large ZIP file?

The Set button link between the TriggerLinc and the SwitchLinc makes it impossible to restore the SwitchLinc without destroying the Set button link as the ISY is not aware of it. However, I think we can take advantage of it to determine the TriggerLinc Insteon address. Right click on SwitchLinc node, select Diagnostics | Show Device Links Table. This will read the SwitchLinc link database and display the results. Look for an Insteon address that does not match any of the devices known to the ISY. That should be the TriggerLinc.

The TriggerLinc address label is located inside on the printed circuit board. Remove the top cover as if going to replace the battery. How are you using the TriggerLinc if it was not added to the ISY? If device status changes are not being displayed, assuming the Current State column is not blank for all devices, it sounds like the PLM has lost its link records. Try doing a Restore Device for one of the SwitchLincs and see if that SwitchLinc does then show status changes.

The RemoteLinc could not have been added to the ISY without putting it into linking mode. For the RemoteLinc the Bright/Dim buttons are held on until the RemoteLinc LED blinks. Otherwise the RemoteLinc is asleep and cannot receive commands from the ISY. Same with the RemoteLinc2, it is asleep until put into linking mode. Press the Set button on the bottom of the RemoteLinc2 until the LED at the top of the device blinks Green. The RemoteLinc2 must be added to the ISY within 4 minutes. Otherwise the RemoteLinc2 will go back to sleep.

The “not switched Off†or “ not switched On†part of the If statements are not needed. They drive the Else clause. Since there is nothing in the Else clause they are unnecessary. The parens in the Fast Off Programs are not needed. With all the statements anded together the parens serve no purpose. If Control 'Kitchen / Under Cabinets' is switched Fast On Then Set 'Kitchen / Coffee' On Else - No Actions - (To add one, press 'Action') If Control 'Kitchen / Under Cabinets' is switched Fast On And Status 'Kitchen / Under Cabinets' is Off Then Set 'Kitchen / Coffee' On Set 'Kitchen / Under Cabinets' Off Else - No Actions - (To add one, press 'Action') The “Set 'Kitchen / Coffee' On†in the following sequence is not needed. The coffee maker is turned On in the first Fast On Program. Set 'Kitchen / Coffee' On Set 'Kitchen / Under Cabinets' Off I assume the Under Cabinets ToggleLinc load is controlling the actual lighting. These may flash On or Off as the Fast On and Fast Off will immediately affect the load which will then be overridden by the Programs. If you are getting reliable Fast On/Fast Off with the ToggleLinc that is fine. Some folks have reported problems being able move the Toggle fast enough to consistently generate Fast On/Fast Off commands.

The OutletLinc with v.00 was added selecting the OutletLinc Device Type in the pulldown. The other OutletLinc was added using Auto Discover. The device firmware is not read when the actual Device Type is selected.

It should not be necessary to Query the TriggerLinc to get the current Status. In addition with the TriggerLinc being an RF device and a Controller Only device there is no Status to Query so having to Query does not make any sense anyway. Also I don't see the TriggerLInc being used in any of the Programs. The last Program, Basement Switch 2 On, is actually turning on Basement Switch 1. Do all the other switches show state changes in the Admin Console as they are turned On/Off? What ISY firmware is being used? Have to get to the point where all the device state changes are being seen in the Admin Console without Query before anything can be expected to work. Once that is done all the logic can be done in a single Program If Status 'TriggerLinc 1-Opened' is On And Control 'Basement / Basement Top' is switched On Then Set 'Basement / Basement Switch 1’ On Set 'Basement / Basement Switch 2’ On Else - No Actions - (To add one, press 'Action')

The individual On/Off nodes perform the same function when Insteon Direct commands are issued to either node. When the On node is a Responder in a Scene a Scene On will Lock the mechanism. When the Off node is a Responder in a Scene a Scene Off will Unlock the mechanism. Once a Factory Reset is done the MorningLinc will have to be Deleted and added using Start Linking with the 3rd link record option to reestablish ISY access to the MorningLinc device.

That message is displayed when the ISY PLM cannot communicate with the device. It could be out of range of a Dual Band device or it was not put into linking mode before doing the New INSTEON Device. Also double check the address label. Sometimes Bs look like 8s, etc.

v99

As an FYI to anyone else who encounters a similar problem with the new InLineLinc, the new device firmware has a new requirement for what is written in the Scene link records. It is necessary to have the Scene link records written by 3.1.15 or later.

The Query is not doing anything to an RF device. Put the RemoteLinc2 into linking mode, left click on the node and select Write Updates to Device.

Refer to the 3.1.13 announcement post. It lists all the URLs for 3.1.13. There is a later Beta, 3.1.15 I suggest upgrading to.

The wrong level of Admin Console is being invoked. The Firmware and UI must be the same. Either the Java cache was not cleared or the wrong URL is being used to invoke the 3.1.13 Admin Console. Don't know if that is causing the symptom but ISY Firmware and Admin Console level (UI) must be the same.

If that is a new InLineLinc delete the Scene and recreate it under 3.1.15.

neupane00 Blinking twice and going out indicates the KeypadLinc button H is in Non-Toggle Off Mode. In this mode it only sends Off commands. If it blinks more than twice (3-4 times) on older KeypadLincs it indicates a comm problem or link problem. Smartlabs did away with the multiple blink reaction to comm. problems several firmware releases ago. Under the Admin Console, in the My Lighting tree, left click the Button H node and select Buttons Toggle Mode button. Left click on Button H and click Toggle On/Off button at bottom of popup. This will put the KeypadLinc button H back into Toggle On/Off Mode (the default). Lee

pc8888 RF devices are somewhat unique in that they send 4 messages when motion is sensed rather than the 2 normally associated with a Scene On (Motion On). Based on the Not Working trace it looks like the motion sensor was still sending part of the motion on sequence when the Scene On from the Program was issued. Try adding a 1-2 second Wait before issuing the Set Scene On in the Program. Lee

This was posted regarding the MorningLinc Lock/Unlock versus On/Off but the solution would seem to apply to the I/O Linc Sensor status as well. .............................................................. We've recently added a feature where you can rename any ON/OFF status to what ever you want. Go to My Devices or My Scenes and find your device or scene and tap on it. Scroll down to Advanced Options and find the "Custom State Names" section. Here you can rename ON/OFF to Locked or Unlocked. You also can rename the Commands here as well. So instead of ON or OFF for the command you can rename these to Lock Door and Unlock Door.

Did you clear the Java cache after upgrading? After successfully adding the 2450 I/O Linc and being able to control the I/O Linc Relay manually what else was done before the "linking" started? Is there an Icon (perhaps green) to the left of the I/O Linc nodes in the My Lighting tree? If so try a right click on the I/O Linc node and select Disable.

Smartlabs never explains what they do but the assumption is the added hardware capability in the 2413 Dual Band PLM to send/receive RF added additional load on the power supply such that it could no longer provide power to an outside device.

Minor point but the Then does execute the Wait. It is the Wait (or Repeat) that allows for the reevaluation because Status has changed. If there was no Wait (or Repeat) the Then clause would run to the end regardless of the change in Status. The suggestion oberkc made regarding changing the If Status to If Control would have allowed the original Program to work. There is no change in state when using If Control 'xxxx' On when the I/O Linc issues the Off command.