LeeG

There are two devices active during that trace, 31.6F.1C and 2C.71.97. What is each device? I first thought 31.6F.1C was the BuzzLinc (whatever that device actually is) but there are no Off commands sent to that Insteon address.

Any time. Changing to "If Control" will stop the termination of the Repeat when door closed before Repeat normally ends. The delays in the Insteon commands within the Repeat loop should still exist. Post the LEVEL 3 event trace when the device commands are not executed as expected. There could be outside causes (other ISY activity) or there can be Insteon comm issues that delay the commands reaching the device.

Another option is to change to "If Control" If From 10:00:00PM To Sunrise (next day) And ( Control 'Door Sensors / Deck Door Sensor' is switched On Or Control 'Door Sensors / Kitchen Door Sensor' is switched On Or Control 'Door Sensors / Man Cave Door Sensor' is switched On ) Then There is no trigger when door closes.

The logic needs to be split into two Programs so closing door does not terminate Repeat. For the speed pattern of On and Off there is likely heavy Insteon traffic or the ISY is busy doing something else. An event trace at LEVEL 3 will show the timing of the On and Off commands and other Insteon activity. What else is the ISY doing on such a frequent basis?

The 99i is down level and I do not think it will support an I2CS SwitchLinc even if at 3.3.10, the last release that will run on a 99i. The command sequence is not correct for adding an I2CS SwitchLinc. You need to upgrade to a 994i running at least 4.2.30 or better yet running 4.3.10.

What does Help | About show for Firmware level, UI level? Describe the exact steps being used to add this device to the ISY?

I don't know what the error was before pressing reset. Now the error is the 2477D no longer accepts the PLM command because reset cleared the link data base. Suggest Deleting 2477D from ISY, add it back, then attempt to turn On/Off 2477D. with the LEVEL 3 event trace active. Sat 08/08/2015 20:32:30 : [iNST-ACK ] 02 62 31.56.44 0F 11 A8 06 LTONRR (A8) Sat 08/08/2015 20:32:31 : [iNST-SRX ] 02 50 31.56.44 39.00.75 AF 11 FF LTONRR (FF) Sat 08/08/2015 20:32:31 : [Standard-Direct Nack][31.56.44-->ISY/PLM Group=0] Max Hops=3, Hops Left=3 The AF is a NAK, the FF indicates source device (PLM) not known to 2477D because device was reset. The 2477D is not spec'ed for LEDs so original problem may be type of LEDs being used.

I used Powerhome for years where you can issue just about any command but moved to the ISY about 8 years ago. The Simplehomenet Utility can set up analog ranges where the I3 and I4 Inputs will send On or off commands based on analog value but the ISY does not access the actual analog value.

The ISY does not have support for reading analogue values from I3 and I4.

A few points to consider when rewriting Program into likely two or more Programs. The Wait in the Else has no purpose. It does not Wait when the only statement in the clause or last statement (no logic after Wait). The Else clause is driven when the Program is triggered and any part of the If is False. This means that the Else clause executes under various conditions, usually more than the Program was designed to handle. This is usually why multiple Programs are needed. The multiple If clause conditions must all be True to drive the Then clause. The more complex the If the more need to put the True logic in the Then and nothing in the Else which is why multiple Programs are required.

"If Status" does not use "switched". "If Control' uses "switched". If Status is using the current state of the device "If Status 'xxxxx' is On" If Control is looking at the command currently being sent by the device "If Control 'xxxxx' is switched On"

The Show Device Links Table will have the same comm issue that the Write Updates had. The RemoteLinc has to be put into manual linking mode and the same location where the Write Updates worked. Was the RemoteLinc Factory Reset while getting the Write Updates to work? If so a Restore Device will be required to rebuild the link records erased by the Factory Reset.

mcwxlsxn The LEVEL 3 trace of the Smoke Bridge looks fine. It is normal to have to Query the two nodes to reset to Off following test. What do you see as the problem?

Is that with the 2635 powered from the PLM circuit?

Move the 2635-222 to the PLM circuit and redo the Show. Do you active coupling of the two 120v legs?

That should have worked if that was actually written to the 2635-222. Do a Show Device Links Table for the 2635-222 and post the results. Could also change the Responder On Level to 0%, after that is written to device change the On Level back to 100%. There is a load plugged into the 2635? Scene Test will show if the PLM link record is correct in the 2635-222. That will not indicate the state of the 2477S related link record in the 2635.

Do a Show Device Links Table for the RemoteLinc and post the display along with the new PLM Insteon address. Note: the All On/Off does not use the link records in the RemoteLinc.

Try a different distant location. The old RemoteLinc RF signal and the newest PLMs have problems communicating. As was mentioned before not everyone encounters the problem. The solution has been to increase the distance between the RemoteLinc and the PLM. The last RemoteLinc may need a different location than the other RemoteLinc. Deleting the RemoleLinc and readding does not solve the problem. If you have a basement try that or take the RemoteLinc outside being sure RemoteLinc is in linking mode.

Click on the Red 2477S Controller entry. What is the Responder On Level and Responder Ramp Rate for the 2635-222? The difference could be a single press is sending an On command where a double click is sending a Fast On. Could affect requested On Level and Ramp Rate as Fast On ignores link record On Level and Ramp Rate.

PLM with hardware v2.x (from white sticker) has capacitor fix.

A PLM with v9B firmware is old enough to have the capacitor problem. They over heat and cause the power supply voltage to drop losing some/all of the PLM link records. Once the link records have been lost it is common for the problem to surface again. The PLM hardware v2.x firmware v.9E has corrected capacitors.

Columns are on the right side

Unfortunately that likely means the current PLM will fail again. What does Tools | Diagnostics | PLM Info/Status show for PLM firmware? xx.yy.zz. v?? / Connected

You can Delete the one Scene that has duplicate Responders and add that Scene's Controller to another Scene. Insteon allows a node to be a Controller in one Scene only so the duplicate Responder Scene is Deleted first and then add the Controller to the other Scene. Note that Controller1 will consider Controller2 a Responder and Controller2 will consider Controller1 a Responder. It is normal to have multiple Controllers in the ISY Scene. ISY Scene xxxx Controller1 Controller2 Responder1 Responder2 Responder3

Absolutely nothing wrong. Where you have ISY it would say My Lighting if you had migrated from a 99i as I did.