AnonymousNovember 4, 2008 at 1:01 amPost count: 3
My EZSrve unit failed and displayed a PLM No Response Error dialog when I logged in through the web interface.
I rebooted the EZSrve unit. It worked fine.
Can any one shed any light on this error, i.e., what might have caused it or how it can be avoided in the future?
Also, many other web-based systems include the ability to send email messages that can be end-user configured to send error messages, system alerts and status change notifications. It would be great if such a capability could be added to EZSrve.AnonymousNovember 4, 2008 at 1:28 amPost count: 1001
Look for conditions where multiple timers and/or macros are being triggered at the same time. Spread the firing times of coincident timers and add a few second delay with the After Delaying: field of macros.AnonymousNovember 5, 2008 at 5:58 amPost count: 3
I did before I encountered the problem that caused me to post my original message.AnonymousNovember 5, 2008 at 6:20 amPost count: 1001
Two points. First, in your other post you mentioned coincident timers causing a problem, no mention that an interaction of a timer and a macro or coincident macros can have the same result. Second, someone looking through the list of Topics for a symptom they are having may well find this Topic and not see your other post. I thought it important for the next person to benefit from your post who has the same symptom to have the complete information in one location. I apologize for any offense.AnonymousJanuary 18, 2009 at 1:25 pmPost count: 29
I have started having this error in the last couple months. I have to physically cycle the power on the EZSrve to make it work again. It happens for a few days then is ok for a couple weeks. Grif, are you suggesting that it is caused by simultaneous macros/timers? I have several macros that trigger on sunrise. I thought I remembered seeing something about a defect in the PLM causing this but I can’t seem to find it in the forums any more.AnonymousJanuary 18, 2009 at 3:31 pmPost count: 1001
Simultaneous execution of Timers/Macros can cause the PLM to lock up where even an EZSrve Restart does not unlock. Pulling the plug seems to be the only solution once it is locked up. If you fire multiple Timers at Sunrise, do the second at Sunrise+ 1 mm, the third at Sunrise+2 mm, etc. If the Timers are working on individual Insteon devices, you can create a Group/Scene with each Insteon Device a responder and then have a single Timer control the Group/Scene. For Macros use the After Delaying: function to add a few seconds between simultaneous executions. SHN has made changes to EZSrve to reduce the lockup exposure but as you have experienced it has not been eliminated completely.AnonymousJanuary 21, 2009 at 9:33 pmPost count: 9
I’m having a similar issue also and it seems intermittent. It’s been rock solid for months, then in January 09 it starts with the “No Response Error”.
I had an Insteon device (Appliance Link) controlling a lamp on and off and it stopped working or throwing the “No Response” message when I tried to command it on without the timer. I removed the area, Timer, device and tried to re-add it and get the “No Response Error”. I thought maybe the Appliance Link was bad so I tried a spare I had and the same thing. I’ve unplugged, restarted and still nothing. Other x10 are unreliable on timers, but work when manually commanded through the EZServe. Any ideas what to try?AnonymousJanuary 21, 2009 at 10:26 pmPost count: 55
One thing you didn’t mention is whether you added any new electrical devices to your environment. Although Insteon is less susceptible to interference than X10, I’ve had to troubleshoot by unplugging things and putting in filters. What happens if you plug in your ApplianceLinc somewhere else, ideally close to the EZSrve?AnonymousJanuary 21, 2009 at 11:47 pmPost count: 192
I would also think real carefully on anything new electrically or an old device moved to a new location. In other automation forums we see things like a new cell phone charger or electronically controlled washer dryer make big problems to name a few.AnonymousJanuary 22, 2009 at 4:34 amPost count: 1001
The suggestions in the previous posts are all good things to look at. Was not clear if you still have a solid “PLM no response” condition. If you do unplug EZSrve for about 30 seconds and then plug it back in without pressing any buttons. Once the PLM has locked up it is generally necessary to unplug the EZSrve to clear. Restarting EZSrve has not been successful in the past unlocking the PLM. The only time I have seen the PLM lock up is when multiple Timer/Macro events are running at the same time. Multiple Timers triggered at the same time, multiple Macros being triggered from the same event, running at the same time, etc. It is not the fact that multiple Timers/Macros are running per say, but that they generate near simultaneous traffic to the PLM which can have a problem handling that kind of traffic.
Can you expand on what the Timers are doing with the X10 devices. How many X10 devices are you controlling at the same time. Are the X10 devices on the same 120V leg as the EZSrve. If not do you have X10 specific phase couplers installed. The Insteon phase couplers do not couple X10 messages. Smarthome has a BoosterLinc device which amplifies X10 that may improve X10 communications.AnonymousJanuary 22, 2009 at 5:34 pmPost count: 9
Thanks for the responses. I did check for new things plugged in or old things moved and nothing is real evident. Had all the christmas lights working pretty well through the beginning of January. Then unplugged x10 modules, deleted timers, areas, devices and put them away until next season. Seems like after that the EZServe got flaky. I have a hardwired x10 phase coupler and also a pair of insteon phase couplers so they should bridge any traffic between phases.
I’m not running a lot of x10 at the moment with just a living room lamp and a hallway nightlight automated on schedules. I had much more running with the holiday season, but as I mentioned that is all removed now. I will review Timer schedules to see if there is any conflict, but I think I’ve checked that already.
I have had the EZServe unplugged, let it sit for a while and then plugged it back in and the same results. I have not been able to successfully add a new insteon device without getting the “PLM No response error” since this thing started going flaky. I was thinking of saving all my *.xml files from the device and resetting to factory and reloading. Pretty extreme but I don’t know what else to try.AnonymousFebruary 5, 2009 at 12:58 pmPost count: 29
Before you save your .xml files, be sure to clear the cache in your browser. I have seen situations where the browser used the old cached version of the xml file instead of getting a fresh version.
- You must be logged in to reply to this topic.