-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
ESPHome based player stays silent even with enforced MP3 stream #2508
Comments
Hallo, |
Not yet. I hope for a fix or explanation of my wrongdoing here, too ^^ |
Is it an esp8266 or esp32? Is your url (all: player, music assistance, ha, music provider) tls secured (http or https)? |
It's a ESP32-S3 based device. |
in my case it is a esp32-s3 and http too 17:43:23][D][media_player:068]: Media URL: http://192.168.178.33:8097/flow/media_player.buero_media_assistant_media_player/23ca5ce125cb480cbf43cea09c330270.flac?ts=1719243803 |
Same problem.
Music Assistant 2.0.7 |
Are there any another settings to permanently change stream from flac to mp3 |
Same settings, same problem. |
The first time I installed the beta version (I don't know why I chose that particular installation) and it worked fine. |
In case it happens to be relevant or useful... I am also experiencing this issue with a standard esp32 and have noticed that the device is sent a url with a .flac extension from MA. Same if I browse to my local media using the "media" tab on the left side tray. However, if i go to settings>devices>esphome and open the media player entity and from there select "browse media" I can play a song from from my local library and my device gets a .mp3 url and plays the song as expected. Could this perhaps indicate the root of the problem is something in HA and not MA? |
Small update regarding the yesterday mentioned issue above. Adding "codec: auto" on the correct place in config indeed fixes the playback issues for my Onju Voice. No clue if this is a mere workaround, but as most ESPHome voice assistants seem to have problems here, it likely is not more than a hack fix. |
Where does one add that, specifically? |
Check the above linked report: gnumpi/esphome_audio#47 it has to go into the "media_player:" section |
Sorry for the late reply. This issue should be fixed in music assistant server version 2.1.0 beta 12 |
Thank you - I can now play from Music Assistant to my ESP32-based onju-voice device for the first time. Appreciate the fix Marcel. |
What version of Music Assistant has the issue?
2.1.0b6
What version of the Home Assistant Integration have you got installed?
2024.6.2
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
I use a Onju voice Assistant and tinkered with it a bit by now. As most ESPHome based players it should do fine with a enforced MP3 stream, but somehow Music Assistant does not care about setting it at all. I verified that MP3 streams are indeed working with the normal media menu inside Home Assistant to play a mp3 on it which works flawless. The stream arriving on my player still looks like this even with mp3 stream enforce activated: http://192.168.181.42:8097/flow/media_player.onju_voice_e27688_onju_voice_satellite_e27688/a9bab3d8c1b1408797a13ddf3334cd68.flac?ts=1718752804 aka it's a FLAC stream.
Later on the player confirms my assumption by logging this:
Opeing the stream inside the webbrowser does work so the stream itself is not the problem, only the format of it.
How to reproduce
Get a ESPHome based player, verify the enforce lossy MP3 stream setting is selected and push play on any audio.
Music Providers
Plex, Spotify,, YT Music
Player Providers
Home Assistant Media Players:
https://github.com/tetele/onju-voice-satellite and especially take a look at tetele/onju-voice-satellite#52
Full log output
log.txt
Additional information
No response
What version of Home Assistant Core are your running
2024.6.3
What type of installation are you running?
Home Assistant OS
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: