Jump to content
C4 Forums | Control4

Alexa "The device is not responding"


Recommended Posts


On ‎08‎/‎10‎/‎2016 at 7:05 AM, South Africa C4 user said:

In terms of Alexa, I can no longer get her to Discover any of the Control4 devices... Even if I change some of the device names / enabled devices in my Control4 and rerun discovery, Alexa tells me she discovers no devices...

Very frustrating :-( 

Are up and running or do you think they have figured out your not in US ?

Link to comment
Share on other sites

9 hours ago, Gary Leeds UK said:

Are up and running or do you think they have figured out your not in US ?

Unfortunately, I am still down... very sad... perhaps you are right and the secret police figured out that South Africa is not, in fact an American state! But I am not sure as I still see the Control4 skill in the Alexa app.

I tried adding an advanced lighting scene and it did not appear in mycontrol4 (admittedly, I only did this 15 minutes ago - maybe I need to wait longer).

I am considering deleting the skill and re-adding it... but that would be irritating (even if it works) as I changed the names of almost all of my 100 odd lights and most of my 100 odd advanced lighting scenes...

Link to comment
Share on other sites

10 hours ago, Gary Leeds UK said:

Are up and running or do you think they have figured out your not in US ?

I'm back! South Africans are still honorary Americans!

Interestingly, not only am I back, but everything is now pretty much instantaneous where it was quite slow previously... and the only response I am getting from Alexa (so far) is OK... which is exactly what one wants. None of this device not being found nonsense.

All I did was disable the skill in the Alexa App and then re-enable it.  Interestingly, I did not lose any of the name changes that I had done for devices in MyControl4 which was a big plus!

Of course, the big question I have is why / how did the connection get broken?

Link to comment
Share on other sites

2 minutes ago, South Africa C4 user said:

I'm back! South Africans are still honorary Americans!

Interestingly, not only am I back, but everything is now pretty much instantaneous where it was quite slow previously... and the only response I am getting from Alexa (so far) is OK... which is exactly what one wants. None of this device not being found nonsense.

All I did was disable the skill in the Alexa App and then re-enable it.  Interestingly, I did not lose any of the name changes that I had done for devices in MyControl4 which was a big plus!

Of course, the big question I have is why / how did the connection get broken?

I don't mean to rain on your parade, but I'm not getting consistent behavior yet. I was, now I'm not. I was, then I wasn't. Kind of like an Aggie checking a turn signal. "Now it's working. Now it's not. Now it's working. Now it's not." Hope yours keeps working great. 

Link to comment
Share on other sites

1 minute ago, Elvis said:

I don't mean to rain on your parade, but I'm not getting consistent behavior yet. I was, now I'm not. I was, then I wasn't. Kind of like an Aggie checking a turn signal. "Now it's working. Now it's not. Now it's working. Now it's not." Hope yours keeps working great. 

Thanks an I hear you... At least I am back for a while :)

Link to comment
Share on other sites

1 hour ago, Elvis said:

I don't mean to rain on your parade, but I'm not getting consistent behavior yet. I was, now I'm not. I was, then I wasn't. Kind of like an Aggie checking a turn signal. "Now it's working. Now it's not. Now it's working. Now it's not." Hope yours keeps working great. 

As a Longhorn fan.. That just made my day.. Lol

Link to comment
Share on other sites

  • 3 years later...

Has anyone figured out a fix for this yet? About a third of the time, when I give a command to Alexa that has to do with Control4, it will give the error that the device is not responding, but it executes the action every time. This is very annoying and makes for a terrible client demo. Can I fix this somehow?

Link to comment
Share on other sites

On 11/14/2019 at 7:02 AM, Aayush Arya said:

Has anyone figured out a fix for this yet? About a third of the time, when I give a command to Alexa that has to do with Control4, it will give the error that the device is not responding, but it executes the action every time. This is very annoying and makes for a terrible client demo. Can I fix this somehow?

I was reading this thread thinking - Great, they are looking into it.... then I saw this was from 2016...
I still have this problem about every 1 in 5.
Alexa says the device is not responding, then the command is executed...

very slow first command, then second and third seem to complete much quicker.

Link to comment
Share on other sites

On 9/29/2016 at 11:55 PM, Elvis said:

I usually get a long delay and then Alexa saying, "The device is not responding." When this happens, there is a chance that Control4 will respond. I've run discovery and checked the customer.control4.com portal, etc.

Just not very consistent and wondering why?

All my other Alexa skills are running full speed. This only seems to be a Control4 issue.

have the same issue and also only C4 gear, unable to figure out why

any help would be fabulous

Link to comment
Share on other sites

It could be a C4 specific issue.

Alexa smart home API has a few parts:

  1. Device recognition and control:  Basically the voice translation mapping to one of your device commands (previously found in discovery).  If this fails, you will get "I don't have a device named X" or "I don't recognize that" etc.   This is all Amazon.
  2. The device command then goes to the Lambda function in the cloud (written by C4 in this case).  The function basically translates from Amazon API to the API used by C4's 4sight  (They might also use an intermediate cloud server as well).  Any error or TIMEOUT returned by this function results in "The device is not responding".
  3. The command eventually gets routed to your Controller, which executes it accordingly

So if you are getting the error message from #2, most likely it is your 4Sight connection or the (possible) C4 intermediate cloud server that is too slow to respond or broken.  Given that your command DID execute it would indicate C4 was too slow to respond so the function timed out.  

You can try using our SimpleC4 skill to see if it works better for you.  We have our own Lambda functions, Cloud servers, and Firebase connections back to C4.  Unless your internet is down, it should be reliable.

 

Link to comment
Share on other sites

On 11/15/2019 at 1:30 AM, Mike_S101 said:

have the same issue and also only C4 gear, unable to figure out why

any help would be fabulous

I disassembled my rack and C4 back in June. At that time, Alexa/C4 skill was still erratic. It worked, but the speed was very inconsistent. Other skills used in the house were consistently responsive, and without any annoying lag. I'm sure it is all a conspiracy on Amazon's part. No way it could be a C4 problem.

Link to comment
Share on other sites

  • 5 months later...
7 minutes ago, drmark12pa said:

Has anyone been experiencing this issue once again?  I cannot get my devices to be recognized no matter what I've done.  Disabled/reenabled skill, refresh on MyControl, discover devices (no new devices found)… etc.

if it was within the past hour is it probably because of this:

https://status.control4.com/incidents/ndbt4fbcfkj4

 

 

 

 

Token Authentication service upgrade

 

Incident status: Monitoring

 

Rollback is complete. All devices will need to reathenticate again. Therefore, on mobile devices, customers will need to "Remove System" in Settings and re-enter their credentials. This should only impact users who have tried to authenticate over the last hour since the upgraded was attempted.

 

Time posted

 

Apr 20, 12:25 MDT

 

Components affected

 

 

Degraded Performance

customer.control4.com

 

Degraded Performance

my.control4.com

 

Degraded Performance

Alexa

 

Degraded Performance

Google Assistant

 

Degraded Performance

Remote Composer Pro

...and 1 more component.

 
Link to comment
Share on other sites

4 minutes ago, vstar said:

if it was within the past hour is it probably because of this:

 

What system needs to be removed?  Is this on the Control4 side or Alexa side of things?

I just tried disabling the Control4 skill on Alexa and then re-enable and it says "We were unable to link Control4 at this time"... I'm assuming there is an issue with C4 at this time?

Link to comment
Share on other sites

It has now been two years since the original post and the reply that "control4 is aware and is working on it". I still continue to have the issue with the Echo and the delay in responding to a command.  anyone have an update?  thanks

 

Link to comment
Share on other sites

Thanks for responding -  when you say "Epic" driver is that the title of the driver or type for the Alexa/Dot driver?  Could you give me the complete driver name that would be found in the Composer software search?

thanks again!

 

Link to comment
Share on other sites

5 hours ago, Ray1013 said:

Thanks for responding -  when you say "Epic" driver is that the title of the driver or type for the Alexa/Dot driver?  Could you give me the complete driver name that would be found in the Composer software search?

thanks again!

 

This is not free driver, check https://www.epic-systems.com, you need only echo Gen 1 in your project rest can be any version. Simply you control C4 locally without Internet or dependency on C4!

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.