Today I bought my first Sonos device which I already start to love. When browsing through the add-on store I found this add-on which will make my Sonos experience even better!
However, I get this “UPnP init failed -203” error when starting the add-on:
-----------------------------------------------------------
Hass.io Add-on: AirSonos
AirPlay capabilities for your Sonos (and UPnP) devices.
-----------------------------------------------------------
Add-on version: 2.0.0
You are running the latest version of this add-on.
System: HassOS 2.11 (amd64 / qemux86-64)
Home Assistant version: 0.91.3
Supervisor version: 159
-----------------------------------------------------------
Please, share the above information when looking for help
or support in e.g, GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 50-airsonos.sh: executing...
[cont-init.d] 50-airsonos.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[20:03:33] INFO: Starting the AirSonos server...
[20:03:33.342744] main:1224 Starting airupnp version: v0.2.2.4 (Dec 16 2018 @ 16:04:42)
[20:03:33.346645] Start:972 UPnP init failed: -203
[20:03:33.346897] main:1265 Cannot start
[20:03:34] INFO: Starting the AirSonos server...
[20:03:34.279069] main:1224 Starting airupnp version: v0.2.2.4 (Dec 16 2018 @ 16:04:42)
[20:03:34.280379] Start:972 UPnP init failed: -203
[20:03:34.280626] main:1265 Cannot start
I’m running HassOS inside a VM on ESXi, is that something that might have to do with it?
P.S. I’ve just tested the add-on on my Pi3 test-unit and on that device the add-on works flawless
Thanks for the quick reply! After some Googling it turned out to be the ‘Discoverable on L2’-service in the UniFi controller. The UniFi controller isn’t running on the testmachine.
Thanks for the pointing me in the right direction!
After a recent update I can no longer access my Sonos devices via AirSonos. I have tried restarting router, i have restarted the Sonos devices and uninstalled and reinstalled component but still can’t get it to work. My log looks like this:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Hass.io Add-on: AirSonos
AirPlay capabilities for your Sonos (and UPnP) devices.
-----------------------------------------------------------
Add-on version: 2.0.1
You are running the latest version of this add-on.
System: Raspbian GNU/Linux 9 (stretch) (armv7 / raspberrypi3)
Home Assistant version: 0.92.0
Supervisor version: 162
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] airsonos.sh: executing...
[cont-init.d] airsonos.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:33:46] INFO: Starting the AirSonos server...
[10:33:46.789876] main:1280 Starting airupnp version: v0.2.8.0 (Mar 17 2019 @ 17:47:58)
[10:33:46.791390] Start:1016 Binding to 192.168.0.73:49152
[10:33:46.998803] AddMRDevice:920 [0x95fa4]: adding renderer (Landing)
[10:33:47.005224] MasterHandler:615 [0x95fa4]: subscribe success
[10:33:47.020982] ProcessEvent:414 [0x95fa4]: UPnP Volume local change 100
[10:33:47.247526] AddMRDevice:920 [0x97ed0]: adding renderer (Kitchen)
[10:33:47.253374] MasterHandler:615 [0x97ed0]: subscribe success
[10:33:47.268101] ProcessEvent:414 [0x97ed0]: UPnP Volume local change 40
[11:08:47.441741] CheckAndLock:220 device is NULL
[11:08:47.495146] CheckAndLock:220 device is NULL
[11:08:47.545553] CheckAndLock:220 device is NULL
[11:08:47.598144] CheckAndLock:220 device is NULL
[11:08:47.647582] CheckAndLock:220 device is NULL
[11:08:47.702024] CheckAndLock:220 device is NULL
[11:08:47.776263] CheckAndLock:220 device is NULL
[11:08:47.826847] CheckAndLock:220 device is NULL
[11:08:47.877495] CheckAndLock:220 device is NULL
[11:08:47.928232] CheckAndLock:220 device is NULL
[11:08:47.982762] CheckAndLock:220 device is NULL
[11:08:48.036787] CheckAndLock:220 device is NULL
[11:08:48.115941] CheckAndLock:220 device is NULL
Just to say I installed this last night and it works great.
Is there any way to link this add on to the spotify playlist type work being done so that Sonos speakers can be seen from the Spotify API as currently Sonos is not supported?
I saw this mention on github that it’s possible to exclude speakers:
Speakers can now be excluded in v0.6.0, using custom configuration file tweaking.
However, I don’t see a way to do this in the documentation. I look at the airsonos.xml and tried changing <enabled>1</enabled> to <enabled>0</enabled> (from 1 to 0) but the change doesn’t do anything and my changes are reverted. What is the right way to do this?
Dear,
I am trying to use this add-on to get my Play:1’s included.
However, I managed to get the plugin started, but since then, I only see endless log messages
I saw that it might be a possibility to cancel the power supply of the speaker for a minute. This does not work for me.
Might it be realted that my Sonos speakers are in another WiFi segment? (hass is in 192.168.1.XXX and the speakers are in 192.168.20.XXX). If so, how can I get the addon to check the other segment (192.168.20.XXX) as well?
Hi @Connor, did you get this working?
I posted this issue once on github but it was classified as not being an issue of airsonos, just system related.
My system has two network adapters, one being the vlan where all the robots live.
At the Moment I try to move to a more simple setup with one nic in the network where all the smarties are.
The internet isn‘t helping with error 208
Best, Bernd
My Sonos media players are in a different network. Is it possible to pre specify the Sonos media players in the xml file? The hassio Raspberry PI has connectivity to the Sonos media players since the Sonos platform is working perfectly!
Release v2.0.1
Upgrades base image to v3.1.0
Removes default config options
Renamed init scripts
Maintaince -> Maintenance
Adds FUNDING.yml
Updates maintenance/license year to 2020
Adjust add-on installation instructions