Bad Modem?

[Zellarman]

Currently in Home Automation Hell over here.

 

First a little history. I was having an issue with one particular SL relay, it seemed to be hosting ghost links that would for some reason only occured every 3rd to 5th cycle of the switch. Unfortunately the relay is damaged and I'm unable to perform an air gap factory reset (nothing happens when you pull the 'button') Then, unassociated to this issue, I added a circuit to my homes wiring, and since I recently upgraded my service, I thought it might be a good time to try and identify some of the circuits I think this was a bad idea) I cycled through circuits of the panel, repeatedly switching breakers on and off while my wire tole me what was going on and off. I fear this may have compromised my modem, while it certianly does still function, my isy 99 'cannot communicate' with devices sporidacally.

 

Then I made an even bigger mistake. I tried to restore my ISY, w/o exporting my programs. I had a file from 6 months ago, and haven't done too much programming recently, so that aspect isn't so catastrophic, and I have multiple back-up from different stages of my networks growth, so all should be OK on that front, right? But it appears not. Now device links are missing, not al device ramp rates and on levels are not what they were.

 

Does anyone have any insight to any of my multiple issues? I plan on replacing the SL relay, removing it from the isy then relinking it while removing existing links offered no relief from the ghost links, but I don't even know where to begin to try resolving my remaining issues.

[Sub-Routine]

The symptoms you describe indicate communication errors. It is unlikely that rebooting the PLM or the ISY would overwrite existing links. Even Restore ISY should not affect device links. If the PLM didn't reboot properly you could try Restore Modem.

 

A bad switch may be sending noise which could cause poor communications. Are the Access Point LEDs flashing? Is the PLM LED flashing?

 

Since you added a circuit you may have to relocate your Access Points. Does the new circuit have a new load?

 

Rand

[Zellarman]

SignaLincs, not Access points, flash only when they should w/ normal insteon communications, same for the PLM. The signaLincs are still on the two different phases of my service, can't imagine them needing to be relocated

 

Still having a host of issues. It's really bizzare to me,One example isthat one SLD "S1" controlls another "S2" as it should, but also now turns on "S3" only w/ a double tap, turns off "S3" w/ single press off, but nothing happens w/ "S3" w/ a single press on of "S1". Unfortunately, like I said this is only one example

[Michel Kohanim]

Hello Zellarman,

 

Were you aware that SignaLincs do not support i2? Have you recently added new i2 devices?

 

With kind regards,

Michel

 

SignaLincs, not Access points, flash only when they should w/ normal insteon communications, same for the PLM. The signaLincs are still on the two different phases of my service, can't imagine them needing to be relocated

 

Still having a host of issues. It's really bizzare to me,One example isthat one SLD "S1" controlls another "S2" as it should, but also now turns on "S3" only w/ a double tap, turns off "S3" w/ single press off, but nothing happens w/ "S3" w/ a single press on of "S1". Unfortunately, like I said this is only one example

[Zellarman]

Nope, guess I need to get me some access points! I added an outletlinc which I understand is i2, but no motion detectors or other newly introduced device types. But is it possible that a newer KPL is i2 as well? Even so, would that cause communication issues w/ older existing and properly functioning devices?

[Michel Kohanim]

Hi Zellarman,

 

The new KPLs, SWLs, ALs, and LLs are all i2 (not a comprehensive list). And, yes, they might interfere with existing installations especially if:

1. you use SignaLincs

2. you are programming them via ISY

 

With kind regards,

Michel

 

Nope, guess I need to get me some access points! I added an outletlinc which I understand is i2, but no motion detectors or other newly introduced device types. But is it possible that a newer KPL is i2 as well? Even so, would that cause communication issues w/ older existing and properly functioning devices?

[Zellarman]

Well, that's some bad news. Thankfully you guys at UDI aren't dropping bombs on us as well. I seem to have worked through most of the communication issues I was having, though I seem to have lost a SLR and KPLD. I'll blame it on myself for cycling through circuits.

 

Now, I just hope I won't have programming issues when I finally get my replacements.

 

I guess my definition of any good insteon system includes having 1 extra of each component.

[Michel Kohanim]

Zellarman,

 

Thanks for the update. I just wished SH would not change the protocol on existing devices. I am hoping for a day day when we'll have a stable enough protocol and all we have to change would be adding support for new devices.

 

With kind regards,

Michel

Well, that's some bad news. Thankfully you guys at UDI aren't dropping bombs on us as well. I seem to have worked through most of the communication issues I was having, though I seem to have lost a SLR and KPLD. I'll blame it on myself for cycling through circuits.

 

Now, I just hope I won't have programming issues when I finally get my replacements.

 

I guess my definition of any good insteon system includes having 1 extra of each component.