I was doing some electrical work earlier today, and the circuit that my EISY is powered from was power cycled in the process. When I flipped the breaker back on, I heard a few notification tones on my phone and assumed it was the result of my EISY rebooting.

When I checked my phone later, I saw a message from UDMobile stating that an upgrade had completed, along with a notification that another upgrade was available. And as nightfall approached, I noticed that none of my indoor and outdoor timed lighting had turned on as it should. I pulled up the admin console and received a warning about available updates that were required. I also noticed that I couldn't manually turn any lighting on or off.

I've had my EISY about 9 months and had not upgraded any of its firmware since I acquired it. In my case all lighting control is 100% Insteon based. After having owned an ISY for 10 years previous, and realizing that 5.9.1 had been available for some time, I was also a bit surprised that the EISY had apparently taken the liberty to do an upgrade on its own without my requesting or initiating it.  And after reading the release notes that the upgrade note referred to, it sounded as if it may have only partially installed all of the updates that were required. So, I opted to dive in and upgrade all packages. 

After repeated upgrade attempts in the hope that they would correct the problems I continue to have, It looks as if this took me from version 5.8.4 to 5.9.1, and then finally to 6.0.0. But in spite of all these upgrades, unfortunately my EISY is no longer humming along and quietly doing its thing every day as it had been for the past 9 months or so.  

The admin console does appear to be fully functional, and time of day clock is correct. If I check the Programs/Summary tab, all of my programs appear to running according to schedule, but none of the scheduled Insteon ON/OFF actions appear to be occurring under program control as they should be. 

When I first start the admin console a few different error messages appear (see attached). And any time I attempt to manually issue an Insteon ON/OFF command a "Request Failed" error message pops up and the controlled item fails to respond. I assume the same thing is happening behind the scenes when a program attempts to turn something on or off.

I'd greatly appreciate it if anyone else has any ideas of what else needs to be done to bring my EISY back to life. I've heard many others speak very positively about the quality of UDI's support and I'm confident we'll be able to correct this situation in short order once its referred to the right people.

In my own case, my past experience with UDI and my ISY has been so good that I've never had a need to create and submit a support ticket.  If someone could kindly advise me as to how to go about doing so, I'd greatly appreciate that as well. Thanks in advance for your assistance.

 

 

 

 

 

1 hour ago, Vwas said:

I'd greatly appreciate it if anyone else has any ideas of what else needs to be done to bring my EISY back to life.

I seem to recall some people mentioning that the "Insteon Support" checkbox became unchecked after an update.  So you might goto the "Configuration" tab and make sure that the "Insteon Support" checkbox is indeed checked.

Great advice, and I wish the fix was that easy. Unfortunately the "Insteon Support" box is checked. I finally navigated around my way around the main UDI web site and figured out how to submit a support ticket. When we hopefully get things fixed, I'll post the solution here in case anyone else runs into the same situation. Thanks again.

Well, it turns out that two totally unrelated events happened concurrently, and falsely led me to believe that a firmware update had gone bad and caused my EISY to lose its Insteon control capabilities. In the end, the root cause of my problems turned out to be a failed PLM. 

It appears that my PLM likely failed as a result of my repeatedly switching each of the circuit breakers in my breaker panel on and off. I was attempting to identify all of the loads connected to each circuit in the panel, in preparation for installing a whole house energy monitor on the circuits with the largest loads. Presumably, a transient was created on the power line when one of the breakers was switched OFF and it damaged the PLM. 

I'm unsure as to whether my power cycling activities had also unknowingly kicked off a pending firmware update due to an EISY reboot, or if UD had coincidentally pushed out an update to my EISY in the midst of my circuit mapping activities.

When I returned from the basement, I noticed that there were firmware update and EISY restart notifications from UD Mobile on my phone. I also noticed that none of my timer initiated lighting scenes had turned on when scheduled. I tried to turn on the same lighting manually through UD mobile and the admin console and also found them both to be non responsive.

Naturally, my first inclination was to presume that this non-functionality was somehow related to the firmware update. My bigger fear was that I might have also unknowingly corrupted the firmware update by killing the power to the EISY in the midst of it.

So I submitted a support ticket, Michel promptly responded, and we quickly determined that the EISY firmware and UI versions had both successfully been upgraded to 6.0.0. We also found that my PLM was non responsive. 

I'd purchased a new USB PLM when I migrated from ISY to EISY last December. USB PLMs are currently out of stock on the Insteon web site and aren't due back until sometime in November. Fortunately, the serial PLM that I'd been using with my ISY is still functional and had only been in service for about a year. 

So, I ordered a serial PLM adapter kit from UD to get things back up and running, and it arrived today. I did a factory reset on the serial PLM and connected it to the EISY earlier this evening. After doing a Restore PLM, I'm happy to report that all is back to normal and my EISY is able to properly control all of my Insteon devices once again.

Thanks to Michel and the rest of the UD team for walking me through the debug and getting me up and running again!