[RELEASE] Echo Speaks V4

[leo_charles]

I hope @tonesto7 is okay and in good health these days! Thanks a million times over for having developed this app. So I have everything working along with cookie authentication on my docker install on a NAS. I’m running into an issue:

Cookie Authentication fails about 1X/week and I have to manually go in to the app and log back in to retrieve a new cookie.

I don’t receive any notifications that the cookie failed other than for devices to stop sending audible alerts.

Does anyone have any way to either prevent this from happening in the first place, an automated way to refresh the cookie, or to at least send a notification when the cookie fails? It’s not that big of a deal in the greater scheme of things—just glad it works in general. Thanks!

[stephen_nutt]

@user236

I want to use it in rule, so how do I do this?

There is a palette in Node Red that can extract which device you are speaking to but it is inconsistent and doesn't work with all Echo devices. It works on majority of my devices consistently but evidently I am one of the lucky ones.

[jtp10181]

@leo_charles

Does anyone have any way to either prevent this from happening in the first place, an automated way to refresh the cookie, or to at least send a notification when the cookie fails? It’s not that big of a deal in the greater scheme of things—just glad it works in general. Thanks!

Make sure your container is set to "Restart: Always", for some reason the cookie server was coded to quit after it gets the cookie so then the container needs to be restarted (but it should not log out if you set it up correctly with a persistent storage space). See guide here: [GUIDE] Echo Speaks Server on Docker (or without)

There are settings in he HE Echo Speaks app to send you alerts if the cookie refresh fails and various other things, I think some are off by default.

[terminal3]

@user236

Yes, I got this -:), I want to use it in rule, so how do I do this?

You use to be able to tell which device was spoken to and respond back to it. That quit working a few years back. So as mentioned above try Node Red, or your out of luck.

[Pantheon]

@terminal3

You use to be able to tell which device was spoken too and respond back to it. That quit working a few years back.

Yep. Several of my webcore pistons went bye-bye because of that.

[user236]

So maybe i'm not clear

I'm sending command via VoiceCmdAsText

Is there a way to ger Alexa "text" response, as you see on Alexa app

[terminal3]

@user236

Is there a way to ger Alexa "text" response, as you see on Alexa app

If you are wanting to send the voice command through Echo speaks and then get the Alexa response at the device that you would have gotten if you had spoken the command yourself, I am not sure if that will work or not to be honest. My suggestion would be to try it and see.

I have some rules that send a echo speaks VoiceCmdasText request to a device in my garage, I do this because the device will give the end of request tone, so I use that device since the tone won't disturb me if it goes off in the middle of the night.

[marktheknife]

@user236

Is there a way to ger Alexa "text" response, as you see on Alexa app

I don’t think so.

[leo_charles]

Thanks. I had it set to "Always" but I've set it to "Unless Stopped." As for notifications, thanks for the heads up as I now have it enabled should the cookie fail.

[Pantheon]

I'm not sure if this is what you are asking, but I did test this piston.

The Echo in my computer room responded with "The AC is set to 73." My upstairs HVAC controller is named "Upstairs."

[user236]

Yeah, i got this part working. What I need is a text response from alexa

[Pantheon]

I use the Parallel Speak command often. But I have to type in the response. Not sure that is what you want.

[Henson_kraj]

I got this weird problem... my echo speaks is on a proxmox server along with my HA VM. Anytime Home Assistant reboots, echo speaks goes silent. whether i reboot the container or not it doesn't matter. The only thing that wakes it back up is to go into hubitat and send a test.

[user236]

No,

I need the "it is off" or "the heat is set to 95" responses from alexa

[Pantheon]

I asked Alexa to set the upstairs temp to 72. She responds with "The AC is set to 72." I was hoping lastSpeakCmd would have that response. But not so...

At this time, I do not see any way to capture the Alexa responses.

[user236]

I was hoping too - @Sebastien what say you, is this possible to push it there, it will complete my revolution, so I will be able to show Amazon thermostats on my Sharptools.io dashboard. I'm really happy as I can send the commands and also setup simple on/off buttons but i also wanted to show current status and temp

[Sebastien]

This is not something I’ve ever seen or tried. Not sure how it could be achieved.

[jsarcone]

I noticed recently under certain conditions such as ecobee notifying that the system's been turned off. I get assignment says when receiving the notification. Has anyone else seen this before? This was working in the past but seems not to be working now. I have tested with the echo app and it seems to be working fine. However, other applications don't seem to be applying it correctly.

[ljp-hubitat]

@jtp10181

Yeah I have the restart in my instructions as well. Someone in one of the threads found an exit statement somewhere in the code they think is probably killing the process under certain circumstances right after the cookie refresh. It sounds like that's what yours is doing.

Jeff, do you recall what, if anything, fixed this, or who might have reported it? I had the server running fine on an RPi until the RPi started getting wonky on the eth0 connection. I decided to move the ES server to my Synology in docker, upgrade my RPi from Bullseye to Bookworm, and start fresh.

I got it up and running. I used your instructions and Tony's image. Everything is working except for the daily container crash messages. It restarts just fine and keeps on humming but it is annoying to get those messages daily. I prefer to find a fix.

Since you mentioned it, I thought I would bug you before bugging Tony. Otherwise, I may just build my own Container, starting with Debian and following the same steps I did on the RPi like @vmsman did.

LJ

[jtp10181]

Do you have it set to refresh the cookie daily? It is coded to exit after a refresh. Its not crashing, it is exiting on purpose. Not sure why it was coded that way, possibly something with Heroku.