Setting up echo speaks

🛎️ Get Help Integrations
59

I have a raspberri pi setup to manage amazon cookies .... I cannot set it on a static address since the router I have will not allow that. Is there a way to to set it up so that if the IP of the PI changes after a router reboot it will still find it ?

60

Couldn't you manually set the IP address of your Raspberry pi on the device itself - outside of the range of DHCP on your router?

61
62

Thanks. So if I set it static on the pi. The router won’t try and reassign?
I will give it a try

63

Should be outside the router’s DHCP pool.

1 Like
64

I believe you stated that you could not do reservations on your router, so from that I'd venture to say it should not reassign anything.

65

It's a little odd, but let's assume you can't. If you can't assign a static IP, that also may mean that you can't assign a DHCP range? In that case, if it was me, I'd go with the last possible IP ... so if your range is 192.168.1.X I would then assign my Raspberry Pi to 192.168.1.255. The chances of a conflict in that case is slim - not impossible, but slim.

66

The last IP would be 192.168.1.254. IP ranges start with 0.

192.168.1.0 = Subnet ID

192.168.1.255 = Broadcast Address

192.168.1.1 - 192.168.1.254 = Host Range

3 Likes
67

I try and click on the goto login page and get an error...ive tried multiple times
and get Alexa 404 Sorry, we couldn't find that page.

image
image541×552 26.5 KB

I've deleted the heroku app and reinstalled, multiple times and ....im stuck ..any help would be appreciated

68

I got stuck with the same error. I kept working on it for weeks and never found a solution. If somebody does have one, I'd love to hear it too!

69

did u ever get echo speaks setup ?

here is the error

image
image1278×358 19.6 KB

70

@sean1 Looks like @tim.ocallag already found my workaround and is trying it, if you have not tried this it is the only way to get it working on Heroku right now: Echo Speaks - Heroku new deployment workarounds

71

Thanks; I'll give that a shot!

72

Can someone please confirm if it's a requirement for Echo Speak to work to have the hub exposed to the internet?

Thanks!

73

Not really "exposed" but it needs to be able to connect to the internet. Everything for Amazon/Alexa is cloud based (so they can mine your data), there is no local communication to Alexa devices.

You can do TTS locally to Apple devices and I think also the Sonos integration is local.

2 Likes
74

Thanks. I’m not able to make it work (login not persisting) and I thought that could have been the reason.

I would have to keep looking then.

Thank you

75

I am currently successfully running a single instance of Echo Speaks (v4.2.4.0) and the docker server for cookie retrieval.
Due to a need to have multiple Spotify accounts linked into different Echos I have multiple Amazon accounts associated with my Echo setups. I've figured how to run multiple instances of the HE app but I'm stuck on the cookie server side. Is there a way to update the app code and docker to reflect a different port number? Or do I just need to get another docker instance running on a different IP (I'm currently using a Synology NAS) and I was just hoping to keep everything bound on the same platform. I searched through the HE code and couldn't find where the port was referenced.

76

Start another docker container on a different Port. When you set it up, it will pass the IP/port back to HE so it knows where to connect.

2 Likes
77

That’s where I’m having an issue. I can’t seem to figure out how to change the port during the container setup. The docker utility on the synology nas won’t allow the port change, it says I can do it in the web portal but when I add an alternate port there the setup on the container doesn’t see it.

78

Are you running it command line? Otherwise I am not sure what interface you are using.
I would actually recommend installing potainer and then using that, then you can use compose / stack files like my main example in that post above.

If you can run it command line you would need to add the port env variable, also change the container name. This uses host networking mode so no bridge and no port mapping needed. Using host mode the IP may not be needed, it should detect it by itself, but it wont hurt to provide it.

docker run \
  --network host \
  --name echo-speaks-server2 \
  -e ipAddress=X.X.X.X \
  -e PORT=8092 \
  --restart=unless-stopped \
  -d tonesto7/echo-speaks-server

For bridged networking mode it would look like this, do not specify host mode and bridge is default, then you also need to map the port with the -p argument.

docker run \
  --name echo-speaks-server2 \
  -e ipAddress=X.X.X.X \
  -e PORT=8092 \
  -p 8092:8092
  --restart=unless-stopped \
  -d tonesto7/echo-speaks-server