CoolToys Posted March 18, 2016 Share Posted March 18, 2016 994i Running 4.3.26 UI and Firmware. I have two 2845-222 Hidden Door Sensors. They were working and then after the batteries died one went stupid. I have replaced the batteries, and they both add fine to insteon hub, but not the ISY. The first one "garage door" reloaded and works fine. The second one, "Front Door" doesn't work. The docs for the Insteon Hub are easy, click "Add" and then press button until it adds. For the ISY, I see all kinds of notes about making sure you have the right firmware and it is close to a dual band switch. It is 3' from a dual band switch, and the "garage" is 12'. When I attempt to "auto discover" I get the "Unable to add device" "Unable to determine Insteon Engine" I know I had this issue when I first bought these, and thought I kept notes, but I can't find anything. I recall it being something about adding them as a specific device that isn't a "hidden sensor" and not to use "Automatic discovery", but I have tried all other sensors, same results. Link to comment
Teken Posted March 18, 2016 Share Posted March 18, 2016 I would probably upgrade to 4.4.5 RC firmware and see if it adds fine after that. Please follow all of the required steps as outlined in the 4.4.5 RC thread. Link to comment
LeeG Posted March 18, 2016 Share Posted March 18, 2016 Use New INSTEON Device to add battery device to ISY. Put Hidden Door Sensor into linking mode. Enter Insteon Address, Name of choice, and Auto Discover into New INSTEON Device popup. Link to comment
CoolToys Posted March 18, 2016 Author Share Posted March 18, 2016 Ok so. 1. How to put the hidden door sensor in "linking mode" it isn't in user guide. It shows how to add it as a controller and remove devices it controls. That works fine. 2. Now that I upgraded to 4.4.5 the Garage Sensor quit completely from the 994i. Both still work on Insteon Hub fine. Link to comment
CoolToys Posted March 18, 2016 Author Share Posted March 18, 2016 Found a thread on linking mode. Got it to beep, Still get "Cannot Determine Insteon Engine" Link to comment
LeeG Posted March 18, 2016 Share Posted March 18, 2016 Using an Insteon device outside of ISY (Hub in this case) and with ISY takes a detail knowledge of Insteon. Press and hold Hidden Door Sensor Set button (3-5 seconds) until it beeps. The Status LED will be flashing. Link to comment
LeeG Posted March 18, 2016 Share Posted March 18, 2016 Run Tools | Diagnostics | Event Viewer at LEVEL 3. Run the New INSTEON Device process with Hidden Door Sensor in linking mode. Post the event trace. The Icon on the bottom of event viewer popup, next to last on right side copies event event trace to Clipboard. Paste into forum post. It sounds like the Hidden Door Sensor is not communicating with PLM. Are the two 120 volt legs coupled? Link to comment
CoolToys Posted March 18, 2016 Author Share Posted March 18, 2016 Yes, I got the device to go into linking mode. I can link it to other devices, or to the hub. Not the ISY 994i Both of the sensors that were working, are now not working. I have deleted them and tried to re-add them, and get "Cannot determine Insteon Engine". With Old software, auto detect didn't work and I recall that I had to select a different device to get it to work. Can't find the email I have tried auto detect, and 2845-222 and both give "Cannot determine Insteon Engine" Pretty large system, 24 devices,10 long programs. Don't want to start over. Link to comment
LeeG Posted March 18, 2016 Share Posted March 18, 2016 Click Help | About. What is displayed for Firmware and UI? What devices are coupling the two 120 volt legs? Link to comment
CoolToys Posted March 18, 2016 Author Share Posted March 18, 2016 Thu 03/17/2016 08:57:52 PM : [2B 0 50 ] Added to list of devices to link to ISYThu 03/17/2016 08:57:52 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00Thu 03/17/2016 08:57:52 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00)Thu 03/17/2016 08:58:01 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00Thu 03/17/2016 08:58:01 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00)Thu 03/17/2016 08:58:10 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00Thu 03/17/2016 08:58:10 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00)Thu 03/17/2016 08:58:14 PM : [2B 0 50 0 ] Failed to add device, reason 3Thu 03/17/2016 08:58:14 PM : [All ] Writing 0 bytes to devicesThu 03/17/2016 08:58:44 PM : [ Time] 20:58:54 0(0) Link to comment
LeeG Posted March 18, 2016 Share Posted March 18, 2016 Click Help | About. What is displayed for Firmware and UI? What devices are coupling the two 120 volt legs? Device 2B.00.50 is not responding to three attempts to communicate with device. Link to comment
CoolToys Posted March 18, 2016 Author Share Posted March 18, 2016 There are dual mode controllers on both phases. The system was working just fine before a recent power outage. Now I can manually turn on a program and it works fine. i.e. "night" whch used to come on at sunset +- 21 minutes random after sunset. It did not come on automatically last night or tonight. From the admin console I can control any scene or switch and yet none of the programs are working as they did. Very confusing. I have powered down, re-booted. Hub works fine when I plug it in and use iPhone app to control it. PLM status is "connected". Link to comment
CoolToys Posted March 18, 2016 Author Share Posted March 18, 2016 Re-wrote to the "Garage" 2845-222 and it appears to be working again. Still can't re-write "front door" but I linked a switch to it and it works fine as a controller, just can't connect it to ISY. Link to comment
CoolToys Posted March 18, 2016 Author Share Posted March 18, 2016 Might have figureed it out. 1. link to a switch. 2. "Add links" from switch 3. add device and "remove links" It didn't accept the name, it added it as an address. Link to comment
LeeG Posted March 18, 2016 Share Posted March 18, 2016 That is normal for the ISY. The nodes can be renamed. Here is what the event trace of a New INSTEON Device adding a Hidden Door Sensor. It is from 4.4.5 but there are no changes for a Hidden Door Sensor Fri 03/18/2016 12:30:50 AM : [2b 9 59 ] Added to list of devices to link to ISY Fri 03/18/2016 12:30:50 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 0D 00 Fri 03/18/2016 12:30:50 AM : [iNST-ACK ] 02 62 2B.09.59 0F 0D 00 06 (00) Fri 03/18/2016 12:30:50 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 0D 02 (02) - this is what device should have sent. Fri 03/18/2016 12:30:50 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:30:50 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 10 00 Fri 03/18/2016 12:30:50 AM : [iNST-ACK ] 02 62 2B.09.59 0F 10 00 06 ID-REQ (00) Fri 03/18/2016 12:30:51 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 10 00 ID-REQ (00) Fri 03/18/2016 12:30:51 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:30:51 AM : [iNST-SRX ] 02 50 2B.09.59 10.11.43 83 02 00 (00) Fri 03/18/2016 12:30:51 AM : [std-Broadcast] 2B.09.59-->10.11.43, Max Hops=3, Hops Left=0 Fri 03/18/2016 12:30:52 AM : [2B 9 59 0 ] Calibrating engine version Fri 03/18/2016 12:30:52 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 03/18/2016 12:30:52 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 03/18/2016 12:30:52 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 2F 00 (00) Fri 03/18/2016 12:30:52 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:30:53 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 11 2F 00 00 01 0F FF 01 62 01 1A 84 BB 01 00 01 03 Fri 03/18/2016 12:30:53 AM : [Ext-Direct ] 2B.09.59-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 03/18/2016 12:30:53 AM : [2B 9 59 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Fri 03/18/2016 12:30:53 AM : [2B 9 59 1 ] Start : Adding device to ISY Fri 03/18/2016 12:30:53 AM : [2B 9 59 1 ] Finish : Adding device to ISY was Successful Fri 03/18/2016 12:30:53 AM : [2B 9 59 1 ] Link 0 : 0FF8 [E20122800B010001] Saving [E20122800B010001] Fri 03/18/2016 12:30:53 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Fri 03/18/2016 12:30:53 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Fri 03/18/2016 12:30:55 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 2E 00 (00) Fri 03/18/2016 12:30:55 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:30:56 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 17 2E 00 01 01 05 50 00 FF 40 00 00 00 00 00 00 D2 Fri 03/18/2016 12:30:56 AM : [Ext-Direct ] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:30:56 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 1F 00 Fri 03/18/2016 12:30:56 AM : [iNST-ACK ] 02 62 2B.09.59 0F 1F 00 06 GOF (FLAGS) Fri 03/18/2016 12:30:57 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 1F 05 GOF (05) Fri 03/18/2016 12:30:57 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:30:57 AM : [2B 9 59 3 ] Start : Adding device to ISY Fri 03/18/2016 12:30:57 AM : [2B 9 59 3 ] Finish : Adding device to ISY was Successful Fri 03/18/2016 12:30:57 AM : [2B 9 59 3 ] Link 1 : 0FF0 [E20322800B010003] Saving [E20322800B010003] Fri 03/18/2016 12:30:58 AM : [2B 9 59 4 ] Start : Adding device to ISY Fri 03/18/2016 12:30:58 AM : [2B 9 59 4 ] Finish : Adding device to ISY was Successful Fri 03/18/2016 12:30:58 AM : [2B 9 59 4 ] Link 2 : 0FE8 [E20422800B010004] Saving [E20422800B010004] Fri 03/18/2016 12:31:00 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Fri 03/18/2016 12:31:00 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Fri 03/18/2016 12:31:00 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 2E 00 (00) Fri 03/18/2016 12:31:00 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:00 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 17 2E 00 01 01 05 50 00 FF 40 00 00 00 00 00 00 D2 Fri 03/18/2016 12:31:00 AM : [Ext-Direct ] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:00 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 1F 00 Fri 03/18/2016 12:31:00 AM : [iNST-ACK ] 02 62 2B.09.59 0F 1F 00 06 GOF (FLAGS) Fri 03/18/2016 12:31:00 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 1F 05 GOF (05) Fri 03/18/2016 12:31:00 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:00 AM : [2B 9 59 0 ] Successfully added device Fri 03/18/2016 12:31:00 AM : [All ] Writing 25 bytes to devices Fri 03/18/2016 12:31:01 AM : [2B 9 59 1 ] Link 0 : 0FF8 [E20122800B010001] Writing [E20122800B010001] Fri 03/18/2016 12:31:01 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 02 0F FF 08 E2 01 22 80 0B 01 00 01 27 Fri 03/18/2016 12:31:01 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 02 0F FF 08 E2 01 22 80 0B 01 00 01 27 06 (00) Fri 03/18/2016 12:31:01 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 2F 00 (00) Fri 03/18/2016 12:31:01 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:01 AM : [MNG-LNK-RSP ] 02 6F 41 A2 01 2B 09 59 10 11 43 15 Fri 03/18/2016 12:31:01 AM : [PLM ] Group 1 : Writing Responder Link matching [2B 9 59 1 ] Link 0 : 0FF8 [E20122800B010001] Fri 03/18/2016 12:31:01 AM : [2B 9 59 1 ] Link 1 : 0FF0 [E20322800B010003] Writing [E20322800B010003] Fri 03/18/2016 12:31:01 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 02 0F F7 08 E2 03 22 80 0B 01 00 03 2B Fri 03/18/2016 12:31:02 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 02 0F F7 08 E2 03 22 80 0B 01 00 03 2B 06 (00) Fri 03/18/2016 12:31:03 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 2F 00 (00) Fri 03/18/2016 12:31:03 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:03 AM : [MNG-LNK-RSP ] 02 6F 41 A2 03 2B 09 59 10 11 43 06 Fri 03/18/2016 12:31:03 AM : [PLM ] Group 3 : Writing Responder Link matching [2B 9 59 1 ] Link 1 : 0FF0 [E20322800B010003] Fri 03/18/2016 12:31:03 AM : [2B 9 59 1 ] Link 2 : 0FE8 [E20422800B010004] Writing [E20422800B010004] Fri 03/18/2016 12:31:03 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 02 0F EF 08 E2 04 22 80 0B 01 00 04 31 Fri 03/18/2016 12:31:03 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 02 0F EF 08 E2 04 22 80 0B 01 00 04 31 06 (00) Fri 03/18/2016 12:31:04 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 2F 00 (00) Fri 03/18/2016 12:31:04 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:04 AM : [MNG-LNK-RSP ] 02 6F 41 A2 04 2B 09 59 10 11 43 06 Fri 03/18/2016 12:31:04 AM : [PLM ] Group 4 : Writing Responder Link matching [2B 9 59 1 ] Link 2 : 0FE8 [E20422800B010004] Fri 03/18/2016 12:31:05 AM : [2B 9 59 1 ] Link 3 : 0FE0 [0000000000000000] Writing [00..............] Fri 03/18/2016 12:31:05 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 Fri 03/18/2016 12:31:05 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00) Fri 03/18/2016 12:31:07 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 23 2F 00 (00) Fri 03/18/2016 12:31:07 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 03/18/2016 12:31:07 AM : [2B 9 59 1 ] Link 4 : 0FD8 : Writing High Water Byte Fri 03/18/2016 12:31:07 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 Fri 03/18/2016 12:31:07 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00) Fri 03/18/2016 12:31:09 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 2F 00 (00) Fri 03/18/2016 12:31:09 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:10 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 13 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1 Fri 03/18/2016 12:31:10 AM : [Ext-Direct ] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 03/18/2016 12:31:10 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 Fri 03/18/2016 12:31:10 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00) Fri 03/18/2016 12:31:13 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 11 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1 Fri 03/18/2016 12:31:13 AM : [Ext-Direct ] 2B.09.59-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 03/18/2016 12:31:13 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 Fri 03/18/2016 12:31:13 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 06 (00) Fri 03/18/2016 12:31:14 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 2F 00 (00) Fri 03/18/2016 12:31:14 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:14 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 24 00 Fri 03/18/2016 12:31:14 AM : [iNST-ACK ] 02 62 2B.09.59 0F 24 00 06 (00) Fri 03/18/2016 12:31:15 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 27 24 00 (00) Fri 03/18/2016 12:31:15 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 03/18/2016 12:31:15 AM : [2B 9 59 1 ] Memory : EPROM Refreshed Link to comment
mikeyg01 Posted March 21, 2016 Share Posted March 21, 2016 I have one hidden door sensor and battery life has been dismal.... i have to change the battery every 2-3 week and if very frustrating due to the work I have to do to change and purchasing batteries more often than I expected. I finally got fed up and got a regular open/close sensor for that door. Now i am looking at a wasted sensor every day. Any thoughts on why battery live has been so horrendous and what can I do to make it any better? Thx, Link to comment
Techman Posted March 21, 2016 Share Posted March 21, 2016 I have one hidden door sensor and battery life has been dismal.... i have to change the battery every 2-3 week and if very frustrating due to the work I have to do to change and purchasing batteries more often than I expected. I finally got fed up and got a regular open/close sensor for that door. Now i am looking at a wasted sensor every day. Any thoughts on why battery live has been so horrendous and what can I do to make it any better? Thx, Are you getting low battery signals from the sensor(s) or are the sensors just not working? Have you or can you physically measure the battery voltage on the sensor when it fails? The batteries should last at least 6 months or longer. Link to comment
jerlands Posted March 21, 2016 Share Posted March 21, 2016 I have one hidden door sensor and battery life has been dismal.... i have to change the battery every 2-3 week and if very frustrating due to the work I have to do to change and purchasing batteries more often than I expected. I finally got fed up and got a regular open/close sensor for that door. Now i am looking at a wasted sensor every day. Any thoughts on why battery live has been so horrendous and what can I do to make it any better? Thx, Yes, my hidden door sensor batteries last at least 6 mos. You might review the option settings. I only use 1 node and and heartbeat check is set for 21 hours 15 minutes. I'm sure using LED on, two node or any other messaging will decrease battery life. Jon... Link to comment
mikeyg01 Posted March 21, 2016 Share Posted March 21, 2016 Are you getting low battery signals from the sensor(s) or are the sensors just not working? Have you or can you physically measure the battery voltage on the sensor when it fails? The batteries should last at least 6 months or longer. I am not getting any low battery signal. It just stops working after and when I replace the battery its all good again. I did not measure the battery voltage when it fails. I am going to use it again with the recently installed open/close sensor and do that test. Link to comment
mikeyg01 Posted March 21, 2016 Share Posted March 21, 2016 Yes, my hidden door sensor batteries last at least 6 mos. You might review the option settings. I only use 1 node and and heartbeat check is set for 21 hours 15 minutes. I'm sure using LED on, two node or any other messaging will decrease battery life. Jon, I am not getting the one/two node thing, and I did not know there is a heartbeat setting....let me know more on both please. I will be setting it up again when I go home today....will report back to you guys... Thx, Link to comment
Techman Posted March 21, 2016 Share Posted March 21, 2016 I am not getting any low battery signal. It just stops working after and when I replace the battery its all good again. I did not measure the battery voltage when it fails. I am going to use it again with the recently installed open/close sensor and do that test. It sounds like you may have a communications issue rather than a battery issue. Do you have any dual band devices within close proximity to the sensors? The open close sensor sends out a heartbeat signal every 24 hours. You can write a simple program to monitor the heartbeat node on the open/close sensor and have it send you an email in the event that the heartbeat signal isn't received. Link to comment
jerlands Posted March 21, 2016 Share Posted March 21, 2016 Jon, I am not getting the one/two node thing, and I did not know there is a heartbeat setting....let me know more on both please. I will be setting it up again when I go home today....will report back to you guys... Thx, You can create two nodes for the sensor. group 1 would give an On for open and Off for close, group 2 would give Off for open and On for close. I haven't used this option but I believe it would allow using the sensor as a controller in two scenes. Heartbeat is a security function that allows you to test for communication/operation status and supplements the low battery function. Laundry Notification - [ID 00D6][Parent 00D4] If 'Door Sensors / Laundry / Laundry - Door Sensor / Laundry- Heartbeat' is switched On Or 'Door Sensors / Laundry / Laundry - Door Sensor / Laundry- Heartbeat' is switched Off Then Wait 25 hours Send Notification to 'Jon Cell Phone' Else - No Actions - (To add one, press 'Action') The more options you add to the sensor the higher the battery drain. Jon... Link to comment
Techman Posted March 21, 2016 Share Posted March 21, 2016 The ISY does not support the CLOSED node on the open/close sensor, only the open node and the heartbeat. Link to comment
jerlands Posted March 22, 2016 Share Posted March 22, 2016 The ISY does not support the CLOSED node on the open/close sensor, only the open node and the heartbeat. Shee! You're right about that! I just test a sensor trying to create "Two Node" and thought I killed it Had a hard time getting it to factory reset for some reason? I had thought this option was software specific which indicated to me ISY firmware? Jon... Link to comment
Techman Posted March 22, 2016 Share Posted March 22, 2016 Shee! You're right about that! I just test a sensor trying to create "Two Node" and thought I killed it Had a hard time getting it to factory reset for some reason? I had thought this option was software specific which indicated to me ISY firmware? Jon... Hi Jon, The open node on the ISY will show either on or off so I guess there was really no need for an off node to be supported. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.