-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while playing a tts message via homepods - random playing homepods after the message #127397
Comments
Hey there @postlund, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) apple_tv documentation |
Did a bit more Research - it seems like the status of the Homepods are not correct. I found out, that the Homepods sometimes are in the status "playing" but they are not playing actually. So maybe this wrong status information is causing the issue? |
我也发现了同样的问题,请问你解决了吗 |
IOS18.1直接提示Unknown error,已经完全无法正常使用了 |
Still same issue with iOS 18.2 |
I have this exact same issue too. |
The problem
I already reported a problem a few days ago after I noticed that my homepods alternately just play something after I run a TTS automation that checks if something was playing before and then resumes playback after the message.
The Homepods then also played randomly if nothing was playing beforehand.
Now, after further testing, I have discovered that even without this check, if a TTS message is simply played, something is played randomly afterwards. This is very annoying.
A look at the logs showed the following error message.
What version of Home Assistant Core has the issue?
core-2024.9.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Apple TV
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: