LeeG

The Motion Sensor will report an ambient light change only after 3.5 minutes have elapsed. This is designed to compensate for passing car lights, etc. This time interval cannot be changed. The only value that can be changed is the light level that generally differentiates Dusk/Dawn.

What did the Compare show for each link record, Identical, mismatch, extra, etc. The count is probably okay. The Show Device Links Table includes the End Of List record which the ISY Links information does not include. Is the switch a SwitchLinc or KeypadLinc? Lets reset. With this switch the load control button/paddle can be pressed On/Off but no state change occurs at the Admin Console. Is the Current State column blank for all devices or do some switches show current state? If some of the switches show a current state do these switches change state as the load control button/paddle is pressed On/Off?

I cannot attempt to recreate on anything that old. Run Show Device Links Table for the LampLinc. There should be these link records A2 07 aa.bb.cc FF 1F 00 where aa.bb.cc is one KeypadLinc Insteon address A2 07 dd.ee.ff FF 1F 00 where dd.ee.ff is the other KeypadLinc Insteon address In the KeypadLinc that does not turn the LampLinc On there should be E2 07 gg.hh.ii xx xx xx where gg.hh.ii is the Insteon address of the LampLinc

What ISY firmware is being used?

You have defined the Scene correctly. Have the Dual Band LampLincs been confirmed to hear the RF and be on opposite 120V legs?

What is being used to couple the 120V legs?

That is the correct Scene definition. Both KeypadLinc button Gs as Controller and the LampLinc either as a Responder or maybe a Controller. The LampLinc can be turned On/Off manually at the LampLinc and it has load sensing which will turn the LampLinc On when the load is manually turned On. The LampLinc has Controller capability to notify the KeypadLinc buttons if the LampLinc is turned On manually. For that to work the LampLinc should be added as another Controller to the same ISY Scene. How the LampLinc is added will not affect the ability of either KeypadLinc button G to turn on the LampLinc. Were there any errors when the KeypadLincs were added to the ISY Scene? Are there any red ! or green Icons to the left of the KeypadLinc or LampLinc nodes?

Without any Scenes defined each 8 button KeypadLinc has 8 Responder links in the PLM, each 6 button KeypadLinc has 5 responder links in the PLM, so the ISY will be aware of a button press. From memory each KeypadLinc also has a Controller link in the PLM to support the My Lighting Query. Each SwitchLinc has two links in the PLM, one Controller link and one Responder link. The link count associated with an ISY Scene depends in the number of devices in the Scene. There will be a Controller link for every Responder and Controller/Responder in the Scene. That is the minimum. There may be others that do not come to mind immediately.

You cannot buy a bigger PLM. The 2412S supports more link records but is no longer sold. Reduce the number of Scenes. That will show what communication if any is coming from each device.

This is a message from a device to the PLM, part of the Insteon Group protocol. They start with Max Hop=1 for performance reasons. Each subsequent retry increases the Max Hops count. Coming from a device with Max Hops 1 and Hops Left=0 is good communication from the device to the ISY PLM. Tue 02/14/2012 06:13:18 PM : [iNST-SRX ] 02 50 19.21.DA 19.70.06 41 11 01 LTONRR (01) Tue 02/14/2012 06:13:18 PM : [standard-Cleanup][19.21.DA-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

Turn Off the 3 AM Query. I would not Restore Device at this point. It may be necessary with the comm errors that have occurred but let’s see what we have after the PLM restore. The Show Device Links Table function has a Compare button that compares what a device has in terms of link records versus what the ISY thinks should be in the device. If a device does not show state changes after the PLM restore and the number of link records in the PLM is not a concern then a Show Device Links Table/Compare for the device not showing state change is the next step Do not have Insteon traffic while the PLM restore is running.

No. The command from the ISY to the Switch will be retried three times before it fails. This is done by the PLM automatically without ISY intervention. These are Insteon Direct commands. Scene management uses Insteon Direct commands to read and write Insteon link records at the device. With link records being 8 bytes long and it taking at least 17 commands to write one link record you can see that message flow associated with updating/creating a Scene is exponentially higher than a simple device On/Off command. Pressing a paddle/button sends an Insteon Group message sequence which is more complex than simple Insteon Direct messages. Too much to go into here. The Group messages are retried. If Scenes can be reliably read/written to the device but button/paddle presses are not seen at the ISY there is a link record issue. Unlike Insteon Direct command which do not use link records at all, Insteon Group messages require valid link records in both the device and the ISY PLM for the ISY to see the button/paddle press.

The PLM Restore could take hours. If there are other Scene consolidations planned you might do them before the restore. Being able to control a device individually does not mean that Scenes can be managed or executed successfully. Individual device control is a single command that is retried multiple times. Scene management can take dozens to hundreds of commands that must all work (with retries). Often a single command will work but the network is not reliable enough to support dozens of (or more) commands back to back. You can get some sense of how the network is working by looking at the Event Viewer with Level 3-Device communications events selected. Look for Insteon messages that show Max Hops and Hops Left. When the Hops Left count tracks down to 1 or 0 when Max Hops start at 3 the network is working at the extreme end of reliability. What you want to see is Max Hops=3 and Hops Left=2. See Red values below. Tue 02/14/2012 05:38:12 PM : [iNST-ACK ] 02 62 15.52.C8 0F 11 FF 06 LTONRR (FF) Tue 02/14/2012 05:38:12 PM : [iNST-SRX ] 02 50 15.52.C8 19.70.06 2B 11 FF LTONRR (FF) Tue 02/14/2012 05:38:12 PM : [standard-Direct Ack][15.52.C8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 02/14/2012 05:38:12 PM : [ 15 52 C8 1] ST 255 Tue 02/14/2012 05:38:18 PM : [iNST-ACK ] 02 62 15.52.C8 0F 13 00 06 LTOFFRR(00) Tue 02/14/2012 05:38:18 PM : [iNST-SRX ] 02 50 15.52.C8 19.70.06 2B 13 00 LTOFFRR(00) Tue 02/14/2012 05:38:18 PM : [standard-Direct Ack][15.52.C8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 02/14/2012 05:38:18 PM : [ 15 52 C8 1] ST 0

"928 IS THE COUNT (CHECKED TWICE)" Although the PLM spec says 1023 tests here indicate 992 as the maximum. All attempts to add link records past the 992 point failed. I suspect you did exceed the PLM link count as some point. I would do a Restore Modem (PLM) followed by a few more Show/Counts to see where the count is now. "WE HAVE DUAL BAND ALSO" Do the Dual Band devices pass the test for receiving RF and installed on opposite 120V legs?

Is there any pattern to the devices that are not reporting state changes? Are they powered from the same 120V leg or powered from the same circuit breaker? What type of PLM is being used with the ISY (2412 or 2413)? How many devices and ISY Scene have been defined? It is possible to define more devices and Scenes than the 2413S PLM has the capacity to support. Run Tools | Diagnostics | Show PLM Links Table. When the display is complete click the Count button. Run the Show/Count multiple times to see if the number of link records is consistent. Insteon traffic reaching the PLM while the PLM link records are being retrieved will produce false link record counts (high or low).

Thanks for the additional information. "ANSWER: (2486D) KeypadLinc Dimmer 6 buttons v.00" The v.00 indicates the KeypadLinc was added to the ISY this time by selecting the 6 button KPL from the New INSTEON Device “Device Type†pulldown. That gives you the words Dimmer 6 (which mean nothing as far as ISY function is concerned) but now the KeypadLinc firmware is not known (v.00) so some of the features that require later firmware levels may not be utilized. “ANSWER: Insteon bridge coupler designed for Insteon†That is a passive coupler. It may still be necessary to have a pair of Dual Band devices installed on opposite 120V legs. “ANSWER: it has its own dedicated circuit with no surge protector.†Are there other equipment on that circuit breaker such as UPS/PC/Audio/Video equipment that are not on a FilterLinc?

1) What specifically (device type) was added to bridge the 120V legs. Most devices at the power panel are passive couplers which do not boost the signal to the other leg. A passive coupler that was designed for X10 may not be effective for Insteon. 2) The action described versus the results achieved do not corrolate. Exactly what does line 2 of the Admin Console right pane show for the 8 button KeypadLinc converted to 6 button mode. I don’t care about the Insteon address, but all information after that. “An 8 button slave main button controls the scene mechanically perfectly. “ Do not under the circumstances being described. The term mechanically is an usual term applied to an ISY Scene. There is an ISY Scene with some devices as Controllers and Responders. An 8 button KeypadLinc Main button (upper left corner) was added to the ISY Scene as a Controller. There were comm errors displayed during the addition of the 8 button Main button to the ISY Scene? 3) It is certainly possible for a device to talk to another device but not able to communicate with the ISY PLM. Often the PLM is plugged into a circuit where there are other devices that interfere with Insteon message traffic. UPS/PC equipment not on a FilterLinc. The PLM could be in a surge suppression outlet that will interfere with Insteon traffic. Have all links been created using the ISY or have some links been established with device Set buttons? Comm problems often have more than one source. There are no good tools for Insteon so it is a process of elimination. Putting UPS/PC equipment on a FilterLinc. No surge suppressor on the PLM circuit. The two are simple and should be done regardless of whether the fix a specific symptom. The overall performance will be better with these. Are the 8 to 6 button KeypadLinc button state changes now appearing in the Admin Console for all the buttons? If so it would indicate a problem when the KeypadLinc was initially added getting all the link records created. With as many symptoms that are occurring it does sound like there are still comm problems. 3.1.17 was extensively tested before being identified as an official release and it is being used by many installations not seeing the issues you are seeing. It is normal to think about the last major ISY change. I had a user tell me his system was working 100% before an upgrade (not to 3.1.17). The root cause of the problem was the PLM was plugged into a surge suppressor. The system could not have been 100% before the upgrade. Just the way the mind works.

The face plate makes no difference. Some users put the 6 button configuration on an 8 button KeypadLinc still configured as an 8 button KeypadLinc. Click on My Lighting which shows all the nodes and displays their status. Scroll to the KeypadLinc in question. Cycle the ON/OFF buttons and each of the Secondary buttons. Which buttons show a state change in the Current State column, which buttons do not? EDIT: the Admin Console is displaying the Device Type the device presented when the device was added to the ISY. The KeypadLinc identifies the Device Type as it was manufactured, not how it is configured. It was manufactured as an 8 button dimmer thus that is the Device Type it indicates. Should the device be factory reset (explicitly or by accident because of a power glitch) it will revert back to 8 button mode. When a KeypadLinc button is pressed the inbound Insteon message carries a Group number that identifies which button was pressed. The Secondary A button in 6 button mode, which is the Secondary C button in 8 button mode uses the same Group number. Regardless of how a button is labeled, regardless of the KeypadLinc button mode (6 or the physical button presents the same Group number. The difference between 6 and 8 button mode is the number of nodes (Groups) the device can present, not what Group number the buttons use.

If the ISY defined 5 nodes it knows it is in 6 button mode. What are you trying to solve.

Unless you specified the Device Type when the KeypadLinc was added back after changing to 6 button mode it will be added as an 8 button KeypadLinc. The ISY uses the Cat/Subcat value (device type) when using Auto Discover. This value will indicate how the KeypadLinc was manufactured, not what mode it is currently in. Take a look at line 2 in the right pane of the Admin Console. What does it show for the device type and what is the device firmware level.

use the Admin Console to set the values to 0/0 to match what you are trying to do with the Program. When I set a KeypadLinc Relay at v.36 the background LEDs are as low as they can go. The ON level cannot be turned Off as there would be no indication which Scenes (buttons) are On. If the Admin Console 0/0 sets the background ON level to an acceptable level then the Program will have to be looked at. Perhaps a Save Changes was missed, the Program is not Enabled, etc. The Programs | Summary tab will show the last time the Program was triggered and what its Status is/was (True/False).

What happens if the LED Brightness button for the Primary node on the Admin Console is used to set the same values? What is the firmware level of the KeypadLinc?

A full X10 command is made up of two messages. The first message contains the house/unit, the second message contains the house/command. They go on the powerline as independent messages so something could interfere with one message or the other. The X10 maxi controller can send only the house/unit or only the house/command as some devices require only one or the other to program them. I don't use X10 motion sensors so have no direct experience but doubt they would send only 1 of the 2 messages. Sending only the house/command would not insure the correct unit is responding. Sending on house/unit without a follow on command message has no effect.

I would define a new Program under 3.1.17 with the same statements. Sounds like that Program has lost the Sunday indication along the way.

"file save with xxx extension instead of zip" That will fail for sure. Must remain a Zip in a Zip. What browser is being used? One of the browsers automatically unzips during download. Since the image is a Zip in a Zip it appears to still be a Zip file but is wrong. Right click the download link and select option that does not unzip.