Cannot determine Insteon Engine - when linking a 2842-222 motion sensor

[Techman]

2 hours ago, notta3d said:

I don't mean to jack the thread, but I my new-ish hidden door sensors 2845-222 v.00 are not being recognized. I bought these back in June because they were on sale and let them sit in a box. Tonight I tried to install one on my front door. I tried both methods of Link a Sensor -> Hidden Door Sensor and Start Linking but the devices are not being found. The PLM was bought in July 2017 after my first one died. I have the ISY 994i/IR Pro Firmware amd UI both running 4.7.3. I get the "cannot determine the Insteon Engine" error. I also get the "following devices could not be added - Insteon Hidden Door Sensor v.00 - Cannot determine device link table address". I have tried 2 brand new sensors with the same result. The rest of the devices in the house seem to be working fine. I just can't add these devices. Also tried adding while having the sensor right next to the modem but same thing.

[EDIT]

Just reset one of the sensors and still receiving "cannot determine device link table address" when trying to add. Restarted both the PLM and the ISY but same result.

[EDIT]

You can disregard. I took my laptop and one of sensors down by the PLM and the ISY. Added the device, yet again, but this time it immediately recognized it. Before I was trying from my second floor thinking it has a range of 150 ft. Should be no problem I thought. Well I guess it does matter.

You'll probably need to add a dual band device close to the door sensor, a plug in module such as a lamplinc or an on/off module works best because of their antenna location.

 

[Techman]

3 hours ago, Reztips said:

Thanks Techman.  I'm actually running 5.0.14 and found the option to add the motion sensor in the dashboard.  It does not exist in the admin console.  Are you seeing the same?

However, I still don't see any of the options available. 

I'm still on 4.7.3. Someone running 5.0.14 should be able to answer your question. I would think that the sensor should show up in your admin console.

[Bumbershoot]

12 hours ago, Techman said:

I'm still on 4.7.3. Someone running 5.0.14 should be able to answer your question. I would think that the sensor should show up in your admin console.

 

15 hours ago, Reztips said:

Thanks Techman.  I'm actually running 5.0.14 and found the option to add the motion sensor in the dashboard.  It does not exist in the admin console.  Are you seeing the same?

However, I still don't see any of the options available. 

Sorry, I didn't review this entire thread, but here's a screenshot from 5.0.14:

 

[lilyoyo1]

On 12/3/2018 at 9:19 PM, Reztips said:

Thanks Techman.  I'm actually running 5.0.14 and found the option to add the motion sensor in the dashboard.  It does not exist in the admin console.  Are you seeing the same?

However, I still don't see any of the options available. 

Make sure you clear your Java cache. I have a few of these and can confirm they work with the newest firmware.

[dbwarner5]

Any suggestions for MDII withV4.7.3?

Specifically, I added two new ones today, no problems, realizing the shortcomings of control using V4.7.3 vs 5.x, but they are reporting motion and battery just fine. 

Tried to add two more tonight and they will Add, but not Report. I can put them into linking mode, get the ISY to find them and write to them and have them show up in my admin tree with the correct MD symbol. I can query the low battery node and it reports "off". However, i cannot get either one of these second two to report motion. The field for the motion node is blank.

I have factory reset them, re-added them, tried every combination of button pushes i can think of. I can put them into linking mode and write to them vie restore device and the ISY will do its job and return them to the MD symbol, but still no motion detection. They blink a quick green when seeing motion so i feel like they are in the right mode, but nothing. I can use the Motion button and get them to blink a long red and then back to a long green. After linking, i have tried 2 button pushes.... 3 button pushes etc. nothing. 

Any suggestions? Seems odd i got two to work and two to not work? 

UPDATE: I purchased 7 of these during the black friday sale, so I went ahead and tried to get the rest of them to work. I am now only 2 for 7.. the original two i did this morning. I cannot get 5 to report.. I will leave them all running overnight and see if they somehow "self correct"... as i know not what else to do!

Thanks. 

[Techman]

When you add them make sure that only 1 sensor at a time is in the linking mode otherwise their link tables can become cross linked.

Try doing a factory reset on only one of the problem sensors then add it to the ISY.  If the sensor has been previously added to the ISY then put it in the linking mode, then do a delete device in the ISY before doing the factory reset and linking to the ISY.

 Make sure that the sensor is in range of a dual band device or close to the PLM.

 

[dbwarner5]

Techman thanks.. that is the procedure I have been doing. To be clear I have now. put each one, individual,ly one at a time into set mode and deleted them from the ISY.  I then individually, one at a time, factory reset them.  Then I removed the battery and replaced the battery shield so that there is no possible way that any of them are powered on.

I have now tried to add just one of them, by pulling the battery strip, removing the battery, resetting it a second time to default, then placing it alone into linking mode and then linking it to the ISY. I did this amongst over 30 dual band switches and then repeated the whole above procedure 3' from my PLM.

It shows up in the ISY almost immediately as a MD with three nodes in both cases. I then press the set button one more time adn get the long double green flash. I then press it again and the flash goes away. I press it quickly one more time and get an acknowledgment flash.  It is recognizing motion as it is reporting a very quick green flash periodically as movement is near it. 

However, there still is NO REPORTING of motion in the ISY. Occasionally I see a long red flash coming from it (indicating linkage issues?)

I am struggling to believe that I have 5 bad sensors out of 7 and cant understand why I cant get these to work.  The first two worked without issue. Also since yesterday just to eliminate any anomalies, I rebooted my ISY as well as my PLM. 

I have nothing else...… thanks.

[Techman]

When you installed them did you link them to the ISY as the old motion sensor 2842-222 which is what you need to do if you're running 4.7.3

[dbwarner5]

yes. I did.. 

here is my log... pardon all the elk activity.  The MD is 4F.8B.E9

 

Mon 12/10/2018 10:05:08 AM : [4F 8B E9 0  ] Using Database Link Table offset 0x0400 (reported 0x0400)

Mon 12/10/2018 10:05:09 AM : [4F 8B E9 0  ] Reading all links

Mon 12/10/2018 10:05:10 AM : [4F 8B E9 1  ] Start : Adding device to ISY

Mon 12/10/2018 10:05:10 AM : [4F 8B E9 1  ] Finish : Adding device to ISY was Successful

Mon 12/10/2018 10:05:10 AM : [4F 8B E9 2  ] Start : Adding device to ISY

Mon 12/10/2018 10:05:10 AM : [4F 8B E9 2  ] Finish : Adding device to ISY was Successful

Mon 12/10/2018 10:05:10 AM : [4F 8B E9 3  ] Start : Adding device to ISY

Mon 12/10/2018 10:05:10 AM : [4F 8B E9 3  ] Finish : Adding device to ISY was Successful

Mon 12/10/2018 10:05:11 AM : [  14 96 D0 1]      DON   0

Mon 12/10/2018 10:05:11 AM : [4F 8B E9 0  ] Successfully added device

Mon 12/10/2018 10:05:11 AM : ---- Start: Generate Scenes from links ----

Mon 12/10/2018 10:05:11 AM : [ELK 0  20  0] Zone : MD Sunroom : Normal (51/0/0)

Mon 12/10/2018 10:05:11 AM : [ELK 0  20  0] Zone : MD Sunroom : Short (52/3/0)

Mon 12/10/2018 10:05:13 AM : [ELK 0  20  0] Zone : MD Sunroom : Violated (51/2/0)

Mon 12/10/2018 10:05:13 AM : [ELK 0  20  0] Zone : MD Sunroom : Open (52/1/0)

Mon 12/10/2018 10:05:20 AM : [  14 96 D0 1]      DON   1

Mon 12/10/2018 10:05:21 AM : ---- End: Generate Scenes from links ----

Mon 12/10/2018 10:05:22 AM : [ELK 0  19  0] Zone : MD Kitchen Slide : Normal (51/0/0)

Mon 12/10/2018 10:05:22 AM : [ELK 0  19  0] Zone : MD Kitchen Slide : Short (52/3/0)

Mon 12/10/2018 10:05:22 AM : [ELK 0  20  0] Zone : MD Sunroom : Normal (51/0/0)

Mon 12/10/2018 10:05:22 AM : [ELK 0  20  0] Zone : MD Sunroom : Short (52/3/0)

Mon 12/10/2018 10:05:22 AM : [ELK 4   0  0] Area : Motion Interior : Ready To Arm (2/1/0)

Mon 12/10/2018 10:05:22 AM : [ELK 0  19  0] Zone : MD Kitchen Slide : Violated (51/2/0)

Mon 12/10/2018 10:05:22 AM : [ELK 0  19  0] Zone : MD Kitchen Slide : Open (52/1/0)

Mon 12/10/2018 10:05:22 AM : [ELK 4   0  0] Area : Motion Interior : Not Ready To Arm (2/0/0)

Mon 12/10/2018 10:05:22 AM : [ELK 0  22  0] Zone : MD Mud Room : Violated (51/2/0)

Mon 12/10/2018 10:05:23 AM : [ELK 0  22  0] Zone : MD Mud Room : Open (52/1/0)

Mon 12/10/2018 10:05:23 AM : [ELK 0  19  0] Zone : MD Kitchen Slide : Normal (51/0/0)

Mon 12/10/2018 10:05:23 AM : [ELK 0  19  0] Zone : MD Kitchen Slide : Short (52/3/0)

Mon 12/10/2018 10:05:23 AM : [ELK 0  22  0] Zone : MD Mud Room : Normal (51/0/0)

Mon 12/10/2018 10:05:23 AM : [ELK 0  22  0] Zone : MD Mud Room : Short (52/3/0)

Mon 12/10/2018 10:05:23 AM : [ELK 4   0  0] Area : Motion Interior : Ready To Arm (2/1/0)

Mon 12/10/2018 10:05:23 AM : [ELK 0  22  0] Zone : MD Mud Room : Violated (51/2/0)

Mon 12/10/2018 10:05:23 AM : [ELK 0  22  0] Zone : MD Mud Room : Open (52/1/0)

Mon 12/10/2018 10:05:23 AM : [ELK 4   0  0] Area : Motion Interior : Not Ready To Arm (2/0/0)

Mon 12/10/2018 10:05:24 AM : [All         ] Writing 24 bytes to devices

Mon 12/10/2018 10:05:24 AM : [4F 8B E9 1  ] Link    0 : 0400 [E2014C1B99010001] Writing [E2014C1B99010001]

Mon 12/10/2018 10:05:25 AM : [PLM         ] Group   1 : Writing Responder Link matching [4F 8B E9 1  ] Link    0 : 0400 [E2014C1B99010001]

Mon 12/10/2018 10:05:26 AM : [4F 8B E9 1  ] Link    1 : 03F8 [E2024C1B99010002] Writing [E2024C1B99010002]

Mon 12/10/2018 10:05:26 AM : [         X10]       A7

Mon 12/10/2018 10:05:27 AM : [PLM         ] Group   2 : Writing Responder Link matching [4F 8B E9 1  ] Link    1 : 03F8 [E2024C1B99010002]

Mon 12/10/2018 10:05:27 AM : [ELK 0  15  0] Zone : Mud Room Door : Violated (51/2/0)

Mon 12/10/2018 10:05:27 AM : [ELK 0  15  0] Zone : Mud Room Door : Open (52/1/0)

Mon 12/10/2018 10:05:27 AM : [4F 8B E9 1  ] Link    2 : 03F0 [E2034C1B99010003] Writing [E2034C1B99010003]

Mon 12/10/2018 10:05:28 AM : [PLM         ] Group   3 : Writing Responder Link matching [4F 8B E9 1  ] Link    2 : 03F0 [E2034C1B99010003]

Mon 12/10/2018 10:05:29 AM : [4F 8B E9 1  ] Link    3 : 03E8 [0000000000000000] Writing [00..............]

Mon 12/10/2018 10:05:29 AM : [4F 8B E9 1  ] Link    4 : 03E0 : Writing High Water Byte

 

[dbwarner5]

In the ensuing 30 minutes from 10:05:29 to now (10:35), the MD (4F 8B E9)  never shows up in the log again, even though it is right in front of me registering blinks with motion.

[Techman]

The second to the last line in your log shows that the link table is empty. Not sure exactly why.

The fact that the sensor blinks means that it's detecting motion, but it seems that the link tables in the ISY are not correct.

At this point it's probably best to submit a support ticket to UDI and let them take a look.

Submit a Ticket:          http://www.universal-devices.com/contact-support

 

[dbwarner5]

ok thanks.

[jds31]

Harking back to my youth "Solder is the best programming language" .  I had a similar problem with a motion sensor that once worked, I took out of service and after a couple years I tried to use it again but it no longer even powered on.  Before pitching it, I removed the PCB and found significant corrosion on the back.  No idea where it came from.  I cleaned the PCB using instructions on line and presto it works again.  

[paulbates]

15 hours ago, jds31 said:

Harking back to my youth "Solder is the best programming language" .  I had a similar problem with a motion sensor that once worked, I took out of service and after a couple years I tried to use it again but it no longer even powered on.  Before pitching it, I removed the PCB and found significant corrosion on the back.  No idea where it came from.  I cleaned the PCB using instructions on line and presto it works again.  

I found that the front bezel, at least of the old model,  does not seal well, if you're using it outdoor. I put a bead of superglue on the left, right and bottom edges and that ended the problem. I have 3 outside.

Paul