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?
No.
1 Like
I followed all of the instructions and I can’t figure out why it’s not recording the IP address. I can see the login page when I go to that ip:8091 address.
Is there anyway to manually change this address?
Check this guide which covers how to set the IP when running with docker: [GUIDE] Echo Speaks Server on Docker (and alternates)
The second post has some alternate install methods as well, and a link to this post which shows how to set the IP when running without docker (via pm2): [RELEASE] Echo Speaks V4 - #1229 by jtp10181
2 Likes
It might see it, not sure what you would be able to do with it though.
From the bottom of the Amazon link you posted:
Echo Glow does not contain microphones or speakers.
I agree with Jeff (@jtp10181). Hard to see how such a device could be used by Echo Speaks.
1 Like
Sorry, yes I know it doesn't have any mic/speaker but was wondering if it had similar API endpoints, etc for being able to control the lights and followed the Echo pattern of integrations. Apologies if that was a dumb assumption 
All this integration can do is speak.
1 Like
gotcha, thanks sir!
i noticed today that echo speaks 4.2.4.0 was released about 3 weeks ago. i tried to update via hubitat package manager but it fails. is it okay to install 4.2.4.0? i don't know what has changed, where can i see release notes? should i manually install it, how would i do that? currently i am paying heroku but would love to stop paying.
It updated fine for me. Believe it was cleanup and adding a few new Echo devices. I have run the local login server on a Raspberry Pi 4b for almost a year and a half (since Heroku announced it would charge), has always been solid for me.
https://raw.githubusercontent.com/tonesto7/echo-speaks/master/CHANGELOG.md
2 Likes
I've started seeing this in my logs every 1/2 hour for one of my Echo devices.
getPlaybackState | 400 Error | Msg: status code: 400, reason phrase: Bad Request
It's a Gen4 Echo Dot without clock. I have various lines commented in the app and device code per the posts below, but I am still seeing the error. Not sure when this started again at this point.
Anyone else seeing this error again? Anyone have a current fix?
I think there was an official update for the app pushed out to remove the unsupported features. Are you running the current version?
Pretty sure I am.
Am I missing something here? Was there an update released not via HPM?
That is current, you can always run a repair in HPM if you want to be sure it is the original code. I am not getting any errors and I don't think I have patched this latest version at all. 
OK. I'll give that a shot. What's weird is that this was all working fine without any errors for ages. Then all of a sudden, I'm seeing them for just this one device.
Could also try power cycling that device.
3 Likes
Good idea. Going to try that next. The repair of Echo Speaks did nothing. I got 2 of those errors right after.
