You are correct, you designate which echo it speaks from. What I would do is create a second identical routine that speaks to a second echo. I also have lights that change colors. Although I don't use it now, I had a routine turn my one of my bathroom lights red, indicating that I had asked Alexa to turn on the coffee maker. So turning a bedroom red could cue you in quietly there is a security issue.
Excellent solution! Thanks, I'll try it tomorrow.
Ah. You’re running Docker on Windows whereas I’m running it off my QNAP NAS using Container Station (which is fairly straightforward.) Perhaps it might have something more to do with the way Windows and Dockers handles networking. I’ve had issues with networking addresses on Windows Dockers in the past.
With QNAP and Container Station/Docker, I almost always use Network Bridging and assign a separate “virtual” static IP address to whatever server application I’m running. For example I keep one separate for my PiHole, another separate IP address for this, Channels, Plex, etc. So they all show up as their own “computer.”
Maybe this is completely unrelated but it could be part of your particular issue. I’d also disable any AV and firewalls on that machine just to see if it connects differently.
1 Like
Well I got the server set up and looking like it right. I go to Hubitat and get as far as clicking the blue login page button and I get redirected to 'localhost:8091/proxy/www.amazon.com/ap/signin?show...' Am I missing something here? I am working on a different machine than the server app is running on.
1 Like
What platform is your echo speaks server on? Sounds like it is not able to detect the IP properly. I have some info about how to avoid that in my guide post. [GUIDE] Echo Speaks Server on Docker (and alternates)
1 Like
Using the node install on windows.
Check this post: [RELEASE] Echo Speaks V4 - #1229 by jtp10181
You should try setting the ipAddress variable
Not sure if this is going to work in the long run, but I disabled my Heroku echo-speaks app basic dyno and I still get TTS working on my setup.
I set it up late December and got charged partially that month.
Then I disabled it early January, and as you can see, I didn't get charged the full $7.
here's where I disabled it..
not sure what this error means:
metrics page:
It will work until the cookie expires, which seems to be much longer than the 5 days the app refreshes it but no one is really sure how long it will last.
I’ve seen mine still going 25 or so days after refresh (my Pi had stopped responding for some reason…).
For me, it quit working when I did something in the app around the end of December (can’t remember what) and that prompted me to setup a computer with Ubuntu. I am now running Pi-Hole, an ntp server, Homebridge (which had been running on Windows), and ES from it. Now I’m glad this happened. It was much easier than I thought it would be.
2 Likes
Check out Adguard Home. I switched from Pi-Hole over the AGH and like it better.
1 Like
Thanks. I’ll check it out.
What do you like about AdGuard over Pi-Hole?
1 Like
- More polished clean interface and settings
- Supports DOT/DOH (and others) upstream out of the box
- Allow-lists built in
- Supports better block lists (regex style), also supports traditional style lists.
- More useful info in query log
Cons:
- Miss some of the charts on PiHole. Mainly the upstream DNS being used pie chart. I was able to make something in Grafana eventually to cover that.
- Custom filtering rules is just a giant text entry box, but has more options.
1 Like
Thanks, this helped me as well
He's mentioned it eventually but he has a couple of other things that take priority.
1 Like
I am still using GitHub - TonyFleisher/echo-speaks-server at docker-enablement which works. Any reason to switch to something else?
