johnnyt Posted April 12, 2013 Share Posted April 12, 2013 Every now and again I get a dialog box that says ISY can't communicate with a motion sensor. Got one a few minutes ago and looked at the log entries (below) to see a whole bunch of good comms followed by some kind of error right after it reports ON then everything goes back to normal. I've separated the bad from the good using a "code" box. Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 04:49:26 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 04:50:31 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 04:50:40 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 04:52:09 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 04:52:16 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 04:52:46 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 04:54:16 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 04:54:46 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 04:54:50 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 04:55:46 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 04:57:05 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 04:57:35 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 04:58:00 PM System Log Basement / Rec Room Motion-Sensor Error 1 Fri 2013/04/12 04:58:01 PM System Log Basement / Rec Room Motion-Sensor Fri 2013/04/12 04:58:01 PM System -2 Basement / Rec Room Motion-Sensor Error 0 Fri 2013/04/12 04:58:55 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 04:58:55 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 04:59:28 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 04:59:57 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 05:00:25 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 05:00:56 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 05:01:12 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 05:01:42 PM System Log Basement / Rec Room Motion-Sensor Status 100% Fri 2013/04/12 05:01:53 PM System Log Basement / Rec Room Motion-Sensor Status 0% Fri 2013/04/12 05:02:48 PM System Log This is a well used motion sensor that fails (or should I say, generates an error) only a fraction of the time relative to how often it doesn't. There's no indication the battery is low, at least not from it's low battery warning. Also, the lithium ion "10 year" battery in it is only a few months old and I track it's usage through a variable (since the low battery warning has proven largely unreliable in my experience) so I know that barring a defect it's got a lot of life left in it. FWIW, the last entry in the error log is: Fri 2013/04/12 02:57:40 PM System -170001 [uDSockets] HTTP:32 error:6 What might be going on? Link to comment
LeeG Posted April 12, 2013 Share Posted April 12, 2013 The log entries show result but not why. Need an event viewer at LEVEL 3 trace to see what is actually happening. Link to comment
johnnyt Posted April 12, 2013 Author Share Posted April 12, 2013 The log entries show result but not why. Need an event viewer at LEVEL 3 trace to see what is actually happening.One is not available and I don't particularly want to run the event viewer at level 3 all day in the hope of catching one of these infrequent events. Recently when I've run the event viewer at level 3 it's hammered my ISY to the point of causing performance problems. See viewtopic.php?f=27&t=11219 for more info. Is there another way, or just some possible causes? Link to comment
LeeG Posted April 12, 2013 Share Posted April 12, 2013 I do not have a list of possible Motion Sensor interactions that result in the Error 1, -2 Log entries. With the entries labeled System I take that to be something the Motion Sensor sent to the PLM. Link to comment
Michel Kohanim Posted April 12, 2013 Share Posted April 12, 2013 Hi LeeG, -2 = Device Communication Error -1 = Request Failed Error With kind regards, Michel Link to comment
johnnyt Posted April 23, 2013 Author Share Posted April 23, 2013 Could comm error messages, in particular like the ones that I get occasionally from motion sensors (this thread) but also ones from always on devices, happen because of network connection problems between the GUI and ISY? I'm wondering about possible network (LAN) problems that might be causing some issues and want to know if comm errors could be a symptom of that kind of problem. Link to comment
LeeG Posted April 23, 2013 Share Posted April 23, 2013 I all previous cases that have been traced the error stems from actual Insteon message flow. Until the actual situation is traced one cannot be 100% sure but it is hard to see how a LAN problem would be interpreted as an Insteon device error. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.