Insteon Leak Sensor 2852-222 Review

[Teken]

Sounds good. So far i have yet to leave a sensor in an sitting in a wet condition for more than 24 hours. All of my tests thus far have been to simulate wet then dry without hitting the set button to reset the nodes status.

 

One other thing im thinking to test is to manually set one of the variables to an number not used in the programming, lets say 5. This should be done on a sensor you are not using for the wt/dry testing. If my thinking is correct the variable should be reset sometime within 24hrs assuming a heartbeat is not missed. I am trying this right now and will report back if the variable changes at heartbeat.

 

How are you getting the status update at 6pm if all of your variables are set to 1?

 

 

I just want to reiterate that the program is working mostly as expected  with the exception of continuous problem emails when a sensor has been wet then dried without manually resetting the sensors status via the set button. Your assumption is correct. If my findings are true my issue would be that if there was a leak detected that happened to dry up, i wouldn't get more than one days (1 leak, 2 problem alerts) worth of reminders to reset the sensor. In reality im hoping that i never have real life use for the sensors and if i do i would think i i would remember to reset the sensor, but hey you never know.

 

Side note: i realize that the person who generously contributed the leak detection program was likely using the sensors that reset themselves when dry. Which could be part of the reason im not getting continuous emails. I agree that 3 emails should suffice to have someone reset the sensor but there could be a slight and i mean very slight chance that a sensor does not get manually reset. I know personally i dont load up the ISY console often enough to notice the node was still showing as wet.

 

I just followed the program outlined by Belias, and since deployment have always received two status update e-mails. To be clear you have (two) separate custom e-mails one for the alert, they other for the status correct?

 

Also, I believe you may be on to something about the program being crafted using a sensor that returns a node from wet to dry and never assumed Smartlabs would change that behavior to be manually changed.

 

This is an excellent discussion about what to expect and what is observed. I am also curious to see what will happen when you and I manually change the value to other than what is listed in the program. This would prove 100% if the program will alter and update the program to a default value known in the program.

 

Thank you for bringing this insight . . .

[rabbit1543]

Another thing i wanted to mention is that one may want to set the init variables to the current value this way states can survive a isy reboot during a leak?

[rabbit1543]

Checked this morning on the variable I manually changed and it has been set back to 1. Also the time of the change is spot on with the time the program for variable 2 was last run.

[Teken]

Checked this morning on the variable I manually changed and it has been set back to 1. Also the time of the change is spot on with the time the program for variable 2 was last run.

 

Which test are you performing today? Are you running the wet to dry test or the wet test and letting it stay wet? Thanks for the update about the variable changing back this is what I expected to happen.

[rabbit1543]

Im running the wet and stay wet test. I have already run the wet and let dry test twice. Plus setting the variable manually. I don't think the wet and let dry tests need to be run anymore. I will run again if you feel necessary. I'm thinking that there well need to be some programming changes to accommodate these newer sensors. Some quick thoughts are to have 3 notification programs.

1. Program for leak detection

2. Program for heartbeat detection

3. Program for prolonged wet node status.

 

I'm not sure what the programs would be just yet but maybe we can do a little brainstorming to see what would work best

[Teken]

Im running the wet and stay wet test. I have already run the wet and let dry test twice. Plus setting the variable manually. I don't think the wet and let dry tests need to be run anymore. I will run again if you feel necessary. I'm thinking that there well need to be some programming changes to accommodate these newer sensors. Some quick thoughts are to have 3 notification programs.

1. Program for leak detection

2. Program for heartbeat detection

3. Program for prolonged wet node status.

 

I'm not sure what the programs would be just yet but maybe we can do a little brainstorming to see what would work best

 

I believe if these questions are posed to the author in the original thread some good feed back may be obtained.

[rabbit1543]

Checked the wet and stay wet test this morn and variable is back to 1. Are you seeing the same results?

[Teken]

Checked the wet and stay wet test this morn and variable is back to 1. Are you seeing the same results?

 

I got side tracked on another project and will need to report back in a few days.

[rabbit1543]

Over the past few days i have reworked the programs from Belias to accommodate the newer sensors that need to be manually reset. I have not taken into consideration the older style sensors that reset themselves when returned to dry. Im running through some tests now and if all works well i will post my solution. The heartbeats are the most difficult thing to test as it takes a full day to truly verify everything is working as expected. 

[jss]

Hi

I've received new leak sensors, and they are 4714REV2.3 v42 in ISY.

Once Wet/ON, they don't flash again, nor return to "OFF" when dry.

 

I'd love to find some devices that are the older version, much more functional to me.

 

Any ideas or work arounds?

[Techman]

Hi

I've received new leak sensors, and they are 4714REV2.3 v42 in ISY.

Once Wet/ON, they don't flash again, nor return to "OFF" when dry.

 

I'd love to find some devices that are the older version, much more functional to me.

 

Any ideas or work arounds?

 

If you have an electrical outlet close by you can use an IOLinc and a wet/dry sensor (Smarthome item #79633). This combination will give you programming flexibility.

[larryllix]

Hi

I've received new leak sensors, and they are 4714REV2.3 v42 in ISY.

Once Wet/ON, they don't flash again, nor return to "OFF" when dry.

 

I'd love to find some devices that are the older version, much more functional to me.

 

Any ideas or work arounds?

Only use "control is switched On" with either signal. Wet and Dry are not reciprocal signals.

 

For Wet there is On for  fleeting second, and there is nothing.

For Dry there is On for a fleeting second and there is nothing.

 

Write two programs like this

 

'Wet Program'

If

   Control 'Leak.wet' is switched On

Then

  Wait 30 seconds

  Run program (else) 'Wet Program'

Else

   ---

 

'Dry Program'

If

   Control 'Leak.dry' is switched On

Then

  Wait 30 seconds

  Run program (else) 'Dry Program'

Else

   ---

 

Make sure they are both enabled and saved.

 

Now   observe your program tree in the Admin Console. Make sure your icons are enabled to turn colours etc.. found in one of the ISY pulldown menus.

 

You should see the program icons turn Green for True (then) and Red for False (else).

 

Let us know how you make out with this.

 

If you touch your Leak sensor contacts to a we surface you should get the Wet program turning green indicating it sent a signal

[gduprey]

Has anyone found anyway to "reset" a wet condition programatically without having to press the button?  While I can get to most of my sensors, one is buried in insulation in the attic (near a water line for the humidifier).  It went off (because of a test before installing it) and while I don't expect it to go off again, it is a royal pain to get to it.

[Techman]

The  current versions of the leak sensors require a push of the set button to reset them when they're in the wet mode, there's no work around. Looks like you're going to have to get familiar with your attic.

[Teken]

The  current versions of the leak sensors require a push of the set button to reset them when they're in the wet mode, there's no work around. Looks like you're going to have to get familiar with your attic.

 

LOL . . .

[gduprey]

Too familiar with it already.  Oh well -- I put it there and should have known to reset it first.  Lesson learned.

[Broyd]

I received my second set of leak sensors (2852-222) from Costco about a month ago and have just started to check out their characteristics. The sticker information is: 1015 REV 2.3 and the device info from the admin console is (2852-222) v.00.

 

I was NOT able to add this device to the ISY-994i until I entered the device address AND selected the device type from the dropdown list on the New INSTEON Device panel.

 

As reported, when the sensor is exposed to a very quick wet situation, the WET condition is switched ON and the DRY condition is switched OFF. The sensor will remain in this state indefinitely (even though the contacts were only wet for a very short duration) until the sensor is reset by pressing the set button on the sensor. 

 

Now the interesting part. The older sensors used to send out ONE wet signal when the sensor became wet. If the wet condition was at the hairy edge of detection, you could get multiple and rapid ON-OFF signals being sent. This new sensor behaves quite differently ... So when I barely touched the contacts to my tongue ...

 

The sensor sends out 9 WET (switched ON) signals, each of which is spaced at approximately 16.5 seconds apart over a period of 2 minutes and 11 seconds. Then it sends out a single signal at 9 minutes following the last signal; then another at 21 minutes 30 seconds; then another at 21 minutes and 39 seconds. I have waited an additional 30 minutes to see if any more signals were received but at this time, I have not seen any others.

 

This is as far as I have followed the sequence so far but it's pretty clear this will require program changes to account for the multiple wet signals being sent. 

[Teken]

I received my second set of leak sensors (2852-222) from Costco about a month ago and have just started to check out their characteristics. The sticker information is: 1015 REV 2.3 and the device info from the admin console is (2852-222) v.00.

 

I was NOT able to add this device to the ISY-994i until I entered the device address AND selected the device type from the dropdown list on the New INSTEON Device panel.

 

As reported, when the sensor is exposed to a very quick wet situation, the WET condition is switched ON and the DRY condition is switched OFF. The sensor will remain in this state indefinitely (even though the contacts were only wet for a very short duration) until the sensor is reset by pressing the set button on the sensor. 

 

Now the interesting part. The older sensors used to send out ONE wet signal when the sensor became wet. If the wet condition was at the hairy edge of detection, you could get multiple and rapid ON-OFF signals being sent. This new sensor behaves quite differently ... So when I barely touched the contacts to my tongue ...

 

The sensor sends out 9 WET (switched ON) signals, each of which is spaced at approximately 16.5 seconds apart over a period of 2 minutes and 11 seconds. Then it sends out a single signal at 9 minutes following the last signal; then another at 21 minutes 30 seconds; then another at 21 minutes and 39 seconds. I have waited an additional 30 minutes to see if any more signals were received but at this time, I have not seen any others.

 

This is as far as I have followed the sequence so far but it's pretty clear this will require program changes to account for the multiple wet signals being sent. 

 

Hello Broyd,

 

That is interesting and is similar to what I found on one sensor. Let me know if you place this new sensor on a plate of water how the LED behaves.

 

I have one leak sensor that makes the LED stay almost steady lit but not if that makes sense. Meaning it appears to the naked eye the LED is pulsing from (guessing here) 70% to 100% LED brightness.

 

I call this out because this sensor is the only one out of 11 that does this?!?!

[Techman]

I received my second set of leak sensors (2852-222) from Costco about a month ago and have just started to check out their characteristics. The sticker information is: 1015 REV 2.3 and the device info from the admin console is (2852-222) v.00.

 

I was NOT able to add this device to the ISY-994i until I entered the device address AND selected the device type from the dropdown list on the New INSTEON Device panel.

 

 

Broyd, if the firmware is showing v.00 then the ISY did not fully recognize the sensor. The firmware version should be v.43 or higher. Try uninstalling, then reinstalling the sensor.  Make sure that the sensor is in close proximity to a dual band device when you re-install it.

[Broyd]

Hi Teken, I tried this as you suggested. My LED behavior is the same as when I just quickly wet the sensor. I let it sit in the water during the test. So, the response I got was just a quick flash every 16.5 seconds. I did wait for 15 minutes and I did not see the flash at 9 minutes as before. I didn't wait any further.

 

I guess they key issue is to ensure that at least ONE leak signal is detected by the ISY. Once detected, notifications programmed by the user can be sent to the user and the user will need to deal with the matter ASAP. If needed, the user can set up their programs to lock out any extra leak signals to prevent unnecessary notification flooding.

[Teken]

Hi Teken, I tried this as you suggested. My LED behavior is the same as when I just quickly wet the sensor. I let it sit in the water during the test. So, the response I got was just a quick flash every 16.5 seconds. I did wait for 15 minutes and I did not see the flash at 9 minutes as before. I didn't wait any further.

 

I guess they key issue is to ensure that at least ONE leak signal is detected by the ISY. Once detected, notifications programmed by the user can be sent to the user and the user will need to deal with the matter ASAP. If needed, the user can set up their programs to lock out any extra leak signals to prevent unnecessary notification flooding.

 

Thanks for testing and the follow up . . .

 

Surprisingly even though the leak sensor sends multiple on's I never received multiple emails indicating the same?!?! Are you seeing multiple emails when the leak sensor is placed in a wet condition?

 

Also, Techman is correct you need to delete the sensor and add it back so the firmware shows up correctly. In the past the ISY had no ability to interrogate battery operated devices and always showed a v.00.

 

Now the system absolutely does query the battery operated device to determine what attributes needs to be used and added. Failure to do so will cause erratic behavior to be seen when deployed in your Insteon network.  

[Broyd]

For anyone following this thread: the whole business of the v.00 being reported in the admin console was due to me using a PLM from 2011. This was also the cause of having to enter the device type when I was trying to add these sensors. A newer PLM corrected this.

 

Hi Teken and Techman

 

I didn't see multiple emails: I was incrementing a variable using a program triggered by the DONs sent from the sensor.

 

I removed the sensor and re-added it. It is within 2 feet of the PLM and I'm getting the same result for the version (v.00)

 

I have 3 more of these sensors. I'll check them out next. 

 

 

Here is the event viewer level 3 if I do not indicate the device type:

 

Thu 02/25/2016 12:18:13 PM : [37 82 3E ] Added to list of devices to link to ISY
Thu 02/25/2016 12:18:13 PM : [iNST-TX-I1 ] 02 62 37 82 3E 0F 0D 00
Thu 02/25/2016 12:18:13 PM : [iNST-ACK ] 02 62 37.82.3E 0F 0D 00 06 (00)
Thu 02/25/2016 12:18:13 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 0D 02 (02)
Thu 02/25/2016 12:18:13 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:18:13 PM : [iNST-TX-I1 ] 02 62 37 82 3E 0F 10 00
Thu 02/25/2016 12:18:13 PM : [iNST-ACK ] 02 62 37.82.3E 0F 10 00 06 ID-REQ (00)
Thu 02/25/2016 12:18:13 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 10 00 ID-REQ (00)
Thu 02/25/2016 12:18:13 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:18:22 PM : [iNST-TX-I1 ] 02 62 37 82 3E 0F 10 00
Thu 02/25/2016 12:18:22 PM : [iNST-ACK ] 02 62 37.82.3E 0F 10 00 06 ID-REQ (00)
Thu 02/25/2016 12:18:23 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 10 00 ID-REQ (00)
Thu 02/25/2016 12:18:23 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:18:32 PM : [iNST-TX-I1 ] 02 62 37 82 3E 0F 10 00
Thu 02/25/2016 12:18:32 PM : [iNST-ACK ] 02 62 37.82.3E 0F 10 00 06 ID-REQ (00)
Thu 02/25/2016 12:18:32 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 10 00 ID-REQ (00)
Thu 02/25/2016 12:18:32 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:18:36 PM : [37 82 3E 0 ] Cannot determine device type
Thu 02/25/2016 12:18:36 PM : [37 82 3E 0 ] Failed to add device, reason 2
Thu 02/25/2016 12:18:36 PM : [All ] Writing 0 bytes to devices 

 

And here it is if I specify the device type:

 

Thu 02/25/2016 12:19:26 PM : [37 82 3E ] Added to list of devices to link to ISY
Thu 02/25/2016 12:19:26 PM : [iNST-TX-I1 ] 02 62 37 82 3E 0F 0D 00
Thu 02/25/2016 12:19:26 PM : [iNST-ACK ] 02 62 37.82.3E 0F 0D 00 06 (00)
Thu 02/25/2016 12:19:26 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 0D 02 (02)
Thu 02/25/2016 12:19:26 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:26 PM : [iNST-TX-I1 ] 02 62 37 82 3E 0F 10 00
Thu 02/25/2016 12:19:26 PM : [iNST-ACK ] 02 62 37.82.3E 0F 10 00 06 ID-REQ (00)
Thu 02/25/2016 12:19:27 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 10 00 ID-REQ (00)
Thu 02/25/2016 12:19:27 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:35 PM : [iNST-TX-I1 ] 02 62 37 82 3E 0F 10 00
Thu 02/25/2016 12:19:35 PM : [iNST-ACK ] 02 62 37.82.3E 0F 10 00 06 ID-REQ (00)
Thu 02/25/2016 12:19:36 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 10 00 ID-REQ (00)
Thu 02/25/2016 12:19:36 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:45 PM : [iNST-TX-I1 ] 02 62 37 82 3E 0F 10 00
Thu 02/25/2016 12:19:45 PM : [iNST-ACK ] 02 62 37.82.3E 0F 10 00 06 ID-REQ (00)
Thu 02/25/2016 12:19:45 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 10 00 ID-REQ (00)
Thu 02/25/2016 12:19:45 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:49 PM : [37 82 3E 0 ] Calibrating engine version
Thu 02/25/2016 12:19:49 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Thu 02/25/2016 12:19:49 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)
Thu 02/25/2016 12:19:50 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00)
Thu 02/25/2016 12:19:50 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:50 PM : [iNST-ERX ] 02 51 37 82 3E 19 6E 0A 11 2F 00 00 01 0F FF 01 E2 01 19 6E 0A 01 00 01 4B
Thu 02/25/2016 12:19:50 PM : [Ext-Direct ] 37.82.3E-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 02/25/2016 12:19:50 PM : [37 82 3E 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)
Thu 02/25/2016 12:19:50 PM : [37 82 3E 1 ] Start : Adding device to ISY
Thu 02/25/2016 12:19:50 PM : [37 82 3E 1 ] Finish : Adding device to ISY was Successful
Thu 02/25/2016 12:19:50 PM : [37 82 3E 1 ] Link 0 : 0FF8 [E201196E0A010001] Saving [E201196E0A010001]
Thu 02/25/2016 12:19:50 PM : [37 82 3E 2 ] Start : Adding device to ISY
Thu 02/25/2016 12:19:50 PM : [37 82 3E 2 ] Finish : Adding device to ISY was Successful
Thu 02/25/2016 12:19:50 PM : [37 82 3E 2 ] Link 1 : 0FF0 [E202196E0A010002] Saving [E202196E0A010002]
Thu 02/25/2016 12:19:50 PM : [37 82 3E 4 ] Start : Adding device to ISY
Thu 02/25/2016 12:19:50 PM : [37 82 3E 4 ] Finish : Adding device to ISY was Successful
Thu 02/25/2016 12:19:50 PM : [37 82 3E 4 ] Link 2 : 0FE8 [E204196E0A010004] Saving [E204196E0A010004]
Thu 02/25/2016 12:19:50 PM : [37 82 3E 0 ] Successfully added device
Thu 02/25/2016 12:19:50 PM : [All ] Writing 24 bytes to devices
Thu 02/25/2016 12:19:50 PM : [37 82 3E 1 ] Link 0 : 0FF8 [E201196E0A010001] Writing [E201196E0A010001]
Thu 02/25/2016 12:19:50 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 02 0F FF 08 E2 01 19 6E 0A 01 00 01 43
Thu 02/25/2016 12:19:50 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 02 0F FF 08 E2 01 19 6E 0A 01 00 01 43 06 (00)
Thu 02/25/2016 12:19:51 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00)
Thu 02/25/2016 12:19:51 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:51 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 37 82 3E 10 08 00 15
Thu 02/25/2016 12:19:51 PM : [PLM ] Group 1 : Writing Responder Link matching [37 82 3E 1 ] Link 0 : 0FF8 [E201196E0A010001]
Thu 02/25/2016 12:19:51 PM : [37 82 3E 1 ] Link 1 : 0FF0 [E202196E0A010002] Writing [E202196E0A010002]
Thu 02/25/2016 12:19:51 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 02 0F F7 08 E2 02 19 6E 0A 01 00 02 49
Thu 02/25/2016 12:19:51 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 02 0F F7 08 E2 02 19 6E 0A 01 00 02 49 06 (00)
Thu 02/25/2016 12:19:52 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00)
Thu 02/25/2016 12:19:52 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:52 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 37 82 3E 10 08 00 06
Thu 02/25/2016 12:19:52 PM : [PLM ] Group 2 : Writing Responder Link matching [37 82 3E 1 ] Link 1 : 0FF0 [E202196E0A010002]
Thu 02/25/2016 12:19:52 PM : [37 82 3E 1 ] Link 2 : 0FE8 [E204196E0A010004] Writing [E204196E0A010004]
Thu 02/25/2016 12:19:52 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 02 0F EF 08 E2 04 19 6E 0A 01 00 04 4D
Thu 02/25/2016 12:19:53 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 02 0F EF 08 E2 04 19 6E 0A 01 00 04 4D 06 (00)
Thu 02/25/2016 12:19:53 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00)
Thu 02/25/2016 12:19:53 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:53 PM : [MNG-LNK-RSP ] 02 6F 41 A2 04 37 82 3E 10 08 00 06
Thu 02/25/2016 12:19:53 PM : [PLM ] Group 4 : Writing Responder Link matching [37 82 3E 1 ] Link 2 : 0FE8 [E204196E0A010004]
Thu 02/25/2016 12:19:53 PM : [37 82 3E 1 ] Link 3 : 0FE0 [0000000000000000] Writing [00..............]
Thu 02/25/2016 12:19:53 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1
Thu 02/25/2016 12:19:54 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00)
Thu 02/25/2016 12:19:54 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00)
Thu 02/25/2016 12:19:54 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:54 PM : [37 82 3E 1 ] Link 4 : 0FD8 : Writing High Water Byte
Thu 02/25/2016 12:19:54 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2
Thu 02/25/2016 12:19:54 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00)
Thu 02/25/2016 12:19:55 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00)
Thu 02/25/2016 12:19:55 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:55 PM : [iNST-ERX ] 02 51 37 82 3E 19 6E 0A 11 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1
Thu 02/25/2016 12:19:55 PM : [Ext-Direct ] 37.82.3E-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 02/25/2016 12:19:55 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2
Thu 02/25/2016 12:19:55 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00)
Thu 02/25/2016 12:19:56 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00)
Thu 02/25/2016 12:19:56 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 02/25/2016 12:19:56 PM : [iNST-ERX ] 02 51 37 82 3E 19 6E 0A 11 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1
Thu 02/25/2016 12:19:56 PM : [Ext-Direct ] 37.82.3E-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 02/25/2016 12:19:56 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9
Thu 02/25/2016 12:19:56 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 06 (00)
Thu 02/25/2016 12:19:57 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00)
Thu 02/25/2016 12:19:57 PM : [std-Direct Ack] 37.82.3E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

 

I don't know how to interpret these logs. Thanks!

[Teken]

Hello Broyd,

 

Can you let us know what firmware and UI is indicated when you select Help -> About?  I ask because earlier ISY firmware may not support later leak sensors.

[Broyd]

Hi Teken, Firmware and UI are both at 4.4.3. Thanks!  

[Teken]

Hi Teken, Firmware and UI are both at 4.4.3. Thanks!  

 

Have you tried adding using the two whirling arrows instead vs using the MAC address method? keeping in mind don't select anything from the drop down list when doing either.