MikeD Posted March 20, 2014 Posted March 20, 2014 Shannong, Have you tried this? It really is only curiosity anyway. This does nothing for the low battery notification claim. I had thought this would also show up with something like the 2842-222 Motion Sensor that has a Low Battery node. Wonder if it is just not implemented into the ISY release? ~Mike
shannong Posted March 20, 2014 Posted March 20, 2014 I haven't tried it. I was only basing my response on the program presented. The next daily state update if it exists will be sent sometime between now and 24 hours. That will cause "Then" to execute which starts with a 25 hour wait. Hence, you'll need to wait somewhere between 24 (really 25) and 48 hours depending on where in the cycle you're currently sitting. Not sure if there are other nodes not implemented by ISY. Note that documentation says http://status updates are sent every 24 hours which I interpret to mean an unnecessary and unsolicited "on" of "off" message that would look identical to the last original on/off message. That's not the same as a heartbeat. An unsolicited on/off message wouldn't need and couldn't use an additional heartbeat node. There would need to be a unique "heartbeat' message for that.
Xathros Posted March 20, 2014 Posted March 20, 2014 This program is assuming there is no heartbeat and using the normal on/off of the one standard node with a countdown timer. Assuming this door is normally opened or closed at least once a day, this should suffice. If not, there will be a notification after 25hrs of no activity at that door. I am doing something like this with the Triggerlincs on my doors. Some of my timers are much longer than 25 hours however as two of the doors are used infrequently. In the 6 or so months that I have had this set up this way, I have yet to receive a notification. Not sure how long a battery lasts in a Triggerlinc but I'm certainly not burning through them. -Xathros
MikeD Posted March 20, 2014 Posted March 20, 2014 Right, I toggled the sensor and my program status is Running 'Then' with a Last Run Time of 'Thu 2014/03/20 02:01:12 PM' I will check that time tomorrow about this time of day and see if it has changed. ~Mike
Brian H Posted March 20, 2014 Author Posted March 20, 2014 How many nodes are showing for the 2845-222?
shannong Posted March 20, 2014 Posted March 20, 2014 Mine response was all speculation assuming the documentation Mike presented was accurate. Adjust Heartbeat IntervalCustomize the duration of time between sensor check-ins; by default, the sensor will broadcast it’s state once every 24 hours. He doesn't have his installed in a door yet so the only reason there would be an on/off would be that it was indeed broadcasting its current state. Mine are installed in interior doors that are used mostly everyday so it's hard for me to check the logs to validate if there is such a message. I only use these Insteon door sensors for when I want lights to turn on/off with the door, since a local direct links between devices is so much faster (near instant) than programs and commands from the ISY after learning about a state change. Beyond those three, I use my Elk w/ Honeywell wireless integrated to my ISY. They have the 5800micra sensor that is totally hidden, years of battery life (so they say), and only 5 dollars more. I let ISY learn about door states from the Elk.
shannong Posted March 20, 2014 Posted March 20, 2014 How many nodes are showing for the 2845-222? The default is one node which either shows an "Off" or "On" status. You can put it in two-node-mode such that there is an "On" node and an "Off" node. I use two-node for a door that I purposely leave open sometimes and that has a light linked to it.
shannong Posted March 20, 2014 Posted March 20, 2014 My logs which can be downloaded from the ISY go back about 6 weeks. I was able to find gaps of two and three days where no messages were received from my door sensors. Therefore, I would conclude no heartbeat or regular status update of any kind.
Xathros Posted March 20, 2014 Posted March 20, 2014 I believe the ISY would only log activity from nodes that it is familier with. If there are unsupported heartbeat and battery low nodes, I don't believe the ISY would not log any activity from those. -Xathros
shannong Posted March 20, 2014 Posted March 20, 2014 Agreed for heartbeat. Status update would simply be an additional On/Off message which isn't seen either.
MikeD Posted March 20, 2014 Posted March 20, 2014 If it would give any insight, here is the Event Viewer Level 3 trace when I added the 2845-222 Hidden Door Sensor: Thu 03/20/2014 10:51:52 AM : [2B F 3 ] Added to list of devices to link to ISY Thu 03/20/2014 10:51:52 AM : [iNST-TX-I1 ] 02 62 2B 0F 03 0F 0D 00 Thu 03/20/2014 10:51:52 AM : [iNST-ACK ] 02 62 2B.0F.03 0F 0D 00 06 (00) Thu 03/20/2014 10:51:52 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 0D 02 (02) Thu 03/20/2014 10:51:52 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:52 AM : [iNST-TX-I1 ] 02 62 2B 0F 03 0F 10 00 Thu 03/20/2014 10:51:53 AM : [iNST-ACK ] 02 62 2B.0F.03 0F 10 00 06 ID-REQ (00) Thu 03/20/2014 10:51:53 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 10 00 ID-REQ (00) Thu 03/20/2014 10:51:53 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:53 AM : [iNST-SRX ] 02 50 2B.0F.03 10.11.43 8B 02 00 (00) Thu 03/20/2014 10:51:53 AM : [std-Broadcast] 2B.0F.03-->10.11.43, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:53 AM : [2B F 3 0 ] Calibrating engine version Thu 03/20/2014 10:51:53 AM : [iNST-TX-I2CS] 02 62 2B 0F 03 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 03/20/2014 10:51:53 AM : [iNST-ACK ] 02 62 2B.0F.03 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 03/20/2014 10:51:54 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 2F 00 (00) Thu 03/20/2014 10:51:54 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:54 AM : [iNST-ERX ] 02 51 2B 0F 03 1E 46 77 11 2F 00 00 01 0F FF 01 E2 01 1E 46 77 01 00 01 01 Thu 03/20/2014 10:51:54 AM : [Ext-Direct ] 2B.0F.03-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Thu 03/20/2014 10:51:54 AM : [2B F 3 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Thu 03/20/2014 10:51:54 AM : [2B F 3 1 ] Start : Adding device to ISY Thu 03/20/2014 10:51:54 AM : [2B F 3 1 ] Finish : Adding device to ISY was Successful Thu 03/20/2014 10:51:54 AM : [2B F 3 1 ] Link 0 : 0FF8 [E2011E4677010001] Saving [E2011E4677010001] Thu 03/20/2014 10:51:54 AM : [iNST-TX-I1 ] 02 62 2B 0F 03 0F 1F 00 Thu 03/20/2014 10:51:54 AM : [iNST-ACK ] 02 62 2B.0F.03 0F 1F 00 06 GOF (FLAGS) Thu 03/20/2014 10:51:55 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 1F 01 GOF (DB-DELTA) Thu 03/20/2014 10:51:55 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:55 AM : [iNST-TX-I1 ] 02 62 2B 0F 03 0F 1F 00 Thu 03/20/2014 10:51:55 AM : [iNST-ACK ] 02 62 2B.0F.03 0F 1F 00 06 GOF (FLAGS) Thu 03/20/2014 10:51:55 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 1F 01 GOF (DB-DELTA) Thu 03/20/2014 10:51:55 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:55 AM : [2B F 3 0 ] Successfully added device Thu 03/20/2014 10:51:55 AM : [All ] Writing 8 bytes to devices Thu 03/20/2014 10:51:56 AM : [2B F 3 1 ] Link 0 : 0FF8 [E2011E4677010001] Writing [E2011E4677010001] Thu 03/20/2014 10:51:56 AM : [iNST-TX-I2CS] 02 62 2B 0F 03 1F 2F 00 00 02 0F FF 08 E2 01 1E 46 77 01 00 01 F9 Thu 03/20/2014 10:51:56 AM : [iNST-ACK ] 02 62 2B.0F.03 1F 2F 00 00 02 0F FF 08 E2 01 1E 46 77 01 00 01 F9 06 (00) Thu 03/20/2014 10:51:56 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 2F 00 (00) Thu 03/20/2014 10:51:56 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:56 AM : [MNG-LNK-RSP ] 02 6F 41 A2 01 2B 0F 03 10 11 43 15 Thu 03/20/2014 10:51:56 AM : [PLM ] Group 1 : Writing Responder Link matching [2B F 3 1 ] Link 0 : 0FF8 [E2011E4677010001] Thu 03/20/2014 10:51:56 AM : [2B F 3 1 ] Link 1 : 0FF0 [0000000000000000] Writing [00..............] Thu 03/20/2014 10:51:56 AM : [iNST-TX-I2CS] 02 62 2B 0F 03 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 Thu 03/20/2014 10:51:57 AM : [iNST-ACK ] 02 62 2B.0F.03 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 06 (00) Thu 03/20/2014 10:51:57 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 2F 00 (00) Thu 03/20/2014 10:51:57 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:57 AM : [2B F 3 1 ] Link 2 : 0FE8 : Writing High Water Byte Thu 03/20/2014 10:51:57 AM : [iNST-TX-I2CS] 02 62 2B 0F 03 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Thu 03/20/2014 10:51:57 AM : [iNST-ACK ] 02 62 2B.0F.03 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Thu 03/20/2014 10:51:58 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 2F 00 (00) Thu 03/20/2014 10:51:58 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:58 AM : [iNST-ERX ] 02 51 2B 0F 03 1E 46 77 11 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Thu 03/20/2014 10:51:58 AM : [Ext-Direct ] 2B.0F.03-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Thu 03/20/2014 10:51:58 AM : [iNST-TX-I2CS] 02 62 2B 0F 03 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Thu 03/20/2014 10:51:58 AM : [iNST-ACK ] 02 62 2B.0F.03 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Thu 03/20/2014 10:51:59 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 2F 00 (00) Thu 03/20/2014 10:51:59 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/20/2014 10:51:59 AM : [iNST-ERX ] 02 51 2B 0F 03 1E 46 77 11 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Thu 03/20/2014 10:51:59 AM : [Ext-Direct ] 2B.0F.03-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Thu 03/20/2014 10:51:59 AM : [iNST-TX-I2CS] 02 62 2B 0F 03 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Thu 03/20/2014 10:51:59 AM : [iNST-ACK ] 02 62 2B.0F.03 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Thu 03/20/2014 10:52:00 AM : [iNST-SRX ] 02 50 2B.0F.03 1E.46.77 2B 2F 00 (00) Thu 03/20/2014 10:52:00 AM : [std-Direct Ack] 2B.0F.03-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 ~Mike
Brian H Posted March 20, 2014 Author Posted March 20, 2014 The Heartbeat and Low Battery functions would have their own group numbers. I didn't see them being added in your Event Viewer Log. If I read the Developers Notes they gave us in the Developers Group Forums correctly.
MikeD Posted March 20, 2014 Posted March 20, 2014 I sent an email to UDI support asking the question. ~Mike
Brian H Posted March 20, 2014 Author Posted March 20, 2014 Will be interesting to see the information they answer with.
MikeD Posted March 21, 2014 Posted March 21, 2014 Got a quick reply from Michel. Here is his response: "We are currently having issues with Hidden Door Sensor as some of them are reporting as TriggerLinc. Once that's resolved, then we can figure out which versions support heartbeat. " It may be that the one I have reports itself as stated above. I purchased it just after they were released but never added it to my ISY until today. Today is the last day of Smarthome's sale so I just ordered three more. I will see how they appear when I add them to My system. ~Mike
Vince Posted March 21, 2014 Posted March 21, 2014 So does this mean the door sensor cannot be added to ISY right now?
Michel Kohanim Posted March 21, 2014 Posted March 21, 2014 Hi Vince, They can be added by they report as TriggerLinc and ISY thinks they are TriggerLinc but they behave like a hidden door sensor. They used be different and behave differently but sometime along the way SmartHome decided to use the same category/subcategory for both. With kind regards, Michel
shannong Posted March 21, 2014 Posted March 21, 2014 I bought mine in Dec and added to ISY then. ISY reports the version as v.92. When I get home I'll yank one to see what's printed on it. They report as Door Sensors and work as expected but then I wasn't expecting a heartbeat. I didn't notice that in the documentation when I installed them. Since I only use them on interior doors for lighting and basic things such as that it doesn't bother me too much. However, it does bother me that SmartLabs has taken such an approach with these sensors.
Vince Posted March 21, 2014 Posted March 21, 2014 So, Michel, I have tried to "add an insteon device" by typing in the device number but I get an error message. My PLM is duel band model 2413S. What am I doing wrong? Thanks.
MikeD Posted March 21, 2014 Posted March 21, 2014 I also purchased my sensor in Dec, the label reads '5013 V 1.1' ISY reports Door Sensor v.43, attached is a screen shot. ~Mike
MikeD Posted March 21, 2014 Posted March 21, 2014 So, Michel, I have tried to "add an insteon device" by typing in the device number but I get an error message. My PLM is duel band model 2413S. What am I doing wrong? Thanks. Vince, What firmware are you running? I was at v4.0.5 and could not add the Door Sensor even though it showed up in the list. It installed with no problems once I upgraded to v4.1.2 Beta. ~Mike
MikeD Posted March 21, 2014 Posted March 21, 2014 Hi Vince, The Hidden Door Sensor did not exist back in v3.3.10. Are you running an ISY99? If so you will need to upgrade to the ISY994 with v4.1.0 or later firmware to use the 2845-222 Hidden Door Sensor. ~Mike
Vince Posted March 21, 2014 Posted March 21, 2014 I appreciate the answer, Mike. Michel, can you confirm this?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.