Model 2844-222

When I try to add I get this message:

Cannot add device

Cannot determine insteon engine

"Cannot determine Insteon engine" means that the PLM can't communicate with the device.

Either the device is out of range of the PLM or the device isn't in the linking mode. Also check your batteries.

I plugged a usb cable in for power to eliminate a bad battery. The motion sensor is a few feet from my PLM. I held the set button until i heard one beep and got a slow flash. Still got the same error message.

If I recall correctly, you must add some sensors a little differently. Rather than "start linking" option and pressing the set button (and hoping that the ISY can hear it), you must go to the drop-down menu and add the MSII by selecting it from the menu and manually entering the requested data.

@PapaBear

Try doing a factory reset on the MS, then attempt to link it

I did a factory reset.

I tried manually adding using both 2844-222 device types [10.16] [10.18]

Still no luck. Same error message.

Another possibility is that your typing in the incorrect 6 digit address. It very easy to mix up the 8 and the B

Double checked the address. Had it correctly.

Did you try to add via simple start linking and then putting ms in setup mode. It’s the only method I use to add devices but admittedly haven’t added a ms in many years. Got rid of all them once I added Ring cameras with motion via Ring plug in.

Edit. Thinking a bit more maybe you can’t link ms using that method.

Edited Sunday at 08:53 PM1 day by hart2hart

@PapaBear , I've been taking some swings at this and have not been able to reproduce what you are seeing. I've tried different communication modes (I1 vs I2), linking methods, power methods, and device versions. Things seem to just work.

Would you mind posting the contents of your Event Viewer when things fail?

The following is what I get when I intentionally enter in the device address. The ISY tries 3x to communicate with the device and then times out with the error message.

Another possible check - If your MSII has been linked to the PLM previously, it will still contain the PLM address (even after a factory reset). Assuming the PLM still contains your MSII link (hasn't been restored from backup), you will see the MSII address pop up in the event viewer when you apply power. The communication below is from my MSII @4A.6F.7A telling the PLM that it has turned on when power is applied. Use this to quadruple check your device address (labels do get old and disfigured).

The following is the method that I've settled on for linking the MSII's. Using "Auto Discover" is easier that scrolling to the bottom of the device list, and it populates the Sensor Version (v.46 below).

If none of this appears to work, it is possible you simply have a defective MSII or RF Interference in the area around your PLM. You could try linking the sensor away from the PLM but close to a different RF repeater. The MSII's are 915 MHz and it's possible that you would have other devices in this range. That's not a problem that I've encountered. It is also possible that you have device(s) spamming the powerline and disrupting things while you're trying to add the device. The event monitor should show evidence if this it the case.

I cleared the event viewer and used auto discover as you suggested

It looked like it would add the MSII

Then it quickly timed out...

My MSII is sitting on my desk 15" from my PLM

@PapaBear , the ISY is trying to contact the MSII. It retries 3x and then times out.

Did you happen to try monitoring the Event Viewer while re-connecting power to the MSII? I'm assuming you had the sensor connected previously.

You also seem to be getting a lot of activity from the device @14.16.B3. I'm guessing it's a thermostat. That's both good and bad. The thermostat is communicating well with the Insteon network (do know the point of access). The bad may be the traffic it's throwing at the system.

You might still try re-locating to a separate room - this will force a different RF access point to the system.

I continue to wonder if you are not doing it correctly. When I attempt to do so, the pop-up windows look differently than the ones you have. Here is how I believe it needs to be done:

Choose "link Management" and navigate to Motion Sensor II, as shown below:

You should get a pop-up that looks a little differently than the one you showed. The pop up is not "auto discover" but should have the device type prepopulated with the motion sensor II.

Manually add your address in the top box. Choose "OK".

Hopefully, it should find it.

@oberkc , simply two different methods to link. Bottom line is the command shown below that is being executed by the ISY is correct (get Insteon Engine Version). If the MSII hears to command it should respond with an I2 engine version.

It is not responding which leaves us with the following options:

1. Device address is incorrect. Possible, although I've never encountered a mis-printed label. There are methods where the device can be manually linked to determine it's address.

2. The device can't hear the PLM because of interference in the area (or PLM can't hear the MSII). Move to a different location and re-try.

3. Faulty MSII (it happens)

3 hours ago, IndyMike said:

simply two different methods to link.

Well, I was not so sure that this is the case for the MSII. I had a recollection that for this device, it needed to be done a specific way. Perhaps I am wrong about this, but it certainly does not hurt to try.

@PapaBear It's been a while, but the last time I got the "cannot determine..." message it was because I was out of space. Once I upgraded to ISY pro version, this situation was resolved. Before the upgrade, I removed a seldom-used device entirely, and the problem device added just fine (I had to test my theory before upgrading). Your situation may be different, but I thought I would throw this out there.

10 hours ago, oberkc said:

Well, I was not so sure that this is the case for the MSII. I had a recollection that for this device, it needed to be done a specific way. Perhaps I am wrong about this, but it certainly does not hurt to try.

@oberkc , You are correct that it doesn't hurt to try... I just ran both methods and they work equally well with my spare MSII's. That said, I am using an ISY994 whereas @PapaBear is running the EIsy.

4 hours ago, GlowingHair said:

@PapaBear It's been a while, but the last time I got the "cannot determine..." message it was because I was out of space. Once I upgraded to ISY pro version, this situation was resolved. Before the upgrade, I removed a seldom-used device entirely, and the problem device added just fine (I had to test my theory before upgrading). Your situation may be different, but I thought I would throw this out there.

@GlowingHair , I believe you are referring to hitting the "Node limit" in the standard ISY994 (254 nodes). PapaBear is running the EIsy. I don't know the node limit but believe it to be substantially higher than the ISY994. I don't recall anyone hitting the Eisy limit as yet.

3 hours ago, IndyMike said:

You are correct that it doesn't hurt to try... I just ran both methods and they work equally well with my spare MSII's. That said, I am using an ISY994 whereas @PapaBear is running the EIsy.

Out of curiosity, I checked the wiki. Unfortunately, it appears out of date. Regardless, it seems to say that one must use the method I suggested. I also have a vague recollection that using the generic "start linking" process did NOT work for me. I look forward to a report from @PapaBear