Amazon Echo Wall Clock no longer available due to connectivity issues

Amazon has stopped selling the Echo Wall Clock because some are experiencing connectivity issues. The Alexa gadget’s product page now says “currently unavailable” and can no longer be ordered. In a statement to The Verge, Amazon says “We’re aware that a small number of customers have had issues with connectivity. We’re working hard to address this and plan to make Echo Wall Clock available again in the coming weeks.”

I just tried setting a timer on the Echo Show that my Echo Wall Clock is paired with and, sure enough, the clock did not react to the timer as it should have. Checking the Echo Show’s Bluetooth settings showed that the clock was disconnected. I hadn’t noticed that it disconnected because I rarely use timers and it was still displaying the correct time. Popping out one of the clock’s 4 AA batteries and putting it back in was enough to get my clock to reconnect to the Echo Show on its own and it’s once again reacting to timers, alarms, and notifications.

It’s unknown at this time if the connectivity issue can be fixed with a simple software update or if it requires the hardware to be changed. The issue might stem from the fact that the Echo Wall Clock temporarily loses its connection to the Echo it’s paired with when multi-room audio is played. Hopefully, the fact that Amazon expects to have the issue resolved “in the coming weeks” means it’s an easy fix.

  1. Dave says:

    If only a “small number of customers have had issues with connectivity”, then why does Amazon feel the need to discontinue selling this product? Sounds like politician speak to me.

  2. Carlos says:

    Mine kept dropping connection, but the replacement they sent has worked fine for weeks without a single issue.

    I think they need to add a cover to the clock because it’s too easy to bump the hands or pull them out entirely.

  3. Sebastien says:

    My echo wall clock was having connections problems. After resetting and configuring, the echo wall clock updated from version 73 to 86. No problem since then. I am wondering if it is the real fix or it is just coincidence

Leave a Reply

Your email address will not be published. Required fields are marked *


Get AFTVnews articles in your inbox!

Get an email anytime a new article is published.
No Spam EVER and Cancel Anytime.