Another Motion Sensor Linking Question (Mini Remote too)

[Buzzhazz]

ORIGINALLY POSTED IN ERROR IN ANOTHER FORUM, BUT NOW MOVED HERE.

 

I have not been on the forum for a while, but I'm back. I purchased a 2842-222 Motion Sensor, but feel stupid because I can't figure out how to install it, even after searching for an answer.

 

When I try linking from the Link Management drop down menu, I have tried "Link a Motion Sensor" and "New Insteon Device" with the same results.

 

The menu pops up, I enter the Insteon address of the MS and give it a name and click OK. The window closes--and that's it. Should I put the MS in Link mode before or after I click OK? I have tried both. Should any of the jumpers be installed to the On position (i.e. Jumer 5 - Remote (Software) Management)?

 

I have a Dual Band PLM, two access points, and four dual band switches spread throughout the house, and my Insteon system overall has been very reliable. I have placed the MS near an access point and near the PLM. No change.

 

On perhaps a related note, I also purchased a Mini Remote switch and experienced the same linking problems, though I used the RemoteLinc option since there is no Mini Remote option. Should that work? I am using the Mini Remote to link to my workshop dust collector so that I can turn it on from wherever I am in the shop. Eventually, I did manual linking per the old fashioned manual way, and it works from all over the house so I think the RF portion of my network is reliable.

 

What am I doing wrong?

[Xathros]

New MS is an I2CS device which requires ISY Firmware version 3.2.6 or later. What Firmware are you running?

 

-Xathros

[Buzzhazz]

New MS is an I2CS device which requires ISY Firmware version 3.2.6 or later. What Firmware are you running?

 

-Xathros

 

3.3.10

[oberkc]

Should I put the MS in Link mode before or after I click OK?

 

I doubt that it matters, but I would put it into link mode BEFORE adding to ISY.

 

Should any of the jumpers be installed to the On position (i.e. Jumer 5 - Remote (Software) Management)?

 

For the purposes of linking, I don't think the jumpers matter. However, I would definitely allow software management of the motion sensor.

 

Of course, the entirety of your problems could be related to version of ISY software, as LeeG suggests.

 

What am I doing wrong?

 

Not being on the forum for a "while".

[LeeG]

Jumper 5 should be in place.

 

Use New INSTEON Device, enter Insteon Address, Name of choice, use default Auto Discover. BEFORE clicking Ok put motion sensor into linking mode by pressing MS Set button until Red LED blinks continuously. Now click Ok. Be sure Motion Sensor is in range of a Dual Band device.

[Buzzhazz]

Jumper 5 should be in place.

 

Use New INSTEON Device, enter Insteon Address, Name of choice, use default Auto Discover. BEFORE clicking Ok put motion sensor into linking mode by pressing MS Set button until Red LED blinks continuously. Now click Ok. Be sure Motion Sensor is in range of a Dual Band device.

 

Well, I think I may have had a browser/Java issue all along. I tested another scene and got some kind of "Node Error; Retry." Nothing was responding. Uninstalled/reinstalled Java and was able to install the MD. Just added it to a scene as a controller and it's working.

 

Then I tried the Mini Remote, which is listed as a Mini Remote on the device and a RemoteLinc 2 on the box--but the part number is 2342-242. It would not link using AutoDiscover (Unrecognized Device) but did link using RemoteLinc as the device type (though the part number is different.

 

I'll play with the options now since using RF devices is new within my system, and I'll return with any questions for the excellent advice you guys always provide.

 

On an unrelated note, I have the 99i and now that it apparently will no longer have firmware updates, is it fair to assume that subsequent versions of existing Insteon devices and any new devices that come along will not be supported by the ISY?

[LeeG]

"is it fair to assume that subsequent versions of existing Insteon devices and any new devices that come along will not be supported by the ISY?"

 

Not supported by 3.3.10 on 99i. The 4.x.x beta stream already has additional I2CS rework which is not in 3.3.10. If it were not for I2CS one might consider staying with 3.3.10 if no new devices were anticipated. However, staying on 3.3.10 is just not realistic with the continuing I2CS changes that are still being reacted to. There was an update path from 99i to 994i but not sure that offer is still in effect. Suggest sending an email to UDI sales@..... for the latest information on upgrade to 994i.