LeeG

Thanks Michel I was looking at it from the device perspective rather than an ISY file question. Would be a good idea to stop the LED updates as well. j0dan please ignore my last comment about LED values being in separate memory area. Lee

jpoje From the Event Log it appears the RemoteLinc was not accessable. However, the "Device communications events" option was not selected so the actual commands issued and the responses were not traced. Suggest doing it again, being sure RemoteLinc is close to a Dual Band device and the RemoteLinc LED is blinking from pressing Dim/Bright buttons. Lee

j0dan The If is coded to trigger the Program any time the Status of any of the 4 devices changes. What would you like to eliminate (minimize)? Changing the link record Responder On Level and Ramp Rate obviously affects the link database in the respective device. Changing the LED level does not alter the link database. The LED level along with other device configuration information is contained in a different area of memory. Since the link database corruption is an open problem there is no absolute that LED changes are not affecting the link database but the probability is low. I think what Michel was suggesting was to temporarily stop changing the Scene Responder On Level and Ramp Rate information. Lee

Device add looks good at first glance. All the expected link records with the correct Group numbers. Since the ISY has no control over what Group number the Motion Sensor sends for any given event I am thinking that maybe one of the battery snaps is not fully seated or perhaps a V1 motion sensor needs to be factory reset after a low battery. I know that not to be true for V2 as I have done various tests using low voltage to see where low battery trips. Once a new battery was installed the V2 MS worked as expected. Perhaps this MS is malfunctioning. Do all the other MS devices that are being added now demonstrate the same behavior?

rlebel For what it’s worth I deleted and added a V2 Motion Sensor under 3.1.7. It worked except it did not prompt to put the device into linking mode. The 3 link records in the Motion Sensor were created (confirmed with Show Device Links Table) and it is signaling motion (confirmed with Event Viewer). Admin Console shows Sensor node On/Off as Motion is detected. Low Batt was initialized to Off during device add and remains Off. Sorry for the misdirect about V1 options. I worked with UDI during the Set Option update from V1 to V2. Was aware of the limited V1 support. Lee EDIT: changed lighting and confirmed Dusk/Dawn is also being correctly shown in Admin Console

Yes, the else command is needed. The Floor Lamp will not turn Off otherwise.

When the SwitchLinc was originally added to the ISY two link records were added to the SwitchLinc, a Controller and a Responder link record. The PLM also receives a Controller and Responder link record. The Controller record in the SwitchLinc and corresponding Responder record in the PLM are necessary for the ISY/PLM to receive a message when the SwitchLinc paddle is pressed. This is independent of any Scenes the SwitchLinc may eventually be associated with. The Controller record in the PLM and corresponding Responder record in the SwitchLinc allows the SwitchLinc to react to the All On/All Off commands directed to My Lighting. When the SwitchLinc is added to a Scene as a Controller the ISY writes a Responder link record in the SwitchLinc for the specific Scene/Group number. The SwitchLinc is assumed to be a Responder as well as a Controller. The responder link record is necessary for the SwitchLinc to respond to Scene On/Off commands directed to the Scene name. What all of this has to do with the results you have observed I do not know.

rlebel I believe the V1 Motion Sensor does not support programmatic setting of options. Jumper 5 had no function with a V1 MS. Don't know what the error message means but perhaps there are updates pending that the motion sensor cannot handle. Are there any Icons to the left of the Motion Sensor node in the My Lighting tree? Lee

If the problem is limited to the physical device losing link records a Restore Device will resolve. If it is the ISY losing track of links that is a different matter.

If Control works, If Status works. The motion sensor sends one low battery message so If Control triggers only once. If Status triggers only once as Status has to change and equal the If condition to trigger.

Click on the Save Changes button in the lower left corner of the Details display. What you see is NOT what you get until the Program definition/updates are saved. A null Then clause is likely being executed if the Program was never saved.

Check the Program | Summary tab and see if Activity column says Not Saved.

Michel Ditto on the two Pro write options (batch and RF) being missing. Did not notice until IM noted the problem. Lee

RBC I'm pretty sure the V27 SwitchLinc does not support I2. The I1 method of setting Local On Level and Local Ramp Rate values (Set MSB, Peek, Poke commands) often require the device to be power cycled (pull Set button for 15-20 seconds) for the changes to take effect. The only way to be sure is to Delete the device and Add it back to the ISY using Auto Discover. The Event Viewer has to be running with the Device communications events option selected to see the commands issued during the device Add process. It is during the device Add process where it is determined if the device supports I2. If device Add determines I2 is not supported it will not be used to change the device configuration. I'll review the Event Log of a new device Add trace if you want to Delete/Add the SwitchLinc. There were issues with v27 SwitchLincs not related to configuration changes. It might be wise to just replace the device with a new SwitchLinc. Not everyone experienced the V27 issues. Lee

RBC Use Wordpad to view the Event Log file, Copy the Log file lines and Paste in post. It will look something like below. The following is what I traced when I set my SwitchLinc V38 On Level to 40%. Click on the Event Viewer Clear button just before changing the On Level. No need to have anything in the post but the actual adjustment of the On Level. Be sure to select the Device communications events option so all the commands will be traced. The using I1 comment is likely the problem if it is related to setting the On Level. What ISY firmware level are you running? Does the Admin Console display of the SwitchLinc Node show the firmware level of the SwitchLinc? Also, just to confirm, this is a SwitchLinc and not an ICON switch? Wed 09/14/2011 04:57:03 AM : [iNST-ACK ] 02 62 16.3F.93 0F 11 66 06 LTONRR (66) Wed 09/14/2011 04:57:03 AM : [iNST-SRX ] 02 50 16.3F.93 12.9F.E4 2B 11 66 LTONRR (66) Wed 09/14/2011 04:57:03 AM : [standard-Direct Ack][16.3F.93-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Wed 09/14/2011 04:57:03 AM : [ 16 3F 93 1] ST 102 Wed 09/14/2011 04:57:03 AM : [ 16 3F 93 1] OL 102 Wed 09/14/2011 04:57:03 AM : [All ] Writing 1 bytes to devices Wed 09/14/2011 04:57:03 AM : [16 3F 93 1 ] Memory : Write dbAddr=0x0032 [66] Wed 09/14/2011 04:57:03 AM : [iNST-ACK ] 02 62 16.3F.93 1F 2E 00 01 06 66 00 00 00 00 00 00 00 00 00 00 00 06 (00) Wed 09/14/2011 04:57:04 AM : [iNST-SRX ] 02 50 16.3F.93 12.9F.E4 2B 2E 00 (00) Wed 09/14/2011 04:57:04 AM : [standard-Direct Ack][16.3F.93-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Lee

matapan According to the release notes the 2487S support was added at 3.1.3 Lee

RLIKWARTZ Describe the Scene. What devices are in the Scene and how are they defined, controller, responder. A KeypadLinc button that is defined as part of an ISY Scene should turn Off when the ISY Scene is turned Off. Under My Lighting, select the Scene name and click the Off button. Does the KeypadLinc button LED turn Off? Lee

RBC “When I manually adjust the swl by slowly ramping up or down the light level, the Admin console follows and shows the Current State changing. When I tap the On paddle once, the light load in the room goes full bright, while the Admin console shows the Current State changing from OFF to what ever the slide "ON level" happens to be--example--the console is set to ON Level of 50%, the Current State goes to 50% but the actual light is full bright.†My v36 SwitchLinc Dimmer goes to the On Level defined after pressing and holding the Off paddle allowing it to ramp down to Off. Then tap the On paddle. Suggest running Tools | Diagnostics | Event Viewer with Device communications events selected. Set the On Level to something different so the ISY will have to update the value. Post the Event Log. Need to verify that I2 is being used to update the On Level. Lee

raydoc As a suggestion on how to proceed why don’t you assign names to the various devices you want to use, the KeypadLinc, the 7 SwitchLincs, etc. You pick the names so they will be familiar. Then describe how the devices should interrelate to each other. Pressing SwitchLincA paddle should do what, turn on its load which is a function of hardware so that it not necessary, should turn On KeypadLincX button B for example. Or pressing KeypadLincX button D should turn On SwitchLincD and pressing SwitchLincD paddle should turn On KeypadLincX button D LED. That level of detail. Once the requirement is stated then Scene examples can be offered to accomplish the tasks. If they cannot be accomplished with simple Scenes then where an ISY Program is required in addition to Scenes. Lee

raydoc Perhaps it will help to understand that one Controller (A) cannot initiate another Controllers ( Scene by turning On that Controller (. For example …. SwitchLincA as Controller of Scene1 has device1 and device2 as responders SwitchLincB as Controller of Scene2 has device3 and device4 as responders KeypadLincC button A as Controller of Scene3 CANNOT turn On SwitchLincA and expect Scene1 to turn On. Insteon does not work that way. Scene3 would have SwitchLincA as a responder as well as device1 and device2 as responders. When Scene3 is turned On by pressing KeypadLincC button A the three responders (SwitchLincA, device1, device2) of Scene3 turn On. Also note that the Primary Load control button on an 8 button KeypadLinc (Main) can be a Controller of a Scene just like any other KeypadLinc button. It does not matter that no physical load is connected to the KeypadLInc. KeypadLincC button Main is controller of Scene4 KeypadLincC button B is controller of Scene5 KeypadLincC button C is controller of Scene6 and so on “I'd like the lights on the 8KP to be on if they control a single SL and if possible be on if the scene is active.†If I understand the requirement, KeypadLincC button B turns On/Off SwitchLincB and if SwitchLincB is turned On/Off with the paddle KeypadLincC button B should also turn On/Off. To accomplish this SceneX has KeypadLincC button B as a Controller and SwitchLincB as a Controller. Multiple Controllers of the same Scene. When either SwitchLincB paddle is pressed or KeypadLincC button B is pressed both SwitchLincB and KeypadLincC button B turn On/Off together. The KeypadLinc button LED and the SwitchLinc status LEDs stay in sync. Lee

captfisk The Motion Sensor On command triggers the posted Program which turns On 'Light'. The Motion Sensor Off command is not programmed to do anything. There are a number of options. The simplest but the least flexible is to define a Scene with the Motion Sensor as a Controller and 'Light' as a Responder. The Motion Sensor On command will turn 'Light' On directly and the Motion Sensor Off command will turn 'Light' Off. This approach is useful for outside lights that turn On with motion and turn Off at some absolute time interval after motion has stopped. The other approach is to do things programmatically as this provides the most flexibility when the Responders will turn Off. A separate Program can be created that triggers with the Off command and the Then clause turns 'Light' Off. This is not much more than using a Scene described above but will turn 'Light' Off. If a simple On/Off is all that is required I suggest using a Scene rather than a Program. There is a very small delay in 'Light' turning On because the ISY Program has to be triggered and run to turn 'Light' On. With a Scene 'Light' will turn On instantaneously to motion being sensed. Sometimes a Motion On condition is gated with a range of time of day, perhaps turning the responders on to a different light level depending on time of day. This requires a Program which you have started. The 'Light' Off can be done following a Wait in the Program that triggers with the On command, not using a separate Program that triggers from a Motion Off. First thing to do is establish the objectives. When should Motion On result in lights turning On. Does it vary with time of day, etc. How long should the responders stay On. If the objectives can be satisfied with a simple Scene that is the path of choice. If not then one or more Programs are required to satisfy the objectives. For my Master Bathroom the motion sensor turns the bathroom light On directly with a Scene. However I suppress the Off command coming from the Motion Sensor (On Only) and use program logic to determine when the light should turn Off. Hope this has not just confused the issue. Lee

Panda88 The I/O Linc sends an On or Off command as the Sensor changes state at which time the ISY marks the device Current State with the corresponding On/Off State. The ISY does not poll/query any Insteon device on a regular basis except for the 3 AM Query of My Lighting. At this time all devices are queried. It should not be necessary to routinely query any device for its current status. Do all Sensor state changes fail to reach the ISY suggesting link record problem or an intermittent failure which would suggest a powerline communication issue. Lee

Panda88 An easy way to determine if there is a powerline problem where the I/O Linc is installed is to move it to where the ISY PLM is plugged. Once there use a simple jumper wire between the I/O Linc Sense connection and GND to cause the Sensor to change state. Does the I/O Linc Sensor node now show Sensor state changes. If not the link records are likely compromised. A Restore Device should resolve the problem. If not delete the I/O Linc and add it back to the ISY. If the Sensor node still does not show state changes likely the I/O Linc is defective. When the I/O Linc shows Sensor node state changes when plugged at the PLM move it back to the garage. If the state changes are no longer registered by the Sensor node there is a powerline problem. Lee

Panda88 When I/O Linc Sensor node Current State does not update either there are link record problems in the I/O Linc or ISY PLM or there are powerline issues with the I/O Linc location. A Restore Device will correct link record problems (if there are any). Sometimes fluorescents in the garage can interfere with Insteon signals or the distance is too far (which may can be fixed with an additional Access Point or filtering the device that is interfering). The Query changing the Sensor node status can be either the result of the I/O Linc state change not reaching the ISY PLM (one of the two situations above) or it can also be the result of using Trigger Reverse I/O Linc option. Trigger Reverse reverses the On/Off commands sent by the I/O Linc Sensor on state change. Normally the I/O Linc sends On command when I/O Linc Sensor turns On. Trigger Reverse reverses the commands. An Off command is sent when the I/O Linc Sensor turns On. The problem is Trigger Reverse does not affect Query. Query returns the true state of the I/O Linc Sensor regardless of Trigger Reverse option. Status versus Control has no affect in a Garage project. Control triggers when the Insteon command flows. Status triggers when the ISY tracked Current State changes. Current State reflects the last On/Off command from the I/O Linc Sensor. Lee

An Insteon Controller, be it a SwitchLinc paddle, an individual KeypadLinc button, etc. can Control only one Scene. SwitchLinc A can have many responders. SwitchLinc B can have many responders. The responders of SwitchLinc A and SwitchLinc B can be the same devices, totally different set of devices or a mixture of both. A device can be a Responder in many Scenes. A device can be a Controller of only 1 Scene. This is Insteon architecture, not ISY design. Each KeypadLinc button can control a different Scene but each KeypadLinc button can control only 1 Scene. KeypadLinc button A as a Controller of Scene1 KeypadLinc button B as a Controller of Scene2 KeypadLinc button C as a Controller of Scene3 and so on. Perhaps if you explain why you need a SwitchLinc with only a single paddle to be able to control multiple sets if devices (Scenes) we can explain how to accomplish within the Insteon architecture.