Sonos Play no longer working

Plugins & Plugin Development Sonos
1

Sonos app stopped working a few weeks ago in that I can no longer use the Device controls to play or stop the device. The mute and volume controls work but none of the others controls.
I have now tried uninstalling the Sonos and uPNP apps and reinstalling them in every different sequences rebooting the controller between each action and deleting all the Sonos files in the /etc/chm-ludl directory just in case this made a difference. It didn’t matter what I did apart from there always seemed to be two of six devices highlighted as “Can’t detect Device” but it wasn’t always the same 2. Although 2 of the devices are marked as such I can still mute these devices and if I change what’s playing on them using one of the old CR100 Controllers the update is displayed by the vera device. The unit is a Vera Plus running the latest firmware which is 1.7.4970 (7.31). When I click on the Play button for a sonos device the log error message is:

01 08/13/20 17:01:02.859 LuaInterface::CallFunction_Job device 171 function SMediaNavigation1_MediaNavigation1_Play_job failed [string “–[[…”]:1436: attempt to index field ‘?’ (a nil value) <0x775f8320>

Hope you can help.

2

OK. For starters, please make sure you have installed the latest hotfix version of the plugin: Hotfixes for Sonos 2.0 - Sonos - Ezlo Community

3

Unfortunately that didn’t fix it. I uploaded the two files, rebooted vera and checked the timestamps in the directory /etc/cmh-ludl to make sure they had been updated. Clicking on the “Play” button gives the following log:

08 08/14/20 14:33:28.320 JobHandler_LuaUPnP::HandleActionRequest device: 169 service: urn:micasaverde-com:serviceId:MediaNavigation1 action: Play <0x743b0520>
08 08/14/20 14:33:28.320 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=169 <0x743b0520>
08 08/14/20 14:33:28.320 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:MediaNavigation1 <0x743b0520>
08 08/14/20 14:33:28.320 JobHandler_LuaUPnP::HandleActionRequest argument action=Play <0x743b0520>
01 08/14/20 14:33:28.326 LuaInterface::CallFunction_Job device 169 function SMediaNavigation1_MediaNavigation1_Play_job failed [string “–[[…”]:1437: attempt to index field ‘?’ (a nil value) <0x77463320>
01 08/14/20 14:33:28.327 Lua_Job::Run job#39 : dev:169 (0xe2caa0) P:50 S:0 Id: 39 failed <0x77463320>

4

While I was tailing the log file I noticed a number of periodic errors related to the IP addresses for the Sonos devices. One example is:

01 08/14/20 14:51:14.812 FileUtils::ReadURL 0/resp:400 user: pass: size 100 http://192.168.0.45:1400/xml/device_description.xml//xml/AVTransport1.xml response: ## Error 400

Error 400

Bad Request
<0x733b0520> 01 08/14/20 14:51:14.813 JobHandler_LuaUPnP::ConfirmUpnpFile can’t retrieve http://192.168.0.45:1400/xml/device_description.xml//xml/AVTransport1.xml basefile AVTransport1.xml <0x733b0520>

I am able to use Device Spy to play and stop a Sonos device so wouldn’t have expected to see such errors in the vera log. Please ignore if these are related to the uPNP app and nothing to do with the Sonos app.

5

Did you update to S2 by chance?

6

I uninstalled the old apps and then re-installed Sonos version 2 and uPNP 5.0. After that I applied the hotfix…

7

No, I mean did you upgrade your Sonos devices to their new S2 firmware?

Let’s do this:

  1. Run the following two lines in Apps > Develop apps > Test Luup code:
    os.execute("/usr/bin/Rotate_Logs.sh 1")
    luup.reload()
  2. Wait 120 seconds.
  3. Open the LuaUPnP log file (insert your local IP address:
    http://your-vera-ip/cgi-bin/cmh/log.sh?Device=LuaUPnP
  4. Right-click in the displayed log and choose “Save As…”. Save the log to a file in HTML format. Do not print it to PDF or copy-paste or try to save it in any other way. “Save As…” is what is needed here.
  5. Email the log to me as an attachment at the email address I’m going to PM to you under separate cover. You can ZIP it before you attach it if you wish, but don’t modify it otherwise.
8

I have a number of the CR100 controllers so decided to stay on the old version. I’ll also include a log of the Sonos units and their versions. Thanks

9

Thanks rigpapa. The hotfix-20229 on github fixed my problem

1 Like
10

I can no longer see correct status (TransportState) for my 3 Sonos devices. I applied the hotfix and followed all steps. That didn’t change anything. If I push “Play” or “Pause” it responds accordingly - but with no update in Vera UI. Since I use the TransportState as a trigger in a few Reactors, it’s kind of a problem. Does anyone know what’s wrong?
Best regards,
/Fanan