Author |
|
BwiggleS Newbie
Joined: October 26 2009 Location: Canada
Online Status: Offline Posts: 35
|
Posted: November 13 2011 at 00:06 | IP Logged
|
|
|
I am trying to figure out why some Insteon devices in my house stop working at different times. I have 4 wireless access points and I have a switch and receptacle that are very flaky.
Previously I had a laptop that when I plugged in the power supply my bus shelter controller (2477) would stop responding.
Now I have installed these two devices (switch and receptacle) and the switch worked at first when I installed it but now, nothing but NAK on the comm stats.
I have a wired in phase coupler coming but with the access points I doubt it will help.
So what I want to do is start tracking the comm stats. My plan is to poll the device status every 10 minutes and use a counter, after 5 consecutive fails I want to send an event message to the log saying the date/time and what device failed.
I need some help figuring out which power home commands to use. Plus any suggestions or advice on what other people use to figure out the comms issues and how other people monitor the communications would be great.
Thanks,
Brad
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: November 13 2011 at 01:10 | IP Logged
|
|
|
Having fought some of the same problems… First don’t get near any surge protectors, power supplies as in computers a laptop or otherwise. You didn’t indicate whether your access points were Dual Band or not but placing the access points in the right locations to hop the noise is critical. Phase coupling is a solid failure when a 220 appliance is not on. If you haven’t tried this trick plug the access point into the plm/plc like piggy back style and place another one within close range to see if that improves the signal. Having said that I use ph_getinsteonlevelrt to verify my stability and when the level I have set in a global doesn’t match what was return I go into my own error recovery routines. In your case you could be upping a counter. I trigger it with dev chg with any. Once you get things settled down you can gate the checking by every 10 or 20 events as using the getinsteonlevelrt will slow you down especially while waiting for an ack. In my list of devices between every device check I place a minimum wait if another macro wants to jump in. If you go this route us the cmd with rt as it waits for the device to respond not what’s in the database. Good luck….
__________________ Pete - X10 Oldie
|
Back to Top |
|
|
BwiggleS Newbie
Joined: October 26 2009 Location: Canada
Online Status: Offline Posts: 35
|
Posted: November 13 2011 at 18:51 | IP Logged
|
|
|
I took your advice on moving an access point to the modem. I also moved my pc UPS to a different outlet on a filter linc. Still no go on the lights.
I took off the switch and set it up with an extension cord so I could test it, still nothing. Then checked address, I had a 5 instead of F.
Comms are pretty good now
Thanks for help with the polling of device status.
Brad
|
Back to Top |
|
|
BeachBum Super User
Joined: April 11 2007 Location: United States
Online Status: Offline Posts: 1880
|
Posted: November 13 2011 at 19:53 | IP Logged
|
|
|
Usually this problem is caused by noise at the 10% crossover on the 110 sine wave. If that is the problem then it becomes a game of isolation which you are experiencing. I’m going to assume you have a PLM if so you might try factory reset followed by a PH Clear then a FULL reload just in case you may have something squirrely going on with the device. The other thing is to watch the Insteon trace (log ) and see if you are getting red timeouts in the trace and identify what is causing those addresses to fail. You’re definitely moving in the right direction. Thing that will also screw things up are CFLs, track lights and florescence lights. The CFLs will sneak up on you as they are becoming popular. I only use those that are dimmable and I have not had a problem so far. But my tracs are so bad I have to use X10 to drive them.
__________________ Pete - X10 Oldie
|
Back to Top |
|
|