Jump to content

Unknown Insteon Device Babbling


Recommended Posts

Posted

Hello,

I have an installation of about 40+ Insteon devices.

A few weeks ago, very few devices would work, I believe I was able to deduce that only local  (non-grouped) devices would turn on/off, whereas any device or button as part of a scene would rarely work, maybe 1 out of 20 on/off attempts would respond.  The problem went away, and then just came back a few days ago with the same behavior.

I have an ISY controller on the network, so I captured some detailed log activity, it seems there is a device on the network "babbling" so much that other network traffic can't seem to propagate.  I attached the log file.

I am unable to determine what or where that device is.  It's not managed in my ISY, maybe I forgot to add it when I installed the system....I tried doing a manual add of 22.80.19, but the ISY interface hangs/waits forever, probably due to the babbling.

Since I don't know what or where this device is, my thought process is leading me to ask:
- Is there a way to determine what kind of device 22.80.19 is?
- Are there any clues to tell me whether 22.80.19 is near other devices? If I knew what devices are nearby, it would help me narrow my search.
- Any way to send an arbitrary command to disable that device or cause it to beep/blink?
- Is there any way to prevent any one device from effectively crippling the Insteon network?

Please advise...any help would be appreciated.

Thanks,

ISY-Events-Log.v4.6.2__Wed 2018.06.20 07.55.53 AM.txt

Posted

Any chance that 22.80.19 is your PLM? Look at Tools/Diagnostics/PLM Info Status

If it is, this might be a program in a loop sending a scene command. Look at your programs tab, open folders to view all programs and see if any program icon is flickering

Paul

Posted

In admin console, display the devices summary tab/page. Now click on the "Address" field title at the top causing the spreadsheet style list to sort by Insteon address. 

Now it should be quite easy to figure the type of device since SH assigns groups of addresses by device type.

Posted

SOLVED!

It was a PLM on the network that was babbling...not the ISY PLM, but rather an I/O link PLM.  I'll have to investigate further to understand which device was initiating the babbling (The I/O link, the sensor it was monitoring, or the PLM itself), but I'd like to delve into this experience further in case something like this happens again:

- What can I look for in my overall configuration to prevent a babbling device from crippling my lighting system?  I can see how Insteon might claim to be scalable by number of devices, but it certainly didn't scale well in an impaired state with a lot of traffic (3-5 msgs per second doesn't seem like a lot of traffic, even if it was amplified by echo's).

- Could I add the PLM to my ISY admin interface such that (per larryllix's suggestion) I can document every address on the network that it would show up in the master list?

- Could I have determined the model number of the insteon module known only by 22.80.19?  Was there something in the event log that hinted this was a PLM, or switch, or keypad, etc?  Knowing the device type by the event log would have helped a lot.  I wanted to add it to my ISY using the "light bulb" icon (add new device), but either the device type or the impaired network prevented me from doing so.

Posted

Insteon diagnostic capabilities is something that has been long asked for in the ISY Admin Console. In the old X10, there were plug-in modules that would show you traffic, the SSI of a packet, retry attempts, etc. I don't know what's possible with Insteon and a PLM, but it's hard to believe we have gone backwards from X10 days.

Posted

PLM on the network connected to a module. Sounds like a Smartenit EZIO8SA as it used its own PLM as an interface. It should show up in the device tree.

A floating Analog Input may cause all kinds of traffic on the Insteon Network. Connecting to ground is usually needed if the Analog inputs are unused.

Posted

This is all making sense now...I had the EZIO8SA with PLM 22.80.19, but since I missed the grounding instruction, I wasn't able to get it to link when I first installed it so I bought a new 4-port integrated IO module that worked.  This was months ago, so I guess someone (probably me) plugged it back in within the past few weeks to cause the babbling.

Bottom line: Note to self to link *all* devices into the ISY upon installation and if unsuccessful linking, fix it or re-pack the device so no one can mistakenly plug it back in.  :)

I really appreciate everyone's attention on this.  You see I'm a newbie to the forum, I am impressed at how well this medium worked for me.  I'll have other topics I'd like to discuss in the near future.  I have a ton of ideas/suggestions for ISY/Insteon to talk about.

Good day everyone...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...