Integretion with Music Assistant

[wave68runner]

Hi,

I have a few questions regarding the new audio functionality, as I am not sure I fully understand the intended architecture.

From the documentation, I understand that HA-compatible audio sources (such as squeezelite/piCorePlayer, WiiM, Cambridge Audio, Chromecast, DLNA, AirPlay devices, etc.) can be connected to the F441/F441M.

My first question is about the physical audio connection. Since the F441/F441M source input is a 2-wire connection, does this mean the audio is ultimately distributed in mono?

I am also trying to understand the relationship with Music Assistant.

Are MyHOME audio zones/sources exposed to Music Assistant in any way? If so, how should they be added or configured within Music Assistant? Can they be used as Music Assistant players, or are they only Home Assistant media_player entities?

Finally, would it be possible to provide a short setup guide or architecture overview showing:

how to configure the decoders , in your description you're talking about " Options UI" what does it means (sorry),
how they should be physically connected to the F441/F441M,
how everything should appear in Home Assistant and Music Assistant once configured?

Are there also specific dashboard cards that you recommend for controlling the audio zones, or does the standard Home Assistant media player card provide the best experience?

Sorry if I have misunderstood part of the implementation, but I think a practical example would help users understand how to deploy and use this feature correctly.

Thank you for your work on this project.

btw: As an experiment, I also tried using the Raspberry Pi that already runs Docker with Home Assistant and Music Assistant as an audio source via Bluetooth, but without much success so far. Audio playback is quite choppy and stutters frequently.

I still need to determine whether the issue comes from the Raspberry Pi itself, the Bluetooth implementation, or simply the fact that the Pi is currently sitting directly on top of my Wi-Fi router and may be suffering from RF interference.

More testing and experimentation to come! 😊

[GreenGrassBlueOcean]

Hi @wave68runner, thanks for the detailed questions. You didn't misunderstand much, and the docs don't explain this well, so here is the whole picture.

Architecture

Music Assistant / HA ──► MyHOME room entity (media_player.<room>)
                              │ claims a free decoder, powers the amplifier, forwards the stream
                              ▼
 Network streamer (Squeezelite/piCorePlayer, WiiM, Cast, DLNA…)
        │ analog audio out
        ▼
 F441/F441M matrix input S1…S4 ──► room amplifiers ──► speakers

• The F441/F441M is purely analog. It has no network audio. It only switches the analog line-level inputs S1–S4 to the rooms.
• You wire a streamer's analog out into a source input. MyHOME then tells HA and Music Assistant to play on it.
• Mono or stereo: the matrix is a stereo (L/R) analog device. The 2-wire connection is the SCS control bus. It carries commands, not audio. Whether you hear stereo depends on your amplifiers and speakers, so check the F441M manual for your exact setup.
• What Music Assistant sees: each room appears in Music Assistant as a player through its Home Assistant media_player provider. You play to the room, and MyHOME does the physical work behind it.
  • It claims a free decoder from the pool.
  • It wakes the amplifier.
  • It routes the room to that input.
  • It sends the stream URL to the decoder.
  • It mirrors the track title and cover art back onto the room entity.
• Don't pick a Music Assistant player as the decoder. The decoder must be the real hardware streamer, otherwise the audio loops back on itself.
• One decoder per concurrent stream. A group of rooms shares one decoder. Two different songs at once need two decoders and two matrix inputs.

"Options UI"

This is the integration's own settings dialog: Settings → Devices & Services → MyHOME → Configure. It has these fields:

• Source 1–4 names: what is wired to each matrix input.
• Default source per environment: optional.
• Decoder rows, up to 4. Each row has:
  • The streamer's media_player entity.
  • The matrix input it is plugged into.
  • A pre-gain offset.

Making a group player in Music Assistant

If you start a group from a room, that room becomes the leader. Music Assistant then keeps it ticked, as in the screenshot with Bureau, and you can't untick it. If you do manage to remove it while nothing is playing, the whole group dissolves. This is Music Assistant's ad-hoc grouping, and MyHOME can't change it. Create a Sync Group player once instead:

1. In Music Assistant open Settings → Players → Add group player → Sync group.
2. Name it, for example Huis. Add the MyHOME rooms under Group members.
3. Turn Dynamic members on and save. Without it the list is fixed.
4. In the player bar, open the player selector (bottom right) and pick Huis.
5. Play to Huis, not to a room. The group icon now shows Group members — Huis, and every room can be ticked and unticked, including the one you started from.

Known gap. If you untick the room Music Assistant is currently streaming to while music plays, you get a gap of a few seconds. Music Assistant has to move its queue to another player, and it can't do that without a stop. Unticking any other room only switches that room's amplifier off.

Dashboard cards

You can use the stock Home Assistant cards on the room entities. Nothing extra is needed:

type: media-control
entity: media_player.kitchen_sound

type: tile
entity: media_player.kitchen_sound
features:
  - type: media-player-volume-slider
  - type: media-player-playback

For a dashboard that only shows the rooms playing right now, use custom:auto-entities (HACS) with tile cards. There's a ready-made version in the docs under Lovelace speaker cards. The recipes page also has a multi-room view with source chips and an all-off button.

What's in b14 and what's coming in b15

Already in b14:

• Decoder pool, automatic companion decoder discovery and the DLNA streaming bridge.
• Multi-room grouping, including leader handover.
• Group state is kept across HA restarts.
• A group stays together when the anti-hiss timer parks it.
• Faster wake-up of a parked group.
• Fixes so rooms that hear a decoder they don't own switch off when it stops.
• A volume of 0 is no longer a mute.

Merged after b14, so in b15:

• The integration no longer guesses a streaming companion decoder.
• Decoders are guarded at runtime.
• The Music Assistant behaviour we depend on is pinned by a contract check, so a Music Assistant update that changes it gets caught.

In progress for b15 (#581):

• Auto-join: if a room is switched on, or its volume is raised, at a wall panel while a group is streaming, it joins that group. Music Assistant then updates the group to match what you hear.
• Source change at a wall panel: a room that switches to another source (for example the FM tuner) leaves the group, and the others keep playing. If the leader does this, leadership and the decoder move to another room without interrupting playback.
• New option: a toggle, "auto-join streaming", on by default.

Bluetooth

That's outside this integration. The choppy audio is more likely radio interference or the Pi's Bluetooth stack than MyHOME. A wired or network streamer (Squeezelite on a Pi, or a WiiM) into the matrix is far more reliable.

If you share your zone and decoder layout, I can help check your setup.

[wave68runner]

thanks for the reply,
but how can you have stereo with only 2 wires?

My Music Assistant doesn't show me the Myhome amplifier. Do i need to had a "player provider"?

There is a wrong link ins your answer : link to lovace speaker card

[GreenGrassBlueOcean]

Hi, thanks for the feedback, and sorry about the broken link. I'll fix the Lovelace speaker card link.

Stereo with 2 wires: The 2 wires are the 441 bus. It carries control only (power, volume, source, zone), not audio. To get stereo audio into the system you need two things:

1. The 441 bus to your amplifier(s), so MyHOME can control them.
2. An audio source interface that takes a normal stereo line-level signal and puts it on the 441 distribution as a source. For example, the Legrand L4561N "stereo control, 4 DIN" is a module like this. You connect it to the 441 distributor, and you connect your audio streamer to its stereo input. In my case that's a Cambridge streamer.

So the streamer provides the stereo audio, the interface module feeds it into the 441 system, and MyHOME and Home Assistant control the zones and sources over the 2-wire bus. MyHOME can't turn the 2 wires into stereo by itself.

Music Assistant doesn't show the MyHOME amplifier: Yes, you need a player provider. The Home Assistant integration for Music Assistant doesn't expose your other HA media players on its own. In Music Assistant, go to Settings → Providers → Add provider → Home Assistant (the Home Assistant player provider). Connect it to your HA instance, then pick the MyHOME amplifier media players you want to expose. They should then show up as players in Music Assistant.

Speaker groups: Once the amplifiers are players in Music Assistant, you can combine them into a speaker group. Here's my setup, with the "Huis" group made of several zones:

This works in b14. If you're on an older beta, please update to b14 and try again.

If the amplifier still doesn't show up after adding the provider, tell me your MyHOME version, whether the entity shows up as a media_player in HA, and any related log lines, and I'll look into it.

[wave68runner]

2. An audio source interface that takes a normal stereo line-level signal and puts it on the 441 distribution as a source. For example, the Legrand L4561N "stereo control, 4 DIN"

So you Always need an audio input interface from Bticino (like L4561N ) between the audio source and the F441M?

[GreenGrassBlueOcean]

I think yes this is the case in my house 2. An audio source interface that takes a normal stereo line-level signal and puts it on the 441 distribution as a source. For example, the Legrand L4561N "stereo control, 4 DIN" So you Always need an audio input interface from Bticino (like L4561N ) between the audio source and the F441M? — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you commented. Message ID: <OpenWebNet-HA/MyHOME/repo-discussions/585/comments/18697792 @ github . com>

[wave68runner]

OK, I think it's important to mention that for all the community

[wave68runner]

The last thing I need a bit of help with:

In my Music Assistant setup, the player that is connected as the audio source to the F441M is Livingroom 1_3519, but I want to play the music in the MyHome room "Bathroom".

How should I do this?

Is that why I need to create a group containing Livingroom 1_3519 and Bathroom, so that both zones play at the same time?

[GreenGrassBlueOcean]

Hi @wave68runner,

No, you should not create a group containing Livingroom 1_3519 and Bathroom.

Here is why and how the setup works:

1. How playing to a room works

Livingroom 1_3519 is your physical audio streamer / decoder (plugged into the F441M matrix input), while Bathroom is the destination room / amplifier zone.

You do not group the streamer and the room together. Instead:

1. Ensure Livingroom 1_3519 is configured as the decoder in the MyHOME integration settings:
   • Go to Settings → Devices & Services → MyHOME → Configure.
   • Under decoders, map Livingroom 1_3519 to the matrix input it is physically connected to (e.g., Source 1).
2. In Music Assistant (or Home Assistant), simply select Bathroom (the MyHOME room media player) and press play.

Behind the scenes, MyHOME automatically:

• Claims Livingroom 1_3519 from the decoder pool
• Turns on the Bathroom amplifier
• Routes the F441M matrix input to the Bathroom zone
• Streams the audio to Livingroom 1_3519

---

2. When would you use a Group in Music Assistant?

You only need a group if you want to play the same music in multiple MyHOME rooms at the same time (e.g., Bathroom + Bedroom). Even then, never add the source streamer (Livingroom 1_3519) to the group—only add the destination rooms.

To create a group player in Music Assistant:

1. In Music Assistant, open Settings → Players → Add group player → Sync group.
2. Give it a name (e.g., House or All Rooms).
3. Under Group members, select the MyHOME room players you want included (e.g., Bathroom, Living Room, etc.).
4. Turn Dynamic members to ON (this lets you tick and untick rooms on the fly without dissolving the group).
5. Click Save.
6. In the player bar (bottom right), pick your newly created group player and start playing.

[wave68runner]

Understood thx!!

[GreenGrassBlueOcean]

Hi @wave68runner,

We have updated the Sound System documentation and troubleshooting guide based on your very logical questions to ensure this is completely clear for everyone in the community!

The changes have been submitted in Pull Request #589 (and will be live on the documentation site once merged):

• Pull Request: docs(audio): address community questions on stereo wiring, source interfaces, and player routing (#585) #589
• Updated Sound System Guide: docs/configuration/media_player.md
• Updated Troubleshooting FAQ: docs/configuration/troubleshooting.md

What we added:

1. The 2-Wire vs. Stereo Audio Question: Explicitly clarified that the 2-wire SCS bus carries digital control frames only (zero audio) and that physical audio distribution travels over dedicated analog cabling. Documented the requirement for an audio source interface (e.g. Legrand / BTicino L4561N, L4560, or 3482) to inject line-level audio into matrix inputs S1–S4.
2. Streamer vs. Destination Room Zone: Added a dedicated section explaining why you should never group your backend streamer (e.g. Livingroom 1_3519) with a destination room (e.g. Bathroom), how Dynamic Proxy routing works automatically behind the scenes, and when groups are used.
3. Music Assistant Player Provider: Detailed the step-by-step setup to expose MyHOME rooms through Music Assistant's Home Assistant Player Provider and noted the prerequisite of having at least one decoder mapped in MyHOME options.
4. Bluetooth Streamer Warnings: Added guidance regarding RF interference and Bluetooth latency when streamers sit near Wi-Fi equipment.

Could you please take a look when you have a moment to see if the new documentation is clear, easy to follow, and answers everything you encountered? Any feedback is greatly appreciated!

[wave68runner]

It’s clear now for me. Maybe because I understand the concept. 😅
I will remove in every documents the part over analog signal on the s1-s4 entry’s : Explicitly clarified that the 2-wire SCS bus carries digital control frames only (zero audio) and that physical audio distribution travels over dedicated analog cabling

In reality you have audio and scs command on 2 Wires.
In this old catalog the different sources and also schematics

Complete catalog