[RELEASE] Echo Speaks V4

[Pantheon]

@kewashi

the total costs will be pennies a month

Agreed. I can spend $275 on a new RPi and case and set this up. Or I can spend $5 a month for several months and see how this plays out.

[tonesto7]

Well said!

[jtp10181]

@Pantheon

Agreed. I can spend $275 on a new RPi and case and set this up. Or I can spend $5 a month for several months and see how this plays out.

If you have ANY always on machines, Linux, Windows, NAS, etc... you can just pop docker on there and install his container. Does not have to be a RPi, in fact you can get way more power from a regular mini-PC for around the same prices.

Side Note, I already had the server installed from the github repo from my initial setup. Once I remembered how to update it I just had to go to the directory and run:
npm install tonesto7/echo-speaks-server

Restarted the pm2 service and its all set.

[gikjll]

What he said. I have mine running on a laptop running ubuntu, ANY cheap old laptop can run ubuntu and do this, no need for docker usually

[ritchierich]

@marktheknife

Who else hasn't donated recently?

I have been monitoring this thread for the past several months as I have been using the Alexa TTS solution for simple notifications. I knew about Echo Speaks from my ST days but the Heroku requirement was a non-starter for me for many reasons that aren't important for this discussion.

Now that things are local I took the plunge and installed this on my NAS yesterday and app installed on my Dev server to test things out. Well worth the time and like @marktheknife I also bought @tonesto7 a case of beer/adult beverage(s) for his continued community support via Paypal donation.

[nrm94ee330]

I did update as well..
I had followed instructions from here

Echo Speaks / Heroku end anxiety support group. See one solution below.

Ok, I have gotten my local Echo Speaks server working. In my case, I created it inside of a LXD container. You can use a Pi or a VM also. I tried the Docker container solution and it worked fine, but was more complicated than needed. In my case, I used a LXD container that was Ubuntu 22.04. So, on my LXD container, I simply installed the app with these steps. sudo apt install nodejs sudo apt install npm npm i https://github.com/tonesto7/echo-speaks-server sudo npm install -g pm2 cd node_m…

I was running local server since a couple of weeks.. and it auto updated to 4.2.0.8 and seems to be working fine so far..

[vmsman]

@tonesto7 Hey, I picked up with the "how to" guide. Great work. I ended up with the node.js install in a LXD container.

[JimB34m]

I was wondering if someone could weigh in on this before I commit the time/effort.

After reading a bit on this thread, I have decided to try to run ES Server locally by setting up a VM using VirtualBox that is running Ubuntu and then installing the Server. I will be following @vmsman instructions that he posted a few weeks ago, earlier in this thread.

I currently have an always-on Windows (10 Pro) machine, which currently runs 6 IP cameras in Blue Iris and Plex Media Server. The specs are: i7-4770 CPU @ 3.40 Ghz, 32 GB RAM and basic on-board video card.

My questions are:

1. Is VirtualBox running a VM with Ubuntu too resource intensive, considering what I am already using my machine for? Currently, when Blue Iris is running as a Service, I am under 30% CPU utilization.

2. With the changes that have been made to ES, is this still a good way to setup/run the ES Local Server on a Windows machine?

Thanks in advance for any insights/advice.

[vmsman]

@JimB34m I think that your approach is viable. Virtual Machines are always much more intensive on resources than containers. Since you have Windows 10 Pro, a better way to lighten the load would be to use the Hyper-V Hypervisor as opposed to VirtualBox. Hyper-V is more efficient as a Hypervisor. I would install the VM as Ubuntu 22.04 Server and not desktop. I would strongly advise configuring LXD containers inside of the Ubuntu Server VM. This will provide the ability to use that VM to install many isolated apps in the single VM. If you would like to discuss this, come by my chat at https://chat.scottibyte.com/.

[rjterry21]

A real OS is something Like IBMi, AIX, or VMS.

[rjterry21]

I hear nonstop is the cat's meow...

[dJOS]

@rjterry21

VMS

I think you are confusing "real" with "dead".

PS, AIX is a Unix OS.

[jtp10181]

@vmsman

Since you have Windows 10 Pro, a better way to lighten the load would be to use the Hyper-V Hypervisor as opposed to VirtualBox

I have not used docker much really myself but if the only thing he wants to run is echo-speaks would Docker for Windows running the official ES docker be even less load?

[plantucha]

@philtor

When I try to get echo-speaks-server running in a Docker container on my Synology NAS the Hubitat app assigns the IP as 0.0.0.0. I have the Docker container using Host. I'm sure why this is happening?

I have the same issue.
It doesn't find any device

[vmsman]

This means that your Docker container on the Synology is not bridging to your LAN for an address. I would expect that address to be the address of the Synology at port 8091.

[plantucha]

@vmsman

This means that your Docker container on the Synology is not bridging to your LAN for an address. I would expect that address to be the address of the Synology at port 8091.

I can reach it in the browser

[luckylovezombie1]

I'm having the same issue... Windows 11 with Ubuntu. Shows "0.0.0.0:8091" on the app, but the correct IP on the server side. Also, I've gotten it to keep the login for about 2 minutes, and then it changes back to "you are no longer logged into Amazon"......

[rjterry21]

I know what AIX is.

[vmsman]

@plantucha ok, then did you paste the app callback URL into the last field on that screen?

[plantucha]

@vmsman

@plantucha ok, then did you paste the app callback URL into the last field on that screen?

Yes. All settings are correct.

I reboot hubitat and it found devices.
Yet still showing IP 0.0.0.0:8091