another PLM failure

[Techman]

I recently noticed that some devices located only within scenes would occasionally fail to either turn on or off.  This problem was consistently inconsistent.

 

When I did a compare link tables on the devices all looked normal. I even did a restore device(s) which didn't resolve the problem.

 

However I noticed that when I ran a scene test on a problematic scene where all the link tables appeared correct I would always get at least one random device that would fail the scene test.

 

The PLM was firmware v9E, Hardware version 2.0 and a date code of 1425, so the unit was about 3 years in service.

 

I suspect that daughter board in the PLM which contains the RS232 circuit may be the culprit.

 

I just replaced the PLM with one just obtained from Smarthome. The new PLM has a date code of 4616, v9E firmware and hardware revision 2.3.   I didn't check to see what RS232 chip the new version has but was told last year that they were updating the RS232 components.

 

After installing the new PLM the scene tests don't indicate any failures.

[Brian H]

I had seen vague reports of the serial chip on the daughter board having issues.
Not sure if the brand was changed or normal production parts availability change.
It is now a TI brand MAX232EI on my latest recently purchased V2.3 PLM.

It has ESD rating I don't believe the older ones had.

[Techman]

Just got off the phone with Smarthome. They're replacing the PLM under warranty even though its 3 years old.

 

The new PLMs, hardware version 2.3, have beefed up capacitors and a new RS232 interface. They believe that these enhancements should rectify the PLM issues.

 

They're open to suggestions as to new products and / or product enhancements. Just send them an email to CustomerService@Smarthome.com.

I'm optimistic that the new management will take the company forward, however it could be awhile before we start to see results

[Brian H]

Time will tell.

My V2.3. Date Code:4216. I see the same questionable brand Fujucon capacitors.

Just C7 and C13 are now 100uF 50V and to fit them in. Laying sideways with a small gob of component glue holding them. As the space is too tight for them vertically in the normal through hole pads on the PCB.

[BigMoose1]

Can I assume that if I am getting devices randomly turning on with nothing in the log indicating an activation and the status of the device not being correct, that I have a failing plm. I replaced it on Aug 10 2016. However it is older than that because I bought it as a spare.

 

Thanks

[Techman]

Can I assume that if I am getting devices randomly turning on with nothing in the log indicating an activation and the status of the device not being correct, that I have a failing plm. I replaced it on Aug 10 2016. However it is older than that because I bought it as a spare.

 

Thanks

 

Most likely

 

What's the version and date code on the PLM?

[stusviews]

Can I assume that if I am getting devices randomly turning on with nothing in the log indicating an activation and the status of the device not being correct, that I have a failing plm. I replaced it on Aug 10 2016. However it is older than that because I bought it as a spare.

 

Thanks

 

Mostly, age implies time in use.

[Brian H]

Can I assume that if I am getting devices randomly turning on with nothing in the log indicating an activation and the status of the device not being correct, that I have a failing plm. I replaced it on Aug 10 2016. However it is older than that because I bought it as a spare.

 

Thanks

Not necessarily the PLM.

Do a search here. There are a few All On, All Off and maybe random changes. In threads here. Not related to a PLM.

[larryllix]

Mine appeared to be a "run-away program" inside an OnOff module that was sending out a bad Scene On code, after ISY would switch it on or off.

 

I don't believe Scenes send out status changes from devices so there is no logging of status changes.

 

This drove me crazy for months changing and turning on certain lights at random. I could query the affected units and find exact dimming levels.  Then I recognised the pattern as a scene I created. ISY had no awareness of the event or levels.

 

I still use the module  to control my humidifier. Ocasionally when ISY would cycle it, the ISY log would show a bad response. After unplugging the module and then plugging it back in, it hasn't done it again since last fall. It seems it would send out a totally unrelated Scene On code, instead of an ACK.

 

PLM was not involved with this. Insteon modules contain CPUs running code and can go into runaway loops just like any other software.

[BigMoose1]

Thanks everyone for your thoughts and ideas. My plm is a V1.B 1403.

 

I have reread some of the issues on the forum. This is the first all on event I have ever had so I retraced my recent activity. I just put in a 2477S and a 6 button switch. I factory reset theses devices and I also increased the wait time before turning off the backlights on my 6 button switch.

 

In the previous Plm that failed, I replaced the capacitors so if I get the event again I will probably replace the plm with this reworked one.

 

The all on event impacted the insteon bulbs that I have and the bricks. None off my insteon outlets or switches were turned on.

[BigMoose1]

Forgot to mention the operational time for the current PLM is just under 11 months since I bought it as a Spare unit.