Change DSP presets via Home Assistant

[fabiankrauss]

It would be great if you could activate the DSP presets that you have saved in Music Assistant for a playback device using Home Assistant.

Maybe some action like music_assistant.select_sound_mode or a input.select field per mediaplayer?

[haldi4803]

Yes that would indeed be great!

[devedsmith]

Yes I love this idea.

[RaceNJason]

Why isn't there a way to do this?? Changing DSP presets and the ability to Enable/Disable them from elsewhere in Home Assistant would definitely have advantages. In my case the wife's acceptance of Home Assistant has a LOT to do with Music Assistant since Music is her thing. The problem is that most of the time she wants nice quite music in the background and therefore wants a 'fine resolution' on the lower end of the volume. When I have 0 dB boost for Input and Output (or even a negative) this gives that 'fine resolution' she wants from the volume control. But...then she wants a party, hears that one song she wants super loud and trying to yell at me to change the DSP preset before the song is over...obviously doesn't work. If I simply had a button on the same screen that she controls her music and the volume from OMG would that make for a happy wife. Instant super boost for blasting out loud music and then instant quite fine control over the lower volume end is the reason for this requested feature. Add me to the list.

Unfortunately I can tell that if there are only 4 people here requesting this feature it will never, ever be done. What is the unfortunate thing about this is that I'm sure this is a feature many people would use if they new about it. Honestly I didn't even know about the DSP presets until maybe 6 months of using Music Assistant and wishing I could get way more volume out of our system because our speakers could easily handle it. Anyway my point is that maybe the developers will look twice at this even if there are not many people requesting it if you better describe your use cases so that they can envision why it would be useful to implement even when people don't realize this is what they want (if that makes sense). So anyone else who decides to add to this list, don't just do it with a vote up or a "I agree" posting...let the devs actually know why this would be a good use of their time to implement.

[remon1496]

I would like to have this ability also, but... I think this would be blocked until the set DSP is remembered/defined in backend.

Afaik there are presets, but there isn't really a way to request which preset is active via api.

I've requested a feature for this: https://github.com/orgs/music-assistant/discussions/5681 and I think its closely related to this one, or even a dependency for this to be implemented.

[Hukuma1]

Was very surprised this wasn't exposed as a service call already! IMO this is a very powerful feature. It could be used in automations during night time for lower volume (my speaker gain is high from my AMP, that I cannot dynamically change). Or going a step further you could automate which preset to use for which music. Maybe classical music gets the less bass preset, etc.

[OzGav]

Just following up here. You can use the API to do this. The endpoint is /config/players/dsp/apply_preset

[remon1496]

Applying a Music Assistant DSP Preset from Home Assistant (MA 2.10+)

(written with robot's help)

Music Assistant doesn't (yet) expose DSP presets as a native Home Assistant service, but you can call its internal API directly using a rest_command. Here's how to set it up.

Prerequisites

• Music Assistant server running and reachable on your network (tested on more recent 2.10 beta, not sure if available in 2.9.x)
• A Home Assistant Long-Lived Access Token (Profile → Security → Long-Lived Access Tokens)
• The player ID of the target speaker/zone
• The preset ID of the DSP preset you want to apply

Step 1: Add the REST command

Add the following to your configuration.yaml:

rest_command:
  ma_apply_dsp_preset:
    url: "http://YOUR-SERVER-IP:8095/api"
    method: POST
    headers:
      accept: "application/json, text/html"
      authorization: "Bearer LONG_LIVED_TOKEN"   # Settings > Profile
    payload: >
      {
        "message_id": "1",
        "command": "config/players/dsp/apply_preset",
        "args": {
          "player_id": "{{ player_id }}",
          "preset_id": "{{ preset_id }}"
        }
      }
    content_type: 'application/json; charset=utf-8'

Replace:

• YOUR-SERVER-IP with your Music Assistant server's IP address (port 8095 is the default MA API port)
• LONG_LIVED_TOKEN with your Home Assistant long-lived access token

Restart Home Assistant (or reload YAML configuration) after saving.

Step 2: Find your player ID and preset ID

Player ID: found under the player's entity attributes in Music Assistant, or via the MA API.

Preset ID: call the config/dsp_presets/get command to list all available presets and their IDs. You can test this directly using the built-in API docs at:

http://YOUR-MA-IP:8095/api-docs/commands

Step 3: Call it from an automation

Use the rest_command.ma_apply_dsp_preset action, passing in the player and preset IDs:

action: rest_command.ma_apply_dsp_preset
data:
  player_id: "THE-PLAYER-ID"
  preset_id: "THE-DSP-ID"

You can drop this straight into an automation's action list, or trigger it manually via Developer Tools → Actions to test it before wiring it into a full automation.

Notes

• Since the token is stored in configuration.yaml, keep that file out of version control or use a !secret reference for the token instead of hardcoding it.
• If the call fails, check the Home Assistant logs for the REST response — a 401 usually means a bad/expired token, while a 400 usually means an invalid player_id or preset_id.

[RaceNJason]

So when I login into the 8095 port and successfully log in with admin credentials, I only see "config/players/dsp/get" and "config/players/dsp/save". I do not see any "config/players/dsp/apply_preset". I've also found "config/dsp_presets/get" and "config/dsp_presets/remove" and "config/dsp_presets/save".

So I successfully created the rest command in my configurations. Successfully made an automation that called it and verified player ID and DSP preset ID. When running the automation I get no errors. But...nothing happens and I suspect because the "config/players/dsp/apply_preset" doesn't exist and was fabricated by an AI tool.

Yes, I did verify my token. Actually I just created a separate user/token just for this. I figured I missed something, but when I can't find that command in the Commands Reference Music Assistant Web UI where it verifies I've logged in as an admin, I suspect it is the API that is preventing my success.

[remon1496]

Ah okay, then it's a 2.10 feature (will release the 26th). Just let the robot write and correct, haha.

I've set this up in HA combined with 2.10 beta and works like a charm. :)

[RaceNJason]

So...would that possibly mean that when 2.10 get's officially released that this will get directly exposed to HA, or will it still require the rest command?

[OzGav]

Still the rest command