Interpreting the Event Log

[tmorse305]

Hi,

 

I was looking for some help interpreting a short section of my event log.  See attached.

 

1E.01.8E is a KPL, I'm using the "A" button

19.3F.29 is another KPL, the load on this KPL and the "A" button above are in a scene, the only 2 elements.

 

Sometime when I push the A button the load does not turn on, so I set the event log at level 3 to see what was up.  Tonight with the logged freshly cleared I caught the "A" button acting up.  The sequence captured in the log was:

 

Press "A" button - light does not turn on, but the "A" button lights up

Press "A" button - the "A" button light turns off

Press "A" button - the light turns on and the "A" button lights up.

 

Why is there no additional detail in the log for the first 2 presses?  It would seem the the load turned on to 255 but it did not.

 

Bonus question, what is device 11.02.03 referenced in the last 2 log entries?  I don't have a device with that ID.

 

Thanks for your help,

 

Tim

[oberkc]

My best guess on the unknown ID is that this is the PLM. But...it is just a guess.

 

I have never dug much into the details of the event log. Given that the two KPL buttons are communicating directly through the scene relationship, I am not sure how much the event log would normally show. This sounds to me as if you have something causing communication problems between the two keypad devices.

 

What is the load on the second keypad? Have you confirmed communication between the two legs of your electrical system (aka phase coupling)? Does the first KPL have a load? Does it matter whether this load is off when activating button A?

[Brian H]

You may want to look at this Wiki page.

http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Using_the_Event_Viewer

 

That ID maybe the PLM's ID. As previously pointed out.

[tmorse305]

Thanks for the replies,

 

The PLM ID is actually 3C.49.D1, you can see the communication to it 6 lines from the bottom of the screenshot.  That's why the other ID is a mystery.

 

I had already looked at the Wiki reference but it doesn't help to explain the lack of details on the first 2 presses.  It looks like ISY was set to a lower level, not 3.

 

The scene load is two LED lamps, the other load is never on when the "A" button is pressed.  The "A" button works the majority of times.   It is likely some kind of noise interference.  That's why I was hoping the event viewer could confirm this, for example hops left =0.

[paulbates]

Here are some basic "process of elimination" steps for finding problems with signalling:

• Eliminate the load as a source of noise. Can you unscrew the bulb and retry the reliability of pressing on / off?
• Eliminate other sources of noise: Are there TVs/electronics, low voltage lighting, plug in chargers, etc, on the same circuit? If so, if you remove them and retry, what happens?
• Have you validated the bridging of the power legs in your house? Look at this document and follow the procedure under "Use PowerLinc Modem as a Phase Bridge"

Paul

[tmorse305]

Thanks Paul,

 

I have an extensive installation that has been trouble free for years.  The phases are well coupled.  Only recently I've noticed some misses so I suspect there is a new noise source or an accumulation of noise sources that has finally started causing trouble.  The issue described above is intermittent, maybe only once a week.

 

If I could I'd like to circle the discussion back to my original post and my questions not about noise but the event log behavior.  Does anyone know why the event log would not pick up the details on the first 2 button presses?  I have not caught another button failure yet so I don't know whether this is just a one time thing or it's related to the failure and perhaps a clue.

 

The other issue I mention was a rouge communication with a device ID 11.02.03.  I looked through the log and I see many other similar communications from other devices to 11.01.01, 11.02.01, 11.03.01, 11.02.03, 13.01.02 and a few others.  What are these?  None of my devices have just numeric IDs.   They are all alpha numeric.  I have some devices that are 12 years old and even those are alpha numeric.

 

Any thoughts would be appreciated, thanks.

 

Tim

[paulbates]

Time

 

3C.49.D1 has 1 hop left. versus 3 hops left for the others. While the scenario should be retried several times at different times to prove consistency, I would look at it as basic signalling problems - which you described above as addressed / not an issue.

 

That being said, I would say that device has noise between it and PLM that it can't overcome and messages aren't making it. The event log not showing something is another sign the noise overwhelmed the signal and it never saw it.

 

Another possibility is that is suffers from older insteon device syndrome and would benefit from a factory reset. I've found this to be the case with togglincs

 

another possibility is a failing plm

 

 

Paul

[tmorse305]

Thanks Paul,

 

I'll report back if I find out anything interesting to share.

 

Tim