LeeG

Illusion Halloween gremlins ??? my ISY has never locked up before and I have run every Beta since 2.8.1. I wish the rest of the Insteon world worked as well as the ISY. Things are so complex, it may not be possible to recreate something that required a very unique set of conditions to fail. Look at the Adjust Scene issue. Not sure that was ever actually recreateable but enough folks reported the symptom to indicate a problem. Time will tell on these symptoms. I still love my ISY!! Lee

Michel I have tried multiple Replace xxxx With operations this morning and all worked perfectly. From watching the Event Viewer this morning I think the Replace that locked up yesterday was at the very end of the process. Since I cannot recreate the symptom please do not spend any time on this. It is an obvious symptom so if anyone else encounters it then look into it. I would not have posted a non-recreateable symptom except the discussion was about Replace. Lee

Michel Except that they were 8 button KPL dimmers, yes. Right clicked on a KPL dimmer, selected the Replace xxxx with option, picked one of the three possible candidates that were listed and off it went. Looked like it was running fine for a few minutes. I had the Event Viewer running so I could watch what was going on. It had gone through the PLM link database commands but I don't remember the last few commands in the trace when it stopped. After I power cycled the ISY the old KeypadLinc address was changed to the new address. The green Writing Icons that were displayed to the left of the old nodes when it stopped running were gone and the KeypadLinc that was being used to replace the old KeypadLinc had been deleted. I have never had the ISY lock up such that a power cycle was necessary. I always access the ISY by entering the local IP address into an IE browser window. This timed out with the normal cannot display the page. Only if I can recreate the lockup should any thought be given to this. I mentioned it in the post in case anyone else sees the same thing. Lee

If KeypadLinc B button C is controlling a Scene with 3 SwitchLincs as responders, the KeypadLinc A buttons that control the three SwitchLincs should also be Responders in the Scene controlled by KeypadLinc B button C. You may run into overlaps that produce undesired KeypadLinc A button LED responses depending on the overlaps of SwitchLincs being controlled by the various KeypadLinc B buttons.

"will I be able to set the top and bottom seperately??" No. The ON and OFF buttons use the same Group number which means the same Scene (group of responders). This would be a case where a Program is needed. One Program triggers with an On command and does something with a device or Scene and another Program triggers with an Off command from the same KeypadLinc node and does something with a different device or Scene. The ON/OFF buttons would not directly control a Scene. Remember the buttons are still tied together so pressing the ON button turns that button LEDs On and pressing the OFF button turns the ON button LEDs Off and the OFF button LEDs On.

RF_Burns For a KeypadLinc A button to light up it must be part of the Scene controlled by the KeypadLinc B button. Insteon does not propagate Scene commands. When KeypadLinc B turns On a SwitchLinc as a Responder that SwitchLinc does NOT then become a Controller and turn On its Responders. Insteon does not work that way. Every device (including KPL buttons) that is expected to react must be a Responder of the Scene. As far as all KeypadLinc B Secondary buttons turning On when Main B is pressed it sounds like the Secondary buttons on KeypadLinc B are linked as Responders to Main B. Lee

Yes. A 6 button KeypadLinc does not have a separate node for the OFF button. The ON and OFF buttons use the same Group number so the combined buttons function like a single KPL button in toggle mode.

Define a new ISY Scene. Add both the KeypadLinc button and SwitchLinc as Controllers to the Scene. The ISY assumes a Controller is also a Responder (assuming the device has Responder capability) so the effect is to cross-link the KeypadLinc button and the SwitchLinc. When the Scene links have been written either the KeypadLinc button or the SwitchLinc will control the load and both will stay in sync regarding status LEDs.

Someone with the A10/X10 Module please jump in here. I am sure they can be controlled through the Admin Console like any Insteon device but I don't have the Module and would like someone with the Module installed to confirm.

Sure does, changes to a Scene are written to the affected devices. No running around the house pressing Set buttons any more (except for RF devices to wake them up). A side benefit is if the device ever loses it link database there is an ISY Restore Device function that can restore the complete device link database. EDIT: my personal preference is to do everything with a Scene that can be done with a Scene. Not because the ISY is unreliable because the ISY is very reliable. Doing things with Programs that can otherwise be done with a Scene introduces a small delay as a Program has to be invoked and another Insteon message issued. There many things that require a Program and they should always be used where it makes sense. Just start with a Scene and if it cannot be done with a Scene then add a Program to the mix.

Yes, do not manually link them. Unless the User Guide and/or Wiki indicates a manual Set button link should be done for special devices links should always be established by defining a Scene and adding the various devices as Controllers or Responders.

Sure. Define an ISY Scene (Link Management | New Scene). Add the KeypadLinc button (right click on KPL button node and select Add to Scene...) as a Controller and the LampLinc as a Responder (right click on LampLinc node and select Add to Scene..). Set button links should not be done as the ISY is not aware of them and can result in problems later on with link database issues. There are some exceptions about Set button links but in general they should not be done.

Yes, the X10 device can be added to the My Lighting tree. The A10/X10 Module is not required to turn X10 devices On and Off. The basic ISY allows ISY Programs to turn X10 addresses On and Off without the optional A10/X10 Module.

Wow, again more thanks. I did not read the last line. Obviously I have been getting that message and ignoring the words after verifying the correct devices were selected. I was thinking about a separate popup message. Shame on me!

jacobs-gc The ControLinc is a Controller only device, no Responder capability. The Secondary KeypadLinc buttons can be turned On/Off but it must be done with a Scene. Define a Scene with the Secondary KeypadLinc button as a Responder and turn the Scene On/Off. The KeypadLinc firmware does not support Direct control over Secondary KeypadLinc button LEDs. Lee

Thanks again. I don’t remember the Admin Console shutting down but that Replace test was run long ago. I ran a new test replacing a KeypadLinc Dimmer with another KeypadLinc Dimmer and after running for a few minutes the Event Viewer trace stopped activity and the ISY locked up. No popup about restarting the Admin Console and there were still green Write Pending ICONs alongside the old KeypadLinc entries in the My Lighting tree. I was no longer able to access the ISY through the Browser. I had to power cycle the ISY to get it back. Does look like the Replace completed successfully even with the lockup. The old KeypadLinc nodes were no longer Grouped after the Replace but all the nodes are there.

Thanks for the info. Does the Admin Console shutdown on its own or is it closed manually? I would have thought closing it down in the middle of the replace function would create problems.

rogressem When changing Scenes the RemoteLincs are a part of it is necessary to put the respective devices into linking mode so any changes that are necessary can be written to the device. Since RF devices sleep they cannot be accessed unless put into linking mode. Lee

"When I was done, I reopened the Admin Console and there were still writes occurring." Was the Admin Console terminated while the Replace was running?

There is no requirement for anything to be in the If. The following Program which is marked to run at startup sets $IVar4 to 10 If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $IVar4 = 10 Else - No Actions - (To add one, press 'Action') EDIT: 3.1.10 has been solid except for a network resource issue that is fixed by applying 3.1.11 on top of 3.1.10. 3.1.10 has to be installed first as 3.1.11 is a firmware only fix. 3.1.11 is required only if having a problem with Network Module network resources not working when the WeatherBug module is not installed.

raydoc Perhaps if the Scene is described in the context of what are Controllers, what are Responders, and how is the Scene being driven, by a Program, by a Controller button/paddle press, through the Admin Console Scene control. Each Controller of a Scene, including the Scene name itself, can have different responder On Levels. Pressing a SwitchLinc paddle (just as an example of a possible Scene Controller) can have an On Level for the Hallway light different from the On Level if the Scene name is being used to control the Scene. Knowing the structure of the Scene and how it is being controlled (with device, with Scene name manipulation by a Program or Admin Console, may help understand what is happening. With the device actually turning Off in response to what should be a change in On Level indicates either a command being issued that is not anticipated or the Responders On Level for the specific Controller is not set to the expected value. Lee Example: Living Room Lights are controlled by a SwitchLinc which is defined as a Controller of the Scene. Adjacent Office Lights are controlled by a KeypadLinc Primary button which is defined as a Controller of the Scene. The Entry Hallway light is controlled by a SwitchLinc which is defined as a Controller of the Scene. Scene is being controlled through the Admin Console by selecting the Scene name and clicking the On button.

polexian A 2412S PLM provides 12V so a separate external power supply is not needed. A 2413S does not provide power so an external power supply is required. Lee

junkycosmos You're welcome. Actually your thinking is not that off base. The ISY UI makes the single ISY Scene definition with multiple Controllers very easy. From an Insteon perspective that single ISY Scene is actually multiple independent Insteon Scenes. Each Controller represents a different Insteon Scene with its own unique Insteon Controller (Motion Sensor in this case) and set of Responders. Each Insteon Scene allows the Responder(s) to store On Level and Ramp Rate values that are associated with the Controller and unique to that Controller. The ISY UI makes it easy to assign the same On Level and/or Ramp Rate to each Responder with the "Apply Changes To All Devices" check box. Or each Responder can have a unique On Level and/or Ramp Rate for each Controller. The ISY Scene UI is really a powerful piece of software. Enjoy your new On Levels. Lee Note: there have been some problems with Adjust Scene leading to the corruption of a device link database. Beta release 3.1.10 has a fix for the problem and I recommend going to that image as soon as possible if Adjust Scene is being used on a regular basis.

junkycosmos When you Adjust Scene the first parameter must be the Controller you want, in this case the Motion Sensor. The Responder values are unique for each Controller. Specifing the Scene name as the first parameter affects the Responder when turning the Scene name On in a Program or Admin Console. It does not affect the Reponder values associated with the Motion Sensor as Controller. Lee

johnnyt 3.1.10 is a full Beta release. 3.1.11 is only a fix for the Network Resource problem in 3.1.10. Install 3.1.10 and if needed for the Network Resource problem install 3.1.11 on top of 3.1.10. Lee