🎵 HOMEii Flow – a full music app experience for Music Assistant inside Home Assistant

akszyn_pl · August 1, 2026, 9:32pm

When polish language and how to help translate ?

No_One_1 · August 4, 2026, 1:52pm

Ok, I’m really at a loss here. As I stated above, since updating to MA 2.10.0, HomeII has lost one of my players (that previously worked fine) and just refuses to get it back. The player works fine in MA and HA with other player cards but nothing I do makes any difference to HomeII.

Since my last post, I’ve removed the card and re-added it - that did nothing.
I’ve re-downloaded the card -no change
I’ve removed the card from HA entirely and ran without it for a full day before adding it again - no good
I’ve even removed and re-added the Wiim Integration itself, but nothing changed.
I even added a second Nvidia Shield in another room and HomeII picked it up almost immediately, so I’m unsure what my little Wiim did to piss it off so much.

If you have any insight you could offer on this, it would be most appreciated as I love this card and not being able to really use it is rather frustrating.

Cheers.

RaA11 · August 6, 2026, 11:38am

Thanks for the additional details. Reinstalling the card not changing anything—and the new Shield appearing immediately—suggests that player discovery itself is working.

HOMEii Flow 5.9.3 only lists Home Assistant entities it recognizes as Music Assistant players. Other media cards may also accept the native WiiM entity, so their seeing it does not necessarily mean HOMEii should. After the rename, the new entity may no longer expose the MA markers or registry platform HOMEii expects.

Please paste the state and attributes of media_player.office_office_player from Developer Tools → States, and confirm whether Home Assistant lists it under the Music Assistant integration or the native WiiM integration. An in-card Diagnostics report would also help confirm whether HOMEii classifies it as an MA player or only as a generic media player.

Replacing the MA token or reinstalling the card will not affect that classification. Also, card removal does not necessarily clear its stored player preferences, so please check that the old entity is not still present under Pinned, Excluded, or player-order settings.

RaA11 · August 6, 2026, 11:40am

There is currently no scheduled date for Polish, but contributions are very welcome.

Please follow the language contribution guide and use the translation glossary for context.

In short:

Copy src/localization/en.js to src/localization/pl.js.
Translate only the text values—do not change the keys or placeholders.
Register pl as Polish in src/localization/index.js.
Test it with language: pl.
Submit the changes as a pull request.

Thank you for offering to help!

No_One_1 · August 6, 2026, 2:14pm

Thanks for taking a look at this. I’ve been tearing my hair out for days over this. To confirm, Home Assistant lists the device under the WiiM integration. In Dev Tools > States, the device lists as “Idle” and it’s attributes are as follows:

volume_level: 0.5
is_volume_muted: false
source: Network
shuffle: false
repeat: "off"
entity_picture_local: null
device_class: speaker
friendly_name: Office Speaker
supported_features: 154175

And here is the in-card diagnostics:


V
Editor version
5.9.3
Visual editor runtime is loaded.
V
Diagnostics version
v7
Diagnostic v7 is active.
i
Browser
Firefox 153.0 / Win32
i
Viewport
1760x876, DPR 1.09, touch 0, lang en-US
i
Diagnostic privacy
External/private hostnames are redacted in visible and copied diagnostic output.
V
Home Assistant frontend
Editor has a Home Assistant frontend object.
V
Music Assistant services
6 service(s) are exposed by Home Assistant.
V
Integration mode
Core card features can run through Home Assistant. HTTP/HTTPS only affects optional Direct/Sendspin browser access.
i
HOMEii Flow Engine
auto
Engine was not detected. This is OK: the card will continue using the current Home Assistant/Music Assistant frontend path. Last error: Unknown command.
V
Integration signal
services yes, direct configured
V
Music Assistant players
6 strict MA player(s), 32 generic HA media_player(s).
i
Player filters
0 pinned, 2 excluded.
V
Music Assistant config entry
loaded
Home Assistant returned a Music Assistant config entry.
V
ma_url
http://<home-assistant-host>:8095
Direct Music Assistant URL is configured. Browser reachability is checked separately. protocol=http, host_type=home-assistant-host, port=8095, path=/
!
Access path
Music Assistant URL is local/private. Direct/Sendspin should work only from the local network or VPN.
!
Direct Music Assistant API
Direct Music Assistant API is blocked by the browser before HOMEii receives a response. This is usually CORS/preflight or local-network browser access. Core playback can still work through the Home Assistant integration; leave ma_url empty unless you need Direct API or Sendspin.
V
Sendspin browser support
WebSocket yes, AudioContext yes
V
Sendspin endpoint
ws://<home-assistant-host>:8095/sendspin
Computed Sendspin WebSocket endpoint. This readiness check does not open a socket.

I don’t see the device in the pinned or excluded players section of the card’s UI. I currently have 2 players excluded (a tv and streambox that aren’t being used) and those show as I would expect. Nor do I see the device in the player-order settings.

It’s funny that you mention the player discovery, though, as I think that may be where things are hung up here. I removed the second shield last night as a test and when I re-added it to HA, it no longer appears in HomeII. Is there any way to clear the stored player preferences and just have the card start over from scratch?

RaA11 · August 6, 2026, 3:40pm

Thanks—this diagnostic identifies the cause. The entity you posted belongs to the native WiiM integration and lacks Music Assistant markers such as app_id: music_assistant, mass_player_type, and active_queue. HOMEii Flow 5.9.3 detects 6 strict MA players, so it intentionally filters out the 32 generic HA media players, including this WiiM entity.

This is not a stored-preferences problem: Diagnostics confirms 0 pinned, 2 excluded. The re-added Shield is likely being filtered for the same reason.

Please open Settings → Devices & Services → Music Assistant → Entities and look for the MA-provided entity corresponding to the Office Speaker. If it is missing, reload the Music Assistant integration and confirm that the player is available/enabled there. Reinstalling HOMEii or the native WiiM integration will not recreate the MA entity.

You can give the card a new unique card_id to start with fresh local settings, but it will not make a generic WiiM entity appear. Also, ma_url can remain empty unless you specifically need Direct API or Sendspin; the reported browser block is unrelated to normal player discovery.

No_One_1 · August 7, 2026, 1:27am

Well, i’ll be a son-of-a …

Yeah, the WiiM had a disabled entity that, for some reason, I had not even noticed all this time. Enabling it made HomeII pick it up immediately. At least now I’ll know where to look first when I hook the other shield back up.

Thank you so much for your help with this! I greatly appreciate it and simply can’t wait for the next release.

Cheers!