0.72+ - Can you still config Sonos via configuration.yaml?

Configuration
1

Hello,

Is it possible to still configure Sonos via configuration.yaml or must you now use auto discovery and enable it via integrations interface?

The following code does not load Sonos devices in my configuration.yaml since upgrading:

sonos:
  media_player:
    hosts:
      - 10.5.1.140 # Kitchen 1
      - 10.5.1.141 # Kitchen 2
      - 10.5.1.142 # Dining Room 1
      - 10.5.1.143 # Dining Room 2
      - 10.5.1.144 # Living Room 1
      - 10.5.1.145 # Living Room 2
      - 10.5.1.146 # Foyer
      - 10.5.1.149 # Family Room Playbar
      - 10.5.1.151 # Guest Bathroom
      - 10.5.1.152 # Bedroom 1
      - 10.5.1.153 # Bedroom 2
      - 10.5.1.154 # Closest
      - 10.5.1.155 # Master Bathroom
      - 10.5.1.156 # Shower
2

I am seeing the same behaviour. I used to define my Sonos devices by IP directly and skip discovery since they reside on another vlan from my home assistant server.

My understanding of the doc is that we should still be able to define them by ip without using discovery but we still have to go through Configuration > Integrations > Sonos to set them up. However this does not seem to work for me and I get " Aborted: No Sonos devices found on the network."

Have you tried the configuration steps?

3

I am currently using the integrations configuration and it works fine but it uses auto discovery. I purposely kept Sonos on my primary network to make controlling it easier from things like HA and iPhones. Personally, I prefer to manually configure everything as I assign subnets to different functions and reserve ip address ranges for devices.

I was curious if this change broke manual configuration and if the documentation is now out of date. My manual nest configuration came through fine so this might be something that only affects devices that can be auto discovered AND have been added to the integrations section.

4

I’ve just set up a test install on a VM, and I’ve seen the same (I’m also seeing the same for cast). I’d recommend raising an issue, and providing the details here so that the rest of us can chip in with more details.

5

Good suggestion, I’ve opened an issue.

6

Curious what you found on this topic. I’ve been struggling with my sonos for a couple months now. All works great and then all stops. requires me to remove and reinstall a couple times with reboots to get the entities back. I’ve tried putting the host ip addresses in config but it doesn’t seem to help. Ideas on what my problem could be? Dave

7

What version of HA are you running? They restored the manual config option many versions back (like .62 I think).

Here is how my Sonos config in my configuration.yaml looks. Is yours similar?

# Sonos config
sonos:
  media_player:
    hosts:
      - 10.5.1.140 # Kitchen 1
      - 10.5.1.141 # Kitchen 2
      - 10.5.1.142 # Dining Room 1
      - 10.5.1.143 # Dining Room 2
      - 10.5.1.144 # Living Room 1
      - 10.5.1.145 # Living Room 2
      - 10.5.1.146 # Foyer
      - 10.5.1.149 # Family Room Playbar
      - 10.5.1.151 # Guest Bathroom
      - 10.5.1.152 # Guest Bedroom
      - 10.5.1.153 # Master Bedroom 1
      - 10.5.1.154 # Master Bedroom 2
      - 10.5.1.155 # Master Bathroom
      - 10.5.1.156 # Shower
      - 10.5.1.157 # Closest
      - 10.5.1.158 # Office
      - 10.5.1.159 # Master Bedroom Beam
8

I’m on version .87. My configuration is similar to this now, and I’ve disabled discovery trying to see if it helps… I’ve gone through multiple iterations of removing all hosts and only a few hosts. No luck yet. Thanks for replying. Dave