Yep! Not broke, don't........
Hi - looking for some help. I am attempting to install Echo Speaks and when I hit step 7 of the configure server instructions and perform the "Tap on the Go to Login Page button" I get a 404 error. The Heroku URL looks similar to what I see in the documentation except that it seems to have an additional dash with additional characters after it - i.e. echo-speaks-XXXXXXXX-YYYYYYYYYYYY.herokuapp.com. I'm not sure what I missed along the way - I tried deleting the Heroku server app and redeploying a new one - any suggestions?
Nevermind - I found the workaround that @jtp10181 posted above. Thanks, Jeff!
I just installed Echo Speaks for the first time with the server hosted locally in a docker container and all seems to working fine (done a few tests to Alexa) however I am seeing an error in the Hubitat log that keeps repeating every 15 minutes. I saw someone else having a similar issue but I am not sure if this is the same. Any help will be greatly appreciated.
This error indicates that Hubitat sent a wake-up request to your Echo Speaks server, but the request timed out (HTTP 408) because the server was unresponsive.
Troubleshooting Steps
-
Check the Server Status:
- Heroku: Log into your Heroku dashboard to verify the app is active, running, and hasn't crashed or exceeded dyno/payment limits. Try clicking Restart all dynos.
- Local Server (Docker / Raspberry Pi / NAS): Verify the container or Node service is running, and check if the host machine's local IP address has changed.
-
Verify Server URL in Hubitat:
- Go to your Hubitat web UI > Apps > Echo Speaks.
- Navigate to the Server Settings page and confirm the server URL matches your active hosting URL or local IP/port.
-
Test the Server Endpoint Directly:
- Open your Echo Speaks server URL in a web browser (e.g.,
https://<your-app>.herokuapp.comorhttp://<local-ip>:port). - If the page fails to load, the issue is on the hosting side. If it loads, check if you are prompted to log in to Amazon again to refresh expired authentication cookies.
- Open your Echo Speaks server URL in a web browser (e.g.,
-
Reboot Hubitat:
- If the server is up and reachable in your browser, perform a clean reboot of your Hubitat hub from Settings > Reboot Hub to clear any hung asynchronous network connections.
Thank you so much Tim for the detailed steps. Step #2, Verify Server URL in Hubitat, did the trick. I had some strange IP address and once I changed it to my local IP, restarted the docker container and restarted the Echo Speaks on Hubitat, there were no more errors in the log. Excellent help and thank you.
I hope this is the right place to ask this question. I have been using ES voicecmdastext() for most of my commands to Alexa plus. Sometimes too many in a very short time to control different devices on Alexa. However, the constant response back from Alexa+ every time a command is executed is making everyone very unhappy. We use Alexa for many other requests and turning the volume off will not work. I tried searching for a resolution but I was not able to find one that works. Any help/recommendations will be greatly appreciated.
It is a setting in the alexa app. But the best you can do is get a ding, but you can def get rid of the annoying OK. Per gemini:
You can stop Alexa from saying "OK" by enabling Brief Mode, which replaces verbal confirmations with a short chime.
Method 1: By Voice
- Say: "Alexa, turn on Brief Mode."
Method 2: In the Alexa App
-
Open the Alexa app.
-
Tap More (bottom right) and select Settings.
-
Under Alexa Preferences, tap Voice Responses.
-
Toggle Brief Mode to On.
(Note: Brief Mode is an account-wide setting, so enabling it applies to all Echo devices connected to your Amazon account.)
I agree this can only be addressed on Amazon’s side with the options they give us.
Since echo speaks is essentially fooling Alexa into taking actions as if someone had actually spoken to it, ES has no means to disable Alexa’s audible responses entirely.
You can use any device for that, so I always use a device that is not in a main area. Or, if you have an old echo device, put it in the basement or a closet and send all voice commands to that Echo and leave the volume down.
This is what I do as well. I have a routine that goes down a list of 4 devices that are in out of the way areas. My garages, laundry room , shop. In case the first one is offline it will go to the next.
Thank you for providing the instructions. Your methods would have worked with Alexa but they will not work with Alexa Plus. Actually Alexa told me that herself. At this point I don't want to downgrade to just Alexa.
This is a good idea. I don't have an extra device but I do use Fire Tables and FireStick. I will see if I can activate Alexa on them and maybe use it to send all voice commands to it. Thank you.
I am on alexa plus... maybe I am not understanding what you are trying to do?
You are incorrect. You can enable brief mode with Alexa+, which should eliminate the responses after issuing commands. You may get a short tone after though. If you are using the latest Alexa app, you can simply type in Brief Mode and it will tell you whether it is enabled or not.
Hello Tim, what I am trying to do is to basically stop Alexa Plus confirming every command executed via ES voicecmdastext(). Of course this command is similar to me asking verbally Alexa to, for example, set temperature on Family Room Thermostat to 77. In this case Alexa replies that Family Room Thermostat is set to 77, which I do not what to hear. Before upgrading to Alexa plus I had Brief Mode turned on and when asking Alexa to do something I used to get a ding sound indicating that the command had been executed. Since Alexa Plus I still have Brief Mode turn on, however, this setting is not longer valid for any device running Alexa Plus. On your device running Alexa Plus, if you ask "Alexa, turn on Brief Mode", Alexa would reply that this setting is not valid for Alexa Plus (that is what I am getting from my device). If yours is working differently than mine then I may have something else not setup correctly.
I have brief mode enabled with Alexa+. You must enable it from the app. Tell the app to Turn on Brief Mode.
I just tested to make sure it is working since I've previously enabled it. I asked "Alexa, turn on Living Room lights", and it did so with just a brief tone/chime after.
Well, then I must have something else going on because I have Brief Mode turned on and I am not getting the short tone, but instead Alexa confirming that the command was executed. I will continue looking into this. Thank you all for your help.
See post above. Enable Brief Mode in the Alexa app by simply typing Turn on Brief Mode. Don't tell a device to enable it. Sadly, Alexa+ is still a bit dumb when it comes to certain things.
begs the question why don't u use one of the other commands that causes it to speak without the notification tone you don't like?
I do.
My posts above were in response to @user6041. I can't speak for what he/she is doing.