Well, after months of having the Sonos plugin work flawlessly, it stopped a few weeks ago (dynamic announcements). I found some time to investigate this morning and found your hotfix (20282). Once I followed the instructions and loaded it up, I am now getting “Sonos: invalid installation” and of course, now all my Sonos devices are showing “Can’t Detect Device”. So I am dead in the water and not sure what to do at this point other than loading up a working backup. Any suggestions?
Were you running the released Sonos 2.0 or an earlier version? If not 2.0, these hotfixes would not apply. One of my pre-releases/betas?
There is likely more detail logged in your LuaUPnP log. Reload Luup, and after it settles, go look at the log file (search for “Sonos”) and look at the messages. I’d like to see what it thinks is going on. That specific message means the UPnP module is not the correct version, but it has not changed since 2.0 was released. You might check to see if you have both encrypted (lzo) and non-encrypted versions of any plugin files, and resolve that if you do. If you followed the procedure (using the Luup uploader), you should only have lzo files for the major plugin files (D_, L_, J_, I_).
Thanks! I was running v. 20081.1005 when I uploaded the hotfix with the identified files. In an attempt to get back to a running status, I reloaded the same files that I had from v. 20081 and it appears to be working again…minus the dynamic announcements. I do have to run some more tests over the weekend however to confirm but right now, I am not get that same error message. Will advise further.
Sonos Plugin version 2.0-hotfix20282.1145; JSUI 2.0-hotfix20282.1145
…but still no joy on the dynamic message even though the assigned scene appears to run fine when manually activated. All other static voice messages/scenes are fine. I did read that another individual was having the same problem but his Azure app had expired. I just checked my account and there are no issues. The keys provided are the same as what I had originally loaded. Will keep investigating.
Firmware: 1.7.4903
And yes, when I run the scene, it’s throwing a error:
10/10/20 16:04:17.711 luup_log:367: Sonos: Say action on device 370 text “Good Afternoon Jagger Family! . It is now 04:04. Here is your daily weather report. It is currently 16.1 degrees outside and Overcast. It is forecasted to be Partly cloudy throughout the day. with a high temperature of 20.5 and a low of 5.6. Tomorrow’s forecast is Clear throughout the day… Todays events are VISIT NANNY from 08:00 to 12:00 . . Have a wonderful day” <0x772eb320>
02 10/10/20 16:04:19.106 luup_log:367: Sonos: AzureTTSEngine:say() conversion request failed, 500 <0x772eb320>
02 10/10/20 16:04:19.107 luup_log:367: Sonos: (tts) engine Azure Speech Service error: request failed 500 <0x772eb320>
02 10/10/20 16:04:19.109 luup_log:367: Sonos: (tts) Engine “Azure Speech Service” produced no audio <0x772eb320>
04 10/10/20 16:04:19.111 <0x772eb320>
just because it’s been a very long week from a work perspective and I am not sure if I thinking correctly (and you are being incredibly helpful), to be clear, as I don’t see TTS debug specifically, which one would you like me to check…or am I in the completely wrong screen (master device…settings)?
Sorry, I’m multitasking today and wasn’t thinking through everything I needed to tell you. My bad for sure. The “TTS Engines” is the one you want. Just that one for this purpose will be fine; leave the others off.
In the log, look for the “Say” action being invoked. Make sure you find the last one, of course, as the logs may have several at this point. A good clue that you’re in the right spot will be a message shortly after saying “AzureTTSEngine:say()…” with some stuff after. I need that Say action and everything after.
OK. Could be a TLS error. Just for lulz, go into the Sonos master device, and change the TTS “Requestor” setting to Curl. Save changes, then reload Luup and try again.
OK, if it’s not working either way, I’m thinking Azure error, or there’s just a problem with the configuration you’ve provided that isn’t standing out. It’s working fine for me in the zone that I’m in (eastus). Lets let it go 24 hours and try again tomorrow. To go any deeper, I’ll need to make one-off versions of the TTS engine for you and we’ll need some bandwidth between us for the exchange of log files and scripts.
OK. So I’ve updated the hotfix ZIP file in the head post of this topic to include a TTS engine with a bit more debug. I’m starting to see more rumbles of this, and one user you may have seen posted a notice from Microsoft about them changing certificate authorities on their servers, and this may have something to do with it, but the nature of the beast is such that multiple issues can all cause similar symptoms, so each case needs to be examined individually.
For anyone having Azure issues, I’d like you to install the hotfix package in the head post here, and then please post the log from the invocation of a (failed) Say action to the final message. This version in particular will log messages of note in yellow in the log file, but all surrounding log entries are necessary for context, so please don’t over-redact.
