Alexa can't find device

Avatar
Jean Michel
  • updated
  • Under review

Hello everyone! 

My Alexa has always worked well. But about 2 days ago it doesn't work anymore...

It no longer responds to devices already configured, and after deleting and registering again, there is no longer any device ... despite everything being configured correctly, I say this because they already worked well. WAN port is ok and Skill also connects well.

Reading in some old threads, I saw that sometimes it stopped working, people asked for support, you checked and it started working again... Is it any of these cases, some incompatibility with the update or something? By the way, someone else with problems with Alexa? Haha ha

Thank you for your support!

Replies 6
Avatar
0
Calin Birtocean
Quote from Calin Birtocean

I am having the same issue, at one point it stopped working. Now I am unable to make it work again. Alexa is not finding any new devices.

Any thoughts?

Regards,

Calin

Thanks to Andraž - problem solved, the server public IP was missing. I may have lost it when the internet provider was changed.

Avatar
0
Calin Birtocean

I am having the same issue, at one point it stopped working. Now I am unable to make it work again. Alexa is not finding any new devices.

Any thoughts?

Regards,

Calin

Avatar
0
ComfortClick Support

Hello, 

it is strange that device stopped working without changing anything. Even if you change devices name it should work normally. We did some additional testing and even when changing the endpoint name (after including it in Alexa API) devices still work normally. So we can't say for sure why devices stopped working.

Best regards

Avatar
0
Jean Michel

Updating:

I found the problem, but I still don't understand why hahaha

There in Alexa's API, after deleting and reprogramming 237 times, at last I decided to change the default name of "Endpoint" to any other name, I reprogrammed the Skill (for the 237 time hehe) and MANUALLY changed the node/Endpoint name there. .. Recognized everything again now!

Why by the default name was no longer recognizing? (detail that it always worked like this)... I have no idea!

But here's the information in case anyone else needs it!

Team, thank you for your feedback and attention, and here's the reflection, if you have an answer, I'll be waiting :D

Avatar
0
Jean Michel

ok, but as I said, the network is the same as when everything was working, including the external access of the bOS, which is working very well... It's only Alexa's services that with Comfortclick that isn't working (but it was ).

Do I need to release any other specified ports now? Out to 443?

Avatar
0
ComfortClick Support
  • Under review

Hello.

when people contacted us for support regarding Alexa there were always issues with network (different IP settings, wrong ports etc. )

Best regards


Customer support portal powered by UserEcho