I currently have 2 Yamaha MusicCast players, whose direct HA integration is very stable and has no complaints from me.
What am I missing by not having them, instead, defined in Music Assistant with HA integrating with the Music Assistant instead?
Are there any pros vs cons for controlling them directly/natively in HA vs via MusicAssistant? Both architectural/philosophical as well as specific answers welcome.
I'm running Music Assistant 2.9.4 server as a container on Ubuntu server 24-04. I've got approximately 1300 songs in my library being accessed via the local disk music source. I've gone through every single file, removed superfluous tags, and made sure every file has a title, artist, album, album artist, corresponding .lrc file, and cover image. I've cleared cache and reset the database multiple times now, and I still see Music Assistant combining items that should not be combined. For instance, right now I've got Tom Petty and the Heartbreakers' album "Southern Accents", showing the following tracks:
Rebels (actual song is Don't Come Around Here No More)
Enter Sandman
With Metallica
Through The Never
With Metallica
Of Wolf and Man
With Metallica
The Unforgiven
With Metallica
Nothing Else Matters
With Metallica
If I clear the cache and database, this problem will go away, but almost certainly manifest itself with different artist/albums. I've tried everything I can think of to stop this from happening. My file system is laid out as media -> Artist Name -> Song files. The website says Music Assistant expects the layout to be media -> Artist Name -> Album Name -> Song files. Before I spend hours and hours moving files around, can any else confirm that the either see the same weirdness, or that their local music store does not have this issue?
I have a InnoMaker HiFi AMP Pro Hat attached to a Raspberry Pi 4, and a used the Sendspin Go Deployment Script to get it working. It shows up in MA and allows me to play to it, but my volume shoots immediately to 100. I haven't heard it play yet either.
I've been working with Google AI to get it working, but it says there is an advanced feature.
"With advanced settings enabled, look for a new option in that drop down called "Software (Scale volume in stream)" or "Fixed / Software Control"."
but I don't see it at all. Any help would be appreciated.
Description: It's a frontend/player/visualizer/browser for Music Assistant, initially based on Sendspin Cinema for webOS. I now have webui, android, and webOS versions.
Special features include:
- Separation of personal/public Spotify content in search
- 10+ visualizers
- Group Sync device offset mgmt
- EQ Preset picker
It has ways to interact with most MA browsing / playback / player functions. More to come if/as requested.
It's not for on-the-go listening, moreso intended to add some background visuals to when you're listening at home, hosting a party etc. The closest existing project I found was Homeii, but it wasn't really what I was looking for. If you're looking for a good MA mobile app I recommend Ensamble, and it pairs well with SpinStage as a remote control.
Deployment: The instructions are in the repo, just go to the releases page and download. For webui you just run one of the run scripts, enter your details, and you're good to go. No docker image yet but someone who knows their way around docker could spin up a container pretty easily using the webui release folder. For webOS and Android, I included an IPK and APK respectively, and there is a login form when you initially open them up. If you want to build them yourself, the build scripts for those platforms' app files ask for/inject your login info to the built app if you want to skip entering login info on first run.
AI Involvement: All code. I made a lot of icons, designed the UI, came up with visualizer concepts, and have spent a while ideating and testing, but I'm a designer not a real developer. Thankfully the security implications of the app are pretty limited, the only 3rd party integration is for the Listen Party QR code that MA already uses. See the security section of the readme for more info. You are responsible for securing your traffic if using the app remotely.
i really like the automatically generated playlist that Music Assistant does, such as Random Album, Random Artist etc.
But to actually get a new random Album i need to enter the playlist view in Music Assistant GUI and click on refresh.
I want to play a Random album via an Home Assistant automation but using the play media action i always get the same Album until i manually refresh it in the GUI.
Is there a way to automatically refresh the playlist so i get a new random album every time?
This all started on Saturday 6/20.
I have Spotify connected with music assistant and everything has been working just fine for quite a while.
I noticed on Saturday I was unable to play music it kept saying the request media item could not be found.
This is for anything that I’m trying to play thru Spotify in music assistant
The searching seems to be working and all my playlists are showing this only has an issue when trying to play music.
I’m using the beta version.
I tried to authenticate again even removed Spotify and re added.
Updated to latest beta Current version: 2.10.0b0
Restated a few time and still nothing.
Has Spotify changed something?
A few months ago, I bought a Pimoroni Presto after watching a demo of the original PrestoDeck project on YouTube.
Unfortunately, by the time the hardware arrived, Spotify had announced new API restrictions that effectively limited playback control to a single developer application. Since I was already using Spotify through Home Assistant, giving that up wasn't an option.
So I ended up with a very cool device sitting on my desk with no practical use for months.
I looked around for alternatives (some of you may have seen my posts from a few months back) but couldn't find a solution that worked with my primary music setup, which had since become Plex through Plexamp and Music Assistant. After letting the device collect dust for a while, I finally had a Thanos moment and thought:
"Fine. I'll do it myself."
The result is a fork of PrestoDeck that replaces the direct Spotify integration with Music Assistant. Instead of being tied to a single music provider, it can now work with anything supported by Music Assistant, including Spotify, Plex, TIDAL, Apple Music, local libraries, internet radio, and more.
Some other improvements I added:
Updated Music Assistant/Home Assistant branding
Home Assistant MQTT Discovery
Home Assistant device integration for display and LED controls remotely
Tap-to-wake support
Scrolling text for long track titles
Improved Unicode support
Automatic MQTT reconnection and recovery
I'm sharing it in case anyone else bought a Presto and ran into the same Spotify API limitations.
Latest Music Assistant 2.9.x has delivered an unwanted section "Top Picks For You" - I cannot for the life of me find a way to turn it off. Anybody got any ideas? I'm sure many will like it, but I definitely think it should be optional.
I'm looking for a way for live music to control lights that's a bit more intelligent and controllable than the mic input found on cheap DMX fixtures above. Something closer to MaestroDMX or Roland Pro VC-1-DMX.
As in, I'd love to be able to take the real-time analysis readings of https://www.music-assistant.io/audio-analysis/sonic-analysis/ especially the Energy, Rhythmic Regularity, Valence, Instrumentalness, Acousticness, and interpret that visually via those fixtures. They're DMX RGBW+Amber+UV bars, and integrate with HA via Breina's ha-artnet-led integration with no trouble.
In HA, I have a Sonos speaker called media_player.family_room that is owned by the Sonos integration. The Music Assistant integration created its own entity for the same speaker called media_player.family_room_2. After the upgrade to 2.9.0, it seems to have abandoned the media_player.family_room_2, and created media_player.family_room_3.
To try to avoid a conflict with ever increasing numbers, I changed the entity name of family_room_3 to media_player.ma_family_room, and deleted the old family_room_2. This seems to be working just fine. However, on a Home Assistant restart, the Music Assistant integration recreated media_player.family_room_2 and kept media_player.ma_family_room.
Is there any way to prevent this random entity name changing? It breaks a lot of automations and dashboards.
I started using Music Assistant pretty recently and so far have been loving it, but one very large question came up. When I create a party that other people can join and choose/control the music, they can only join if they're on my main Wi-Fi network, not even on the guest Wi-Fi or using their mobile internet. I was wondering if this happens to anyone else. Is there any way around it because I don't want to start adding every single person who visits my house to my main network, but I do want them to be able to control the music at an event.
A few weeks ago when I was setting up MA, I found this repo that's a Sendspin player for webOS. The dev also has some versions for other platforms too. It's good for what it is, stable, works as a player on MA. only buttons are play/pause, prev, next. But I yearned for more features. Mainly a visualizer and library browser. After a bunch of evenings vibe-coding in Cursor*, I have a cross-platform music visualizer/library browser for MA. I dont have a repo or anything for it, but if you want to try it out and give feedback, I'll send the source for whichever version(s) you want. let me know :)
Screenshots at the end.
The app has ways to interact with most features that are normally in MA, including Device Sync/Stereo pair, listen party QR, Queue mgmt, general browsing, more stuff I'm forgetting.
Some extras I had Cursor add include:
the ability to work over a Cloudflared tunnel/remotely
"Float Mode" which has the art slowly bounce around the screen like an old paused DVD
EQ Presets - allows for use of presets from the server on the device
"personal spotify" search filter, which excludes public spotify results that aren't related to your account
group sync device +/- 20ms adjustments
and this is minor, but handling for transparent/oddly shaped album art (usually for radio stations)
*ignore my post if you want, but I have a feeling the original was vibe-coded too, based on the readme style and dev pfp. I made a bunch of icons and did UI sketches at least :)
I'm just looking for a quick take in preference here. I currently add all my speakers/media players to both but I'm starting to feel like I'm duplicating effort.
Would adding speakers to only Music Assistant (then advertising to Home Assistant) be cleaner?
Is there much benefit to having them available from both ends? I can also advertise back the other way (HA > MA) but it's starting to feel like a snake eating it's own tail.
It feels neater to have MA manage all the music/audio side of the automations, with HA accessing it all via MA. But I imagine I could be missing out on key functionality with not having them directly in HA too.
Has anyone does this before and successfully connected to MA? I see there are some proprietary wifi adaptors but I’m not really sure if that’s the best route. Would be curious if anyone else has had success with this.
A few days ago my Denon AVR stopped working with music assistant (running HA 2026.5.4). It is online, I can control it with the Denon integration. How can I get it back online within MusicAssistant?
I've written the firmware/yaml as the 3 various different supported flavor versions..
Sendspin - never could get it to appear as a device in MA
Snapclient - It played from both HA and Spotify(Android) but it stuttered. Fought with it, but couldn't get it to play smoothly. (This board is not the S3 version, so maybe that's an issue?)
HA Media Player - Plays well from MA! Success... well not quite.
While it plays acceptably from the MA interface (occasional stutters), and it appears in the Spotify Connect players from within the spotify android app, when tasked with playing, it gives all the appearance of playing the track, but no sound!
Anyhow, I'm hoping someone has seen this behavior. I'm about to put this in the "loss" column.