LeeG

No one has reported an All On from using a device. Every device (except battery powered) has a PLM inside. That is what a device uses to communicate Insteon.

The Program should not produce the varying results. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Trace the activity when KPL button pressed and post trace. Repeat 1 brackets the above Repeat and statements after Repeat 1 execute once.

V.EF is a test only variant. I think the PLM firmware with the fix will be V.9C or later V.9x The Utility works with a 2413U. Sounds like the wrong Comm port number is being supplied to the Utility.

"Devices behave as controller only when they re acted upon directly." That is the important point. Turning On a Scene from a Program, it does not matter whether a KPL button is a Controller or Responder in that Scene. The PLM is the Controller of the Scene in that case and Insteon devices DO NOT daisy chain Controller actions. It only matters when that KPL button is pressed.

The latest PLM available from Smarthome may have a fix for this. It should arrive here in a day or two. If really running 4.1.2 upgrade to 4.2.18. This is not an ISY problem but there is good maintenance between 4.1.2 and 4.2.18

The is/is not Responding indicates if the device is responding to commands. Can be used in a Program or Admin Console to see if device is having comm problems. A device that is important such as a water tank pump control device can be checked remotely, for example.

It should not be necessary to Wait 3 seconds between Set Scene statements. It is possible for conflicts to happen between devices. Devices such as a Motion Sensor, being battery powered and RF only, can have issues with other devices. The PLM can start a command sequence at the same time the Motion Sensor is progressing with its Scene On/Off. That is why it may be necessary to Wait 1 or 2 seconds before a motion sensor triggered Program issues its first Set Scene. Device A will not physically step on device B message if aware of the message. Insteon will terminate a Scene if two Scenes are running at once. This aspect of Insteon has always been true and is covered in the latest insteondetails.pdf document on insteon.com

That combination of LEDs blinking indicates the ISY cannot reach the LAN. Make sure the modem/router has not assigned the ISY IP to some other device and all the internet cables are fully seated.

That depends on local electrical code. Some require metal boxes, some do not. My geographic area does not require or use metal boxes. The reason for asking is a metal box reduces the coverage of the RF signal for a device in a metal box. It could require the use of a pair of plug-able Range Extenders for good RF coverage. That is likely why the PLM in the basement would not reach the I/O Linc at times because of marginal RF coupling.

There is no need to add devices to 2nd and 3rd floor on phase 2. Would serve no purpose. The existing devices on 2nd and 3rd floors are Dual Band which will support coupling a future device on phase 2 on those floors if one is added in the future. Again, no need to install a device on phase 2 on 2nd and 3rd floors just to have something on phase 2. The Insteon LED Bulb would not respond if not powered so that is not a problem. Are the boxes in the walls metal? The I/O Linc should be reliable. If not that is an area to look into. It not being Dual Band could make it more exposed to powerline issues as that is the only communication path.

What devices are Dual Band? When the PLM was put into RF test mode what Dual Band devices responded and how did they respond? Was the Dual Band device response consistent giving the appearance of good RF reception? Are the wall boxes metal? Are all the issues with the I/O Linc in garage resolved with move of ISY/PLM? There is no need to have devices powered from phase 2 on 2nd and 3rd floors just to have something on phase 2 on those floors.

The 2477D requires a Neutral. It will not function without it. The 2474D is a completely different design that takes power through the incandescent load which has the Neutral connection. The 2477D cannot be installed where only two wires and no Neutral exist at the switch.

Check out this section of the Wiki http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Custom_Email_Substitution_Variables

Also note the latest KPL Dimmers DO NOT indicate the ability to generate the RF test message. This would mean they respond to another devices RF beacon but cannot generate one. That may explain why the LampLiinc does not respond to the KPL.

The I/O Linc is not Dual Band, powerline only. The latest KPLs are Dual Band. Earlier KPLs are not Dual Band. I have several KPLs installed (over ten) which are powerline only. If necessary remove the device from the box (leave connected) and look at the label on the back of the device to see if labeled Dual Band. The first thing to understand is how the Dual Band devices react to the PLM. That will show how well the PLM coverage as far as RF. I have a functional house with no RF usage for basic function, except good RF phase coupling so RF is not an absolute. It certainly does help to get to some areas. How does the PLM communication work.

The way to determine how the electrician distributed the house electrical load is to tap the PLM Set button 4 times. That puts the PLM into RF test mode. Check how the various Dual Band devices react by watching the device status LED. The device reaction varies based on the device firmware. Later devices will blink Red when the device is on the same 120v leg as the PLM and blink Green when on the opposite 120v leg. Some devices will blink bright White if on the opposite 120v leg. The User Guide for each device covers how the device reacts.

4.0.5 is the last "Official" release that came out some 18 months ago. 4.2.18 is the latest "Release Candidate" (RC) which was released about 2 weeks ago.

The 120v legs alternate vertically. On the left side, vertically, Left side leg 1 leg 2 leg 1 leg 2 leg 1 . . Right side leg 2 leg 1 leg 2 leg 1 leg 2 . . . The Program sequence could be something like this Then Repeat 10 times Set Scene 'x' On Wait 1 second Set Scene 'x' Off Wait 1 second The action should be very predictable. If it is not consistent then that is another symptom of poor comm.

Michel The I/O Linc trace is misleading as most of the Insteon traffic is for a different device. Only the first command is sent to the I/O Linc (2F 8D 28) which fails to get any response from I/O Linc. The majority of the trace is for (2B 32 DE 1) which is a different device. Not disagreeing will all your suggestion, just noting that the I/O Linc Sensor is not being commanded as those messages are for a different device address. Tue 11/11/2014 12:06:07 PM : [iNST-TX-I2CS] 02 62 2F 8D 28 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 11/11/2014 12:06:07 PM : [iNST-ACK ] 02 62 2F.8D.28 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 11/11/2014 12:06:11 PM : [2F 8D 28 0 ] Failed to add device, reason 9 Tue 11/11/2014 12:06:11 PM : [D2D EVENT ] Event [2B 32 DE 1] [DOF] [0] uom=0 prec=-1 Tue 11/11/2014 12:06:11 PM : [ 2B 32 ED 1] DOF 0 Tue 11/11/2014 12:06:11 PM : [D2D EVENT ] Event [2B 32 DE 1] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 12:06:11 PM : [ 2B 32 DE 1] ST 0

10(per day)*365=3650 per year. 3650*10 (years)=36500 That activity is so small even if the cycles were 100,000 it is not important. More likely the age of the electronics than the memory updates.

Backlight level changes all the button bright levels, not just button A. To change a button LED assign the KPL button as a Responder in a Scene and turn the Scene On/Off. There is a limit to which device memory can be updated but it is so large (a million) as to not be a concern.

The ISY does NOT use the special commands to keep a battery device from sleeping. Battery devices must be manually put into linking mode to do updates. The I/O Linc (2F 8D 28) trace indicates it is not responding to an Extended command. The command is tried three times with no response from device. Best not to use Trigger Reverse option. It does reverse the Sensor On/Off commands but it does NOT reverse the Query response. A Query, done manually, or automatically at 3 AM will change the state of the I/O Linc Sensor when Trigger Reverse is used.

The pending link record for the Hidden Door Sensor is to make the Sensor a Controller for 30.0F.AA. Once pending it will require putting the Hidden Door Sensor into linking mode to allow the update to happen. The I/O Linc (GarageLinc) is powerline only. If it takes more than one Write Updates action there is poor comm to the I/O Linc.

A link record is queued for update. The Hidden Door Sensor being battery powered is asleep. Manually put the Hidden Door Sensor into linking mode. Then right click on Sensor and select Write Updates. After update completes take the Hidden Door Sensor out of linking mode or wait 4 minutes.

Not a good idea to have device and Scene with same name. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Press KPL button so device cycles On/Off a few times and post the event trace