LeeG

Insteon Direct device commands control only the device it is directed to. Sending an Insteon Direct On/Off command to the switch has no affect on any devices linked to the switch. This is the way Insteon is designed to work. An individual device can be controlled with Direct commands or all the linked devices can be controlled using Scene commands. If all devices should react turn the Scene On/Off from the Admin Console. I believe MobiLinc will turn the Scene On/Off if it finds the device is a Controller of a Scene. This is a feature of MobiLinc rather than an Insteon device response.

Use a different load on the ApplianceLinc such as an incandescent lamp. When a device will turn On remotely but not turn Off remotely it is often the load the device is controlling is generating enough interference that it does not see the Off commands. If the ApplianceLinc works with a simple lamp the motor needs to be filtered.

jeff000 The SwitchLincs are not linked together as far as the ISY is concerned. Note the event trace below of two SwitchLincs that have been defined as Controllers of one ISY Scene. The first event represents pressing the On paddle on one of the SwitchLincs. Note that the ISY indicates two devices have turned On. Your trace shows only one SwitchLinc turning On. Fri 01/04/2013 01:23:40 AM : [iNST-SRX ] 02 50 1D.23.6B 00.00.01 CB 11 00 LTONRR (00) Fri 01/04/2013 01:23:40 AM : [std-Group ] 1D.23.6B-->Group=1, Max Hops=3, Hops Left=2 Fri 01/04/2013 01:23:40 AM : [ 1D 23 6B 1] DON 0 Fri 01/04/2013 01:23:40 AM : [ 16 3F 93 1] ST 255 Fri 01/04/2013 01:23:40 AM : [ 1D 23 6B 1] ST 255 Fri 01/04/2013 01:23:40 AM : [iNST-SRX ] 02 50 1D.23.6B 19.70.06 41 11 01 LTONRR (01) Fri 01/04/2013 01:23:40 AM : [std-Cleanup ] 1D.23.6B-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 01/04/2013 01:23:40 AM : [iNST-DUP ] Previous message ignored. This is from pressing the Off paddle. Two SwitchLincs are marked as turning Off. Fri 01/04/2013 01:23:55 AM : [iNST-SRX ] 02 50 1D.23.6B 00.00.01 CB 13 00 LTOFFRR(00) Fri 01/04/2013 01:23:55 AM : [std-Group ] 1D.23.6B-->Group=1, Max Hops=3, Hops Left=2 Fri 01/04/2013 01:23:55 AM : [ 1D 23 6B 1] DOF 0 Fri 01/04/2013 01:23:55 AM : [ 16 3F 93 1] ST 0 Fri 01/04/2013 01:23:55 AM : [ 1D 23 6B 1] ST 0 This is what the Scene definition should look like

The 2412N SmartLinc does not function as a Serial PLM substitute. Safe Mode is the result of the ISY not being able to connect to a Serial PLM.

The v.41 will be fine.

Pressing the actual KeypadLinc buttons will work on a variety of KeypadLinc firmware levels. To be able to have another Controller such as a RemoteLinc2 or the ISY PLM (if the Scene is used in a Program) the KeypadLinc must have firmware v.40 or above. Otherwise using the 0% On Level for the Secondary KPL buttons will not turn them Off. If using an older KPL additional ISY Programs and Scenes are required to turn the Secondary KPL buttons Off when using the RL2 or ISY Scene. It is much better to use a newer KPL with v.40 or above firmware.

spaterson76 Thanks for taking the time to post the results. We are all looking forward to Variables being expanded. The development cost to implement the I2CS protocol changes has impacted several planned enhancements according to Michel.

Not necessary to use that option (was in the past) and if used the device firmware level is not retrieved. I just Deleted and added a 4 Scene RemoteLinc2 using New INSTEON Device with Auto Discover. Added successfully and shows RL2 firmware as v.36. Running 3.3.7 (RC4) now but have used Auto Discover for all my device adds for the last several ISY images. I want to know what the device firmware level is and Auto Discover is the way to find that out. With all the rewrite associated with I2CS over the last 10 months Auto Discover works for all the devices I have added over that time including devices which are not I2CS. The RL2 I just added using Auto Discover is not I2CS.

oberkc Yes, it is valid to change the Responder value when the Motion Sensor is a Controller because it is the Responder light node that is having the Responder On Level changed. The Motion Sensor node has to be specified in the Adjust Scene statement 'In Scene' parameter to identify the Controller. As you said each Controller has a unique set of Responder On Level and Responder Ramp Rate values which are stored in the Responder device, not the Controller device. However, that is only providing the Controller Insteon address to know which Responder link in the Responder light node to change. There is nothing in the Motion Sensor that needs to be changed and could not be changed because the Motion Sensor is asleep.

The Adjust Scene statement should specify the Motion Sensor - Sensor node in the 'In Scene' parameter and the light node name in the 'Set' parameter. What ISY firmware level is being used? The Motion Sensor nodes are Controller Only nodes. They have no ability to set an On Level for the Motion Sensor itself. The Scene I have with the Motion Sensor - Sensor node as a Controller and a SwitchLinc Dimmer as a Responder does not show being able to set any On Level for the Sensor node (running 3.3.7).

Define one ISY Scene. Add both SwitchLincs as Controllers of the Scene. This will cross-link the SwitchLincs. Click each SwitchLinc node name below the Scene name and be sure the On Level is set to 100%.

EDIT: forgot to include setting the Responder On Levels for the RemoteLinc2 buttons as Controllers. Define an ISY Scene A. Using a 6 button KPL and 4 Scene RL2 for this example. Add the FanLinc Motor as a Responder, KeypadLinc Secondary button A as a Controller, KPL Secondary button B as Responder, KPL Secondary button C as Responder, KPL Secondary button D as Responder, RemoteLinc2 button A as Controller. Click the ISY Scene A name, set the FanLinc Motor to High, KPL Secondary button A to 100% On Level, KPL Secondary button B to 0% On Level, KPL Secondary button C to 0% On Level, KPL Secondary button D to 0% On Level. Click the KPL Secondary button A node name below Scene A name. Set FanLinc Motor to High, Secondary KPL button B to 0% On Level, Secondary KPL button C to 0% On Level, Secondary button D to 0% On Level. Click RemoteLinc2 button A node name below Scene A name. Set FanLinc Motor to High, Secondary button A to 100% On Level, Secondary KPL button B to 0% On Level, Secondary KPL button C to 0% On Level, Secondary button D to 0% On Level. Define an ISY Scene B. Add the FanLinc Motor as a Responder, KeypadLinc Secondary button A as a Responder, KPL Secondary button B as Controller, KPL Secondary button C as Responder, KPL Secondary button D as Responder, RemoteLinc2 button B as Controller. Click the ISY Scene B name, set the FanLinc Motor to Med, KPL Secondary button A to 0% On Level, KPL Secondary button B to 1000% On Level, KPL Secondary button C to 0% On Level, KPL Secondary button D to 0% On Level. Click the KPL Secondary button B node name below Scene B name. Set FanLinc Motor to Med, Secondary KPL button A to 0% On Level, Secondary KPL button C to 0% On Level, Secondary button D to 0% On Level. Click RemoteLinc2 button B node name below Scene B name. Set FanLinc Motor to Med, Secondary button A to 0% On Level, Secondary KPL button B to 100% On Level, Secondary KPL button C to 0% On Level, Secondary button D to 0% On Level. Define an ISY Scene C. Add the FanLinc Motor as a Responder, KeypadLinc Secondary button A as a Responder, KPL Secondary button B as Responder, KPL Secondary button C as Controller, KPL Secondary button D as Responder, RemoteLinc2 button C as Controller. Click the ISY Scene C name, set the FanLinc Motor to Low, KPL Secondary button A to 0% On Level, KPL Secondary button B to 0% On Level, KPL Secondary button C to 100% On Level, KPL Secondary button D to 0% On Level. Click the KPL Secondary button C node name below Scene C name. Set FanLinc Motor to Low, Secondary KPL button A to 0% On Level, Secondary KPL button B to 0% On Level, Secondary button D to 0% On Level. Click RemoteLinc2 button C node name below Scene C name. Set FanLinc Motor to Low, Secondary button A to 0% On Level, Secondary KPL button B to 0% On Level, Secondary KPL button C to 100% On Level, Secondary button D to 0% On Level. Define an ISY Scene D. Add the FanLinc Motor as a Responder, KeypadLinc Secondary button D as a Responder, KPL Secondary button B as Responder, KPL Secondary button C as Responder, KPL Secondary button D as Controller, RemoteLinc2 button D as Controller. Click the ISY Scene D name, set the FanLinc Motor to Off, KPL Secondary button A to 0% On Level, KPL Secondary button B to 0% On Level, KPL Secondary button C to 0% On Level, KPL Secondary button D to 100% On Level. Click the KPL Secondary button D node name below Scene D name. Set FanLinc Motor to Off, Secondary KPL button A to 0% On Level, Secondary KPL button B to 0% On Level, Secondary button C to 0% On Level. Click RemoteLinc2 button D node name below Scene D name. Set FanLinc Motor to Off, Secondary button A to 0% On Level, Secondary KPL button B to 0% On Level, Secondary KPL button C to 0% On Level, Secondary button D to 100% On Level. ------------------------------------------------- If an 8 Scene RL2 is used it is not a good candidate for this situation because individual RL2 buttons cannot be set to non-toggle On mode. The entire RL2 has to be set to non-toggle On mode OR the RL2 buttons have to be pressed twice to turn On a particular speed because the buttons Toggle On/Off

Use New INSTEON Device, enter the Insteon Address, Name of choice, leaving the Device Type set to Auto Discover. Before clicking Ok on New INSTEON Device, put the RemoteLinc2 into linking mode by pressing the Set button on the RL2 until the LED is blinking. Then click Ok. Be sure the RL2 is near a Dual Band device. If that does not successfully add the RemoteLinc2, run Tools | Diagnostics | Event Viewer at LEVEL 3. Repeat the above process and post the event trace. Click Help | About and verify both the Firmware and UI lines indicate 3.3.7.

There is nothing within existing capability. I cannot speak for UDI regarding future changes. If you want the Motion Sensor to report Low Batt when the battery is closer to failure point the Smarthome forum has a category for requesting product changes.

This Program needs parens If ( Status 'Outside Garage Motion-Sensor' is On Or Elk Zone 'Motion - Front' is Violated ) And From Sunset To Sunrise (same day) Then Set 'Outside Garage' On Else Wait 15 minutes Set 'Outside Garage' Off Also need to know what motion sensor options are in effect. Things like On Only mode can affect how a Program like this is coded.

arw01 Did you purchase the Garage Kit which does include NC magnetic switch. If the I/O Linc was purchased as a separate device nothing comes with it to support any of the various I/O Linc kits.

Go to Programs | Summary tab, look at the Last Run Time and Status columns a little past 5 PM. What do these columns indicate? Last Run Time should indicate 5PM and Status should be True. EDIT: Is the Program in a Folder?

foxcob The last record that is labeled mismatch is not an error. In the device it has the first byte as 00 which marks the End Of List. The remainder of the data (7 bytes) have no meaning in the End Of List record. It is labeled a mismatch because the ISY Links Table display shows a dummy End Of List record which is all 00's. The ISY does not store an actual End Of List record in the ISY data as it would take up 8 bytes unnecessarily. That looks like a Show Device Links display from something earlier than 3.3.7 as the End Of List record is now annotated with ignored/mismatch rather than just mismatch. So long as the active records are identical the actual device link database is correct.

Thanks. That should be fixed to avoid someone else falling into the same hole. I just ran a Replace xxxx with .... function on 3.3.7 to be sure nothing had changed as it had been a few images since I used that function to replace one of my KPLs. The Replace xxxxx with ..... did all the changes to the existing old node as expected. All Program references using the old node name still exist and now issue commands against the new Insteon address. All the Scenes that had link records with the old node device Insteon address were updated with the new Insteon address. The new device with a temp name is gone when the Admin Console was restarted. The Replace xxxx with .... popup does warn the Admin Console will be shut down. Perhaps there was an old Replace function at one time that required all that manual device name find/replace activity. Not needed now with the current Replace xxxx with ..... function. Thanks for pointing out the doc problem. It will be helpful to folks in the future who find this topic.

Where on the Wiki did you find those instructions? It sounds like a valid manual procedure for replacing a device, just not built around the current Replace xxxxx with ..... function which does all the heavy lifting automatically.

The new replacement device is added under some temp device name that will be deleted after the Replace. After the new device is added right click the old node and select Replace xxxx with .... which will list all the potential Replace candidates which should include the new device added under the temp name. The Replace xxxx with .... function changes the Insteon address of the existing old node to the new device Insteon address, keeping the old node name in tack, so Scenes and Programs require no changes. The new temp device is deleted automatically by the Replace function. The old node Insteon address is not referenced on the powerline on the assumption it is defective and physically replaced by the new device. EDIT: the Admin Console has to be cycled so that two devices (old and new) are not listed with the same Insteon address. Once the Admin Console is restarted the old node will have the new device Insteon address and the duplicate will be gone.

The Motion Sensor has no Status to query. Of course it is also asleep so no command execution is possible anyway. All the battery RF only devices (except thermostat) have no actual Status. Even if the devices are put into linking mode a Query would not return the Status of a Motion Sensor, TriggerLinc, RemoteLinc2, RemoteLinc. The Status the ISY maintains is simply the last command received for a particular node. The Low Batt node is set to Off during an ISY boot up because that node only ever sends a low battery condition once when the battery voltage drops. If the ISY did not prime the Low Batt node to Off the node would have a blank Status until the battery is low.

Okay, my bad. The initial post is not discussing two Last Run Time columns. The question is why do Start and Finish have the same value. Two of the Programs have a Status of False which means the last time they were triggered the Else clause ran. Likely there is little to no logic in the Else clause so the both columns show the same time. Two of the Programs are actually running, Activity column shows 'Running Then' which means the Then clause is still active. Could be in a Wait but the clause itself has not completed so the Finish time has not been updated. When a clause finishes the Finish Time column will be updated.

"what does the 'Status' column stand for." In case the explanation in my first post was missed, Status column shows the result of the If clause evaluation. It will be True or False. If True the Then clause executes. If False the Else clause executes.

Would need to see the Program that is not running. Two of the Programs have not completed so the Finish time is not accurate as they have not finished. I do not see two Last Run Time columns. What was done to eliminate the extra columns. The Program that is finished was last triggered with a False condition. Depends on what is in the Else clause whether the Finish time makes sense.