Dashboard: Sonos card

Thanks, @Neep
I’ll take a look

1 Like

@PunxsutawneyPhil, I’m doing a bit of self trouble shooting as well - is the SONOS card reliant on the Spotify integration and/or Spotcast (custom) integration? I have both installed and that might be what’s causing a conflict.

If it’s not I can try deleting both those


So I’ve removed (disabled) the Spotify integration - that fixes the issue but means I then can’t see any of my Spotify media via the media browser.
When I then re-enable the Spotify integration I get the same issue.

Removing the Spotcast integration appears to have resulted in nothing. It seems to be an issue with the Spotify integration.

I’m on the latest release of HA core, SONOS card and Spotify integration.

That makes no sense to me, that Spotify integration should affect it.
I have the Spotify integration and don’t see any issues.
Since I can’t reproduce it here, could you try the following:

  1. Enable Spotify integration.
  2. Remove one config at a time from your Sonos card, and see if the problem is still there. I.e. start by removing mediaBrowserItemsPerRow: 4

…please also try with earlier versions in HACS. By finding which version it stopped behaving it will be a lot easier for me to try and find a fix.
image

I reinstalled my Spotify integration which appears to have fixed the problem, at least currently.

Never mind - will continue troubleshooting based on your advice, thank you :slight_smile:
It’s particularly frustrating as the whole instance freezes when it happens so I can’t extract logs as well. Do you have any recommendations on how to extract logs in this case?


V6.10.1 = described prior behaviour.
v6.10 = when I click on a folder, such as ‘playlists’ it just auto returns me to the to level view (favourites in this case). Same with each menu I select - kicks me back and returns me to the favourites view. Also the card as a whole ‘flickers’, no other cards are doing it.
v6.9 = described prior behaviour.

All of the above is happening with just the base media-browser settings. No changes to the yamel less for specifying the entity as one of my Sonos speakers.


The rest of the card works perfectly - it’s purely when using the media browser.

Does the Spotify integration need to the Sonos speakers specified as an output source for the card to work correctly perhaps?

See - ‘Selecting output source’ above? I haven’t done that but I haven’t need too previously with other media cards. You mention you also run the Spotify integration, have you done this?

No, you don’t need to do anything specific for the Spotify integration.
Does v6.7.2 work?

It did not.

However I’m noticing other odd things - such as none of the music I have added to My Sonos is showing in HA at all (both the media browser in the card and the native Media library). Not entirely sure this is an issue exclusively with the card Phil but more and issue with my HA somewhere. Thanks for all the help.


Okay so I’ve developed a work around, for those that might face the same problem as me:

Previously I was using the media browser to browse to my spotify playlists. This was ultimately what was causing my HA instance to crash. I have now added all my spotify playlists to My Sonos as favourites and they work fine.
Interestingly it was a similar story when using the native HA media library - not sure if it’s something to do with the Spotify integration in this case. However, once you get everything into My Sonos it works absolutely fine.

Great card and a great creator - it’s rare to see Devs be so quick to respond and help! Thanks Phil.

1 Like

Hi, i’m at a loss. I ran this custom addon (absolutely love it btw) for a while with no problems at all. Then from one day to the other, it didn’t work anymore and I started seeing these errors in my browser console.

I’ve reinstalled multiple times, used older versions, restored backups of my HASS instance, nothing seems to work. I haven’t changed anything about it either in quite a while, but it just doesn’t want to work anymore.

Error messages:

custom-sonos-card.js:397  Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'id')
    at Xt.createStore (custom-sonos-card.js:397:188)
    at Xt.render (custom-sonos-card.js:385:938)
    at Xt.update (custom-sonos-card.js:23:292)
    at Xt.performUpdate (custom-sonos-card.js:11:5085)
    at Xt.scheduleUpdate (custom-sonos-card.js:11:4732)
    at Xt._$Ej (custom-sonos-card.js:11:4640)

Anyone have an idea how to fix this?

Hi, what an amazing pieco of software this card! Almost all I wanted in 1!

I have asked for a feature. Might already be possible but I do not know how. Feature:

The question:
I would like to disable some lines in the card. E.g,:
image

Synology Photos

mediaBrowserTitlesToIgnore

It’s in the readme and the first post

1 Like

Yes, got it. Totally read over that as I was searching for “hiding” and “favorites”.

Another question. I added spotify. Then add another “users” (2nd api).

Another user does not see “my” spotify. Is there some card setting to show it or is that a homeassistant overall setting?

Sorry for being blunt, 1st time doing “media” in HA.

EDIT: Never Mind, solved it

Great card this! Thanks!

However need some help;

I have 4 different Sonos devices, all Play 1, in 4 different rooms.

But this card can not find all of the devices.

It is there in my IPhone Sonos app…

And it’s also visible as an entitie in Ha.

See screenshots…

Can they be controlled in the standard media player?
http://homeassistant.local/media-browser/browser

No, I see now they are greyed out there…

What to do now?

Looks like they are deemed unavailable by the Sonos integration. For further questions, contact the Sonos integration people.

What does the device say in the sonos integration? Are they perhaps “disbabled” in HA?

Well did the only solution… Restarting all systems… Ha, Sonos, my raspberry… and now it works!

1 Like

Today my favorites stopped showing artwork except for a few of them. Any idea?

EDIT: just check my wall tablet dashboard and desktop browser, and the favorites are showing perfectly. However not on my home assistant companion app on my phone.

Any idea what would cause this?