I am most concerned about this one:
![]()
@tonesto7 anything to worry about with this?
Not sure if this will help you but I had some 408s after updating. I went back in to HPM and checked for updates and it showed ES had updates still. I updated again opened ES and that seemed to have stopped the errors.
I'm fully updated thanks.
Are you seeing this on multiple devices? If yes is it specific to a certain echo device model?
It doesn't seem to be tied to a specific device. My Echo devices themselves do not show any warnings in the logs. What I see is from the app.
All of my Echo devices show online in the app.
I have a mix of Echo Dots, an Echo Spot and an Echo Show.
I only noticed these 408 errors after updating to the latest version.
The 408 warnings may have stopped after my last hub update and reboot.
I’ll post back if they start up again.
I'm happy to see ES get some love. It feels like it's been a long time. I forked this app and began cleaning somethings for myself - I've switched it back to see if the inbound fixes improve my environment.
I had fixed the playback, icons and playlist stuff - here are the icons I made or use in case they are helpful
Here are a few more _ comm only lets you upload 5 images at a swipe.
I get errors on my dashboards for missing icons - and in the app:
I'm happy to zip them and make them avail - they are also on my Git.
Please submit pull requests and i will gladly accept them. I was hoping the community would help me keep up with things.
In case anyone is interested I just installed the server on WSL on windows 11. Super simple
This means you would not need a VM or Docker...
Does anyone know if the introduction of the Alexa+ early access breaks anything in Echo Speaks or the Echo Speaks local server?
Alexa+ works with Echo speaks.
I'm glad to hear that... I enabled A+ today but haven't played with it yet
I have noticed the below errors in my Echo Speaks logs. Can anyone assist how to correct as this is appearing many times each day..
Your cookie refresh server is offline / unreachable
You are in the right place now as we discussed in your other post. I guess you didn't see my other response.
My cookie server has lost its brain again and is showing the wrong IP address. The fix a few years ago was to run a pm2 command and it fixed it. Now I get an error. And I admit I have no idea what any of this does so I'm at a loss to troubleshoot.
I’m using docker so not really sure but maybe this will help you:
You need to do a pm2 list to get the name of the process in pm2, it is saying it doesn't know what index.js is, so maybe it is named something else.