There will be times when you may receive an error message or encounter an issue
Hopefully you will find a fix from one of the items below!


No Speech Output

#

This is kind of a tricky one because it could be a few things.

For the most part you will get a clear reason in the Hubitat/SmartThings live logs.

I’ve experienced the rare occasion where the internet connection was going up and down. and because it wasn’t for extended periods Amazon never reported the device offline. So commands were being sent successfully but never reached the device. (I have no way to fix this because I have no way to know if Amazon itself could reach the device. Only that it successfully received the command we sent.)

When your device is offline (according to Amazon) you will see this entry in the logs for every command received by the device.

[WARN] Commands NOT Allowed! Device is currently (OFFLINE) | Type: (TTS)


Status Code 400/401

#

This failure is almost always due to the expiration of your cookie.  Simply clear the log in information for the Heroku App and log back in to Amazon. This should fix your issue right away.

Steps to Fix

Step 1:

#

Log into the https://dashboard.heroku.com website and click on your echo-speaks-xxxxxxx app.

Step 2:

#

Then click on the Settings.

Step 3:

#

Scroll down to the Domains and Certificates section (pictured below).

Step 4:

#

Click on the link listed next to Domain.

screenshot

This will take you to the Amazon Cookie Retrieval page which looks similar to the picture below. If it shows ‘Authentication Good` then you should then be good to go.

If you are directed to log in again, then just do it and you should then be good.

screenshot


Status Code 404 (DEPRECATED)

#

Failed with status code 404 @line 890 (asyncCommandHandler)

The Heroku service will put an app to sleep once it detects no activity for 30 minutes. 

The Echo Speaks system has a “Heart Beat” that talks to Heroku to keep the app awake. We are dealing with the cloud here, so sometimes there may be a delay in the Heart Beat, resulting in a nap for your server.

Steps to Fix

Step 1:

#

To remedy this it is helpful to open the Web Config page. Which normally wakes the service up. Sometimes this may take a couple of minutes. 

Step 2:

#

You can easily navigate to this page by following these steps. We recommend that you create a link to the page in case of any future incidents, then it will be a simple one click fix.

Step 3:

#

Log into the Heroku.com website and click on your app. Then click on Settings and scroll down to the Domains and Certificates section (pictured below). 

Step 4:

#

Click on the link listed next to Domain.

screenshot

This will take you to the Amazon Cookie Retrieval page which looks similar to the picture below. If it shows ‘Authentication Good` then you should then be good to go.

If you are directed to log in again, then just do it and you should then be good.

screenshot


/ap/cvf Request Error

#

If you see this error when you are attempting to do the Amazon Login part of the server deployment, We have found this to be due to having had the Amazon 2FA (2 Step Verfication) service activated, and then later turned off. Unfortunately, once you have had this service turned on, it will have to be on for Echo Speaks to work properly. You may or may not remember ever having it turned on in the past, but with the presence of this error, it is very possible. To remedy this error you will need to turn the 2FA service back on and redeploy the server.


Didn’t See your Issue here?:

#

You can view open issues or create a new one by following this guide:

Reporting Issues