having a bad day

[gfrnd]

OK, things have really taken a turn for the worse;

I was able to set up remote access to the sysem: still have certificate problems but lets skip that till later

I was at 6;.13, system started being erratic and suddenly all communication between ISY and PLM (26 and older PLM) was lost; upgraded to 6.14 but no change.

Initially, there was no communication between ISY and PLM but after 2 disconnects, I now see the PLM: 5.EA.30v4A

 

One major thing has happened: the electician was in and installed some new devices: 3 wall outlets, and new switchlink and a new KPL; they were purchased a while ago but he just got around to putting them in.

 

Is there something going on with the is1 is2 business? No devices are recognized by the system. I haven't been there to attempt to link any of the new devices.

 

Any thoughts about what is going on?

 

Many thanks

[gfrnd]

OK, I won't flare, I promise but here is a little more:

I was able to link one of the new outlet links but immediatly, communication failed; reset an older (v.28) and the same thing happened - can link but after a system busy it can't communicate

 

so, after many many months of a smootly running system nothing works: the ISY communicates with the PLM but I can communicate with none of the devices, tried several disconnect reconnect: get minutes of system busy during which every device comes back 'can't communicate'

 

I'm not flaring, just unplugged everything and do without until some bright idea comes up

 

thanks

[MikeB]

Have you tried rebooting both the ISY and PLM, or are you just rebooting the ISY?

 

Did everything stop working right after the electrician? If so, and if it's possible, I would unplug/airgap/disable everything he added to see if the problem goes away. If it does, you can add things back in to see what's causing your issue.

 

Otherwise it sounds to me like you may have a bad PLM.

[gfrnd]

Thanks Mike;

I disconnected bot the PLM and the ISY several times; at first, ISY showed no connectivity to PLM but now it does but the symptoms remain, no device in the house can be seen by the ISY even after immedate linking via ISY that does work (except communication never happens)

I am suspecting the PLM; one thing I noted- the standard links throughout the system seem to be working so it might not be noise caused by an errant device; the electrician was here on 2 days, first installed some switches==> things were ok, came back 2 days later and installed 3 outlet links and that's when the trouble began.

Looked at manual, don't see how to 'air gap' outlet links.

I did go ahead and order a new PLM for overnight, needed an excuse to get a new one anyway Just suspicious this won't solve this problem..... sometimes things fail in the middle of changes but gotta question it.

 

Thanks

at least I'm nice and calm after a night's sleep; this it no biggie, for sure a solution is available just need to find it lol. So thanks for your help, if any other thoughts come along, be sure and let me know.

[MikeB]

You're right, there is no way to "air gap" an OutletLinc. If they are on a different circuit than your PLM, you could try powering down the breaker they are on and testing communications to some other device.

 

If you have an ApplianceLinc or LampLinc, you could plug it in right to the back of the PLM and see if you are able to communicate with it.

 

But, based on your description it honestly does sound like a failed PLM to me. You have a very old rev firmware (4A) as far as I can tell, so an upgrade is probably for the better anyway.

 

Please keep me posted.

[gfrnd]

Michael

Put the new PLM in and problem solved; what was kind of interesting, the system had starting working a little, some devices were communicating but most were not; anyway, thanks for the input; all things are go now;

turns out the PLM was less than 2 yrs old so I am going to get it replaced and use it as a backup

reminds me again debugging requires an open mind; when I had the new devices installed and the system stopped working it was kind of hard to blame an existing part of the system.

 

thanks again

[MikeB]

Glad to hear you're all set!