larryllix Posted June 2, 2015 Share Posted June 2, 2015 This is the usual style heartbeat used elsewhere. Think of the heartbeat this way. "I'm alive".... "I'm alive".... "I'm alive".... "I'm alive".... I just hope my heartbeat never goes off but just beats, beats, beats, also. To monitor the health your heartbeat program (ISY already does it) but... OK lesson in most database programme basics - In the Admin Console - select Program tab - select the sub-Tab "summary" or right click on the very top "My programs" and select "status" - in the database chart of your programs click on the title "Last Run" You will probably see a chunk of blank entries at the top of this column - click the "Last Run" title gain to re-sort the column in descending order - find your heartbeat program in the left and second columns and view the last time ISY received a heartbeat from your device. - also if it shows true and running then... your ISY is again watching out for you and making your life easier! Link to comment
Techman Posted June 2, 2015 Author Share Posted June 2, 2015 - In the Admin Console - select Program tab - select the sub-Tab "summary" or right click on the very top "My programs" and select "status" - in the database chart of your programs click on the title "Last Run" You will probably see a chunk of blank entries at the top of this column - click the "Last Run" title gain to re-sort the column in descending order - find your heartbeat program in the left and second columns and view the last time ISY received a heartbeat from your device. - also if it shows true and running then... Thank you. What's interesting is that the heartbeat node signal doesn't always show up in the ISY log. I have a handful of devices that send out heartbeats but for some unknown reason they're not recorded. I was looking through the log when I tried to trouble shoot the open/close sensor. It appears that the sensor is working correctly. I had been searching for the off signal which is no longer sent in the current firmware release and assumed it was a bug. Link to comment
LeeG Posted June 3, 2015 Share Posted June 3, 2015 Heartbeat On received at 06:51 PM. Will Leave Open Close Sensor Open to see what the v1.9 generates for command at Wed Heartbeat. The ISY Log will show the Heartbeat message status (On or Off) only if the value is different from the last Heartbeat Log entry. The ISY Log does not show repeated On or repeated Off commands. Link to comment
bipto Posted June 3, 2015 Share Posted June 3, 2015 Heartbeat On received at 06:51 PM. Will Leave Open Close Sensor Open to see what the v1.9 generates for command at Wed Heartbeat. The ISY Log will show the Heartbeat message status (On or Off) only if the value is different from the last Heartbeat Log entry. The ISY Log does not show repeated On or repeated Off commands. Ok, so I guess I'm back to my initial befuddlement... If the battery dies in a sensor monitoring a door that is rarely opened / closed, how will we know..? Link to comment
Teken Posted June 3, 2015 Share Posted June 3, 2015 If we are using the leak sensor monitoring program I would expect a 2 to show up. Ideals are peaceful - History is violent Link to comment
LeeG Posted June 3, 2015 Share Posted June 3, 2015 bipto The Heartbeat message is still there at v1.B according to what Smarthome told Techman. Of course this is not the same information UDI was told. I have 2 v1.B Open Close sensors coming from Smarthome. I'll run the same Heartbeat Program logic using one of the new Open Close Sensors and see what actually happens. Link to comment
Techman Posted June 3, 2015 Author Share Posted June 3, 2015 I now have a program that will email me each time the on heartbeat signal is sent. My log currently shows one heartbeat "ON" status. Based on LeeG's explanation the log is of no further value for trouble shooting. I also have a second program that will email me if a heartbeat signal is not received at least once every 25 hours. Once I know communication is reliable I'll disable the first program and rely on the second to monitor battery and communication status. The downside is that you could go a full 25 hours before you realize you have a problem. It's most frustrating that Smarthome does not make their release notes public. As Teken mentioned there are now three different versions of this sensor, all different. Even more frustrating is the fact that the manuals are incomplete. Link to comment
Teken Posted June 3, 2015 Share Posted June 3, 2015 I now have a program that will email me each time the on heartbeat signal is sent. My log currently shows one heartbeat "ON" status. Based on LeeG's explanation the log is of no further value for trouble shooting. I also have a second program that will email me if a heartbeat signal is not received at least once every 25 hours. Once I know communication is reliable I'll disable the first program and rely on the second to monitor battery and communication status. The downside is that you could go a full 25 hours before you realize you have a problem. It's most frustrating that Smarthome does not make their release notes public. As Teken mentioned there are now three different versions of this sensor, all different. Even more frustrating is the fact that the manuals are incomplete. Add to the frustration is the removal of the jumper pin. I am hoping UDI was able to determine what the software code was to allow those changes via a soft option. Link to comment
Techman Posted June 3, 2015 Author Share Posted June 3, 2015 Add to the frustration is the removal of the jumper pin. I am hoping UDI was able to determine what the software code was to allow those changes via a soft option. You should be able to work around that issue with a program. Link to comment
Teken Posted June 3, 2015 Share Posted June 3, 2015 You should be able to work around that issue with a program. A program will not help when you need the dual mode option. Unless you mean something else? Link to comment
larryllix Posted June 3, 2015 Share Posted June 3, 2015 Ok, so I guess I'm back to my initial befuddlement... If the battery dies in a sensor monitoring a door that is rarely opened / closed, how will we know..? Your ISY heartbeat monitoring program will send you a notification. The heartbeat is a spare node transmitted to your ISY and not dependant on the door sensor operating. When the heartbeat stops the timer in the program times out and notifies you. Link to comment
G W Posted June 3, 2015 Share Posted June 3, 2015 Ok, so I guess I'm back to my initial befuddlement... If the battery dies in a sensor monitoring a door that is rarely opened / closed, how will we know..?You won't get a heartbeat within the last 25 hours. Link to comment
LeeG Posted June 3, 2015 Share Posted June 3, 2015 My v1.9 Open Close Sensor Heartbeat tonight sent an ON command just like last night because I left the Open Close Sensor Open. Wed 06/03/2015 06:42:13 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.04 CB 11 04 LTONRR (04) - 0X11 On command from Heartbeat node Wed 06/03/2015 06:42:13 PM : [std-Group ] 31.C1.1D-->Group=4, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:42:13 PM : [D2D EVENT ] Event [31 C1 1D 4] [DON] [4] uom=0 prec=-1 Wed 06/03/2015 06:42:13 PM : [ 31 C1 1D 4] DON 4 Wed 06/03/2015 06:42:13 PM : [D2D-CMP 0071] CTL [31 C1 1D 4] DON op=1 Event(val=4 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 06/03/2015 06:42:13 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.04 CB 11 04 LTONRR (04) Wed 06/03/2015 06:42:13 PM : [std-Group ] 31.C1.1D-->Group=4, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:42:13 PM : [iNST-DUP ] Previous message ignored. Wed 06/03/2015 06:42:13 PM : [iNST-SRX ] 02 50 31.C1.1D 22.80.0B 41 11 04 LTONRR (04) Wed 06/03/2015 06:42:13 PM : [std-Cleanup ] 31.C1.1D-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Wed 06/03/2015 06:42:13 PM : [iNST-DUP ] Previous message ignored. Wed 06/03/2015 06:42:14 PM : [iNST-SRX ] 02 50 31.C1.1D 11.01.04 CB 06 00 (00) Wed 06/03/2015 06:42:14 PM : [std-Group ] 31.C1.1D-->11.01.04, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:42:14 PM : [iNST-INFO ] Previous message ignored. Wed 06/03/2015 06:42:14 PM : [iNST-SRX ] 02 50 31.C1.1D 11.01.04 CB 06 00 (00) Wed 06/03/2015 06:42:14 PM : [std-Group ] 31.C1.1D-->11.01.04, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:42:14 PM : [iNST-INFO ] Previous message ignored. Wed 06/03/2015 06:52:13 PM : [ Time] 18:52:15 16(0) I set the Open Close Sensor to Closed after Heartbeat On message to test Heartbeat command sent tomorrow night. I'm expecting an Off command to match Open Close Sensor state Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.01 CB 13 01 LTOFFRR(01) Wed 06/03/2015 06:56:34 PM : [std-Group ] 31.C1.1D-->Group=1, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:56:34 PM : [D2D EVENT ] Event [31 C1 1D 1] [DOF] [1] uom=0 prec=-1 Wed 06/03/2015 06:56:34 PM : [ 31 C1 1D 1] DOF 1 Wed 06/03/2015 06:56:34 PM : [D2D EVENT ] Event [31 C1 1D 1] [sT] [0] uom=0 prec=-1 Wed 06/03/2015 06:56:34 PM : [ 31 C1 1D 1] ST 0 Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.01 CB 13 01 LTOFFRR(01) Wed 06/03/2015 06:56:34 PM : [std-Group ] 31.C1.1D-->Group=1, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:56:34 PM : [iNST-DUP ] Previous message ignored. Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 22.80.0B 41 13 01 LTOFFRR(01) Wed 06/03/2015 06:56:34 PM : [std-Cleanup ] 31.C1.1D-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Wed 06/03/2015 06:56:34 PM : [iNST-DUP ] Previous message ignored. Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 13.01.01 CB 06 00 (00) Wed 06/03/2015 06:56:34 PM : [std-Group ] 31.C1.1D-->13.01.01, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:56:34 PM : [iNST-INFO ] Previous message ignored. Link to comment
Techman Posted June 4, 2015 Author Share Posted June 4, 2015 I'm still testing the current firmware release, so I don't have anything to report yet. . The status of the contacts on the sensor shouldn't have an effect on the heartbeat node. The heartbeat should report regardless of the state of the open/close node. Link to comment
larryllix Posted June 4, 2015 Share Posted June 4, 2015 My v1.9 Open Close Sensor Heartbeat tonight sent an ON command just like last night because I left the Open Close Sensor Open. Wed 06/03/2015 06:42:13 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.04 CB 11 04 LTONRR (04) - 0X11 On command from Heartbeat node .... Wed 06/03/2015 06:52:13 PM : [ Time] 18:52:15 16(0) I set the Open Close Sensor to Closed after Heartbeat On message to test Heartbeat command sent tomorrow night. I'm expecting an Off command to match Open Close Sensor state Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.01 CB 13 01 LTOFFRR(01) .... Wed 06/03/2015 06:56:34 PM : [iNST-INFO ] Previous message ignored. Very interesting. I don't know why they wouldn't have gone full protocol on the open or closed node and copy the style what other protocols have done. One signal that is updated on status change but a resend every x hour/minutes as a heartbeat. Wait! I think I just figured out why not. Simple HA would get triggered and not be able to sort out whether the status changed. ...Of course, ISY could do it because it has variables that could remember the last known status and react accordingly sorting out whether the door was just operated or it was just a heartbeat. Link to comment
LeeG Posted June 6, 2015 Share Posted June 6, 2015 My new V1.B hardware Open Close Sensor under test. Will update as test results obtained. Link to comment
Techman Posted June 6, 2015 Author Share Posted June 6, 2015 My new V1.B hardware Open Close Sensor under test. Will update as test results obtained I'm not getting a heartbeat signal, how about you? Link to comment
LeeG Posted June 6, 2015 Share Posted June 6, 2015 I did get a Heartbeat when I installed the v1.B, with an On command even though the Open Close Sensor was closed. May have been when I pressed the Set button as it was powered for only a few minutes. Sending an On command seemed consistent with what had been posted. It will be another 5 hours +/- before getting the 24 hour Heartbeat message. The Open Close Sensor is near a Dual Band device so I am expecting to see the heartbeat message if the device generates one. Program is HeartbeatOCS3 Link to comment
Techman Posted June 6, 2015 Author Share Posted June 6, 2015 I also got a heatbeat "on" signal the first time I inserted the battery. That was the last time I got one. I have good communication as the "open" node works flawlessly. UPDATE: I just got a hearbeat "ON" signal. Unfortunately I was playing with the magnet just about the same time as the heartbeat arrived so I don't know if that had a bearing on anything. Guess I have to wait another 24 hours to see what happens. Link to comment
LeeG Posted June 7, 2015 Share Posted June 7, 2015 The v1.B Open Close Sensor sent Heartbeat On message, Group 4, On command. Sat 06/06/2015 07:25:00 PM : [ Time] 19:25:00 1(0) Sat 06/06/2015 07:29:36 PM : [ Time] 19:29:39 1(0) Sat 06/06/2015 07:39:36 PM : [ Time] 19:39:39 1(0) Sat 06/06/2015 07:40:35 PM : [ Time] 19:40:38 1(0) Sat 06/06/2015 07:50:35 PM : [ Time] 19:50:38 1(0) Sat 06/06/2015 07:53:03 PM : [iNST-SRX ] 02 50 36.ED.98 00.00.04 CB 11 04 LTONRR (04) Sat 06/06/2015 07:53:03 PM : [std-Group ] 36.ED.98-->Group=4, Max Hops=3, Hops Left=2 Sat 06/06/2015 07:53:03 PM : [D2D EVENT ] Event [36 ED 98 4] [DON] [4] uom=0 prec=-1 Sat 06/06/2015 07:53:03 PM : [ 36 ED 98 4] DON 4 Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 00.00.04 CB 11 04 LTONRR (04) Sat 06/06/2015 07:53:04 PM : [std-Group ] 36.ED.98-->Group=4, Max Hops=3, Hops Left=2 Sat 06/06/2015 07:53:04 PM : [iNST-DUP ] Previous message ignored. Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 22.80.0B 41 11 04 LTONRR (04) Sat 06/06/2015 07:53:04 PM : [std-Cleanup ] 36.ED.98-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Sat 06/06/2015 07:53:04 PM : [iNST-DUP ] Previous message ignored. Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 11.01.04 CB 06 00 (00) Sat 06/06/2015 07:53:04 PM : [std-Group ] 36.ED.98-->11.01.04, Max Hops=3, Hops Left=2 Sat 06/06/2015 07:53:04 PM : [iNST-INFO ] Previous message ignored. Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 11.01.04 C3 06 00 (00) Sat 06/06/2015 07:53:04 PM : [std-Group ] 36.ED.98-->11.01.04, Max Hops=3, Hops Left=0 Sat 06/06/2015 07:53:04 PM : [iNST-INFO ] Previous message ignored. Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 11.01.04 C3 06 00 (00) Sat 06/06/2015 07:53:04 PM : [std-Group ] 36.ED.98-->11.01.04, Max Hops=3, Hops Left=0 Sat 06/06/2015 07:53:04 PM : [iNST-INFO ] Previous message ignored. Sat 06/06/2015 07:55:35 PM : [ Time] 19:55:39 1(0) Sat 06/06/2015 07:59:59 PM : [ Time] 20:00:00 1(0) Sat 06/06/2015 08:09:59 PM : [ Time] 20:09:59 1(0) Sat 06/06/2015 08:12:47 PM : [iNST-SRX ] 02 50 2C.71.C2 00.00.04 CB 11 04 LTONRR (04) Sat 06/06/2015 08:12:47 PM : [std-Group ] 2C.71.C2-->Group=4, Max Hops=3, Hops Left=2 Sat 06/06/2015 08:12:47 PM : [D2D EVENT ] Event [2C 71 C2 4] [DON] [4] uom=0 prec=-1 Sat 06/06/2015 08:12:47 PM : [ 2C 71 C2 4] DON 4 Sat 06/06/2015 08:12:47 PM : [iNST-SRX ] 02 50 2C.71.C2 00.00.04 CB 11 04 LTONRR (04) Sat 06/06/2015 08:12:47 PM : [std-Group ] 2C.71.C2-->Group=4, Max Hops=3, Hops Left=2 Sat 06/06/2015 08:12:47 PM : [iNST-DUP ] Previous message ignored. Sat 06/06/2015 08:12:47 PM : [iNST-SRX ] 02 50 2C.71.C2 22.80.0B 41 11 04 LTONRR (04) Sat 06/06/2015 08:12:47 PM : [std-Cleanup ] 2C.71.C2-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Sat 06/06/2015 08:12:47 PM : [iNST-DUP ] Previous message ignored. Sat 06/06/2015 08:12:48 PM : [iNST-SRX ] 02 50 2C.71.C2 11.01.04 CB 06 00 (00) Sat 06/06/2015 08:12:48 PM : [std-Group ] 2C.71.C2-->11.01.04, Max Hops=3, Hops Left=2 Sat 06/06/2015 08:12:48 PM : [iNST-INFO ] Previous message ignored. Sat 06/06/2015 08:12:48 PM : [iNST-SRX ] 02 50 2C.71.C2 11.01.04 CB 06 00 (00) Sat 06/06/2015 08:12:48 PM : [std-Group ] 2C.71.C2-->11.01.04, Max Hops=3, Hops Left=2 Sat 06/06/2015 08:12:48 PM : [iNST-INFO ] Previous message ignored. Link to comment
Techman Posted June 7, 2015 Author Share Posted June 7, 2015 The v1.B Open Close Sensor sent Heartbeat On message, Group 4, On command. That's good news. Let me know what you get tomorrow. Did your sensor also install as a 2421 triggerlinc? Does your "closed" node populate? Link to comment
LeeG Posted June 7, 2015 Share Posted June 7, 2015 I'll post what happens tomorrow evening as that will be a more normal 24 hour period. It adds as a 2421 TriggerLinc. Firmware is v.43 Closed node does not populate. The documentation for the v1.B indicates the Closed node is now controlled/activated by software since the Jumper no longer exists. This will require some new function by the ISY. Link to comment
Techman Posted June 8, 2015 Author Share Posted June 8, 2015 I'll post what happens tomorrow evening as that will be a more normal 24 hour period. It adds as a 2421 TriggerLinc. Firmware is v.43 Closed node does not populate. The documentation for the v1.B indicates the Closed node is now controlled/activated by software since the Jumper no longer exists. This will require some new function by the ISY. I just got a heartbeat signal, 25 hours and 15 minutes after the last one. I guess we just need a way to access the Closed node via the ISY. Link to comment
LeeG Posted June 8, 2015 Share Posted June 8, 2015 The next Heartbeat On message came approx 23 hours 50 minutes after last Heartbeat message. I had done some testing with the magnet position and pressed the Set button a few times during that testing. This last Heartbeat message came nominally 24 hours after last Heartbeat message generated with Set button. It had an On command even though Open Close Sensor was now Open. Want to see one more Heartbeat message but feel certain it will be 24 hours (23 hours 50 minutes) after this last Heartbeat On message. This is so much better than dropping Heartbeat message at hardware v1.B. Link to comment
Techman Posted June 8, 2015 Author Share Posted June 8, 2015 I had also been playing with the sensor contacts. Today I'll leave it alone and just monitor the heartbeat. Seems the heartbeat only sends an "ON" signal and the state of the contacts has no bearing. I had problem with my SD card in the ISY which may have interfered with the previous heartbeats. I cleaned the contacts on the card and reinserted it. The ISY is now functioning normally. Prior to reseating the card I had trouble accessing the ISY and I had a few programs that got corrupted. In retrospect I guess we really don't need software access to the "closed" node. That node could theoretically be removed from the ISY. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.