I missed the word new
1 Like
Just had the same issue happen again to me with the same device (a Google Home Mini, the only one I have). Tried doing what I thought worked before with no luck. Then tried a combo and adding/removing it from the cast group (in the Google Home app) and then restarting the Chromecast provider in MA and it finally showed up.
thx, iâll try my luck when i get homeâŚ
TLDR; Is MA supposed to install on HAOS using a 172.30.x.x address instead of my 192.168.1.x LAN ? Is that why it canât detect my squeezelite device ?
I assume this is me mis-reading the instructions, rather than reporting as a bug.
I have given up on trying to get Voice Assist and a music_player playing nicely together on the same RasPi. It sounds like Nabu Casaâs future VoiceKit may do that, and I am happy to wait for it to be released.
In the meantime I have gone back to the objective of setting up a music player in the kitchen, mainly so my lady can listen to her old Italian 45s while cooking.
Install squeezelite player and Music Assistant ⌠sounds simple but obviously I am doing something wrong.
- I have installed squeezelite on the RasPi 4B and tested that it plays music locally.
- Next I installed Music Assistant server (2.1.0) add-on to my Home Assistant OS (running in a proxmox VM), and started it.
- I added MAâs Home Asssistant Plugin Provider and Home Assistant Media Player Provider, and selected both my existing MPD devices.
I add Slimproto (Squeezebox players) Player Provider with default settings.
I add RadioBrowser Music Provider - but not the Filesystem (remote share) because it is large and I need to finish copying all the [artist] ID3 tags into [albumartist] tags first. - Ohhh, thereâs a notification of new devices detected by HA. It is Music Assistent, so click [configure] and it asks "Do you want to add the Music Assistant Server
http://172.30.32.1:8095to Home Assistant? "
Now, my LAN is is the 192.168.1.x range, so why would I want to add a server at an unreachable address ? But the only option is [submit]. It finds both the existing MPD devices which are configured in HA, I add the Areas for them, and [finish].
MA does not detect the new squeezelite device.
When I click the Integrationâs [configure] button again it defaults to this unreachable address.
Now, ⌠I have enough IT experience to understand that HAOS internally uses docker containers for its addons, and that 172.30.. addresses is probably used by docker to communicate between different containers. BUT HAOS is supposed to do this all transparently, so the instructions in Installation - Music Assistant which refer to docker are for other HA installation types.
- Is MA unable to find my squeezelite RasPi because it is looking on the 172.30.. network ?
- Am I supposed to change the 172.30.32.1:8095 to 192.168.1.98:8095 ?
- Or would that mean two machines are using the same IP address - in which case I should allocate a different 192.168.1.x address for MA server ?
Everything you said is correct. That IP is the internal docker address.
Go through the troubleshooting page of the docs as the squeezelite player should be detected. If you havenât tried picoreplayer give that a go as it definitely works.
I am experiencing Music Assistant ARTWORK ANGUISH (for days now)!
I use the exact same smb share for Music Assistant, Volumio, and EMBY. The latter two show artist and album artwork perfectly without any fuss. MASS shows artist artwork for about 10% of the 1757 artists (even though I have included artist.jpg and folder.jpg files within all the artist folders). All tracks contain an albumartist tag.
What arcane requirement have I yet to discover?
Thanks for any suggestions.
Look in the logs for errors. Ask the question in a GitHub discussion for more extensive assistance.
One warning (port 1400 already in use). No errors. No clues.
If two other music managers can find and supply the artwork, why canât MASS? I have scoured github and this discussion topic to no avail.
As I said ask in GH if you want more help but if you are happy with the other music managers then stick with those
I am having a problem where music assistant sees the juke audio zones but will not play music to them. If I choose a homepod it will play music. But with the juke audio zones it just never changes from > to " when trying to start a track. Any help would be greatly appreciated.
What is Juke?
Yes. That is it. It is an AirPlay receiver. I can AirPlay to it from an iPhone. But music assistant can see it it but play doesnât work.
1 Like
It appears it may only support Airplay 2 which MA does not (most manufacturers make it backwards compatible but some do not)
Thatâs such a bummer. Any plans to support AirPlay 2? Or does anyone else use juke audio amps and have a work around?
Probably eventually but it is low priority as manufacturers should be making their devices backwards compatible and there are many other jobs to do.
1 Like
Thanks. I learn something every day, even at my age 
2 Likes
This is looking great! I need help with two things -
- I mainly use Google Home mini and Nest mini as my speakers throughout the house. When I start to play a song on any of these speakers (from Jellyfin library that I connected), the audio stops after a minute or so. The MA interface shows that the song is continuing to play. If I manually change the track position, audio starts back up (but goes out again after a minute. Same if I change the track, audio plays for a bit and then stops even though the track is progressing.
- I am trying to add my Plex Music library to get all my playlists. However, MA will by default pick my âAudiobooksâ library (which is also configured as a Music library in Plex. I tried to change the library from the interface, but no interface opens up to let me select the other library. I also tried adding my Plex server the second time, but it keeps picking the âAudiobooksâ library by default and doesnât let me pick the âMusicâ library.
For 1 have a look here Google cast : plays a few seconds then stops ¡ Issue #2659 ¡ music-assistant/hass-music-assistant ¡ GitHub
Canât help with Plex sorry. Try asking in Discord.
Thanks ⌠but not helpful. You couldnât even say whether MA server is supposed to use the 172.30.32.x address ?
The MA documentation ? The squeezelite documentation ? Is there any real documentation for squeezelite ? Iâm currently reading various threads at https://forums.slimdevices.com/forum/, but of course it doesnât hive hints on how to connect to Music Assistant.
I already spent weeks going down dead ends trying to find out whether a music_player can work with wyoming-satellite, reading through all the documentation I could find before starting on this. Obviously I missed something - or more likely I missed an oblique hint that only an experienced developer is supposed to know (like the reference to ârun in the same Layer 2 networkâ).
When you say âdefinitely worksâ, does that mean that piCorePlayer can access the MA music database ⌠or only that MA can push music to squeezelite ?
piCorePlayer is not automatically detected. But going into Music Assistant > Settings > Players and doing [Add group player] was able to find it at 192.168.1.90. This allows MA to âpushâ tracks and radio to the piCorePlayer, but piCoreplayer and/or Jivelite are unable to connect to Music Assistantâs library.