jerlands Posted February 25, 2016 Share Posted February 25, 2016 I don't really know but am gonna guess here Looks to me your heartbeat node isn't being written correctly. Thu 02/25/2016 12:19:53 PM : [PLM ] Group 4 : Writing Responder Link matching [37 82 3E 1 ] Link 2 : 0FE8 [E204196E0A010004]Thu 02/25/2016 12:19:53 PM : [37 82 3E 1 ] Link 3 : 0FE0 [0000000000000000] Writing [00..............]Thu 02/25/2016 12:19:53 PM : [iNST-TX-I2CS] 02 62 37 82 3E 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1Thu 02/25/2016 12:19:54 PM : [iNST-ACK ] 02 62 37.82.3E 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00)Thu 02/25/2016 12:19:54 PM : [iNST-SRX ] 02 50 37.82.3E 19.6E.0A 2B 2F 00 (00) Edit: apparently this is normal response for this node. don't really understand that though I would move the sensor 4-6 feet from the PLM and try again. I've noticed with battery operated devices being too close to dual-band device can cause problems. Jon... Link to comment Share on other sites More sharing options...
Broyd Posted February 25, 2016 Share Posted February 25, 2016 I tried the "whirling arrows" button; put the sensor in linking mode, pressed finish, and the popup instantly went away. Nothing happened ... Link to comment Share on other sites More sharing options...
Teken Posted February 25, 2016 Author Share Posted February 25, 2016 I tried the "whirling arrows" button; put the sensor in linking mode, pressed finish, and the popup instantly went away. Nothing happened ... Hrmm, and what happens when you use the other option of add device and simply enter the MAC address and leave the default settings in place? Link to comment Share on other sites More sharing options...
Broyd Posted February 25, 2016 Share Posted February 25, 2016 See post 72. It fails to add, Cannot determine engine type. Thu 02/25/2016 12:18:36 PM : [37 82 3E 0 ] Cannot determine device typeThu 02/25/2016 12:18:36 PM : [37 82 3E 0 ] Failed to add device, reason 2 Link to comment Share on other sites More sharing options...
Teken Posted February 25, 2016 Author Share Posted February 25, 2016 If you haven't done so yet reboot the controller and try again. Ensure the Leak Sensor is about 5-10 feet away from a dual band device or the PLM. Link to comment Share on other sites More sharing options...
Broyd Posted February 25, 2016 Share Posted February 25, 2016 Just grabbing a quick lunch. I will reboot next and then try the other 3 sensors I have. And a motion sensor. Link to comment Share on other sites More sharing options...
Broyd Posted February 25, 2016 Share Posted February 25, 2016 I have rebooted and power recycled the ISY and PLM. No change to the version number on the leak sensor AND all of the 3 other leak sensor show v.00 as the version number. ALSO I added a motion sensor and it shows v.00 for the version number. Suggesting that no RF devices are showing the correct version number? Wired or plugin devices show the version number OK when added... ????? I have added the original leak sensor I started with and will wait to see if I get a heartbeat from it tomorrow. In the meantime, does the v.00 I'm getting from RF devices suggest anything? Thanks! Broyd. Link to comment Share on other sites More sharing options...
Teken Posted February 25, 2016 Author Share Posted February 25, 2016 I have rebooted and power recycled the ISY and PLM. No change to the version number on the leak sensor AND all of the 3 other leak sensor show v.00 as the version number. ALSO I added a motion sensor and it shows v.00 for the version number. Suggesting that no RF devices are showing the correct version number? Wired or plugin devices show the version number OK when added... ????? I have added the original leak sensor I started with and will wait to see if I get a heartbeat from it tomorrow. In the meantime, does the v.00 I'm getting from RF devices suggest anything? Thanks! Broyd. Hello Broyd, I really don't know what to say to be honest. As stated earlier much older ISY firmware never queried the Insteon devices correctly and hence the v.00. It never impacted the device from operating correctly at all. I would suggest you submit a service request to have UDI determine root cause and report back to the group: http://www.universal-devices.com/contact-support/ Please ensure you link this thread so they can mark it resolved once they have completed all their tasks. Link to comment Share on other sites More sharing options...
jerlands Posted February 26, 2016 Share Posted February 26, 2016 I have rebooted and power recycled the ISY and PLM. No change to the version number on the leak sensor AND all of the 3 other leak sensor show v.00 as the version number. ALSO I added a motion sensor and it shows v.00 for the version number. Suggesting that no RF devices are showing the correct version number? Wired or plugin devices show the version number OK when added... ????? I have added the original leak sensor I started with and will wait to see if I get a heartbeat from it tomorrow. In the meantime, does the v.00 I'm getting from RF devices suggest anything? Thanks! Broyd. Do you have a lot of RF devices nearby the area you're linking in? Your comms look good (Hops=2) but a lot of crosstalk I believe can cause problems. You might play with placement of devices, moving them in different directions from the PLM and also maybe experimenting with distances (5-10ft) until you get one to link properly. Another helpful tip is to factory reset device before each attempt and keeping event viewer open to level 3 allows you to observe events. Jon... Link to comment Share on other sites More sharing options...
Broyd Posted February 26, 2016 Share Posted February 26, 2016 Hi Teken, I'll look into that. I want to wait to see if I get a heartbeat from that device tomorrow afternoon. Hi Jon, YES I do have a lot of RF devices in that area. I can temporarily eliminate all of them. I'll work on this step next but it will have to wait until tomorrow. One other thing, I had to select the device type for all leak sensor and the motion sensor. This does bother me a bit. I don't recall having to do that when I put in my first leak detectors or motion sensor. ... Con' t Link to comment Share on other sites More sharing options...
Broyd Posted February 26, 2016 Share Posted February 26, 2016 OK! Problem solved Years ago I had purchased a ISY-99i and the PLM that came with it was : 2413S V1.5 1122 19.6E.0A The PLM that came with my ISY-994i was: 2413S V1.B 1317 23.97.D2 I had recapped the old PLM and drilled the case full of holes hoping to stem the PLM 2 year failure and I was using this old unit. I have not yet recapped the newer one but that is my next priority! Anyway using the older PLM, I got v.00 with all RF devices AND to add any of them, I had to enter the device address AND select the device type. The newer PLM works fine. @Jon: even though I have many RF devices very near the place I was doing the linking, there no interference accomplishing linking new devices. Thanks Jon and Teken for all your time and suggestions! Very much appreciated Link to comment Share on other sites More sharing options...
Teken Posted February 26, 2016 Author Share Posted February 26, 2016 OK! Problem solved Years ago I had purchased a ISY-99i and the PLM that came with it was : 2314S V1.5 1122 19.6E.0A The PLM that came with my ISY-994i was: 2314S V1.B 1317 23.97.D2 I had recapped the old PLM and drilled the case full of holes hoping to stem the PLM 2 year failure and I was using this old unit. I have not yet recapped the newer one but that is my next priority! Anyway using the older PLM, I got v.00 with all RF devices AND to add any of them, I had to enter the device address AND select the device type. The newer PLM works fine. @Jon: even though I have many RF devices very near the place I was doing the linking, there no interference accomplishing linking new devices. Thanks Jon and Teken for all your time and suggestions! Very much appreciated Hello Broyd, I gather you meant to say the older 99 Series Controller came with a 2412S Single Band PLM? Where as the 994 Series Controller came with a dual band 2413S PLM, no? Link to comment Share on other sites More sharing options...
Broyd Posted February 26, 2016 Share Posted February 26, 2016 Hi Teken, No! That older unit is also a dual band 2413S. Link to comment Share on other sites More sharing options...
Teken Posted February 26, 2016 Author Share Posted February 26, 2016 Hi Teken, No! That older unit is also a dual band 2413S. For the benefit of others reading could you offer the hardware revision and production date. If you have the ISY firmware for this 2413S PLM that gave you the v.00 issue that would also be great. Link to comment Share on other sites More sharing options...
Broyd Posted February 26, 2016 Share Posted February 26, 2016 Hi Teken. I'll do that. The newer PLM that works completely is: 2413S Hardware revision: V1.B Date code: 1317 ISY reported version: V9B The older PLM that generates v.00 is: 2413S Hardware revision: V1.5 Date code: 1122 ISY reported version: V98 Link to comment Share on other sites More sharing options...
Teken Posted February 26, 2016 Author Share Posted February 26, 2016 You may wish to edit your post to reflect its a 2413S and not a 2314S. Link to comment Share on other sites More sharing options...
Broyd Posted February 26, 2016 Share Posted February 26, 2016 Completed updates and corrections. Link to comment Share on other sites More sharing options...
starmanj Posted January 13, 2017 Share Posted January 13, 2017 Brand new 2852-222 v.44 ...Anyone know what the ISY variable "beep" is for? It ranges from 0 to 254. Seems to do nothing... Link to comment Share on other sites More sharing options...
Chris Jahn Posted January 13, 2017 Share Posted January 13, 2017 Brand new 2852-222 v.44 ...Anyone know what the ISY variable "beep" is for? It ranges from 0 to 254. Seems to do nothing... Hi starmanj, Some devices use the beep parameter as volume, some as duration, but it seems most just ignore it. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.