-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Music sometimes doesn't start via automation #3510
Comments
Please review the troubleshooting pages of the docs again. You need to narrow this down further so the devs can try and reproduce it. |
@marcelveldt you mentioned that you've experienced this problem before and have seen reports on it on Discord. Do you have any ideas on how to narrow this further or reproduce? Should I increase the global log level to VERBOSE and see if that exposes anything? |
We have only seen this issue being reported with the Voice PE but then it was simply not possible to start music at all (this issue was there every time). A power cycle of the Voice PE fixed the issue. After the recent firmware updates of the Voice PE it was reported as fixed. Anyways, could have been a slightly different issue but it surely looks the same, what you see in the log is that the whole audio chain stops again because the player disconnected again. Now you mention Apple Music and there is one thing about Apple Music and that is that sometimes retrieving the key takes a while so this could simply be a timeout. Did you ever test any other music source or only Apple Music ? |
No, and it's not so easy for us to test other sources. I only see this 1-3 times per week and I run it in an office with a shared playlist. So to test other sources I'd need to switch our whole office's music for at least a week. What would be the best way to figure out from logging whether this is an issue with the player or an issue with the music source? If we could start there by adding some logging then we would at least know which direction to pursue. |
Is this still happening in the most recent betas (or RC's in the meanwhile) ? |
@johnboiles please see question above. |
Yeah it still happens regularly. Here's the log from this morning on 2.3.6. I've been on and off the betas too with similar issues. I can try going back to the beta if you think there's a chance this could be fixed. My question above still remains: What would be the best way to figure out from logging whether this is an issue with the player or an issue with the music source? It looks like from the
|
beta would be best (although will be be promoted to stable very soon) as there are heaps of improvements. Having said that the log may provide some useful clues |
Ok! I switched to |
2.4.0 has been released. |
I didn't want to open a new issue in case this is the same thing. I have been seeing this around 30% of the time after upgrading from 2.3.3 to 2.4.2. This is using HA automations to play annoucements and occationally it won't resume what was originally playing with error code 255. These are local MP3 files. |
@MarkHofmann11 If you aren't sure where your query should go then first ask in Discord or the Q&A Discussion section of this repo. Your error is not the same as the OP. (Try the latest beta as part of your troubleshooting) @johnboiles This will be closed soon assuming fixed |
I didn't notice it happen again yet but it is intermittent so I'm hesitant to declare victory until it works for a week. Is there a patch you think that fixed it that I could review? If @MarkHofmann11 is getting his ffmeg process killed prematurely by MA ( @MarkHofmann11 are you using an ESPHome player? |
I'm using the native Chromecast players from MA inside of HA. I just changed the way it plays the file from "local filesystem" to http: (HA's internal web server) to see if it behaves differently and resumes consistantly. |
What version of Music Assistant has the issue?
2.4.0b20
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
A few times a week (I haven't found a pattern) my HA automation to play a playlist does not start the music. I see the queue get appropriately populated with the playlist, and music assistant seems to start to play for a few seconds (the button transitions from the play button to the pause button), then it gives up (the UI goes back to the play button)
Opening an issue as promised here.
In the log I see both FFMPEG processes exiting with code 255, which I think means they were killed by MA via a signal.
How to reproduce
Unsure!
Music Providers
Apple Music
Player Providers
HA Media Player w/ Home Assistant Voice ESPHome (Nabu Media Player)
Full log output
d5369777_music_assistant_beta_2025-01-27T18-51-48.554Z.log
Additional information
I've gotten this issue occasionally as long as I've been using MA (since ~September 2024)
What version of Home Assistant Core are your running
2025.1.4
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Raspberry Pi
The text was updated successfully, but these errors were encountered: