Echo stopped working.In the portal it said the ISY has been off line since 3 am this morning..

Any ideas how to fix this

 

Thanks

Paul

There are a couple threads in the portal forum talking about overnight portal issues. A quick ISY reboot solved the problem for me.

fixed it thanks

Perhaps this is accounting for my problems with Connected Home: Although I've changed nothing with my configuration, as of last evening  when I issue a request to turn on/off a previously discovered device I get a new error response "Sorry the device XXXX is not responding. Please check its network connection and power supply." Interestingly, the IZZY skill works fine with the same device. Apparently Amazon has made some change. I'll try rebooting IZZY and report my results.

I got same message about 3:00 am. Is it coincidence that is same time as nightly query all?

I got same message about 3:00 am. Is it coincidence that is same time as nightly query all?

 

Paul, no. Are you on central time? It was 4:01am for me on ET.

 

Paul

Paul, I am on central time.

Just an observation, but to an outsider, we would likely appear to be some pretty wacky folks. Who other than true geeks would be troubleshooting their smarthomes at 3 (or 4) in the morning. I'm not sure exactly why time I began experiencing the problem, but I believe it was around then for me as well.

Woke up this morning after a late night and found the Echo's not working. Got the "Sorry the device XXXX is not responding. Please check its network connection and power supply." message on both echo's.  Tried a reboot and that did not clear it up, in fact the ISY was having a hard time starting up. The ISY was acting very sluggish with "System Busy" being displayed. I rebooted the network switch that the ISY is connected to and then rebooted the ISY.  Gave it a few minutes and started the Admin console. The ISY came up normally and was its usual responsive self. Tried the Echo's and they are now working as they were before.

 

Bottom line: I suspect the network switch got hosed up during some thunderstorms last night even though it is sitting on a UPS as are all the electronics in the house.

 

There is nothing foolproof in the world of software driven devices, stuff happens. As along as it easily recoverable I am okay.  Not happy, but okay. 

 

For information purposes; I have 99 connected devices and all voice operations start with the two Echos which deal with the ISY. I have a Proxy that runs on a RPi that handles special network commands from the ISY that are triggered by the Echo via a set of simple programs. For example "Alexa, turn on the Kitchen T V" will cause the ISY to send a simple "DOIR House,1,ITV,Power" command to the proxy which then sends the appropriate timing strings to a Global Cache named "House" using the first port of that GC device. The "power" entry in the timing tables for the device ITV (Insignia TV) will be used. The Proxy handles my Pool/SPA control system and my Home Theater in a similar manner but not via IR but rather TCP.  The Proxy also handles the Skill I started to develop, but stopped as the Work by ISY to implement the connected home now handles about 98% of my needs. One of these days I will get back to finishing the Skill (Sarah).

 

If you are interested in the Proxy drop me an eMail and if there is enough interest I will write up a detailed User document and make it available.  BEWARE: To use it for other than IR, you need to be able to deal with javascript and using TCP or whatever your end point device needs. 

I am interested -- sent PM.

Edited March 26, 20169 yr by hart2hart

My portal still says ISY offline.  I have rebooted the ISY several times.  Anyone have any ideas??

I had the same offline message this morning.  A reboot a few minutes ago (of the ISY) fixed it.  Love it so damm much!

I tried to just reboot the ISY and it did not work.. I had to reboot modem, router, and ISY then it was ok.

 

It seems to much of  a coincidence that so many people had this problem over night.  I'm in New England so I doubt a t-storm in Florida impacted me.  I think something else was the root cause, perhaps at the portal since that is common to all of us.

 

Just a thought.

More information is available in this parallel thread

 

http://forum.universal-devices.com/topic/18605-3-26-16-portal-issue/

I agree, it was not the thunderstorm. When I rebooted my ISY the first time it was very sluggish and system Busy" just stayed up.  I reset the switch and again rebooted the ISY.  This time the ISY came up properly and when I tried the Echo it was fine.

A simple reboot of IZZY took care of this for me. Given the number of us effected I feel pretty sure we all didn't suffer a simultaneous power outage;-) 

I'm a little taken aback that the ISY Portal would have any direct impact on the NIC on the controller. Its apparent to me the cloud portal service was allowed to impact the network attributes of the controller itself.

 

This should never be the case . . .

 

I try to limit the use of the phrase impossible when talking about certain things in life. But in this case its near impossible everyone had a off line condition and many of us found the actual controllers NIC also not being seen by the modem / router.

 

On a related matter I have stated this problem several times over the years. Since 4.XX firmware the controller does not respect the soft reboot and many times requires a hard reboot where the power must be removed for the controller to come back on line in a good known state.

 

Everyday I thank God I spent the little amount of money on a remote web power switch. I can't even imagine asking someone to come to my home and to pull the power from some random electronic device in my home!

 

Just to bring it back to life . . .

A simple reboot of IZZY took care of this for me. Given the number of us effected I feel pretty sure we all didn't suffer a simultaneous power outage;-) 

 

How did you reboot "IZZY?"  BTW, I wasn't affected by the stoppage.

By "reboot" I mean to say power-cycled.

By "reboot" I mean to say power-cycled.

 

I'm still confused. AFAIK, Izzy is an echo skill. So, what specifically did you power cycle (i.e., remove and restore power)?

a cold start or reboot resets all the firmware in the ISY to a known state.  As with many software controlled devices this serves to clean up issues, at least for a while. As an example lets say a bug in the ISY connected home code/ISY code causes the ISY to get into an illogical state due to some garbage transmission. A reboot will put the ISY back to a well known state  

Hello everyone,

 

Sincere apologies ... we found the issue and it has been fixed.

 

With kind regards,

Michel