Jump to content

Hidden Door Sensor Heartbeat


hedgehogfrenzy

Recommended Posts

Posted

Call me a rube...but I've searched the entire forum up and down to figure out exactly what the heartbeat function accomplishes and haven't seen a simple explanation. And of course, it's not documented by Smarthome.

 

I know it sends a "I'm here" signal on it's set interval...but what does that do?  I could see where it would be important for a leak sensor...because if it broke and you didn't know, you'd be boned.  

 

But is there anything else it accomplishes other than that?

 

Thanks.

Posted

It lets you know the Hidden Door Sensor battery and device are functional.   Some use the Hidden Door Sensor on a door where usage of door is important to know, particularly a door that is not opened/closed under normal circumstances.  An example is the side door to my garage.  It is rarely used and a door open is important to know.  If battery drops to the point where the device is not operating Heartbeat (or lack of it) is important.  

 

Other doors it makes little difference. 

  • 1 month later...
Posted

Hi all,

 

Sothat is why the Open/Close Sensor's Hearbest is always on, its the same as the Motion Sensor Battery Low which is normally OFF and only goes ON when the battery is low?

 

I have a program set up to notify me if any off my motion sensor's batteries are reporting a low (an ON status). So if I want the same with the Open/Close Sensor, I would just set up the same program but test for an OFF instead of an ON status, since the Heartbeat of the Open/Close Sensor's Heartbeat is in an ON status all the time?

 

Thanks!

 

Rob

Posted

It depends on the Open Close firmware level whether the Heartbeat will be On or Off based on Open Close Status; or always On.

 

It is easiest/best to check for both On and Off

 

If Control 'OpenClose1 Heartbeat' is switched On

Or Control 'OpenClose1 Heartbeat' is switched Off

Then

   Wait 25 hours 

   some action to alert Heartbeat missed
Else

Posted (edited)

It depends on the Open Close firmware level whether the Heartbeat will be On or Off based on Open Close Status; or always On.

 

It is easiest/best to check for both On and Off

 

If Control 'OpenClose1 Heartbeat' is switched On

Or Control 'OpenClose1 Heartbeat' is switched Off

Then

   Wait 25 hours 

   some action to alert Heartbeat missed

Else

why the wait for 25 hours?

 

This is what I wrote to alert me on a battery low condition of the Open/Close Senor:

 

Front Door O-C Sensor Low Battery - [iD 0031][Parent 0017]
 
If

        Status  'Door O-C Sensor-Opened / Door O-C Sensor-Heartbeat' is Off

 

Then

        Repeat Every  24 hours

           Send Notification to 'Email Program Alerts' content 'Email Program Runs'

           Send Notification to 'Text Program Alerts' content 'Text Program Runs'

 

Else

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

 

 
This is what I programmed for the motion sensors battery low alert:
 
Foyer Closet Motion Low Battery - [iD 0028][Parent 0017]
 
If

        Status  'Foyer Closet Motion-Sensor / Foyer Closet Motion-Low Bat' is On

 

Then

        Repeat Every  24 hours

           Send Notification to 'Email Program Alerts' content 'Email Program Runs'

           Send Notification to 'Text Program Alerts' content 'Text Program Runs'

 

Else

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

 

 

​You say I probably should add the test for both On and Off.

 

I'm using a check STATUS. I did this because there is no change that's going to happen because with the model/firmware I have its always showing ON. I guess when the battery goes low it should turn OFF at that point.

 

Which is better to use the STATUS or the CONTROL?

 

Rob

Edited by rlanza1054
Posted

For Heartbeat I would use "If Control".    The Heartbeat check is looking for command flow every 24 hours.  I use 25 to give the device some flexibility in its timing.   If the device only sends Heartbeat On "If Status" does not detect a missing Heartbeat message.    

Posted

As per LeeG above.

 

IOW:  ISY does not know the actual status of anything...only what the last thing it has been told. Some more recent heartbeats never send Off... just On = "I'm alive!"

 

Some device can be queried forcing them to send their status. Otherwise ISY just remembers on the last signal it saw that changed the device's status.

 

If the heartbeat is always an On signal, ISY thinks the status is always On.

 

Think about this one. If the battery goes dead, you didn't expect it to send a signal telling anybody that, did you? :)

I know MS units are supposed to but many are reporting they never do.

I have had three MS batteries go dead without a peep, now.

Posted (edited)

As per LeeG above.

 

IOW:  ISY does not know the actual status of anything...only what the last thing it has been told. Some more recent heartbeats never send Off... just On = "I'm alive!"

 

Some device can be queried forcing them to send their status. Otherwise ISY just remembers on the last signal it saw that changed the device's status.

 

If the heartbeat is always an On signal, ISY thinks the status is always On.

 

Think about this one. If the battery goes dead, you didn't expect it to send a signal telling anybody that, did you? :)

I know MS units are supposed to but many are reporting they never do.

I have had three MS batteries go dead without a peep, now.

The Open/Close Sensor is like the Motion Sensor in that it cannot be Queried.

 

I don't understand this 24 hour thing.

 

I think I need to look at the documentation of Open/Close Sensor and see what it says about what the Hearbeat does and how it works.

 

Rob

 

I've had the Motion Sensors do a battery low, its supposed to send that signal way before the battery dies. You just can't watch for it to change, you need the ISY to do something when it does change. Like send an email. This way you don't miss it.

 

I am curious why some of my Motion Sensors report the Dusk/Dawn status. It seems that about 6pm the Dusk/Dawn Status changes from OFF to ON.  I'm not using the NIGHT mode setting in Options. I don't care about this.

 

But I noticed that most of the Motion Sensors show this, but one or two don't. I don't know why the one or two don't show and have to assume they have a different firmware.

 

Funny, I just checked the manual, there is not one single word referencing the HEARTBEAT?

 

Why would they leave that out completely?

 

I downloaded several versions of the manual, 2843.pdf.  Can someone verify that there isn't anything that talks about the HEARTBEAT?

 

Thanks

 

Rob

 

Update:

 

It seems the Hidden Door Sensor Model 2845 talks about the Heartbeat in the manual. But not one of the different versions of the Open/Close Sensor's manual talk about the Heartbeat.

 

I wonder if the Open/Close Sensor actually contain the Heartbeat at all, if its never mentioned?

 

Maybe that's why people have trouble using it, its not really there?

 

Rob

Edited by rlanza1054
Posted (edited)

Consult the Developer information on 2483-222 for Heartbeat information.  Link to Developer information ....

 

http://www.insteon.com/developer/#devdocs

 

"I don't understand this 24 hour thing."

 

One of the comments from the 2483 guide ....

 

Heartbeat

 

This command is sent about once every 24 hours as a check that the device still has power.

 

I take from this the 24 hour time period is not absolute.   I chose 25 hours.  If the Heartbeat has not been received in 25 hours there is a problem.  My Open Close Sensors with a Heartbeat node send a Heartbeat message,  Your Heartbeat program does not work because it is using If Status.

 

As far as "If Status", for those versions of the Sensor that send only Heartbeat On, If Status will not trigger the Program as the Status does not change, it is always On.  That is why "If Control" must be used for checking Heartbeat.  If Control triggers the Program when the command is received.  Does not matter if it is the same command.

 

This Program works for older Open Close Sensor where Heartbeat can be On or Off.   Also works for newest Sensor where only Heartbeat On is received.

 

HeartbeatOCS1 - [iD 0071][Parent 0001]
 
If
        Control 'OpenClose1-Opened / OpenClose1-Heartbeat' is switched On
     Or Control 'OpenClose1-Opened / OpenClose1-Heartbeat' is switched Off
 
Then
        Wait  25 hours 
        Send X10 'A11/On (3)'
 
Else
   - No Actions - (To add one, press 'Action')
Edited by LeeG
Posted (edited)

The Open/Close Sensor is like the Motion Sensor in that it cannot be Queried.

 

I don't understand this 24 hour thing.

 

I think I need to look at the documentation of Open/Close Sensor and see what it says about what the Hearbeat does and how it works.

 

Rob

 

I've had the Motion Sensors do a battery low, its supposed to send that signal way before the battery dies. You just can't watch for it to change, you need the ISY to do something when it does change. Like send an email. This way you don't miss it.

 

I am curious why some of my Motion Sensors report the Dusk/Dawn status. It seems that about 6pm the Dusk/Dawn Status changes from OFF to ON.  I'm not using the NIGHT mode setting in Options. I don't care about this.

 

But I noticed that most of the Motion Sensors show this, but one or two don't. I don't know why the one or two don't show and have to assume they have a different firmware.

 

Funny, I just checked the manual, there is not one single word referencing the HEARTBEAT?

 

Why would they leave that out completely?

 

I downloaded several versions of the manual, 2843.pdf.  Can someone verify that there isn't anything that talks about the HEARTBEAT?

 

Thanks

 

Rob

 

Update:

 

It seems the Hidden Door Sensor Model 2845 talks about the Heartbeat in the manual. But not one of the different versions of the Open/Close Sensor's manual talk about the Heartbeat.

 

I wonder if the Open/Close Sensor actually contain the Heartbeat at all, if its never mentioned?

 

Maybe that's why people have trouble using it, its not really there?

 

Rob

The MS units and the Leak Sensors have different styles of reporting their health. I assume the Door Sensor is the same as the Leak Sensors.

 

MS Units

------------

Have no heartbeat

Send a low battery signal when a voltage threshold is crossed

Report immediately

You have to be monitoring the signal at the time to know.

If you do not have a LowBatt node, in ISY, for your MS units they are not linked correctly. FACTORY RESET (always) and start over.

 

 

Leak Sensors (and door sensors?)

--------------------

Have an every 24 hour  heartbeat - older units alternate sensing On and Off. Newer units just send On.

Do not send a low battery signal - you assume "long time no hear" = lowbatt.

You have to be monitoring every signal sent and use a timer to know if the next one is late.

Edited by larryllix
  • 5 months later...
Posted

I'm also trying to understand how to use the heartbeat function of the hidden door sensor, and am a bit puzzled by my experience to date. Under the 'Options' for the Heartbeat device, I've set the heartbeat interval to 4 hours. Following the advice (I think) in this thread, I've created the following program:

Heartbeat Checks - [ID 0036][Parent 0001]

If
        (
             Control 'Laundry Room Door - Opened / Laundry Room Door - Heartbeat' is switched On
          Or Control 'Laundry Room Door - Opened / Laundry Room Door - Heartbeat' is switched Off
        )
 
Then
        Send Notification to 'Default' content 'Heartbeat Warning'
 
Else
   - No Actions - (To add one, press 'Action')
 


Approximately every 4 hours (more or less matching the heartbeat interval), I receive an email message stating that the heartbeat was lost. A sample message:

 

From: ISY Alerts <alerts@universal-devices.com>
Subject: Heartbeat Notification - Heartbeat Checks : Laundry Room Door - Heartbeat Off - Alert

The heartbeat in sensor Laundry Room Door - Heartbeat was lost.
Value = 0
Details =      At: 2016/04/11  3:05:59 AM
Program: Heartbeat Checks
Device: Laundry Room Door - Heartbeat (3B B 25 4)
Action: Off
  Value: 4

 

The Action is always 'Off', and the ${alert.subject} is always 'Heartbeat Off - Alert'

Since this happens every 4 hours, and I don't really believe that the heartbeat is being lost that frequently (in fact the programs triggered by the device run flawlessly), I think this is 'just how it works'. That said, since I'm only getting a switch off event, and it comes consistently at the same timing as the heartbeat interval, I don't know how this information is actionable. Should I remove the 'is switched Off' from the if clause and assume that the 'is switched On' event indicates that there is a heartbeat problem? I was thinking of triggering on a status change rather than a switch event, but posts earlier in this thread suggest that 'switch' is preferable to 'status' to indicate lost heartbeat. The alternative is to ignore the heartbeat entirely, and let my family warn me when/if connectivity is lost to this device.

Posted

The Heartbeat Warning customized content:

 

Subject

Heartbeat Notification - ${alert.subject}

 

Body

The heartbeat in sensor ${sys.node.#.name} was lost.

Value = ${sys.node.#.ST}

Details = ${alert.details}

 

In airing this in public, I realize that the 'was lost' statement might not be supported by the evidece, so I've updated the language to state that only a notification was received. That said, the ${alert.subject} always has 'Heartbeat Off', and the 'Action: Off' is always present in the body.

Posted (edited)

I'm also trying to understand how to use the heartbeat function of the hidden door sensor, and am a bit puzzled by my experience to date. Under the 'Options' for the Heartbeat device, I've set the heartbeat interval to 4 hours. Following the advice (I think) in this thread, I've created the following program:

Heartbeat Checks - [ID 0036][Parent 0001]

If
        (
             Control 'Laundry Room Door - Opened / Laundry Room Door - Heartbeat' is switched On
          Or Control 'Laundry Room Door - Opened / Laundry Room Door - Heartbeat' is switched Off
        )
 
Then
        Send Notification to 'Default' content 'Heartbeat Warning'
 
Else
   - No Actions - (To add one, press 'Action')
 


Approximately every 4 hours (more or less matching the heartbeat interval), I receive an email message stating that the heartbeat was lost. A sample message:

 

From: ISY Alerts <alerts@universal-devices.com>

Subject: Heartbeat Notification - Heartbeat Checks : Laundry Room Door - Heartbeat Off - Alert

 

The heartbeat in sensor Laundry Room Door - Heartbeat was lost.

Value = 0

Details =      At: 2016/04/11  3:05:59 AM

Program: Heartbeat Checks

Device: Laundry Room Door - Heartbeat (3B B 25 4)

Action: Off

  Value: 4

 

The Action is always 'Off', and the ${alert.subject} is always 'Heartbeat Off - Alert'

Since this happens every 4 hours, and I don't really believe that the heartbeat is being lost that frequently (in fact the programs triggered by the device run flawlessly), I think this is 'just how it works'. That said, since I'm only getting a switch off event, and it comes consistently at the same timing as the heartbeat interval, I don't know how this information is actionable. Should I remove the 'is switched Off' from the if clause and assume that the 'is switched On' event indicates that there is a heartbeat problem? I was thinking of triggering on a status change rather than a switch event, but posts earlier in this thread suggest that 'switch' is preferable to 'status' to indicate lost heartbeat. The alternative is to ignore the heartbeat entirely, and let my family warn me when/if connectivity is lost to this device.

Think about this as an analogy.

 

You are listening to somebody's heartbeat.

When you hear one you notify somebody that the person's heartbeat is missing.? Not quite making sense?

 

You need to make use of the retriggerable aspect of ISY programs using a WAIT timer.

 

The heartbeats are yelling "I'm alive!, I'm alive"

....so you give the person 5 more hours and if he doesn't yell "I'm alive" again now notify somebody.

Edited by larryllix
Posted

Doh! Now I get it. In my mind I was treating a heartbeat off as an actionable event. Now I understand that the absence of a heartbeat related event is the actionable condition. Somehow it didn't sink in after multiple readings of this thread, so thanks for the additional analogy.

Posted

Doh! Now I get it. In my mind I was treating a heartbeat off as an actionable event. Now I understand that the absence of a heartbeat related event is the actionable condition. Somehow it didn't sink in after multiple readings of this thread, so thanks for the additional analogy.

:)

Posted

It should be noted the heart beat function can also be used as a method to perform a remote update based on the interval set. This obviously only applies to hardware that support it and have the ability to change the heart beat send interval.

 

For the device that do not have a heart beat like the motion sensor you simply need to walk past the FOV and this will wake up the unit and keep it awake long enough to up load the pending writes.

 

Also, not all hardware revisions support the remote device write feature so YMMV.  

 

As noted above some devices report back their heart beat using on vs off so both should be monitored. 

 

Lastly, some hardware require anywhere from 0 - 3 seconds to be inserted into the program to allow the device enough time to complete the remote device write.

 

Using this method for none critical hardware is great as it avoids climbing a 25 foot ladder or moving some huge random object that has access issues.

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

  • Forum Statistics

    • Total Topics
      37.1k
    • Total Posts
      371.7k
×
×
  • Create New...