Sonos issues with .64

Configuration
1

Upgraded to .64 today and the Sonos media player card no longer shows the currently playing information and while it will let me play from the media card, it doesn’t change to the pause icon so I can’t pause it once playing. Anyone else having issues with Sonos on .64?

2

I just did a quick test. Mine seems to be working on .64 and hass.io.

3

The Sonos integration was rewritten in 0.64 so growing pains are not surprising. In general, though, it appears to work well. Please share the part of your configuration that relates to sonos, that could give clues. Also share any errors/warnings from the log file.

It seems like you do not receive events from the speakers. Do you have an advanced network setup?

For others having sonos problems in 0.64: please file individual reports and feel free to tag me … preferably in the HA GitHub issue tracker though I try to keep up with the forum as well.

4

I only have one speaker and am just using the auto discovery in HASS.IO for it which had worked well. I don’t see anything currently in the log about it, but I did see yesterday some lines about it taking longer than 10 seconds to update sonos.

5

Update - so I just did an app update for Sonos that appeared today and also had a firmware update for my Sonos unit. After that firmware update, the HA Sonos card is now working again. I see the now playing and get the player controls.

1 Like
6

So updating the Sonos firmware fixed your issue completely? That’s great, thanks for reporting back!

7

It seems like it. It certainly has fixed the play/pause function and showing the currently playing, so that is a big improvement.

8

Well…perhaps I spoke to soon. Sonos had been working fine for a couple days, but today I decided to add a password on my ha (had been running without it for setup) and now that I have rebooted, the Sonos card is back to not working correctly. Again, I can click to start, but the card does not get updated with now playing information or change to the pause button to be able to pause. I am on 64.1 which was working okay until the password addition today. Everything else seems to be working fine.

9

First try 0.64.2 and if it keeps happening please file a GitHub issue with error logs.

10

Updated to 64.2 and still doesn’t work correctly, could press play but no “now playing” and no pause. I power cycled my sonos unit and now I get the now playing information but still don’t get the pause, like the play/pause button is not updating. I was going to submit the logs, but haven’t done that before and if I look at the home-assistant.log file there is almost nothing in it and nothing about sonos, is that the correct one or do I need to enable some higher logging level somehow?

11

@chubRock1 That is the right one. To enable more debug info you can copy this file to config/custom_components/media_player/sonos.py and add this snippet to config/configuration.yaml:

logger:
  default: warning
  logs:
    soco: debug
    custom_components.media_player.sonos: debug

That should give you a lot of output that you can PM to me.

12

I’ve had the same issue with my sonos gone since I upgraded to 0.64 and 0.64.2 didn’t fix for me. I’m using HA on Ubuntu 16.04 server.

13

@mistrovly You are also welcome to PM me debug logs as described above.

14

I don’t see a custom_components folder in my hass.io install, is it safe to create one in the config directory to put the sonos.py file into?

Also, it really seems hit or miss. I was getting some Alexa errors on the sonos one in the last hour so I tried power cycle on it again (a min ago realized Alexa is having major outages right now so not an issue on my end) but after the power cycle the card is again working correctly in the hass.io frontend, but not working correctly on my HADashboard but that could be that they need to update that widget to support the changes recently made on the sonos component.

15

You can create the necessary folders. It probably breaks when you play a particular kind of music source.

16

Hi,
It’s the same bug as the 12738 issue.
https://github.com/home-assistant/home-assistant/issues/12738

It is closed.

Is it necessary to reopen a new issue?

Tnx

17

That issue does seem to be the same, when you say it is closed does that mean it has been addressed in the next release or should already be fixed?

18

Hi,
The issue has been wrongly closed.
It was an inducer for the developer (amelchio)

19

I reopened 12738 for good measure but it will not be fixed without more logs, sorry.

@ranathan14 You are also welcome to follow the improved debug instructions above.

20

@amelchio : ok for new log!!!