-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
I can not play any stations to any Google Mini Speakers #3235
Comments
Try with a different player provider (e.g. snap cast) to see if this is a tune in problem. Load the radio browser provider and try some stations from there |
When you add the snap cast provider in MA it installs a server for you. Don’t install it in HA edit: someone else is also reporting this so it does appear to be a chromecast issue. Let us look into this. |
I hopped on to see if anyone else was having issues. Tidal plays on Snapcast, but there are issues on chromecast. After a few minutes it will finally start a song, but it will fail to queue the next even after several minutes. It also keeps reporting that the Chromecast speaker is off. I turned the logs to verbose and saw some exceptions from pychromecast. |
@kevinm2 Hang on sorry. You are the OP but you started talking about something completely different to your original post. Everything in your original post looks in order? So just wait please until we can look at this. |
What version of Music Assistant has the issue?
2.4.0b7
What version of the Home Assistant Integration have you got installed?
2024.11.4
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
During the past week I noticed the automation I had created a while ago stopped working. The automation setup is, when the camera sensed a motion on the drive way, MA would turn on both of my Google Mini speakers named "Mini office" and "Mini MB", and play two different stations from TuneIn, "Mini office" would play 89.9 | KCRW (US News), and "Mini MB" would play another station from TuneIn, and turn off after a certain amount of time.
I have done all I could to try to figure out why MA would not play to these speaker anymore. By restarting HA, MA, and have read your troubleshooting FAQs, and can not find anything that is related to this problem.
I can directly play to these speaker from Win 11 and Spotify without any problem.
The behavior I have noticed in MA, trying to play KCRW to Mini Office, is when I am on MA > Radio > Select KCRW > Click Play, the Mini office bling's with a sound ounce once, with out any stream from KCRW (TuneIn). When I click to play again, it does not play the bling on the speaker any more, and of course, no streaming of KCRW. I am guessing Mini Office goes to sleep.
Also, I have noticed Beta version is installed. Do I have to have the Beta version installed? If not, how can I replace the Beta with a stable version?
I have tried other TunIn stations, and not just KCRW, with the same result.
Additionally I received an error "CastMediaPlayer.media_play Failed: Failed to execute play.", and can not replicate and see it on UI anymore. Please view the screen capture.
Here are some screen capture for your reference. Please let me know if I have missed anything. Thank you
How to reproduce
When in MA, clicking on Radio > Select a station (ie: KCRW)
Before click screen capture:
After click screen capture:
Music Providers
List the music providers that you have tried which result in the problem:
Before clicking play:
After clicking play:
Player Providers
List the player providers that you have tried which result in the problem:
Google Mini
Note: These where working in MA before! They are functional when playing form Spotify, iOS , etc.
Full log output
d5369777_music_assistant_beta_2024-11-27T13-48-41.006Z.log
Additional information
Running HA on a Dell CFC5C OptiPlex 3050 Micro Form Factor Desktop Computer
What version of Home Assistant Core are your running
2024.11.3
What type of installation are you running?
Home Assistant Core
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)
The text was updated successfully, but these errors were encountered: