Echo 1st Gen cannot connect (x55)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Echo 1st Gen cannot connect (x55)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Echo 1st Gen cannot connect (x55)
Echo 1st Gen cannot connect (x55)
2023-07-12 21:31:37
Model: Deco X55  
Hardware Version:
Firmware Version: 1.1.0

Just installed 3 x55 routers. Everything has reconnected fine (including the echo studio) except all of my gen 1 echo devices.

I have already tried:
* deactivating beamforming
* deativating 5ghz
* using 8.8.8.8 and 4.4.4.4 for DNS
* using the IoT Network
* removing the password
* deregistering the echo devices
* reseting the echo devices
* rebooting the routers

Help...

  0      
  0      
#1
Options
2 Reply
Re:Echo 1st Gen cannot connect (x55)
2023-07-13 02:15:25

  @AwesomeScott 

Hi, 

Have you tried the following combination:

IOT network+ no password+deactivating fast roaming

If yes but still failed to connect, would there be any error message?

Could you please help me test whether it could connect to a mobile hotspot?

 

Wait for your reply.

Thank you very much.

Best regards.

 

  0  
  0  
#2
Options
Re:Echo 1st Gen cannot connect (x55)
2023-07-13 14:13:04

  @David-TP 

Thanks for replying and giving me more debugging options. I think I have concluded that this is in fact an error with Amazon.

> IOT network+ no password+deactivating fast roaming

No Luck.

> If yes but still failed to connect, would there be any error message?

Using the mobile hotspot the error was:
"There was a problem setting up your device. Please try again."

Using the passwordless IOT network the error was:
"The password you entered was incorrect. Please try again."

The password message could be because that network is "saved" 

> Could you please help me test whether it could connect to a mobile hotspot?

No Luck. (This surprised me), so I just checked with my old nighthawk router and it won't connect to that anymore either, so this is probably an error with Amazon and the "deregistering" process. 

 

  0  
  0  
#3
Options