LeeG

The KeypadLinc User Guide describes the process of changing from 6 to 8 or 8 to 6. It requires changing the KeypadLinc button frame which is available in a KeypadLinc change kit. After the KeypadLinc has been converted to either 6 or 8 button mode it has to be added to the ISY so that the correct number of nodes is defined. The ISY will detect the number of buttons when it is added to the ISY. An existing KeypadLinc device definition cannot be dynamically changed from 6 to 8 or 8 to 6. Must go through the device add process with the KeypadLinc in the desired button configuration.

I think Auto-DR has to do with power management but I'm not sure of that. On the East coast power management is not the topic it is in the West. The QueryAll insures the ISY has the current Status of all devices. All the devices are linked to the PLM so it should be aware of state changes. However, not every powerline is good so it is possible to miss a state change.

Avast is another common blocker. The ISY can be put into a White or Trusted list (nomenclature may be wrong, I don’t use Avast). There should be several forum entries describing the Avast configuration. The QueryAll Program is as follows ... If Time is 3:00:00AM Then Set Scene 'My Lighting' Query Else - No Actions - (To add one, press 'Action') I renamed the Scene on my 994. It may be ISY Lighting or something like that on yours. Do not delete Auto DR. There is a forum entry that explains what it is for. Not a good idea to be deleting things you do not understand.

That can be AV or firewall blocking the data the ISY is pushing out to the Admin Console. What AV is being used? Kaspersky is a common blocker.

I think the point that was missed is the extreme example was all KeypadLincs plus Scenes. Realistically no one has 60 KeypadLincs installed. Each KeypadLinc can account for 8 devices/nodes where a SwitchLinc accounts for 1. In device nodes alone that is a difference between 480 nodes if all 8 button KeypadLincs versus 60 nodes if all SwitchLincs. In practical terms there will be far more SwitchLinc type devices than KeypadLinc type devices. Search/look through the forums. You will not find discussions where everyone is running out of nodes. EDIT: I have appox 50 devices installed between the house/garage/dock which account for approx 150 device nodes. Of those 13 devices are multi node devices.

My apologies. Each PLM comes with a cable with a Serial connector on one end and an RJ45 connector on the other. This cable is tucked inside the folds of the interior packing material of the PLM box.

Using a Serial port. There are some USB to Serial adaptors on the market. Some have proven to be unreliable, others seem to work pretty well. I have no direct experience as I have Serial Ports on my PCs. Since the usage would be very limited which USB to Serial adaptor may not matter.

The Folder has no False condition so once either time is reached for the specified days the Folder condition is set to True and remains True. Makes the existence of the Folder irrelevant. The Current State column will be blank from an ISY boot until the Motion Sensor signals motion. The motion sensor options can be determined by pressing the Set button on the motion sensor until the Red LED blinks indicating the device is in linking mode (and awake). Click the motion sensor Sensor node and select Set Options. The current motion sensor options will be displayed. It looks like the Folder and Program conditions are expected to limit the action of the motion sensor to evening operation. Once they are set up correctly the motion sensor probably does not need any new options.

Yes, the SHN Utility works with a Serial or USB PLM including the special 'H' HouseLinc variant. Also works with the small USB RF PLM. All the PLMs interface in exactly the same way (as though they were serial) using the same command set. Although the later versions of the SHN Utility display the cat/subcat values when it connects with the PLM the Utility has no awareness of the type of PLM as far as execution is concerned. The latest version on the SHN web site supports I2CS as far as the Checksum requirement. It can read and write a link database of an I2CS device so long as the PLM is authorized. It has no function to authorize a PLM to access an I2CS device.

Simple one first, yes I2 is wired the same as I1. I2+ to 5V and I2- is switched to Gnd. Note that Input 3 (AN1) and Input 4 (AN2) should be connected to Gnd if not used to prevent them from floating and generating unwanted message traffic. These inputs do not have a pullup resister built in because they can optionally function as analog inputs. The commands can be reversed. It requires running the Simplehomenet Utility Suite (free download from SHN web site) which requires a PLM to act as the powerline interface. The ISY PLM can be used if no spare PLM is available. The SHN Utility makes no changes to the PLM so the only impact is the ISY is down while the SHN Utility is being run. Also requires a Windows environment on a PC with a Serial connection if using the ISY PLM. Once the SHN Utility is connected to a PLM select the EZIOxx tab. Enter the EZIO2X4 Insteon address in Insteon ID field. Once connected to the EZIO2X4 select Inputs Settings and Monitor tab. The specific Input is selected from the Insteon All_Links Group Commands Setting | Input pulldown. Click Read to read the current Input settings. The Off to On (11) and On to Off (13) field values are reversed. Off to On is set to 13 and On to Off is set to 11. Click Write to save the changes.

Right click on the node (primary node if multiple node device), select Diagnostics | Query Insteon Engine.

Assuming the same commands are being issued the manufacturer will have to supply the explanation.

Check the SwitchLinc firmware for those with different responses. Run Tools | Diagnostics | Event Viewer at Level 3 and see if there is any difference in the commands being issued to set the LED status LEDs brightness level. Right click SwitchLinc node, select Diagnostics | Query Insteon Engine can correct a command issue if the ISY has incorrect information regarding device capability.

Is the question about the device status LED brightness (which is what I thought) or the load brightness?

Need some additional information. The Motion Sensor (assuming it is the Insteon Motion Sensor (2842-222 or 2420M, same device) has a Dusk/Dawn sensor in combination with a Night Only mode. The ISY can set the Dusk/Dawn light level as well as the Night Only Option. If the lighting is being turned on with an ISY Program there are Sunset/Sunrise options that can be used to gate when a Motion On message has an effect. Need more information about the specific installation. Are Direct links between the Motion Sensor and the lights being used or is an ISY Program being triggered by the motion? Also need to confirm the type of motion sensor

Compensating for West coast time difference Yes, they have found a work around. I suspect there will be more link records written before the End of List record is written. Regardless of approach wait for next Beta (3.3.3) estimated for end of week

That green Icon indicates updates are pending. Should only be necessary to right click the node and select Write Updates to Device. Sounds like either an RF device was involved in one of the Scenes or communication to the new device is not reliable.

Might be worth a try. I've not heard of a condition that cannot be cleared with a factory reset.

SmartLabs produces the products and firmware. They will not talk to you (or me). Even if you paid $200 for a developer subscription an additional fee is charged for individual assistance. Plus you would have to sign an NDA agreement which prevents sharing the useful information with us mere mortals. Contact the Smarthome Gold Line and see what they say. If you don't get the answer you want wait a day or two and try again. It often depends on which support person you talk to.

How is the KPL factory reset being performed?

GregE Another user may have found a work around. After the device add fails, do a Restore Device on the Load Controller and see if it can then be controlled with the Admin Console.

Wow. What a diagnostic procedure. The reason the sequence works is the original Automatic device add wrote an End Of List 00-00 link record in slot 2. The must be wiping out the authorization link in slot 1. The Restore device recognizes the Load Controller as an I2CS device that has lost its authorization link and restores the link record in slot 1 just as was done in the Automatic device add pass. The difference is ISY switches to I1 using Peek/Poke which always fail but the effort to write the End Of List record using I1 Peek/Poke failed so the authorization link in slot 1 is not wiped out. Once the device has been Restored the needed authorization link adding the Load Controller to Scenes works because the authorization link in slot 1 exists and the End Of List link record write using I1 Peek/Poke failed so the authorization link was not wiped out. Doing a Restore Device in Automatic mode might have also worked because there is one more link record written during the restore so even if the write of the End Of List record wipes out one link record the other link record will function as the needed authorization link. This diagnostic sequence clearly shows a problem with the Load Controller firmware.

Thanks. I thought that was the sequence. I did that I have not been able to recreate the functional problems reported. Using an 8 button KPL Dimmer with v40 firmware, created 7 Scenes one for each Secondary button. Each of the 7 Scenes was assigned one of the Secondary buttons as Controller, with all the other buttons, including the load (Main A) as Responders. Set all the responders to 0% On except the Main A which has a different On level for each Scene. SceneB - Main at 90% SceneC - Main at 80% SceneD - Main at 70% SceneE - Main at 60% SceneF - Main at 50% SceneG - Main at 40% SceneH - Main at 30% Pressing Main turns the load on to 100%, each press of the Secondary buttons, B,C,D,E,F,G,H reduces the load by 10%. I did recreate the Ramp Rate at 9 minutes. Since the Secondary Ramp Rate sliders have no functional aspect the values have no adverse affects. I will now set the Secondary buttons to non-toggle On mode which should have no functional change except the buttons will blink twice when pressed.

Are you holding all the Scene updates, doing all the physical KPL changes at once?

Not addressing the load button reaction, trying to recreate that here. A Secondary KPL button has no Ramp Rate. A Secondary button does not ramp up or ramp down. It is simply On or Off which is why the Ramp Rate sliders are grayed out. The 9 minute ramp rate indicates some field in the ISY configuration has a value of 00 (9 minute ramp rate) rather than the conventional 1F which is .1 seconds. The value has no meaning for a Secondary KPL button.