416to305 Posted November 11, 2014 Share Posted November 11, 2014 Hi everyone, hoping someone can make sense of the below. Since switching back to the ISY last night I keep getting random errors mainly with the hidden door sensor on the front door, or the garage door opener. I never had problems before and my network is basically the same as it was before but I always get random errors can't configure device etc. However they always seem to work. Like the hidden door sensor always has a ! beside the name and will pop up about can't communicate whenever I load the admin console. However it still works, like opening/closing the door reports properly and scenes trigger based on it and so on. Here's the event log level 3 when I tried to select write updates to device. First I got a pop up saying: Failed writing device link. Front Door Sensor -200000/-51 PLATFORM ERRORS - 10108 Check log Then the error log: Tue 11/11/2014 09:58:24 AM : [2B 2F 4B 1 ] Link 3 : 0FE0 [E201300FAA010001] Writing [E201300FAA010001] Tue 11/11/2014 09:58:24 AM : [iNST-TX-I2CS] 02 62 2B 2F 4B 1F 2F 00 00 02 0F E7 08 E2 01 30 0F AA 01 00 01 03 Tue 11/11/2014 09:58:24 AM : [iNST-ACK ] 02 62 2B.2F.4B 1F 2F 00 00 02 0F E7 08 E2 01 30 0F AA 01 00 01 03 06 (00) Tue 11/11/2014 09:58:33 AM : [iNST-TX-I2CS] 02 62 2B 2F 4B 1F 2F 00 00 02 0F E7 08 E2 01 30 0F AA 01 00 01 03 Tue 11/11/2014 09:58:33 AM : [iNST-ACK ] 02 62 2B.2F.4B 1F 2F 00 00 02 0F E7 08 E2 01 30 0F AA 01 00 01 03 06 (00) Tue 11/11/2014 09:58:42 AM : [iNST-TX-I2CS] 02 62 2B 2F 4B 1F 2F 00 00 02 0F E7 08 E2 01 30 0F AA 01 00 01 03 Tue 11/11/2014 09:58:42 AM : [iNST-ACK ] 02 62 2B.2F.4B 1F 2F 00 00 02 0F E7 08 E2 01 30 0F AA 01 00 01 03 06 (00) Tue 11/11/2014 09:58:46 AM : [2B 2F 4B 1 ] Link 3 : 0FE0 [E201300FAA010001] *Failed Writing [E201300FAA010001] The door sensor is literally 3 feet away from a KPL so there's no way it could be that. Should I maybe delete and re-add the device? It was connected back and forth to the Vera and other controllers, but I thought adding it to the ISY selecting remove existing links would have taken care of any of those issues. Link to comment
Michel Kohanim Posted November 11, 2014 Share Posted November 11, 2014 Hello 416to305, Please note that for battery operated devices, they have to be in awake mode otherwise ISY cannot program them. As you can see: TX/ACK but no SRX or ERX: TX - ISY sends a command to PLM ACK - PLM Acks the command SRX - The device Acks the command from the PLM So, please do make sure your battery operated devices are awake before you do anything to them. Also, our tech support is available to help you with all these issues. Please do not hesitate to contact us (links below). With kind regards, Michel Link to comment
LeeG Posted November 11, 2014 Share Posted November 11, 2014 A link record is queued for update. The Hidden Door Sensor being battery powered is asleep. Manually put the Hidden Door Sensor into linking mode. Then right click on Sensor and select Write Updates. After update completes take the Hidden Door Sensor out of linking mode or wait 4 minutes. Link to comment
416to305 Posted November 11, 2014 Author Share Posted November 11, 2014 Thanks I'll try that, I'm definitely aware of the limitations of a battery device, it's just weird because I never had these problems before. Like picking write updates to device I thought was just forcing it to update, but there's nothing I need to write. I added the device to the ISY, it added and was fine, but then any time I log into the admin console it pops up saying error communicating with hidden door sensor. I've opened and closed the door a bunch of times which I thought wakes it up and then it gets any updates but I still get that error. I think I'll try also to remove it and re-add it, as I know with motion sensors etc holding it for 5 secs or so, letting go and then holding set for another 5 seconds, is different than holding it for 5 seconds letting to and then just tapping it once type thing, so I may have added it wrong as I basically just kept holding and pushing set while adding it until the ISY finally did it. Thanks! Link to comment
416to305 Posted November 11, 2014 Author Share Posted November 11, 2014 Oh I forgot to mention it's not just the battery devices though. I know not much help with no logs, but the GarageLinc does it as well sometimes. Like if I try to add it to a scene, or change a setting like Trigger Reverse. Here I caught part of it when trying to add change trigger reverse, it pops up after a min "Cannot communicate with Garage Door - Sensor 2F 8D 28 1. Please check connections. Here's the log: Tue 11/11/2014 11:38:35 AM : [D2D EVENT ] Event [2F 8D 28 1] [ERR] [0] uom=0 prec=-1 Tue 11/11/2014 11:38:35 AM : [ 2F 8D 28 1] ERR 0 Tue 11/11/2014 11:38:35 AM : [All ] Writing 1 bytes to devices Tue 11/11/2014 11:38:35 AM : [2F 8D 28 1 ] Memory : Write dbAddr=0x4006 [0F] cmd1=0x20 cmd2=0x0F Tue 11/11/2014 11:38:35 AM : [iNST-TX-I2CS] 02 62 2F 8D 28 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 Tue 11/11/2014 11:38:35 AM : [iNST-ACK ] 02 62 2F.8D.28 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (0F) Tue 11/11/2014 11:38:44 AM : [iNST-TX-I2CS] 02 62 2F 8D 28 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 Tue 11/11/2014 11:38:44 AM : [iNST-ACK ] 02 62 2F.8D.28 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (0F) Tue 11/11/2014 11:38:53 AM : [iNST-TX-I2CS] 02 62 2F 8D 28 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 Tue 11/11/2014 11:38:53 AM : [iNST-ACK ] 02 62 2F.8D.28 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (0F) Tue 11/11/2014 11:38:57 AM : [2F 8D 28 1 ] Memory : Write dbAddr=0x4006 [0F] cmd1=0x20 cmd2=0x0F - Failed Tue 11/11/2014 11:38:57 AM : [D2D EVENT ] Event [2F 8D 28 1] [ERR] [1] uom=0 prec=-1 Tue 11/11/2014 11:38:57 AM : [ 2F 8D 28 1] ERR 1 Tue 11/11/2014 11:38:57 AM : [All ] Writing 0 bytes to devices Does anything in this mean anything? Just weird because never had this issue before, garage door opener is a plug in device and even so, the KPL is maybe 10 feet away from it. I'm going to remove it as a device, factory reset it and then try to add it again as doing that for the door sensor seemed to shut it up with the errors it was getting. Will post the above here anyway just since I have it now. Thanks! Edit: Didn't work at all, now I can't even add the device it just detects it, adds it, then after a minute says cannot communicate with IOLinc - Sensor and then the Sensor and Relay both have a ! beside them. Link to comment
LeeG Posted November 11, 2014 Share Posted November 11, 2014 The pending link record for the Hidden Door Sensor is to make the Sensor a Controller for 30.0F.AA. Once pending it will require putting the Hidden Door Sensor into linking mode to allow the update to happen. The I/O Linc (GarageLinc) is powerline only. If it takes more than one Write Updates action there is poor comm to the I/O Linc. Link to comment
LeeG Posted November 11, 2014 Share Posted November 11, 2014 The ISY does NOT use the special commands to keep a battery device from sleeping. Battery devices must be manually put into linking mode to do updates. The I/O Linc (2F 8D 28) trace indicates it is not responding to an Extended command. The command is tried three times with no response from device. Best not to use Trigger Reverse option. It does reverse the Sensor On/Off commands but it does NOT reverse the Query response. A Query, done manually, or automatically at 3 AM will change the state of the I/O Linc Sensor when Trigger Reverse is used. Link to comment
416to305 Posted November 11, 2014 Author Share Posted November 11, 2014 Okay thanks. I thought it was like Vera where a motion sensor checks in every 30 minutes and if there's updates it receives them. I can't make it work at all now for some reason though. I removed the IOLinc and factory reset it, but now I cannot link it to the ISY no matter what I do. Tried to reboot the ISY but no luck. I add it and it says adding, and then after a couple minutes says: The following device could not be added: 2F.8D.28 (2450) IOLinc v.41 - Cannot determine device link table address. I'll try to move the ISY and PLM but I don't see what that would do. What is confusing to me is that when I had the ISY previously, it was the same set up as I have today, except I have more Insteon devices now, where as back then I only had a few. So like I said even if the IOLinc was a RF only device, I have devices even closer to it now than I did the last time. Just tried putting a LampLinc dimmer about 10 feet away from it just in case, but same thing. This is what the log shows also: Tue 11/11/2014 12:06:07 PM : [iNST-TX-I2CS] 02 62 2F 8D 28 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 11/11/2014 12:06:07 PM : [iNST-ACK ] 02 62 2F.8D.28 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 11/11/2014 12:06:11 PM : [2F 8D 28 0 ] Failed to add device, reason 9 Tue 11/11/2014 12:06:11 PM : [D2D EVENT ] Event [2B 32 DE 1] [DOF] [0] uom=0 prec=-1 Tue 11/11/2014 12:06:11 PM : [ 2B 32 DE 1] DOF 0 Tue 11/11/2014 12:06:11 PM : [D2D EVENT ] Event [2B 32 DE 1] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 12:06:11 PM : [ 2B 32 DE 1] ST 0 Tue 11/11/2014 12:06:11 PM : [All ] Writing 0 bytes to devices Tue 11/11/2014 12:06:11 PM : [All ] Writing 0 bytes to devices Tue 11/11/2014 12:06:33 PM : [iNST-SRX ] 02 50 2B.32.DE 00.00.01 C7 11 01 LTONRR (01) Tue 11/11/2014 12:06:33 PM : [std-Group ] 2B.32.DE-->Group=1, Max Hops=3, Hops Left=1 Tue 11/11/2014 12:06:33 PM : [D2D EVENT ] Event [2B 32 DE 1] [DON] [1] uom=0 prec=-1 Tue 11/11/2014 12:06:33 PM : [ 2B 32 DE 1] DON 1 Tue 11/11/2014 12:06:33 PM : [D2D EVENT ] Event [2B 32 DE 1] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 12:06:33 PM : [ 2B 32 DE 1] ST 255 Tue 11/11/2014 12:06:33 PM : [iNST-SRX ] 02 50 2B.32.DE 00.00.01 CB 11 01 LTONRR (01) Tue 11/11/2014 12:06:33 PM : [std-Group ] 2B.32.DE-->Group=1, Max Hops=3, Hops Left=2 Tue 11/11/2014 12:06:33 PM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 12:06:33 PM : [iNST-SRX ] 02 50 2B.32.DE 2C.08.F8 41 11 01 LTONRR (01) Tue 11/11/2014 12:06:33 PM : [std-Cleanup ] 2B.32.DE-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Tue 11/11/2014 12:06:33 PM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 12:06:33 PM : [iNST-SRX ] 02 50 2B.32.DE 11.01.01 CB 06 00 (00) Tue 11/11/2014 12:06:33 PM : [std-Group ] 2B.32.DE-->11.01.01, Max Hops=3, Hops Left=2 Tue 11/11/2014 12:06:33 PM : [iNST-INFO ] Previous message ignored. Tue 11/11/2014 12:06:34 PM : [iNST-SRX ] 02 50 2B.32.DE 11.01.01 CB 06 00 (00) Tue 11/11/2014 12:06:34 PM : [std-Group ] 2B.32.DE-->11.01.01, Max Hops=3, Hops Left=2 Tue 11/11/2014 12:06:34 PM : [iNST-INFO ] Previous message ignored. I think I'm going to remove all devices and factory reset the PLM as something seems up. Just realizing I never did that after using Insteon with my Vera, so there's probably lots of junk in the PLM still even if I did do remove existing links when adding. Link to comment
Michel Kohanim Posted November 11, 2014 Share Posted November 11, 2014 Lee, please contact our tech support. There's a problem with the setup and all the factory reset, moving around, changing things will only exacerbate finding the root cause. With kind regards, Michel Link to comment
416to305 Posted November 11, 2014 Author Share Posted November 11, 2014 Okay thanks I will later. I factory reset the ISY, PLM and IOLinc and it still doesn't work. Adds it for a few minutes then says again Cannot communicate with 2F.8D.28 - Sensor. Please check connections. Will contact support after work, thanks! Link to comment
Michel Kohanim Posted November 12, 2014 Share Posted November 12, 2014 Hello 416to305, Just a few pointers: From what I see in your posts, I am very much concerned that the issue is not even with ISY/PLM/IOLinc. The reason is that the communication issue is related to the Sensor and not the Relay. ISY does not send any commands to the Sensor node of IOLinc because you really cannot do anything with it (it's read only). So, not only I urge you to contact our tech support but also check your Tools | Log and look for entries for your IOLinc-Sensor node. This will give us clues as to what else maybe trying to control the IOLinc. From over 8 years of experience I can assure you that factory resetting ISY will never solve any issues especially when communications related. Not only that, factory reset will prevent us from figuring out what the root causes are and, in case something starts working (intermittently), it's bound to fail again. And, thus a waste of your time. Factory resetting the PLM is sometimes useful but mostly when the issue is related to a full database on the PLM. I have never seen factory resetting the PLM fix communication issues. So - and to save you time and frustration - I do recommend not factory resetting ISY/PLM without a good reason (see above). With kind regards, Link to comment
LeeG Posted November 12, 2014 Share Posted November 12, 2014 Michel The I/O Linc trace is misleading as most of the Insteon traffic is for a different device. Only the first command is sent to the I/O Linc (2F 8D 28) which fails to get any response from I/O Linc. The majority of the trace is for (2B 32 DE 1) which is a different device. Not disagreeing will all your suggestion, just noting that the I/O Linc Sensor is not being commanded as those messages are for a different device address. Tue 11/11/2014 12:06:07 PM : [iNST-TX-I2CS] 02 62 2F 8D 28 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 11/11/2014 12:06:07 PM : [iNST-ACK ] 02 62 2F.8D.28 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 11/11/2014 12:06:11 PM : [2F 8D 28 0 ] Failed to add device, reason 9 Tue 11/11/2014 12:06:11 PM : [D2D EVENT ] Event [2B 32 DE 1] [DOF] [0] uom=0 prec=-1 Tue 11/11/2014 12:06:11 PM : [ 2B 32 ED 1] DOF 0 Tue 11/11/2014 12:06:11 PM : [D2D EVENT ] Event [2B 32 DE 1] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 12:06:11 PM : [ 2B 32 DE 1] ST 0 Link to comment
Michel Kohanim Posted November 12, 2014 Share Posted November 12, 2014 Hi LeeG, Thanks so very much for the feedback and it makes sense. Tue 11/11/2014 12:06:11 PM : [2F 8D 28 0 ] Failed to add device, reason 9 Reason 9 = Cannot determine device link table address So perhaps we are dealing with an older PLM that does not support I2CS? Thanks again LeeG. With kind regards, Michel Link to comment
416to305 Posted November 14, 2014 Author Share Posted November 14, 2014 Hi everyone sorry I forgot about this thread. So after learning more about it from other posters in another thread, I found out that almost all my Insteon dual link devices are on phase 1, but the PLM in the basement was on phase 2, with only a single LampLinc upstairs also on phase 2. What's weird is couple months ago it always worked fine like this no issue and that was the Vera controlling it. (Bit of history, had the ISY couple months ago worked fine with PLM downstairs, ended up switching to Vera and having it and the Altsteon plugin control Insteon and I never had any issues with the garage. Switched back to using the ISY and the Garage doesn't work at all, so did a factory reset on the PLM with no success.) So I then moved the PLM upstairs to an outlet which is also phase 1 now, and doing that immediately caused the Garage IOLinc to register as a device, and the ! beside the Sensor to update and go away. That was a few days ago, whenever I started this post and so far everything has been perfectly fine. So will keep an eye on it but yeah been fine since then. I bought the PLM just a few months ago so not sure if you can tell the details on it but the bottom says 2413S V1.B, 1420. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.