Don Cohen Posted November 10, 2020 Share Posted November 10, 2020 Out of nowhere, I woke up this morning to find that every voice command to Alexa results in "x-device is not responding." Everything was fine yesterday. No other network or connectivity problems present. 4Sight is active, and confirmed to be active when I log into 'customer.control4.com'. Other non-Control4 voice commands to Alexa seem to be working fine (what time is it and so forth). Control4 works fine via SR260, Android App, etc. I rebooted both devices - no change. I re-discovered devices - no change. I disabled the Control4 Skill within the Alexa App, and tried to re-enable it, receiving this error message: "We were unable to link Control4 at this time. Please try again later." I checked status.control4.com and no problems are currently identified there. Is anyone else experiencing problems? Any suggestions on what else I can try? Or is it just a matter of there being a glitch somewhere and I have to wait it out? Thanks. Quote Link to comment Share on other sites More sharing options...
msgreenf Posted November 10, 2020 Share Posted November 10, 2020 unlink the skill and relink it Quote Link to comment Share on other sites More sharing options...
Don Cohen Posted November 10, 2020 Author Share Posted November 10, 2020 1 minute ago, msgreenf said: unlink the skill and relink it Thanks for the quick reply - I had already done this, and I included the Error Message I received: "We were unable to link Control4 at this time.Please try again later." Quote Link to comment Share on other sites More sharing options...
Don Cohen Posted November 10, 2020 Author Share Posted November 10, 2020 Update: I tried to re-link again, and for whatever reason, this time it worked. I had given it a half hour or so before posting, but whatever glitch there was went away. I'm good to go now. Quote Link to comment Share on other sites More sharing options...
Don Cohen Posted June 20, 2021 Author Share Posted June 20, 2021 This problem recurred this morning. I've seen it from time to time in the past. Usually I unlink the accounts, reboot the controller, and then re-link the accounts. This time, it's not working, even after 2 controller reboots, and multiple attempts. It's been more than an hour now. I'm still getting: "We were unable to link Control4 at this time.Please try again later." Anybody else seeing this today, or it just a local quirk in my system? Quote Link to comment Share on other sites More sharing options...
Don Cohen Posted June 20, 2021 Author Share Posted June 20, 2021 Still unable to re-link. And now the Google Voice connection is also indicating it can't reach Control4. Seems like it has to be on the Control4 side of things. I checked the Control4 Status page, and no outages are currently reported. Nobody else? Quote Link to comment Share on other sites More sharing options...
Don Cohen Posted June 20, 2021 Author Share Posted June 20, 2021 The Status page has been updated: Google and Alexa voice services are currently unavailable for all customers. At least it's not some quirk in my system. Quote Link to comment Share on other sites More sharing options...
Matt Falce Posted June 20, 2021 Share Posted June 20, 2021 same thing going on here. Long Island, NY. In addition, which I assume it is all related that I unable to connect to my system once I am off my home network Quote Link to comment Share on other sites More sharing options...
Matt Falce Posted June 20, 2021 Share Posted June 20, 2021 Fantastic response. All fixed. Quote Link to comment Share on other sites More sharing options...
Don Cohen Posted June 20, 2021 Author Share Posted June 20, 2021 Yup. All good now. Quote Link to comment Share on other sites More sharing options...
HowardP Posted October 21, 2021 Share Posted October 21, 2021 The behavior here is a bit different. If idle for a while having not issued any commands through Alexa to the C4 skill, the first reply is “not responding.” When I ask immediately afterwards, it works properly. It will work properly for hours. And once idle again for a while, it will fail the same way. All non C4 commands succeed. It seems to me likely a bug in the skill. It’s incredibly annoying and completely predictable. Quote Link to comment Share on other sites More sharing options...
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.