LeeG

C Martin Sorry, I should have been more explicit. Restoring the PLM following a PLM reset was necessary to restore device status change awareness and Scene control. Neither the PLM reset nor the PLM Restore would have an effect on the original symptoms. Lee

C Martin Resetting the PLM erased all the link records in the PLM. A File | Restore Modem (PLM) is now required to restore the PLM. Lee

birdman This program will accomplish what you are looking for. The ICON ON OFF would be the closet light switch and replace the Send X10 On with your email Notify. If Status 'ICON ON OFF' is On And Status 'ICON ON OFF' is not Off Then Wait 10 minutes Send X10 'A1/On (3)' Else - No Actions - (To add one, press 'Action') When the closet light is turned On the Program Then is invoked starting a 10 minute wait. If the closet switch is turned Off before the 10 minute Wait completes the Program Then clause is terminated and the Else clause is run. Lee

MarkJames I don't have a specific number the Controller waits before sending the next retry. I think it will be measured in hundreds of milliseconds and it does vary depending on the max hop count being used at the time. The larger the max hop count the slower (relative) thru put as the responder has to wait the maximum possible time it could take a message to arrive so the next available time slot to send an ACK can be calculated. This means the smaller the max hop count the sooner the Controller can reissue if the command is not ACKed. A button/paddle press command starts out with a max hop count of 1 for performance reasons. If that is not ACKed the next retry increments the max hop count, and so on. It gets complex when getting into next available time slots and hop counts. There is an insteondetails.pdf document on the Smartlabs web site that goes into great detail on this subject if you want to understand the details of what is going on. Far too much information to put in a post. Was not sure if you meant the delay was still there with the I/O Linc unplugged or some amount of delay came back when the I/O Linc was plugged in again. Lee

foxglove The ISY Programs are created through the Admin Console. Select the Program tab to enter the area where Programs are created and updated. The process of creating Programs is a matter of selecting options from pulldowns. No need to understand grammar or syntax. As mentioned earlier an X10 device cannot be added to the My Lighting tree without the optional A10/X10 Module which IS NOT NEEDED to create ISY Programs which are triggered by X10 events and issue X10 commands. Select the Send X10 Action to send X10 commands. For X10 events to trigger a Program select X10 in the Condition. Again, everything is done by selecting choices from a pulldown so no need to learn grammar or syntax. The samples I posted are real life Programs in my ISY which I copied and posted. Lee

dennisric Was the URL to access the Admin Console changed to point to the 3.1.6 Admin Console code that is in sync with the ISY 3.1.6 firmware? Lee

The KPLs are likely on different electrical circuits than the PLM. Some folks have had success with LEDs. Others have had problems. I don't have any direct experience with LEDs but they are likely to be like CFLs. Some work fine, others destroy the ability to communicate over the powerline. If it is the transformer/LEDs disconnecting the InLineLinc load wire and watching the InLineLinc status LED should show any delay in reacting to a KPL button press. There is also a difference in the Insteon commands involved between a KPL button press and a Direct command from the Admin Console. A button/paddle press starts out with a Group Broadcast which normally causes all responders to react simultaneously. That command cannot be ACKed so the Controller follows that up with a Group Cleanup Direct command to each responder. This command is ACKed. If the Group Broadcast was not received by the InLineLInc it would be the second command issued by the KPL before it was known there is a communications problem.

MarkJames With two responder devices, even of different types, having the same result I would think the problem is powerline communication related. The Controller (KPL in this case) will retry up to three times if the responder's ACK is not received. Sounds like it is taking multiple On commands for either of the responders to react. Try disconnecting the LEDs and see it the InLineLinc responds immediately. The status LED will indicate when the InLineLinc turns On. Could be load specific or something about that specific electrical circuit. Lee

foxglove The EZX10RF is an Insteon device from Simplehomenet that receives X10 RF signals and converts them to Insteon powerline commands. Since the Smartlinc has no X10 RF capability you may have no need for the EZX10RF as the current configuration must already have a means for taking X10 RF signals and placing them as X10 messages on the powerline. The ISY can trigger ISY Programs with X10 messages and send X10 messages as Program Actions. A simple X10 triggered Program could look like the following .... If X10 'D3/On (3)' is Received And X10 'D3/Off (11)' is not Received And X10 'D3/All Units Off (13)' is not Received Then Wait 2 seconds Set 'LampLinc-5' On Else Set 'LampLinc-5' Fast Off A time based X10 Program might look like this ... If Time is 3:00:00PM Then Send X10 'A1/On (3)' Else - No Actions - (To add one, press 'Action') What do you want to implement? Lee

tome In Insteon each Controller has a unique set of Responder On Level and Ramp Rate values. Selecting the KPL button Controller entry under the Scene name presents the On Level in effect when the KPL button is pressed. Selecting the Scene name itself presents the On Level in effect when the Scene is used in a Program or the Scene is controlled through the Admin Console. From an Insteon perspective the PLM is the Controller when the Scene name is used. This allows the Responders to react differently if desired for each Controller. When KPL button B is pressed the responders might turn On to 100%. When KPL button C is pressed the responders might turn On to 50%. The On Level and Ramp Rate values are stored in link records in each responder device. Each Controller has a unique link record in each Responder. Lee

tome Look at the Responder I/O Linc Relay On Level in the Scene that has the KPL button as a Controller and the I/O Linc Relay as a Responder. The On Level determines whether the Relay turns On or Off with an On command. If I/O Line Relay On Level is now 100% set it to 0%, or if it is now 0% set the On Level to 100%. I don't remember which is which, just swap what you have to reverse the On command action. Whether the Relay stays energized until the Off command or opens after the timeout depends on whether the I/O Relay is in latching mode or one of the momentary modes. Lee

satwar Thanks. The loop was likely not an actual loop. When a device is added keeping existing links the process often involves the access of many devices. The TriggerLinc was pointing to the "light switch" which means the “light switch†link database was read. If "light switch" had links to other devices those devices would have their link database read. This often spreads out to large portions of installed devices. The general recommendation is not to keep existing links. There are some exceptions such as the MorningLinc lock interface which must use the keep option. The two TriggerLinc nodes, Opened and Closed, equate to Scene 1 and Scene 2 respectively, described in the TriggerLinc user guide. Closed (Scene 2) is used only when the TriggerLinc Jumper is removed. Lee

satwar The TriggerLinc is added with two nodes, Opened and Closed. Define an ISY Scene with the Opened node as the Controller and the "light switch" as Responder. Be sure to put the TriggerLinc into linking mode so the link record updates can be written into the TriggerLinc. Lee

I am familiar with the 2-wire diagram. If turning the 2474D On, which acting as a Controller to the In-Line Linc should be turning the In-line Linc load On, prevents communication with the In-Line Linc, there is a problem there. Would expect to see the same problem if the In-Line Linc is turned On through the Admin Console. This configuration required retasking the existing wiring. Has the wiring been verified with a voltage meter?

tome This has nothing to do with the ISY and/or how it is powered. Something on the electrical circuit containing the I/O Linc has changed. Where appliances are plugged in, something new such as a cell phone charger, flat screen TV, laptop charger, CFLs that have degraded. One approach to verify the I/O Linc itself is not an issue would be to connect it to an Appliance cord and plug the appliance cord into the PLM circuit. Unless the I/O linc is defective it should now work. The next step is to identify everything on the original circuit containing the I/O Linc. Turn the breaker Off and note everything that no longer works. Unplug everything that can be unplugged (turning a device Off does not eliminate the device as a problem) and turn Off everything else. Reconnect the I/O Linc and see if it can now be added. If so then plug things back in one at a time until the I/O Linc is no longer reliable. If the I/O Linc is not reliable with everything else Off that electrical circuit may need a Dual Band device to improved the Insteon mesh network. Lee

Tome Powerline communication with the I/O Linc is unreliable. The command issued at 07:11:48 did not get a response from the device. The command was issued again at 07:11:57 and did get a response. Wed 08/17/2011 07:11:48 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:11:57 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:11:59 PM : [iNST-SRX ] 02 50 0F.52.86 19.71.B8 27 28 0F SET-MSB(0F) Later two commands failed back to back at which point the process was terminated. The command issued at 07:11:59 and 07:12:08 did not get a device response. Wed 08/17/2011 07:11:59 PM : [iNST-ACK ] 02 62 0F.52.86 0F 2B E1 06 PEEK (E1) Wed 08/17/2011 07:12:08 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:12:12 PM : [F 52 86 1 ] Link 3 : 0FE0 [E2031971B8000003] *Failed Writing [E2031971B8000003] Lee

C Martin "can you please explain what you mean by wired correctly?" When a symptom is described as it works unless I turn On x, at which point it never works, how the device(s) is wired is a consideration. The other consideration is what type of load is receiving power when x is turned On. There are a number of noise generating/signal absorbing devices that can interfere with Insteon when powered On. What type load is the In-Line Linc controlling? Perhaps if the companion switch can be explained. What is it, how is it wired relative to the In-Line Linc, when On what is its relationship to the In-Line Linc. I am not disputing that this started at 3.1.5. The last OP that described the symptom in the context of starting when image x.x.x was installed turned out to be a noise/surge suppressing power strip. It is normal to relate to installing an image but most times symptoms involved with intermittent communication with a device, particularly when no communication is possible when x is turned On, has anything to do with a particular firmware level. Lee

tome The cable from the 2412 is fine with the 2413. The ISY sequence to install new PLM is correct. The verification that all went well is to see device state changes appear in the Admin Console display as devices are manually operated by pressing button/paddle. Lee

ericdhvac With the motion sensor linked to the hall light you want to follow Tim's suggestion to use Adjust Scene function to change the hall light responder On Level. There is no way to suspend a Scene where the motion sensor is linked to the hall light. The approach is to change the Scene responder On Level based on time of day as Tim's example does. If you would delete the Scene such that the motion sensor no longer directly controls the hall light then my initial post example will work. Lee

Same situation. Is this a new EZFlora or one that has been updated with the latest firmware and late internal PLM. The EZFlora firmware must be at v.28 with PLM firmware at v.92 for the device add to function on and after 2.8.x.

Assuming the In-line Linc turns On/Off correctly otherwise (correctly wired) the type of load the device is controlling can be a problem. What type of load (CFL, LED, simple incandescant, etc) is the In-Line Linc controlling?

According to the Event log the EZFlora is not responding to any commands. The attempt to read the first link record fails to get any response from the device. Note the 9 seconds between command attempts. This indicates no response from device. Plug the EZFlora into the same circuit as the PLM and try the add again. It is not necessary to have any Zones connected for the add to function. Suggest doing a factory reset of the EZFlora before doing the next add. Tue 08/16/2011 07:29:41 PM : [iNST-ACK ] 02 62 19.AD.A7 1F 2F 00 00 00 3F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Tue 08/16/2011 07:29:50 PM : [] EZxx start address at 3FFF Tue 08/16/2011 07:29:50 PM : [iNST-ACK ] 02 62 19.AD.A7 1F 2F 00 00 00 3F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Tue 08/16/2011 07:29:59 PM : [] EZxx start address at 3FFF Tue 08/16/2011 07:29:59 PM : [iNST-ACK ] 02 62 19.AD.A7 1F 2F 00 00 00 3F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Tue 08/16/2011 07:30:03 PM : [ 19 AD A7 1] ** Not added ** Remove Device Links failed

The only way I know of is to delete and readd the EZFlora device.

This Program will turn On LampLinc to 80% when motion is sensed and it is between 6:01 AM and 12:59 PM. If From 6:01:00AM To 12:59:00PM (same day) And Control 'MotionSensor3-Sensor' is switched On Then Set 'LampLinc 6' 80% Else - No Actions - (To add one, press 'Action') There is nothing in this process to turn the LampLinc Off.

Device 07.F3.1A had its responder link record for Scene 14 Ramp Rate set to 1F which is the fastest ramp rate. The ISY changes only those devices where a Ramp Rate applies (KPL Secondary buttons do not Ramp so they are not updated) and where it believes the existing Ramp Rate is different than the new value.