LeeG

Set the Load Control button (ON/OFF) to non-toggle Off mode. The OFF button LEDs will no longer be On when the KPL is Off.

This is a 2413 Dual Band PLM? Sorry, I think my suggestion about being positioned close to the PLM was unclear. Set the Motion Sensor 6' from PLM within line of site. Not sure how well the RF will work when sitting inches apart. The trace shows no response from the motion sensor. This is actually worse than when using an Access Point. Makes me wonder if the PLM is Dual Band.

The Red LED flashing indicates motion sensed but may not have a direct relation to Insteon Motion On message being sent. It sounds like the new Motion Sensor may not be setup for Sense Mode and On Only mode so the MS is waiting for the timeout interval to expire. The Set button press sends Insteon messages regardless of the options.

My motion sensors are stable. The only time I have problems is when a battery gets too low. When more than one device stops working it could be an RF problem. Are the MS's using the same dual band device? Any wireless baby monitors, other wireless devices in the 900 MHz range?

The trace entries with Hops Left=0 were the old trace entries from when the motion sensor was positioned near an Access Point on the opposite 120v leg (phase). The trace entries at the very end of the last post, which I think reflect the attempt at the PLM location, got no response at all which makes me think the motion sensor timed out of linking mode before the device add was attempted.

There is a Clear button on the Event Viewer. It should be used to clear out old entries when starting a new trace. The trace entries at 09:43:45 which I think reflect the attempt to add with the Motion Sensor when at the PLM location show no device response at all. This can happen if the device times out of linking mode before the device add was attempted. Suggest trying once more. Click Clear on the Event Viewer to clear old trace entries. Place the Motion Sensor near the PLM and put into linking mode. The motion sensor will remain in linking mode for approx 4 minutes before timing out. The device add has to be initiated before the 4 minute timeout.

Thanks. The trace is very helpful. A few commands to the Motion Sensor worked but at the very extreme. Several commands got no response which eventually terminated the device add. A new battery could be installed Move the Motion Sensor to the ISY PLM location to eliminate the rest of the Insteon network. Repeat the device add with the Event Viewer running at LEVEL 3 with the Motion Sensor near the 2413 PLM.

Delete to old shortcut. Clear the Java cache. Issue http://isy.universal-devices.com/99i/3.3.9/admin.jnlp Should create a new Icon

Edit the file with WordPad. Select all the lines, copy to clipboard, paste into post.

Next step is to run Tools | Diagnostics | Event Viewer with LEVEL 3. Use New INSTEON Device as previously described to attempt to add Motion Sensor. Post the event trace. From the message I think there will be no communication from with the Motion Sensor. The event trace will confirm that.

ISY 3.3.9 (RC6) is the latest image. If the Insteon address of the Motion Sensor is in question it can be manually linked to some responder such as a LampLinc or ApplianceLinc. Press the Motion Sensor Set button putting it into linking mode. Press the Set button on a LampLinc or ApplianceLinc to link it as a Responder to the Motion Sensor. Then do a Show Device Links Table on the LampLinc/ApplianceLinc. Unless there were deleted link records in the device the Motion Sensor address will be in the last link record. The LampLinc/ApplianceLinc requires a Restore Device to get rid of the Set button link. If the ISY PLM is a 2413 the Access Point closest to the Motion Sensor can have the 4 tap Set button test initiated. Then look at the 2413 PLM status LED to see if it can hear the Access Point. A few days ago a user found a dead spot in his RF coverage was responsible for a thermostat problem. Seems like a space between two Access Points had no RF coverage. Can also try moving the Motion Sensor to a different location to see if better RF coverage is obtained.

The 2842-222 and 2420M are the same device. The 2842-222 is Smarthome new Item number Scheme for RF devices. The -222 suffix indicates it uses an RF frequency for the US. Do not specify a Device Type. Use New INSTEON Device, enter Insteon Address of Motion Sensor, Name of choice, leave Device Type set to default Auto Discover. BEFORE clicking Ok, put the Motion Sensor into linking mode by pressing the MS Set button until the Red LED blinks continuously. Then click Ok on New INSTEON Device. Be sure the Motion Sensor is near a Dual Band device.

Regarding the ApplianceLinc turning on in response to a Scene, devices do not add themselves to Scenes. Run a Show Device Links Table against the ApplianceLinc. Check the Scene/Group number (2nd byte of link record) in each Responder link record (starts with A2) for a match to the Scene it is reacting to. Sounds like there is an old link record in the ApplianceLinc that matches an existing ISY Scene. 1 : 0FF0 : A2 11 19.70.06 FF 1F 00 This REST command issued through a browser will display all the ISY Scenes http://192.168.2.7/rest/nodes/scenes The deviceGroup tag contains the Scene/Group number which is displayed in decimal. The Show Scene/Group number is in hex. Convert the hex number to decimal to find in the REST display 22412 SceneLampLinc 69 M13 - 14 41 95 1

Thanks for posting back. The link records in my example were Responder link records. When the Active bit is reset the A2 Flag byte becomes 22. The link record in your last post was a Controller link record for KPL button 3 (either button C if 8 button, or button A if 6 button). When the Active bit is reset the E2 Flag byte becomes a 62. An Unlink with a Set button and some applications set the Flag byte to 02 to mark a link record inactive. Thus the possibility of 02, 22, or 62 for an inactive logically deleted link record.

The PLM is on the end of the chain. If there is an ISY Log entry that indicates a Program turned a device On this is not the result of a PLM issue.

Here is a sample of a link database that contains logically deleted link records. The three link records with 22 in the first byte (Flag byte) have an Insteon device address for a device that was removed from a Scene. Same thing happens when a device is Deleted. When the link record Flag byte is marked inactive (22) the device no longer looks at that link record when determining if it should respond. In this case 1B.57.F8 is a device that is still defined to the ISY. Unlinking with a Set button (should not be done when using an ISY), removing a device from a Scene, Deleting a device from the ISY, changes the Flag byte only. It could take an additional 14 commands per link record to zero out the remaining 7 bytes for no functional benefit. 3 : 0FE0 : A2 21 0F.44.DC 80 1F 02 4 : 0FD8 : 22 06 1B.57.F8 FF 1F 02 5 : 0FD0 : A2 00 19.70.06 FF 1F 01 6 : 0FC8 : 22 04 1B.57.F8 FF 1F 02 7 : 0FC0 : A2 35 19.70.06 BF 1F 02 8 : 0FB8 : 22 05 1B.57.F8 FF 1F 02 9 : 0FB0 : A2 37 19.70.06 00 1F 02

The I/O Linc address being in the KPL link database does not in and of itself mean anything. The link records are likely marked inactive (start with 02, 22, 62) which means the KPL is not using them. Can you do a Show Device Links Table on the KPL and post the results.

I don't see a link table issue since the Responder link records would be Full On or Full Off, with no Ramp Rate settings other than default 0.1 seconds which the dimmer can handle. More the impact of regression testing I suspect.

Dimmer to Dimmer is fine. Does not matter whether SwitchLinc to Icon to ToggleLinc, so long as a dimmer to dimmer. Dimmer to Relay, Relay to Dimmer (although this seems like it could be accepted it is not), is not supported. Easy test, right click a Dimmer of any kind, select Replace xxxx with and look at the devices listed the ISY considers eligible for Replace. They are all dimmers. Repeat the Replace xxxx With test on a Relay type device. Only other Relay devices are listed. The Replace xxxx With can be cancelled so there is no lasting effect of the above test

As noted the device is being commanded to turn Off then On to a less than 100% On Level. Check the Programs being triggered. The ISY does not turn a device Off on its own. The trace suggests two different Programs are being triggered, each turning Off a separate device. Check Programs | Summary tab, Last Run Time column should show Programs that are being run at that time.

Cannot replace a Relay with a Dimmer.

Set 'xxxxxx' On turns the device to 100% On Level. Run Tools | Diagnostics | Event Viewer with LEVEL 3 selected. Run the Programs and post the trace. From the posted information the device is physically reacting in an unexpected way. What type of device is being controlled by the Program?

A Scene with 20 devices can require over 300 commands in the Controller device alone, all of which must work, for the restore to complete. The results of testing a few Query/On/Off commands does not mean much when compared to 300+ commands for the restore. When there are issues with more than one device it is very likely there is an Insteon network issue. Start at the source, the PLM. Is the PLM plugged directly into an outlet, no power strips which may have noise suppression that absorbs Insteon signals. Other electronic devices powered from the same point, UPS, PC, Laptop, etc, should be isolated with a FilterLinc. Any new appliances? Another user this weekend found a new washer was interfering with Insteon traffic. Make sure the Access Points are within reliable RF range and on opposite 120v legs (phases). Analyze what circuits contain the devices that have issues. Are they contained on the same circuit, on the same 120v leg? Determining the cause(s) of powerline problems is often a process of elimination. nearly

You need a State Variable for the Folder Condition. Also making the Folder Condition True allows the Programs in the Folder to be triggered (Run). It does not make the Programs in the Folder Run. The Program If Conditions control when/if a Program triggers once the Folder Condition is True

There is nothiing I am aware to show how the RF aspects of the Insteon Mesh Network affects any given Insteon message.