+1 here aswell, seems this is bug, most likely due to that “old token” mentioned in this chat is still on and has not been fixed yet.
I’ve opened a request here, couldn’t find any, but also hoping not duplicating:
Once in while I also get this invalid authentication error for one of my 5 Sonos speakers. It can be the one in the kitchen or in bathroom or… couldn’t find any pattern why.
Your solution worked fine for me. I actually used the another TTS service, the one from amazon and it also worked. To clear the playlist did not work though
It’s back!
I’ve started getting this referencing a non-existent mp3. This only started within the last couple of days (maybe even today).
I rarely use the Sonos speakers, except for house-wide announcements using ChimeTTS integration. Despite the error messages, the announcements play just fine.
2024-11-04 14:40:30.465 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from sonoszp.lan (192.168.86.48). Requested URL: '/media/media/barbara_arriving_home.mp3?
No path (/media/media/barbara_arriving_home.mp3) exists, so I’ve no idea where this is coming from. I did have an old mp3 of that name, but it was in the folder /config/www/sounds. Where the /media/media bit comes from, I’ve no idea.
However, getting these notifications popup is very annoying.
Tangential to this, my Homepods have suddenly stopped responding to ChimeTTS as well (Unable to browse media for Homepod), so don’t know if all this is related to a bad configuration on my side.
So the a week or so ago, I was editing my configuratin.yaml file and saw it had both “external_url” and “internal_url” set. I commented out the internal_url (which I shouldn’t have since I have a domain name), and it seems to have fixed my Sonos problem. Still keeping an eye on things.
This also seems to have fixed the random fails I was getting when trying to cast audio/video to my Google Nests