Hello,
I’m experiencing two issues with my new Raspiaudio MuseRadio, running the MuseRadioHomeAssistant firmware.
- Audio cuts and strange noises
While listening to music (Radiobrowser), playback randomly stops. At the same time, I hear a strange noise coming from the speaker, like a crackling or popping sound. This happens without any interaction on my part.
- Freeze in Assist Satellite mode for Home Assistant
When I use the device repeatedly as an Assist satellite for Home Assistant, it eventually becomes completely unresponsive. I have to manually restart it to get it working again.
In addition to the above, I see a lot of warning messages in the logs (of home assistant), such as:
[W][component:238]: Components should block for at most 30 ms.
[W][component:237]: Component speaker.media_player took a long time for an operation (223 ms).
[W][component:237]: Component speaker.media_player took a long time for an operation (248 ms).
[W][micro_wake_word:173]: Wake word is already running
[W][component:237]: Component binary_sensor took a long time for an operation (456 ms).
I also get repeated debug logs in the serial console, like:
[D][sensor:093]: 'button_adc': Sending state 3.06147 V with 2 decimals of accuracy
[D][light:036]: 'Screen Backlight' Setting:
[D][light:085]: Transition length: 1.0s
Could you please help me diagnose or fix these issues?
Thanks in advance for your support!
P.S.: I’m French and used ChatGPT to help write this message.
Hi,
The warnings are not related.
Could you try with the basic “Radio” apps available here apps.raspiaudio.com and check if you have the same issue?
thx
Hello,
When I use the preset radio stations (buttons 1, 2, and 3), I haven’t noticed any strange noisee or crackling sounds so far. However, after a fairly long period of listening, the radio stops unexpectedly (Is this behavior considered normal?).
To check whether the issue was related to the Music Assistant app in Home Assistant, I tested with an older version, the stable version, the beta version, and the development version. Unfortunately, the problem occurred in all four cases.
I also checked the logs. Apart from more than 200 occurrences of the following warnings:
[W][component:238]: Components should block for at most 30 ms.
[W][component:237]: Component speaker.media_player took a long time for an operation (223 ms).
I didn’t find anything else, even with debug mode enabled.
Thx
Good evening,
Tonight, I tested my MuseRadio with the Squeezelite-ESP32 firmware and performed two separate tests:
-
First test: I added the device to Home Assistant using the official integration, then linked it to Music Assistant. Unfortunately, it didn’t work as expected. The serial console shows recurring network errors, even though there’s no issue detected on the Wi-Fi side or with the firewall between the network and Home Assistant.
Log: I (18341) httpd_handlers: serving /messages.json to peer 192.168.42.42 port 4527 - Pastebin.com
-
Second test: I used the MuseRadio directly in Music Assistant (without adding it to Home Assistant). This setup works, but I’m noticing random audio “pop” noises during playback. These occur without any user interaction, and nothing relevant appears in the logs when it happens.
Also, after some time, it seems that Music Assistant “forgets” it’s playing a radio stream on the MuseRadio — it shows the status as paused, even though the music is still playing.
I’ll keep testing over time, as the issue doesn’t always occur right away.
Thanks in advance for your feedback.
Please check with the default app
You could also try with LMS rather than Music-Assistant … just in case it is the LMS SlimProto emulation in Music-Assistant that is causing problems for Squeezelite-ESP32
indeed
here is the link : Getting Started with LMS - Lyrion Music Server
It will replace your Home Assistant / Music Assistant server, thi sway we can diagnose if this is your device that is in cause or not<
thx
Hello,
I tested the Radiko firmware and didn’t encounter any issues — at least during the entire testing period.
After that, I reflashed the MuseRadioHomeAssistant firmware, and this time, I’m no longer getting audio “pop” sounds or noise artifacts (even though I had already reflashed it a few times earlier without solving the issue).
I also noticed that the “Components should block for at most 30 ms.” warnings have disappeared from my Home Assistant logs.
→ Is this a known firmware issue, or could it be related to how the flashing process is done?
Thanks
It’s unlikely that a reflash could be the reason for the fix, try it longer and let us know.
thx
Hello,
After a full day of testing with the MuseRadioHomeAssistant firmware, I haven’t encountered any more audio pops or crackling. The sound remained clean throughout all listening sessions.
At one point, music playback stopped, and the logs showed a network issue. It only happened once, possibly due to a brief Wi-Fi disconnection.
Also, the “Components should block for at most 30 ms.” warnings have completely disappeared from the Home Assistant logs.
All of this makes me think I might have made a mistake during the first flashes. I’ll probably try the Squeezelite-ESP32 firmware again, this time using a full LMS server as suggested by PaulWebster.
Thanks again for your support.
1 Like
Hello,
After 7 day, no new audio pops or crackling with the MuseRadioHomeAssistant firmware.
i have one last question, can i pull out the battery and desactivate led ?
Thank’s
no you cannot turn off the led and the battery is actually needed for the audio amplifier even when plugged. For the led you may use a piece of black tape or look at the post of @Hacker33 I do not support this and it will disable your warranty)
1 Like
Thank you for your reply. Could you please confirm if the battery is of good quality? I would like to avoid any risk of overheating or fire.
