Adding 2852-222 leak sensor -> comes up as Triggerlinc instead

[oskrypuch]

OK, the title notes my problem.

 

I have a 994i running 4.4.6 in a complex network. I have successfully added the original 2852-222 sensors before, and these are running in the system. I had one left over that I hadn't added in at that time, and decided to today.

 

Followed the New Insteon Device dialog, typed in the address, selected 2852-222, put the device into discover mode with the fast blinks. The dialog disappears, for a moment 2852-222 is shown, and then it changes to (2421) Triggerlinc v.40, with an Opened, Closed and Heartbeat node.

 

Also tried AutoDiscover, same thing.

 

The other units were correctly added in (a year or two ago) with Leak Sensor v.41 shown and Dry, Wet & Heartbeat nodes.

 

What am I doing wrong?

 

* Orest

 

[stusviews]

You don't seem to be doing anything wrong. Try a factory reset.

[Teken]

The device should be in a slow blink - fast blink indicates multi-unlink.

[oskrypuch]

OK, how do I get it to slow blink? Holding the button for five seconds or so will get into a 0.75 sec blink mode.

 

If I hold it longer, the light will go ON, and then momentarily blink OFF, kind of in reverse. I think that is forced a "wet" condition.

 

Not sure how to factory reset it.

 

The unit is 0114 revision 2.1

 

* Orest

Edited August 14, 2016 by oskrypuch

[Techman]

OK, how do I get it to slow blink? Holding the button for five seconds or so will get into a 0.75 sec blink mode.

 

If I hold it longer, the light will go ON, and then momentarily blink OFF, kind of in reverse. I think that is forced a "wet" condition.

 

Not sure how to factory reset it.

 

The unit is 0114 revision 2.1

 

* Orest

 

 

After the factory reset try using auto discover rather than selecting the device type.

[stusviews]

Factory reset:

 

1. Using a small flat blade screwdriver, carefully open the bottom case of Leak Sensor

2. Pull out the battery

3. Wait 5 seconds

4. Push in Set button and hold it. Do not let go

5. Reinstall the battery while holding down the Set button

          LED will turn on solid Green for a few seconds

          LED will then turn off

6. Release Set button

 

To place the sensor into linking mode, don't hold the set button for more than about 3 seconds.

Edited August 14, 2016 by stusviews

[oskrypuch]

Thanks.

 

Did a factory reset. Still same behavior, either with auto discover or specifying the type, I end up with a Triggerlinc v.40.

 

Dipping in water turns all the modes ON, and they stay ON.

 

Perhaps I have a bad unit.

 

* Orest

[stusviews]

On older leak sensors, you need to tap the set button to reset from a wet condition.

[oskrypuch]

On older leak sensors, you need to tap the set button to reset from a wet condition.

This was in the same bunch, purchased with my other ones, and the others reset to OFF by themselves. Believe that is an older behavior?

 

In any case, ON or OFF, the nodes are still listed as Opened, Closed and Heartbeat node as for a triggerlinc, the unit is identified as a Triggerlinc and not a Leak Sensor, so this one unit is still dead in the water. (no pun intended)

 

* Orest

Edited August 15, 2016 by oskrypuch

[Teken]

Hello Orest,

 

Can you please confirm in the Admin Console that both the UI & Firmware are the same: Help -> About

[larryllix]

On my two newer units of four that I have pressing the button for about two seconds sends an off and pressing the button very quickly sends an on.

[oskrypuch]

Hello Orest,

 

Can you please confirm in the Admin Console that both the UI & Firmware are the same: Help -> About

 

Yes, they are.

 

 

* Orest

[Teken]

Hello Orest,

 

If you have completed the hard reset and the device still comes up as a Trigger Linc perhaps its defective and needs to be replaced. Can you follow the steps outlined by Stu one more time and see what happens when you try to add the device back?

 

For the sake of asking can you also install fresh batteries to the unit.

[oskrypuch]

Hello Orest,

 

If you have completed the hard reset and the device still comes up as a Trigger Linc perhaps its defective and needs to be replaced. Can you follow the steps outlined by Stu one more time and see what happens when you try to add the device back?

 

For the sake of asking can you also install fresh batteries to the unit.

 

Will do, and report back.

 

* Orest

[oskrypuch]

OK, did the factory reset, battery is good.

 

I do have to hold the button down about 3.5s or so, else there is no blink, and no device seen.

 

Used Auto discover, same results, two pics below.

 

* Orest

 

[Techman]

A possibility is that the Leak Sensor was programmed with the wrong firmware at the factory

 

What's the date code and hardware version on the sensor?

[Teken]

Hello Orest,

 

Can you update the ISY Series Controller to the latest official firmware: http://forum.universal-devices.com/topic/19162-release-451-is-now-official/

 

Once done can you try to add the new device back in using both methods and let us know the results?

[Teken]

A possibility is that the Leak Sensor was programmed with the wrong firmware at the factory

 

What's the date code and hardware version on the sensor?

 

 

 

The unit is 0114 revision 2.1 firmware v.40

[Techman]

OK, did the factory reset, battery is good.

 

I do have to hold the button down about 3.5s or so, else there is no blink, and no device seen.

 

Used Auto discover, same results, two pics below.

 

* Orest

 

 

Did you first delete the sensor from the ISY before you tried to add it back in, if not try doing that.

[oskrypuch]

Did you first delete the sensor from the ISY before you tried to add it back in, if not try doing that.

 

Yes, always deleted the errant entry. Otherwise, nothing happens.

 

Will try updating to the latest firmware, and repeat.

 

* Orest

[oskrypuch]

OK, upgraded to 4.5.1 for firmware & UI.

 

Deleted the unit.

 

Tried autodiscover, ended up with Triggerlinc like before.

 

Deleted the unit.

 

Tried again specifying 2852-222, ended up with Triggerlinc.

 

So still, no joy,

 

* Orest

Edited August 15, 2016 by oskrypuch

[Techman]

Do your other leak sensors also show a firmware version of v.40

 

Did you buy them all at the same time

[oskrypuch]

Yes, bought them all at the same time. Six of them, one was a spare, the one I'm trying to hook up now.

 

The other units are identified as firmware v.41, but they are also identified (correctly) as 2852-222 units, so the apparent v.40 firmware identification on this unit could be incorrect, or it may in fact be the issue.

 

I am thinking that either this unit is defective, or there is a bug in the earlier firmware. I have ordered a couple more 2852-222's, will see what happens with them, and will report back. 

 

* Orest

[Techman]

Yes, bought them all at the same time. Six of them, one was a spare, the one I'm trying to hook up now.

 

The other units are identified as firmware v.41, but they are also identified (correctly) as 2852-222 units, so the apparent v.40 firmware identification on this unit could be incorrect, or it may in fact be the issue.

 

I am thinking that either this unit is defective, or there is a bug in the earlier firmware. I have ordered a couple more 2852-222's, will see what happens with them, and will report back. 

 

* Orest

 

The ISY queries the sensor to get its firmware version so it sounds like the sensor is defective.

 

The date code indicates that they were built in January 2014. Not sure if those units even had a .40 firmware.  Sensors built in late 2014 had a .43 firmware.

[oskrypuch]

New Leak Sensors arrived. 

 

Both set up correctly in ISY with the v.43 firmware for the correct device.

 

One of them senses correctly, but looks like the other one is NOT sensing water. There is no flash on a water dip, nor a state change in ISY, unlike with the other unit. Guess that one may have to go back!

 

* Orest