Would you happen to know how to do this on a raspberry pi?
My guide I posted works on the RPi, you just need to swap a line in the config file to build your own image which is listed below the config example. Should work for Portainer or Docker Compose.
3 Likes
And, there are also instructions in that same PDF (great guide) for installing the Echo Speaks server directly on the RPi, which is what I have done, without docker or portainer. Works fine, keeps chugging along.
1 Like
I followed the install instructions for Raspberry Pi and it works like a charm!
Sorry for my ignorance but could you please point out to “an old man” where exactly this particular set of instructions is (for installing Echo Speaks directly on RPi with docker nor portainer)? Thank you so much for your kind help! And again, I apologize if the location was obvious (I just could not find which PDF and what portion of said PDF referred to this, LOL). TIA again!
Ok, here is the guide:
Scroll down about a page or so until you see the heading:
ALTERNATE INSTALLATION OF ECHO SPEAKS AUTHORIZATION SERVER WITHOUT DOCKER
Follow the instructions immediately following that heading until the line:
That’s it!
Mine is running on a 1 GB Raspberry Pi 4. I understand that it will also run on a Pico.
I am probably older than you are, I turn 73 in a few months.
4 Likes
I noticed these errors Echo Speaks error messages in my log,
Is this error thrown due to a programming issue or change on the Alexa side or is there something in my configuration that causes this.
Thanks
dev:2202023-04-15 05:09:38.426 PMerrorEcho (v4.2.2.0) | getPlaylists Response Exception | Status: (404) | Msg: status code: 404, reason phrase: Not Found
dev:2172023-04-15 05:09:19.389 PMerrorEcho (v4.2.2.0) | getPlaylists Response Exception | Status: (404) | Msg: status code: 404, reason phrase: Not Found
Can someone please post a sample of what your callback URL looks like? I can't seem to get mine working properly. Thanks in advance.
The Hubitat app gives you the exact url to use, you just copy and paste it. Using a local address is optional.
Thanks. I'm using the URL provided and still get this exactly every 15 minutes in my logs:
I've tried the local URL and get the same.
I'm getting the same errors and I haven't been able to resolve it yet.
The error message says the ES server you have setup is unreachable from ES running on your HE hub
It could be down, or the network address is not correct.
408 means timeout,
Echospeaks on your HE hub tried to send a message to the ES server, and it timed out.
Which, for clarity, has nothing to do with the callbackUrl. The callback is how the server responds BACK to the hub.
If you go into the HE app where you setup the cookie server, it should show the IP:PORT for your server. Is it correct?
Yes.
I'm looking further into it. Just realized it might be a firewall issue on my part.
Check your firewall rules. I had the wrong IP address in a rule that allows my hub to speak to my ES server, which is on a different VLAN.
1 Like
@jtp10181 & @nh.schottfam Thank you both for steering me in the right direction. All is working now. I had an incorrect IP in a firewall rule that I use to allow my hub to speak to the ES Server. Must have fat fingered a key when I setup the rule initially. Until now, it never phased me to go back and check it.
Many thanks to you both!!
2 Likes
I realize I'm late to the party - I just fought an issue where Hubitat DNS was hosed. So the hostname I was using actually was failing. I proved it by replacing it with the hard IP and it worked, but with a hostname it didn't. Once I forced hubitat to use a local DNS that includes all my local machine names, the problem stopped. Crap..I wanted to take a screen cap of the DNS entries in HE I put to override and my hub was crashed. again. 6th time in the last 9 days. This is getting old.
They are on the same network so that shouldn't be an issue. Thanks for the advice.
