Leak Sensor Heartbeat and Messaging

[Dean]

I have a couple of leak sensors that do not seem to be behaving well. I'm using the communication programs that have been posted for the leak sensors by Belias, but two sensors constantly report a status of 2, causing the messages to be triggered. When I view them in the ISY Admin Console, both sensors show "Heartbeat - On", just like all of the other leak sensors. Is there something I am missing? I've tried factory reset to no avail. All of my leak sensors are v.43. I've searched through the Forum sections, but can't find a similar problem. If the heartbeat status is ON, why would it say that the Heartbeat was missed?

[Techman]

I have a couple of leak sensors that do not seem to be behaving well. I'm using the communication programs that have been posted for the leak sensors by Belias, but two sensors constantly report a status of 2, causing the messages to be triggered. When I view them in the ISY Admin Console, both sensors show "Heartbeat - On", just like all of the other leak sensors. Is there something I am missing? I've tried factory reset to no avail. All of my leak sensors are v.43. I've searched through the Forum sections, but can't find a similar problem. If the heartbeat status is ON, why would it say that the Heartbeat was missed?

It's possible that there's a  communications issue with the leak sensor.  Being that they usually sit down low the RF signal may not be reaching a dual band device.

Try plugging in a range extender, on/off module, or a lamplinc module close to the sensor to see if that resolves the problem.

 

The heartbeat status will usually show as on in the ISY and is not a indication that your heartbeat signal is always being received

[Teken]

Login to the Admin Console: Programs -> Summary -> Variable Control 2 for those leak sensors. What is the last run / last finish time recorded in the summary log?

 

If the logs show they haven't changed for example 2-3 days or what ever. It could mean the sensor is too far from a RF to power line device or the battery is low. Even though the batteries have been spec'd for 10 years of service Smartlabs has indicated a few batches released in the wild came with less than fresh batteries.

 

1. Measure battery voltage for both units ensuring they are with in specs.

2. Verify your Insteon RF to Powerline mesh is adequate in those areas.

[Dean]

It's possible that there's a  communications issue with the leak sensor.  Being that they usually sit down low the RF signal may not be reaching a dual band device.

Try plugging in a range extender, on/off module, or a lamplinc module close to the sensor to see if that resolves the problem.

 

The heartbeat status will usually show as on in the ISY and is not a indication that your heartbeat signal is always being received

Yes, I found that in one of the Forum posts and actually picked up the leak sensors, switched to new batteries and placed them on my desk. I have at least 50-75 devices in my system, so "something" should be nearby for it to pick up a signal. I also tried the factory reset, etc.

Edit: I have an RF 2 wire switch right behind my desk, but will also try plugging in a lamplinc module near the desk.

[Dean]

Login to the Admin Console: Programs -> Summary -> Variable Control 2 for those leak sensors. What is the last run / last finish time recorded in the summary log?

 

If the logs show they haven't changed for example 2-3 days or what ever. It could mean the sensor is too far from a RF to power line device or the battery is low. Even though the batteries have been spec'd for 10 years of service Smartlabs has indicated a few batches released in the wild came with less than fresh batteries.

 

1. Measure battery voltage for both units ensuring they are with in specs.

2. Verify your Insteon RF to Powerline mesh is adequate in those areas.

I'm showing a last run time of 2:09 pm on 6/3/2016 on both sensors, give or take a few seconds. That means it hasn't run in in over 10 days. Both summaries show a status of "True". Regarding the communication, see the last post where I mentioned that I moved both sensors to my desk. Also, I replaced both batteries with new batteries that showed full charge.

[Michel Kohanim]

Hi Dean,

 

Are you using Status or Control?

 

With kind regards,

Michel

[Dean]

Hi Dean,

 

Are you using Status or Control?

 

With kind regards,

Michel

All of the "Variable Control 2" programs use "Control". I'm using the programs from Belias. Here's what I have.

AC-Variable Control 2 - [iD 00E7][Parent 0082]

 

If

        Control 'Sensors - Leak / Leak-AC-Dry / Leak-AC-Wet' is switched On

     Or Control 'Sensors - Leak / Leak-AC-Dry / Leak-AC-Wet' is switched Off

 

Then

        $s_LeakAC  = 1

        Wait  25 hours and 10 seconds

        $s_LeakAC  = 2

 

Else

   - No Actions - (To add one, press 'Action')

[Teken]

Hello Dean,

 

Lets keep this simple and do the following when your able to do so.

 

1. Reboot the controller and validate they return to a status 1. If it does your code is solid - if not you need to review.

 

2. Manually change the value from 2 to 1. Press the set button on one sensor and toggle it from wet to dry. The system should reflect the two states. The device will also send a heart beat to the controller.

 

Verify that all of the above come in as expected if not you have a communication issue, device needs to be hard reset, removed, added, or defective product.

[Dean]

Hello Dean,

 

Lets keep this simple and do the following when your able to do so.

 

1. Reboot the controller and validate they return to a status 1. If it does your code is solid - if not you need to review.

 

2. Manually change the value from 2 to 1. Press the set button on one sensor and toggle it from wet to dry. The system should reflect the two states. The device will also send a heart beat to the controller.

 

Verify that all of the above come in as expected if not you have a communication issue, device needs to be hard reset, removed, added, or defective product.

1. Done, no problems.

2. Change the variable value back to 1, but pressing the set button to toggle from wet to dry did not change the state in the Admin console. Dry stayed on and wet stayed off. Heartbeat still shows on. 

3. I've tried a hard reset, but have not tried to remove and re add back. I will try that later today.

Thanks for your guidance. BTW, all code for each sensor (I have 10) is identical and these are the only 2 that are not playing well with others.

[Teken]

1. Done, no problems.

2. Change the variable value back to 1, but pressing the set button to toggle from wet to dry did not change the state in the Admin console. Dry stayed on and wet stayed off. Heartbeat still shows on. 

3. I've tried a hard reset, but have not tried to remove and re add back. I will try that later today.

Thanks for your guidance. BTW, all code for each sensor (I have 10) is identical and these are the only 2 that are not playing well with others.

 

Hello Dean,

 

Before you go through the whole ordeal of hard resetting the one sensor. Please bring it next to a Insteon dual band device and perform step 2.

 

If the Admin Console does not reflect the correct state you can hard reset the unit per the full users manual. As a reminder once you hard reset the leak sensor you need to do a restore device so all the links are associated to the program(s) you have at hand.

 

Should the above steps not resolve the issue - I would press forward and initiate a RMA via cross dock with Smarthome. They are very good about in warranty returns so keep us all updated to the outcome.  

[LeeG]

Dean

 

Be careful about the firmware level in the Leak Sensor.

 

My v.43 Leak Sensor does not cycle between Dry On/ Dry Off with each set button press.

 

My v.3E Leak Sensor does cycle Dry On, Dry Off.

[Dean]

Dean

 

Be careful about the firmware level in the Leak Sensor.

 

My v.43 Leak Sensor does not cycle between Dry On/ Dry Off with each set button press.

 

My v.3E Leak Sensor does cycle Dry On, Dry Off.

All of my leak sensors are v.43. I tried to toggle on another sensor and it didn't toggle either.

 

You know, I just noticed that one of my leak sensors is showing Dry - On, Wet - On and Heartbeat - Off. I tried a hard reset and it stayed the same. I'm struggling to understand how I would ever be confident enough to install a whole house cutoff valve. I can't see how these would not be communicating, given the number of devices that I have and also a couple of access points to make sure that I had bridged the two phases.

[Teken]

All of my leak sensors are v.43. I tried to toggle on another sensor and it didn't toggle either.

 

In that case you will need to place the device in a dish of water. Once it trips you should see it reflected in the Admin Console for wet on, when you wipe it dry and press the set button it should go back to dry on.

 

Please confirm that behavior is seen . . .

[Dean]

In that case you will need to place the device in a dish of water. Once it trips you should see it reflected in the Admin Console for wet on, when you wipe it dry and press the set button it should go back to dry on.

 

Please confirm that behavior is seen . . .

Placed it into water and it immediately switched to Wet-On and sent the appropriate text message. I dried it, then pressed the set switch and it returned to Dry-On.

[Dean]

Placed it into water and it immediately switched to Wet-On and sent the appropriate text message. I dried it, then pressed the set switch and it returned to Dry-On.

By the way, I tried placing the leak sensor that showed Dry-On and Wet-On at the same time into the water. It immediately switched Dry to Off and sent the appropriate text message. When I dried it off and pressed the set button, it toggled back to Dry-On, but Wet stayed in the off position. So, the Wet-On is there all the time. 

Sign me - "Puzzled in Atlanta"

[Teken]

Placed it into water and it immediately switched to Wet-On and sent the appropriate text message. I dried it, then pressed the set switch and it returned to Dry-On.

 

Now, if you watch the Admin Console do those two problem leak sensors (variables) change state as expected?

[Teken]

By the way, I tried placing the leak sensor that showed Dry-On and Wet-On at the same time into the water. It immediately switched Dry to Off and sent the appropriate text message. When I dried it off and pressed the set button, it toggled back to Dry-On, but Wet stayed in the off position. So, the Wet-On is there all the time. 

Sign me - "Puzzled in Atlanta"

 

Smartlabs changed the behavior in the latest firmware where the end user *must* press the set button to make the unit send out the dry on command.

 

There is a use case (like / dislike) for this new behavior vs the old . . .

 

I personally don't mind either so long as you know how the sensor is going to react and what the person needs to do in the future moving forward.

[Dean]

Now, if you watch the Admin Console do those two problem leak sensors (variables) change state as expected?

Yes, the variables changed appropriately in the Admin Console when I placed it into the water and then when I dried it off and pressed the set button. Text messages performed correctly, as well.

 

Also, the leak sensor that showed both Dry and Wet On at the same time . . . I deleted it and added it back in. That fixed the issue with that sensor, as it now shows Dry-On and Wet-Off. It also passed the water test.

[Teken]

Yes, the variables changed appropriately in the Admin Console when I placed it into the water and then when I dried it off and pressed the set button. Text messages performed correctly, as well.

 

Also, the leak sensor that showed both Dry and Wet On at the same time . . . I deleted it and added it back in. That fixed the issue with that sensor, as it now shows Dry-On and Wet-Off. It also passed the water test.

 

Well, it looks like your in good shape now - Rock On . . .

[larryllix]

Smartlabs changed the behavior in the latest firmware where the end user *must* press the set button to make the unit send out the dry on command.

 

There is a use case (like / dislike) for this new behavior vs the old . . .

 

I personally don't mind either so long as you know how the sensor is going to react and what the person needs to do in the future moving forward.

I have four of these Leak sensors.

 

The two newer units are tap length sensitive.

IIRC a long tap sends Wet On, Dry off, and a short tap sends Wet Off, Dry On. or maybe verse visa?

 

This caused me a lot of confusion when testing.

[Dean]

Well, it looks like your in good shape now - Rock On . . .

I'll wait the 26 hours (or so) and see if the message goes away regarding the heartbeat. If not, I think I will delete those two and add them back. Thanks again for all the help!

[Teken]

I'll wait the 26 hours (or so) and see if the message goes away regarding the heartbeat. If not, I think I will delete those two and add them back. Thanks again for all the help!

 

For the benefit of others could you please indicate the production date, revision, and ISY firmware for this unit. This information will help others in the future and provide context when they compare their hardware / behavior.

 

Let us know if the 26 hour heart beat test pasts . . .

[Dean]

For the benefit of others could you please indicate the production date, revision, and ISY firmware for this unit. This information will help others in the future and provide context when they compare their hardware / behavior.

 

Let us know if the 26 hour heart beat test pasts . . .

So, after the 26 hours, it went back to displaying the same behavior, so I'm back to square one. I have to think these two are defective. I don't see a production date, but the revision is 4714REV2.3.

[Teken]

So, after the 26 hours, it went back to displaying the same behavior, so I'm back to square one. I have to think these two are defective. I don't see a production date, but the revision is 4714REV2.3.

 

Your device was produced on the 47th week of 2014 and is revision 2.3 of the hardware. When looking at the ISY Admin Console for the device it will list the firmware for the leak sensor and recall you said it was v.43.

 

Lets try a few simple things and reply back what you observe, OK?

 

1. Take one of the bad sensors while viewing the admin console place it in a dish of water. Does it change state for both wet and dry?

 

Yes / No?

 

If it changes state I want you to carefully look at the green LED on the top of the unit. Is it blinking every XX seconds or is kind of fluttering / flickering?

 

2. Taking the unit out of water dry the unit and press the set button. Does the status change in the admin console at this point?

 

Yes / No?

 

3. I am going to assume your office is no where near the final placement is, correct? If so I want you to do the same two tests listed above (at the final location) and go back to the admin console and report back if the signal is received and reflected in the admin console.

 

If it is this generally means RF is fine - if it doesn't you need to add in another plug in dual band device near the leak sensor.

[Dean]

Your device was produced on the 47th week of 2014 and is revision 2.3 of the hardware. When looking at the ISY Admin Console for the device it will list the firmware for the leak sensor and recall you said it was v.43.

 

Lets try a few simple things and reply back what you observe, OK?

 

1. Take one of the bad sensors while viewing the admin console place it in a dish of water. Does it change state for both wet and dry?

 

Yes / No?

 

If it changes state I want you to carefully look at the green LED on the top of the unit. Is it blinking every XX seconds or is kind of fluttering / flickering?

 

2. Taking the unit out of water dry the unit and press the set button. Does the status change in the admin console at this point?

 

Yes / No?

 

3. I am going to assume your office is no where near the final placement is, correct? If so I want you to do the same two tests listed above (at the final location) and go back to the admin console and report back if the signal is received and reflected in the admin console.

 

If it is this generally means RF is fine - if it doesn't you need to add in another plug in dual band device near the leak sensor.

1. Yes, it did change state, going from Dry-on to Dry-off, etc. It blinked every XX seconds. No fluttering.

2. Pressing the set button did cause the status to change back to Dry-On, etc.

3. Here's where it gets kind of strange. I placed the leak detector in the same dish in water underneath the sink at the bar. That's about 20 feet from my office. (always convenient to have a bar near the office, but I digress) When I placed it in the water, the status did not change in the console, but I did immediately get the text message telling me there was a leak detected at that location. I then took the sensor out from under the bar and sat it on the cabinet and repeated the test. Status changed in the console and the text message came, When I dried and reset the leak sensor, it behaved correctly.

 

That being said, I have an access point plugged into the wall not 5 feet from the bar sink. Of course, there is a dishwasher and and refrigerator in its path of direct sight from the access point to the sensor underneath the bar. I also have the paceyben Somfy bridge in the outlet just above the sink, although I don't know if that relays a signal. I'm going to leave it on the top of the cabinet for the 26 hours and see what happens, unless you have another suggestion. Thanks again for all your help!