smokegrub Posted October 17, 2015 Posted October 17, 2015 I installed a TriggerLinc v.43 in an outbuilding yesterday to assess the status of a door. I was amazed that although the building is about 40 yards from the nearest dual-band device in the house it worked well. However, as compared to Hidden Door Sensors, the nodes in the device tree (opened, closed, heartbeat) do some weird things: 1) The “opened” node displays ON and OFF indicating whether the door is opened or closed; 2) The “closed” node displays nothing; and 3) The “heartbeat” node is always ON. The fact that the “closed” node does nothing isn’t of concern since the “opened” node displays the door status…just weird. My question pertains to the “heartbeat” node. Will this node display OFF when a heartbeat is no longer received from the device? If so, I assume I can use a simple program that assesses the status of the heartbeat and, when it is OFF, notify me.
LeeG Posted October 17, 2015 Posted October 17, 2015 (edited) My v.43 Open Close Sensor (TriggerLinc) always sends a Heartbeat On message. That is one of the differences at v.43. Like all Heartbeat messages, regardless of device type, a Program is required to monitor the Heartbeat node, testing for an On command in this case. I use a Program that checks for both commands so I do not have to care what commands the device sends on Heartbeat message. HeartbeatOCS3 - [iD 0090][Parent 0001] If Control 'OpenClose3-Heartbeat' is switched On Or Control 'OpenClose3-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A11/On (3)' Else - No Actions - (To add one, press 'Action') The Heartbeat message timing can vary by device and battery condition so I Wait for 25 hours before taking an Action that indicates a Heartbeat failure. It sends an X10 message but it is more likely a Notify wil be used by most folks. The above Program logic is used on all the devices that issue a Heartbeat message. A missing Heartbeat message indicates a problem. EDIT: for the benefit of others with earlier versions of the Open Close Sensor, the v.40 Sensor sends a Heartbeat On and Heartbeat Off based on the state of the Closed node (magnet position). Edited October 17, 2015 by LeeG
smokegrub Posted October 17, 2015 Author Posted October 17, 2015 Thanks, Lee. Do you know why the closed node is inactive yet included?
LeeG Posted October 17, 2015 Posted October 17, 2015 The Jumper that normally controls single node (Closed node only) or 2 node (Closed and Open nodes) was removed from the Open Close Sensor at hardware level v1.B which is v.43 firmware. Two node operation is now set with software only as it is with the Hidden Door Sensor. The Hidden Door Sensor has an Options button that brings up a popup where software controlled features are set. The Hidden Door Sensor started out that way. The Open Close Sensor change (removing jumper from PC board) was done after several iterations of the device. The original TriggerLinc and initial versions of the Open Close Sensor have the jumper. My v.40 firmware, v1.9 hardware Open Close Sensors have the jumper which controls single/2 node operation. Eventually I assume the ISY will add an Options button for the v1.B hardware.
smokegrub Posted October 17, 2015 Author Posted October 17, 2015 The Jumper that normally controls single node (Closed node only) or 2 node (Closed and Open nodes) was removed from the Open Close Sensor at hardware level v1.B which is v.43 firmware. Two node operation is now set with software only as it is with the Hidden Door Sensor. The Hidden Door Sensor has an Options button that brings up a popup where software controlled features are set. The Hidden Door Sensor started out that way. The Open Close Sensor change (removing jumper from PC board) was done after several iterations of the device. The original TriggerLinc and initial versions of the Open Close Sensor have the jumper. My v.40 firmware, v1.9 hardware Open Close Sensors have the jumper which controls single/2 node operation. Eventually I assume the ISY will add an Options button for the v1.B hardware. Thanks, Lee.
ggdowski Posted January 1, 2017 Posted January 1, 2017 Old thread, but read it out of curiosity because I have a number of these sensors. So what do folks do with the closed node... it seems like a useless distraction. Do you hide it in a folder labeled "junk not worth looking at"? What do you do?
paulbates Posted January 1, 2017 Posted January 1, 2017 Old thread, but read it out of curiosity because I have a number of these sensors. So what do folks do with the closed node... it seems like a useless distraction. Do you hide it in a folder labeled "junk not worth looking at"? What do you do? Yes, I have a folder sorted to the bottom of the tree. Inside of there, I have a sub folder for battery alerts and a sub folder unused devices in another. Unused Devices includes the complementary sensor nodes, nodes I'm not currently using (eg an io linc where I'm only using the sensor, and also devices i'm not currently using and have disabled but are ready to to go (appliancelincs, etc). Paul
stusviews Posted January 1, 2017 Posted January 1, 2017 Old thread, but read it out of curiosity because I have a number of these sensors. So what do folks do with the closed node... it seems like a useless distraction. Do you hide it in a folder labeled "junk not worth looking at"? What do you do? It's only a useless distraction if you aren't using it
ggdowski Posted January 1, 2017 Posted January 1, 2017 I just did a similar thing and created a folder for "heartbeats" so that they were all easy to find. The problem is that you look at some of these things and they lead you into believing your system isn't functioning right when it is.
Recommended Posts