KEVINLT Posted July 24, 2011 Share Posted July 24, 2011 I have a small Insteon network, with a front porch light switch added to the 99i. I am trying to add my first RF device, a Skylink 2420M motion sensor, with no success. I have added two Insteon Access points, and it appears that the phases bridged successfully. When trying to add the 2420M, I place the 2420M device near an access point and put the 2420M in link mode. I manually enter the 2420M address, name, and device type in the ISY-99i web management software. The device does not get added, and gives the following error: "Node not added - failed reading links" I have searched for posts with this error, and found some, but not with anything that pointed me to a fix for this issue. My ISY-99i is using firmware v2.8.16 and a the diagnostic report from Event Viewer is: Sun 07/24/2011 04:22:34 PM : ---- Initializing the linked devices ---- Sun 07/24/2011 04:22:34 PM : ---- All Linked Devices are now initialized ---- Sun 07/24/2011 04:22:34 PM : ---- Add remaining devices ---- Sun 07/24/2011 04:22:34 PM : [ 13 ED BA 1] Reading all links Sun 07/24/2011 04:22:34 PM : [13 ED BA 1 ] Querying engine version Sun 07/24/2011 04:22:34 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) Sun 07/24/2011 04:22:43 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) Sun 07/24/2011 04:22:52 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) Sun 07/24/2011 04:22:56 PM : [13 ED BA 1 ] Failed getting engine version. Reverting to i1. Sun 07/24/2011 04:22:56 PM : [13 ED BA 1 ] Using engine version i2 Sun 07/24/2011 04:22:56 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/24/2011 04:23:05 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/24/2011 04:23:14 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/24/2011 04:23:18 PM : [ 13 ED BA 1] ** Not added ** Read device links failed Sun 07/24/2011 04:23:18 PM : ---- All Remaining Device Added ---- Sun 07/24/2011 04:23:18 PM : ---- Start: Generate Scenes from links ---- Sun 07/24/2011 04:23:18 PM : ---- End: Generate Scenes from links ---- Sun 07/24/2011 04:23:18 PM : [All ] Writing 0 bytes to devices Thanks for the help. Link to comment
LeeG Posted July 24, 2011 Share Posted July 24, 2011 KEVINLT Great information. The ISY PLM is not able to communicate with the motion sensor. Note the time stamp on the following outbound messages are 9 seconds apart. They are being retried because the motion sensor did not respond. Move an Access Point to the ISY PLM plug point and move the motion sensor near the access point. Put the motion sensor into linking mode and try again. Sun 07/24/2011 04:22:34 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) Sun 07/24/2011 04:22:43 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) Sun 07/24/2011 04:22:52 PM : [iNST-ACK ] 02 62 13.ED.BA 0F 0D 00 06 (00) un 07/24/2011 04:22:56 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/24/2011 04:23:05 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/24/2011 04:23:14 PM : [iNST-ACK ] 02 62 13.ED.BA 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Lee Link to comment
LeeG Posted July 24, 2011 Share Posted July 24, 2011 KEVINLT One thing to check is the Insteon address. Make sure 13.ED.BA is the address. Sometimes B’s and 8’s can be misread. Lee Link to comment
KEVINLT Posted July 25, 2011 Author Share Posted July 25, 2011 Lee, I verified the device address and moved one of the access points to the PLM plug. I attempted to add the sensor again, with the same results. The motion sensor seems to link with the access point manually, if I put the access point in link mode and then set the motion sensor in link mode, they both end link mode like they communicated. After this, I linked the motion sensor with the ToggleLinc relay switch for my front porch and motion will turn the lights on. However, I can't get the ISY-99i to pick it up. The motion sensor is Ver 2, which I read some others were having a tough time with also. One guy said he repeatedly tried and finally just left it overnight with the battery connected and it linked the first time the next day. I appreciate you taking the time to offer help. If you have other suggestions, please let me know. Thanks! Link to comment
LeeG Posted July 25, 2011 Share Posted July 25, 2011 KEVINLT I have seen those posts and have no explanation why Extended messages over RF would not work and then did work the next day. The ISY (Insteon) has no function to block executed Extended commands or RF by the Insteon mesh network. There are reports that motion sensors need to sit for a few minutes after changing the battery but that would not be the case here. With the PLM and the Access Point on the same circuit the Access Point must be seeing the Extended commands used to program the motion sensor. With the motion sensor within range of the Access Point things should be working, Venstar thermostat dongles have been known to block RF activity but I don’t think you have any of those. Lee Link to comment
KEVINLT Posted July 27, 2011 Author Share Posted July 27, 2011 I tried several more times after letting the sensor sit with the battery installed, with no success. To verify that the Device ID sticker is accurate, I assume I could link the sensor manually to my Insteon light switch again, and then scan links on the light switch (switch added fine in ISY-99i software) to verify the sensor device ID. I plan to try this sometime this week. Link to comment
KEVINLT Posted August 1, 2011 Author Share Posted August 1, 2011 This weekend, I added the sensor manually to an Insteon switch that is already linked to the 99i, and then scanned for link changes from the 99i web tool. I found an unmatched link (vs ISY table) for a device with ID 0C.0C.0C. I used this ID instead of the ID printed on the sensor label, and it linked to the 99i. The sensor shows as v00, but works as expected. I am able to trigger events using the sensor through the 99i and send programming changes (LED brightness, delay, etc) to the sensor. It appears that my sensor was either not fully configured at the factory (further evidence picked up as v00 instead of v2), or has an incorrect ID label. Have any of you seen this type behavior? Link to comment
LeeG Posted August 1, 2011 Share Posted August 1, 2011 The v.00 is normal for all devices added when the specific Device Type is specified as is required for the Motion Sensor. That was a great diagnostic approach. How far off was the Insteon address label that came with the Motion Sensor? EDIT: never mind. I see you posted the address earlier. That does look like some test address that should have been replaced after testing. I would contact Smarthome Gold Line and see if they will replace. That may not be the only problem with that Motion Sensor. Link to comment
KEVINLT Posted August 1, 2011 Author Share Posted August 1, 2011 Thanks Lee, this is the first device I have added where I had to manually select the device type so I wasn't aware of the common v00 with this method. I agree that there could be other things wrong with the device, though I have had the device for many months due to the trouble adding the device to the 99i. (I had tried several months back and shelved it until this past week). I will likely still call them to see what they say. Thanks again for all your input, Kevin Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.