Trouble Linking A Hidden Door Sensor

[smokegrub]

I have already linked and I am using a Hidden Door Sensor (2845-222). I am trying to link a second device and, under Link Management, I have selected Link a Sensor, Hidden Door Sensor, typed in the device’s address and assigned it a name. I then put the device in linking mode and proceed. I get the message “Cannot determine Insteon Engine". I then tried Link Management, New Insteon/A10/X-10 device with the same results. I have done a factory reset and repeated the foregoing steps with the same outcome.

The device is located the width of a doorway from 2 dual band devices that are linked and functioning properly.

[LeeG]

Run Tools | Diagnostics | Event   Viewer at LEVEL 3.

 

Repeat the add process and post the event trace.

 

Check the Insteon address for an 8/B, 0/D type misread.   The query of the Insteon Engine is usually the first command issued which would mean the Hidden Door Sensor is not responding at all to that Insteon address.

[smokegrub]

Here is the events log:

 

Fri 10/03/2014 02:57:13 PM : [          IR]     014A Press

Fri 10/03/2014 02:57:24 PM : [          IR]     0156 Press

Fri 10/03/2014 02:58:03 PM : [          IR]     014A Press

Fri 10/03/2014 02:58:26 PM : [2B 2F 26    ] Added to list of devices to link to ISY

Fri 10/03/2014 02:58:26 PM : [iNST-TX-I1  ] 02 62 2B 2F 26 0F 0D 00

Fri 10/03/2014 02:58:26 PM : [iNST-ACK    ] 02 62 2B.2F.26 0F 0D 00 06                 (00)

Fri 10/03/2014 02:58:35 PM : [iNST-TX-I1  ] 02 62 2B 2F 26 0F 0D 00

Fri 10/03/2014 02:58:35 PM : [iNST-ACK    ] 02 62 2B.2F.26 0F 0D 00 06                 (00)

Fri 10/03/2014 02:58:44 PM : [iNST-TX-I1  ] 02 62 2B 2F 26 0F 0D 00

Fri 10/03/2014 02:58:44 PM : [iNST-ACK    ] 02 62 2B.2F.26 0F 0D 00 06                 (00)

Fri 10/03/2014 02:58:48 PM : [2B 2F 26 0  ] Failed to add device, reason 3
 

[LeeG]

That is the first command and the Hidden Door Sensor did not respond to the three attempts.  Make sure the 2B is not really a 28.  Move the Hidden Door Sensor near the PLM if it is a 2413.

[smokegrub]

I was able to get the device to link by positioning it near the PLM. However, it does not display its state after linking. Moreover, the linking display on the device (flashing green light) keeps blinking after linking. I have deleted the device from ISY, factory rest the device and relinked with the same result.

[LeeG]

The linking process does not take the Hidden Door Sensor out of linking mode.  It will time out in 4 minutes (approx) or can be taken out manually (see user guide for Set button sequence).

 

It will not signal state changes until out of linking mode.

[smokegrub]

Didn't know that. will chack again later.

[smokegrub]

I deleted the device, factory reset it, linked it and waited until the flashing light was off (several minutes). The device's current state is still not displayed. The Low Battery state is presented; the Heartbeat is not.

[LeeG]

Tap the button on the end of the Hidden Door Sensor.   That will produce the first state change message.   The heartbeat default time is 24 hours.

[smokegrub]

I have already done that several times and it still does not show its state.

[LeeG]

Is the Hidden Door Sensor still positioned near the PLM?

 

What level ISY firmware is being used?

[smokegrub]

It wasn't, but I carried it back to within 2 feet of the PLM and tapped the button. Nothing. The firmware is 4.2.10. As I stated above, I have already linked one of these devices, programmed it and it is working beautifully.

[smokegrub]

I am going to knock off for the day; I am getting tired. Will do a factory reset tomoroow and go through the drill. If that diesn't work, II will then try the one additional device I have on hand. If it links successfully, I will call Smarthome and get a replacement for the one that doesn't work.

[LeeG]

I doubt a device that did not receive the query of the Insteon Engine could communicate in the reverse direction.  Thus the question whether the device was near the PLM when state change messages not received.

 

I was considering the possibility this Hidden Door Sensor is at a different firmware level,  thus the question about whether on the latest ISY firmware. 

[smokegrub]

I linked a different Door Sensor this morning and it also will not report its state.
I queried the device and got the following message:
Subscriber didn’t reply to event:1
147
No network connection
[DHCP) state = RENEW}
I then exited the ISY and reentered with my password. I queried the device again and got the message:
Subscriber didn’t reply to the event.

What is interesting is that the device that is successfully installed and reporting is 2C.71.97. The two failed devices are 2B.2F.35 and 2B.2F.26. These latter two devices both begin with the preface 2B.2F and may have something intrinsic to their manufacture that is defective.

I look forward to any feedback.

[LeeG]

The Hidden Door Sensor cannot be queried because it is a battery device which goes to sleep.    The ISY does issue a Query command which is a bug UDI acknowledged a few days ago.

 

The Insteon address does advance over time as new devices are manufactured.   Look at the Hidden Door Sensor firmware level which is on the second line, right side of node display.

[smokegrub]

I have looked for the firmware level and I obviously do not know where the "right side of the node display is located". 

[LeeG]

Line 2 on the right side, this one is v.43

[smokegrub]

LeeG:

 

Thanks for all your help. It was very much appreciated.

 

I contacted Smarthome and reviewed all we had done with this problem and they agreed the firmware in the batch beginning with the device number 2B.2F. was likely defective. They have agreed to replace the devices.

 

Again, many thanks.

[LeeG]

Post back the results with the new devices.   First time I have heard of an issue that was traced to an Insteon address range. 

[PurdueGuy]

I have a 2B.2F.xx Hidden Door Sensor that linked just fine, once I realized I realized I needed to upgrade to Pro, as I hit the non-Pro device limit.

[smokegrub]

I have a pro and I am nowhere near the device limit. The replacements are in the mail. If they don't link.....

[LeeG]

Thanks PurdueGuy, I had never heard of such an issue before and I've been at this along time..   I'll be surprised if the replacements work differently.

[smokegrub]

LeeG:

I received the replacement door sensors today and you were correct, as usual, the original devices apparently weren’t defective. Let me review my process for linking and setting up the devices and, perhaps, you will see something I am doing incorrectly:
1. When the battery tab is pulled I wait until the Status LED stops flashing.
2. I place the device within 18-inches of the PLM.
3. Link Management > New Insteon/A10/X10 Device > Remove Existing Links
4. Press and hold the Set Button on Device until it beeps and the Status LED flashes green..
5. Execute the Link.
6. All 3 nodes for the device appear in the Device Tree.
7. I wait until the green light in the device stops flashing (about 5 minutes).
8. I press the Contact Plunger until the Status LED turns green. I release the Contact Plunger and the device turns red.
9. Checking the Current State of the device in the Admin Console shows no status.
10. Writing Updates to the device gives a response that ISY cannot communicate with the device and a red exclamation point appears adjacent to all 3 nodes in the device tree.

[MikeD]

Hi smokegub,

 

To write updates to the door sensor it has to be in linking mode.

 

Here is the Hidden Door Sensor linking procedure I follow.

When you press and hold the Set button the first time the LED starts flashing. While in this mode you can link it to your ISY, write changes to the Door Sensor, include it in Scenes and Programs, and Query it.

 

To exit linking mode you do not have to wait for the LED to stop flashing, it is a two step process.

1. Press the Set button again and the LED will continue to flash but at a different rate. I believe this is referred to as the unlinking mode, this mode is not used in the setup with your ISY and can be ignored.

2. Press the Set button one more time to exit. The LED should be completely off at this point.

 

Once the Door Sensor is out of linking mode it is a one way communicating device, sending Open/Close, Heartbeat, and Battery Status information to your ISY. It cannot receive any changes until it is placed in linking mode again.

 

Hope this helps clarify linking mode for you.

~Mike