ergodic Posted August 31, 2011 Posted August 31, 2011 What exactly is the ISY pop-up saying when it reads "can't communicate with " ? Does it mean it got a corrupt message from the MS, or is it something else?
LeeG Posted August 31, 2011 Posted August 31, 2011 ergodic It means the ISY tried to send something to the Motion Sensor and could not reach the device. Normally the result of not having the Motion Sensor in linking mode when updates are made. Run Tools | Diagnostics | Event Viewer with Device communications selected. Then put the Motion Sensor into linking mode with the Set button. Then click on Write Updates to Device or Query and see what the ISY is trying to write. Lee
ergodic Posted August 31, 2011 Author Posted August 31, 2011 I get these things popping up at random several times a day -- 9 out of 10 of them for various motion sensors. The one that prompted me to ask the question is about 4' from the access point that is connected to the ISY. It hasn't been in link mode for months and there are no updates pending on it or anything else. So why would it be doing that?
LeeG Posted August 31, 2011 Posted August 31, 2011 If you can catch one of those messages with the Event Viewer running it may provide the answer. Does the Error Log show anything at the time one of the messages appears? Hopefully someone has seen it before and knows the cause.
Michel Kohanim Posted September 1, 2011 Posted September 1, 2011 Hi ergodic and LeeG, This error has two causes: 1. Device not responding even after 3 retries 2. The device sends a NACK As far as I know - and as LeeG mentioned - ISY does not sending anything to motion sensors at all unless you are programming it. With kind regards, Michel
ergodic Posted September 1, 2011 Author Posted September 1, 2011 LeeG/Michel: Thanks. I've turned on the event viewer for device comm events. Sooner or later I'll be there to catch one. I've always assumed that an MS won't even be listening unless it is in link mode. And I gather from the remarks that's true. Which is what made them seem a little puzzling.
ergodic Posted September 3, 2011 Author Posted September 3, 2011 Well, one thing I've learned is that these "cannot communicate with..." dialogs really need a timestamp on them or be recorded in the log. Unless I happen to be watching at the exact moment it happens, I have no idea what in the 100s of lines of logging I'm looking for. I did catch one fairly soon after it happened today - a motion sensor in a closet where I'm doing some work. The MS was never in link mode during that time. I did a search on the entire log history I had and there was only one "NACK" message. I've posted that section of the log below. The closet MS is 13.F3.E9 . It is linked in one scene with an SL dimmer. There is an AP in the same closet. (13.AD.64 is a front path MS, 11.9B.5A is a garage MS - Unfortunately some messages from both of those seem to be mixed in.) Sat 09/03/2011 09:33:37 AM : [standard-Cleanup][14.97.AA-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Sat 09/03/2011 09:33:39 AM : [iNST-SRX ] 02 50 13.F3.E9 00.00.01 C7 11 01 LTONRR (01) Sat 09/03/2011 09:33:39 AM : [standard-Group][13.F3.E9-->Group=1] Max Hops=3, Hops Left=1 Sat 09/03/2011 09:33:39 AM : [ 13 F3 E9 1] DON 1 Sat 09/03/2011 09:33:39 AM : [ 14 A1 37 1] ST 255 Sat 09/03/2011 09:33:39 AM : [ 13 F3 E9 1] ST 255 Sat 09/03/2011 09:33:39 AM : [iNST-SRX ] 02 50 13.F3.E9 00.00.01 C7 11 01 LTONRR (01) Sat 09/03/2011 09:33:39 AM : [standard-Group][13.F3.E9-->Group=1] Max Hops=3, Hops Left=1 Sat 09/03/2011 09:33:39 AM : Duplicate: ignored Sat 09/03/2011 09:33:39 AM : [iNST-SRX ] 02 50 13.F3.E9 00.00.01 C7 11 01 LTONRR (01): Process Message: failed Sat 09/03/2011 09:33:39 AM : [standard-Group][13.F3.E9-->Group=1] Max Hops=3, Hops Left=1 Sat 09/03/2011 09:33:39 AM : [iNST-SRX ] 02 50 13.F3.E9 18.D0.38 41 11 01 LTONRR (01) Sat 09/03/2011 09:33:39 AM : [standard-Cleanup][13.F3.E9-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Sat 09/03/2011 09:33:39 AM : [iNST-SRX ] 02 50 13.F3.E9 18.D0.38 A3 BB 81 (81) [color=#FF0000]Sat 09/03/2011 09:33:39 AM : [standard-Direct Nack][13.F3.E9-->ISY/PLM Group=0] Max Hops=3, Hops Left=0[/color] Sat 09/03/2011 09:33:41 AM : [iNST-SRX ] 02 50 13.ED.64 00.00.01 CB 13 01 LTOFFRR(01) Sat 09/03/2011 09:33:41 AM : [standard-Group][13.ED.64-->Group=1] Max Hops=3, Hops Left=2 Sat 09/03/2011 09:33:41 AM : [ 13 ED 64 1] DOF 1 Sat 09/03/2011 09:33:41 AM : [ 13 ED 64 1] ST 0 Sat 09/03/2011 09:33:41 AM : [iNST-SRX ] 02 50 13.ED.64 00.00.01 C7 13 01 LTOFFRR(01) Sat 09/03/2011 09:33:41 AM : [standard-Group][13.ED.64-->Group=1] Max Hops=3, Hops Left=1 Sat 09/03/2011 09:33:41 AM : Duplicate: ignored Sat 09/03/2011 09:33:41 AM : [iNST-SRX ] 02 50 13.ED.64 00.00.01 C7 13 01 LTOFFRR(01): Process Message: failed Sat 09/03/2011 09:33:41 AM : [standard-Group][13.ED.64-->Group=1] Max Hops=3, Hops Left=1 Sat 09/03/2011 09:33:41 AM : [iNST-SRX ] 02 50 13.ED.64 18.D0.38 41 13 01 LTOFFRR(01) Sat 09/03/2011 09:33:41 AM : [standard-Cleanup][13.ED.64-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Sat 09/03/2011 09:33:54 AM : [iNST-SRX ] 02 50 11.9B.5A 00.00.01 CB 11 01 LTONRR (01) Sat 09/03/2011 09:33:54 AM : [standard-Group][11.9B.5A-->Group=1] Max Hops=3, Hops Left=2 Sat 09/03/2011 09:33:54 AM : [ 11 9B 5A 1] DON 1 Sat 09/03/2011 09:33:54 AM : [ F D2 24 1] ST 255 Sat 09/03/2011 09:33:54 AM : [ 14 EF BD 1] ST 255 Sat 09/03/2011 09:33:54 AM : [iNST-SRX ] 02 50 11.9B.5A 00.00.01 CB 11 01 LTONRR (01) Sat 09/03/2011 09:33:54 AM : [standard-Group][11.9B.5A-->Group=1] Max Hops=3, Hops Left=2 Sat 09/03/2011 09:33:54 AM : Duplicate: ignored Sat 09/03/2011 09:33:54 AM : [iNST-SRX ] 02 50 11.9B.5A 00.00.01 CB 11 01 LTONRR (01): Process Message: failed
LeeG Posted September 3, 2011 Posted September 3, 2011 ergodic The Motion Sensor sent a Direct command NAK to the PLM. No command was sent from the PLM to the Motion Sensor, Direct or Group. Appears to be an erroneous message. The From device address is that of the Motion Sensor but no way to tell if it was generated by the Motion Sensor or the PLM. Is this the only device address generating the Comm failed message? Lee
CopyRon Posted October 10, 2011 Posted October 10, 2011 viewtopic.php?f=25&t=6966&start=75 read my same problems reported a while back, about halfway down page 6. Also scroll down to my reply. Maybe just coincidence...but since upgrading to 3.1.9, all of my early (1st version) Motion Sensors have failed. I have replaced them with newer versions, and all appears OK. Actually I have one V1 still working . They not only don't report their status, but they do not control the lights they are linked to.However, if I manually push the button inside the motion sensor they will activate their linked device. I removed and reinstalled the MS v1's and they might work for another day or so and then same behavior. ISY would say they were not responding and to check connections. Replacing with V2 solved this.
ergodic Posted October 11, 2011 Author Posted October 11, 2011 I'm not really seeing any actual problem with my motion sensors so far as I can tell - though for a while I thought I was - neither V1 or V2. Just the miscast error report pointing a finger at them.
Michel Kohanim Posted October 11, 2011 Posted October 11, 2011 Hello ergodic, As LeeG pointed out, the Motion Sensor is sending a Nack on its own. The only thing I recommend (which I think you have already done) is: 1. Make sure you are on 2.8.16 and above 2. Delete one of the motion sensors from ISY 3. Do a factory reset on it 4. Add it back Perhaps there's a lingering link in there somewhere and this might fix it. With kind regards, Michel
ergodic Posted October 11, 2011 Author Posted October 11, 2011 You're correct: all that's been done (several times) and I'm on 3.1.9 I think I have a log extract where the MS Nack happens. Does this contain anything useful? 11.A4.43 is the MS, it currently is a V1 device. Tue 10/11/2011 10:36:09 AM : [standard-Cleanup][11.A4.43-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Tue 10/11/2011 10:36:19 AM : [iNST-SRX ] 02 50 11.A4.43 00.00.01 CB 11 01 LTONRR (01) Tue 10/11/2011 10:36:19 AM : [standard-Group][11.A4.43-->Group=1] Max Hops=3, Hops Left=2 Tue 10/11/2011 10:36:19 AM : [ 11 A4 43 1] DON 1 Tue 10/11/2011 10:36:19 AM : [ 11 A4 43 1] ST 255 Tue 10/11/2011 10:36:20 AM : [iNST-SRX ] 02 50 11.A4.43 00.00.01 CB 11 01 LTONRR (01) Tue 10/11/2011 10:36:20 AM : [standard-Group][11.A4.43-->Group=1] Max Hops=3, Hops Left=2 Tue 10/11/2011 10:36:20 AM : Duplicate: ignored Tue 10/11/2011 10:36:20 AM : [iNST-SRX ] 02 50 11.A4.43 00.00.01 CB 11 01 LTONRR (01): Process Message: failed Tue 10/11/2011 10:36:20 AM : [standard-Group][11.A4.43-->Group=1] Max Hops=3, Hops Left=2 Tue 10/11/2011 10:36:20 AM : [iNST-SRX ] 02 50 11.A4.43 18.D0.38 41 11 01 LTONRR (01) Tue 10/11/2011 10:36:20 AM : [standard-Cleanup][11.A4.43-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Tue 10/11/2011 10:36:20 AM : [iNST-SRX ] 02 50 11.A4.43 18.D0.38 A3 BB 81 (81) Tue 10/11/2011 10:36:20 AM : [standard-Direct Nack][11.A4.43-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Tue 10/11/2011 10:37:02 AM : [iNST-SRX ] 02 50 13.ED.64 00.00.01 CB 11 01 LTONRR (01) Tue 10/11/2011 10:37:02 AM : [standard-Group][13.ED.64-->Group=1] Max Hops=3, Hops Left=2
Michel Kohanim Posted October 11, 2011 Posted October 11, 2011 Hello ergodic, The main issue here is that the Motion Sensor is spontaneously sending those messages back to the PLM without ISY doing/sending anything to it. Perhaps one test would be to request a replacement for one of the motion sensors and see if the problem goes away. With kind regards, Michel
Recommended Posts