Insteon Open/Close Sensor 2843 Heartbeat missing

[PeterF]

I have reason to believe that the currently shipping Insteon Open/Close Sensor 2843 no longer has a Heartbeat signal.  Either that or I have 4 recently purchased defective sensors, or who knows what else might be going on.

 

I have 10 Open/Close Sensors (2843-222), 6 of them are REV 1.B installed a couple years ago, and 4 are REV 2.1 installed recently. 

 

On the ISY 994i, when I look at the Administrative Console Main tab, all of the REV 1.B have the Current State of the Heartbeat node showing "On" at all times, while all of the REV 2.1 show “Off”.  I’m using a program to constantly monitor each of them.  The REV 1.B sensors respond every 24 hours with a Heartbeat signal.  The REV 2.1 sensors never respond.

 

Thoughts anyone?

[larryllix]

On 12/20/2018 at 10:05 AM, PeterF said:

I have reason to believe that the currently shipping Insteon Open/Close Sensor 2843 no longer has a Heartbeat signal.  Either that or I have 4 recently purchased defective sensors, or who knows what else might be going on.

 

I have 10 Open/Close Sensors (2843-222), 6 of them are REV 1.B installed a couple years ago, and 4 are REV 2.1 installed recently. 

 

On the ISY 994i, when I look at the Administrative Console Main tab, all of the REV 1.B have the Current State of the Heartbeat node showing "On" at all times, while all of the REV 2.1 show “Off”.  I’m using a program to constantly monitor each of them.  The REV 1.B sensors respond every 24 hours with a Heartbeat signal.  The REV 2.1 sensors never respond.

 

Thoughts anyone?

They may have changed the codes sent.
So some devices only send on. You cannot use status in those cases. Control/switched is the only logic that can detect the same signal as there is no change in status.

Sent from my SM-G930W8 using Tapatalk
 

[JSEmso]

I am having the same problem with 2 new Insteon Open/Close Sensors.  UDI is current researching this but has not yet determined the cause.  Will provide an update if they do.

[kfrazack]

I have a newly purchased (from Amazon) 2843-222 rev 3.0 and the heartbeat status is simply blank. No on or off. Am I missing something?

[larryllix]

1 hour ago, kfrazack said:

I have a newly purchased (from Amazon) 2843-222 rev 3.0 and the heartbeat status is simply blank. No on or off. Am I missing something?

Until the device tells ISY something there will be no status shown. Leak detectors only send a heartbeat once every 24 hours and then it is only On each time so they never register Off status.

[kfrazack]

Larry thanks for clarifying.

[larryllix]

6 hours ago, kfrazack said:

Larry thanks for clarifying.

I forgot the follow up information.

To detect a heartbeat that only ever sends "On" a status based trigger cannot work. You would require "switched" to detect the signal, since the status would not change after the first time.
Also, since some heartbeats may send alternating On/Off signals, we typically include both so we don't care what it sends.

If
    XXXXX is switched ON
    OR
    XXXX is switched OFF
Then
     Wait heartbeat period less about 10%
     Do heartbeat failed things
Else
    ------

[Techman]

This is the program I use to monitor the heartbeat signals. If it doesn't detect a heartbeat within 27 hours then it runs a program that sends me an email. Note that this program is enabled at Startup.

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

 Sensor Heartbeat Fail Monitor - [ID 0094][Parent 0092][Run At Startup]

If
       Control 'Screen Door Opened / Screen Door Heartbeat' is not switched On
     Or Control 'Screen Door Opened / Screen Door Heartbeat' is not switched Off
 Then
        Wait  27 hours
        Run Program 'Screen Door Sensor Heartbeat Fail' (Then Path)
 Else
   - No Actions - (To add one, press 'Action')
 

 

[larryllix]

10 hours ago, Techman said:

This is the program I use to monitor the heartbeat signals. If it doesn't detect a heartbeat within 27 hours then it runs a program that sends me an email. Note that this program is enabled at Startup.

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

 Sensor Heartbeat Fail Monitor - [ID 0094][Parent 0092][Run At Startup]

If
       Control 'Screen Door Opened / Screen Door Heartbeat' is not switched On
     Or Control 'Screen Door Opened / Screen Door Heartbeat' is not switched Off
 Then
        Wait  27 hours
        Run Program 'Screen Door Sensor Heartbeat Fail' (Then Path)
 Else
   - No Actions - (To add one, press 'Action')
 

 

Your program has no triggers that run Then. "Not switched" only runs Else.

Checked the icon status of this program to see if Then is actually running.

[Techman]

If the device is NOT switched on or if it's NOT switched off then the IF clause becomes TRUE which then starts the 27 hour timer.

If the heartbeat signal is received then the IF clause becomes FALSE.

When my batteries fail I always get the email.

[Techman]

If the ISY reboots then the IF clause will run, and evaluate as true,  which starts the timer.

When you first create the program you have to manually run the IF clause to start the timer loop. 

I used this programming approach to avoid multiple programs.

 

.

 

[larryllix]

35 minutes ago, Techman said:

If the ISY reboots then the IF clause will run, and evaluate as true,  which starts the timer.

When you first create the program you have to manually run the IF clause to start the timer loop. 

I used this programming approach to avoid multiple programs.

 

Well, I was absolutely wrong on this one!! It does work. I confess, I had to test it for myself before realising how it works.
Each trigger line depend on the other line to be True during either trigger event. Trouble is the logic is convoluted using all negative states and it makes it hard to understand but....
….It is ingenious and it works with "Enable run at startup" !
 

If
    device is switched On
   OR
    device is switched Off

a simpler logic, works as well, but will not self start with the "Enable run on startup" option.

Thanks for your persistence and patience! I learned something new today!!!! Well done!  

[Techman]

In answer to PeteF  as I recall some of the sensors sent an off heartbeat signal and some sent an on heartbeat signal so you have to cover all the bases. If you include those options in your programs the heartbeat signal should be detected.

The problem with Smartlabs is that they have a propensity to change their firmware without providing the release notes. The earlier sensors were called triggerlincs and the current sensors are called open/close sensors. Basically the same product with a few minor hardware and firmware modifications.

[breischaft]

Thank you for putting this information out.  very helpful. 

 

[Derek Atkins]

I am running the program that @Techman suggested above (although I changed the 27 to 26).  I've got 10 sensors currently deployed:

* 5 Open/Close sensors (2421 TriggerLinc v.43)
* 3 Hidden Door Sensors (2845-222 v.47)
* 2 Leak Sensors (2852-222 v.44)

I started the programs running yesterday, and 4 out of 10 have failed to see a heartbeat in 26 hours.  Specifically, all 3 hidden door sensors have failed, and one of the open/close (triggerlinc) has failed.  There is a dual-band device located within 5 feet of each of the 3 hidden door sensors, although I do admit that the failed open/close sensor is further from a dual-band, but only like 15 feet.   All the other 6 sensors have received a heartbeat in the past 24 hours (which I can tell because the Last Finish Time == Last Run Time).

Any ideas how to debug this?  The sensor open status definitely works on all the devices.

Strangely, the ISY says that the hidden door sensors have heartbeats configured at 5 minutes.  I tried to change it to 21 hours, but then when I quit and restart the ISY Admin Console it reverted back to 5 minutes.  If I try to uncheck the LED option, it says to turn the device into communication mode (which it did not do when trying to change the heartbeat config).  Even more fun, right now all three sensors read 5min.  If I change ONE to 21h, then all three read 21h!   Strange, huh?

 

[btwinc]

I'm new to the hidden door sensors. Just bought my first 2. Just like Derik above, I am having the exact same communication issues. I'm unable to change heartbeat value, not receiving heartbeats and getting a communication error when I try to update the sensor. The device is 5 feet away from my PLM. My ISY994i is getting open/close (On/Off) status from the door sensor just fine. I did link it as as a hidden door sensor. I uninstalled it, performed the factory reset and re linked it. Same issue. I suppose I should open the second box and try that one, but it feels like I am missing something in configuration. 

Any thoughts?

 

[Techman]

Did you put the sensor into the linking mode before you tried to update it?

What version of the ISY firmware and UI are you running?

 

[btwinc]

Well, it took many 27 hour intervals to figure this all out. Just now getting up to speed on Hidden Door sensors. Duh, they can't hear the ISY until they're in linking mode.

Thanks Techman, the heartbeat program is not something I could have come up with on my own. It works brilliantly. My thinking is more IN the box.

Does the low battery status work? Should I build a routine to look for that as well?

Now that I have this working on 2 doors, Smarthome has sold out on these sensors.

[PhanTomiZ]

This is an easy way to change the setting of all battery operated device that is not easily accessible. 

I have a separate program for each device.  They are all disabled until I need to update that device.  When an update is needed, I will enable the specific program for that device.  When it is updated, I disable that program once again.  

This program (below) will change the setting of a battery operated device without having to physically access the device and put it in linking mode.  All that is needed is to activate the device.  (open/close a door or when a leak sensor is involved, use the heartbeat.  Of course you'll have to wait 24 hours for the HB, but it beats having to crawl under appliances and such).

Depending on network traffic, you may have to adjust the wait time up or down.

I took this simple idea a step further and use a program to force that program to disable after a 25 hour period so it's not constantly writing device updates.  The 25 hour period will catch the leak sensors.

 

 

Open/Close Sensor Garage Door Write Updates - [ID 01F9][Parent 01D1]

If
        Control 'Garage / Garage Door Lock / Devices / Garage Side Door-Opened' is switched On
     Or Control 'Garage / Garage Door Lock / Devices / Garage Side Door-Opened' is switched Off
     Or Control 'Garage / Garage Door Lock / Devices / Garage Side Door-Opened / Garage Side Door-Closed' is switched On
     Or Control 'Garage / Garage Door Lock / Devices / Garage Side Door-Opened / Garage Side Door-Closed' is switched Off
 
Then
        Wait  3 seconds
        Set 'Garage / Garage Door Lock / Devices / Garage Side Door-Opened' Write Device Updates
        Send Notification to 'Default' content 'Default Subject'
 
Else
   - No Actions - (To add one, press 'Action')
 

PhanTomiZ