mitchmitchell Posted June 23, 2017 Posted June 23, 2017 Tonight we came home and Alexa reports all ISY devices as "not responding". I can login into the ISY Portal and refresh devices and all looks ok. From the ISY I can control everything. I did the forget and discover and got no devices twice but they all came in the third time, but Alexa still reports them all not responding. Quote
mitchmitchell Posted June 23, 2017 Author Posted June 23, 2017 Now the Alexa smarthome portal shows all the devices offline. Is anyone else having trouble? Quote
lgilsenberg Posted June 23, 2017 Posted June 23, 2017 I am having the same problem. Alexa reporting "Not Responding" and Alexa app shows all devices offline. Quote
dbuss Posted June 23, 2017 Posted June 23, 2017 Same problem here.Seems to be working now. Sent from my XT1650 using Tapatalk Quote
webminster Posted June 23, 2017 Posted June 23, 2017 (edited) AWS is reporting a lot of service problems at least in N. Virginia area, and the Web page for Alexa says "we are experiencing technical difficulties." So it's the Echo that's sick. Mine is erratic, only works occasionally. https://status.aws.amazon.com/ Edited June 23, 2017 by webminster Quote
mitchmitchell Posted June 23, 2017 Author Posted June 23, 2017 Yeah, mine seems to be working intermittently Quote
mitchmitchell Posted June 23, 2017 Author Posted June 23, 2017 I asked Alexa what her status was and she did not understand how to respond to that so I provided feedback -- it would be nice if she could report service problems if she is working enough to respond at all. Ok, now I'm calling a computer 'she' -- we are being assimilated. Quote
Michel Kohanim Posted June 23, 2017 Posted June 23, 2017 Hello everyone, We are investigating but it does seem to be AWS in the east. We'll keep you posted. With kind regards, Michel 1 Quote
Michel Kohanim Posted June 23, 2017 Posted June 23, 2017 Hi all, Definitely AWS Lambda related. Unfortunately, there's no ETA. We'll keep you posted. With kind regards, Michel 1 Quote
Xathros Posted June 23, 2017 Posted June 23, 2017 I can confirm the same problem from Vermont. -Xathros Quote
mitchmitchell Posted June 23, 2017 Author Posted June 23, 2017 (edited) Quick thread hijack (does it count if I started it? Xathros -- I see you have Emoncms -- what type of sensor did you buy to use it in the US? Edited June 23, 2017 by mitchmitchell Quote
Michel Kohanim Posted June 23, 2017 Posted June 23, 2017 FYI from Amazon : "8:48 PM PDT We have identified issues in AWS Lambda's capacity subsystem related to the increased API error rates and latencies in the US-EAST-1 Region and continue to work toward resolution." With kind regards, Michel Quote
maxnorth Posted June 23, 2017 Posted June 23, 2017 Same problem in California. All skills and SmartHome, not just ISY. Quote
nickp Posted June 23, 2017 Posted June 23, 2017 (edited) My Alexa "smart home skills" did not list the ISY. I added the "ISY Optimized for SmartHome v2". I told it to forget my devices, and them re-discover them. It found nothing... Arrgh... After hitting discover a bunch of times, everything has finally come back. However "turn on desk lights" will result in "desk lights is not responding". Come on - let there be light. Edited June 23, 2017 by nickp Quote
MWareman Posted June 23, 2017 Posted June 23, 2017 FYI from Amazon : "8:48 PM PDT We have identified issues in AWS Lambda's capacity subsystem related to the increased API error rates and latencies in the US-EAST-1 Region and continue to work toward resolution." With kind regards, Michel Good to know. My daughter was pretty stressed out last night because all our FireTVs lost their connection to Amazon and stopped working for a bit. Other devices on the network were fine, so I assumed it was AWS related. Now I have a ton of stuff at work to check... Since we use Lamda for a ton of stuff... Quote
MWareman Posted June 23, 2017 Posted June 23, 2017 (edited) Interesting. Looking at my AWS dashboard, it seems that AWS retried and processed the queue. So, I likely didn't miss any notifications generated. Given that Alexa apparently uses this subsystem, I wonder if anyone had Alexa commands process hours after the instruction was issued... Edited June 23, 2017 by MWareman Quote
bmercier Posted June 23, 2017 Posted June 23, 2017 Interesting. Looking at my AWS dashboard, it seems that AWS retried and processed the queue. So, I likely didn't miss any notifications generated. Given that Alexa apparently uses this subsystem, I wonder if anyone had Alexa commands process hours after the instruction was issued... Good question. I looked at the logs, searching specifically for device discovery requests. Those are sent every hour or so for every ISY. I can see erratic request for about 5 hours, and definitely 2 major drops in that period. I don't see spikes after it recovered. It may be that device discoveries were blocked before hitting our lambda function. Benoit 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.