Errors in log

[ScottRennie]

Anyone know what what this means in the log & how to fix it??

This is a wired Sonos Play One with no networking issues. Ping times are good. It is one of 10 Sonos speakers. no errors showing for the others.

2019-12-14 11:27:46	Sonos Warning	Unsuccesfull MyUPnPService.SendRenew for ServiceID = http://192.168.0.136:1400/xml/AVTransport1.xml because code 412. Typically means the client had a problem communicating an event and released the subscription. We will try to re-subscribe. Network issue?
2019-12-14 11:27:46	Sonos Warning	Unsuccesfull MyUPnPService.SendRenew for ServiceID = http://192.168.0.136:1400/xml/AVTransport1.xml while sending URL = http://192.168.0.136:1400/MediaRende...ransport/Event with SID = uuid:RINCON_7828CA15284201400_sub0000000303 sent renewal with elapsed time = 0.815 and error = The remote server returned an error: (412) Precondition Failed.
2019-12-14 11:27:43	Sonos Warning	Unsuccesfull MyUPnPService.SendRenew for ServiceID = http://192.168.0.136:1400/xml/AlarmClock1.xml because code 412. Typically means the client had a problem communicating an event and released the subscription. We will try to re-subscribe. Network issue?
2019-12-14 11:27:43	Sonos Warning	Unsuccesfull MyUPnPService.SendRenew for ServiceID = http://192.168.0.136:1400/xml/AlarmClock1.xml while sending URL = http://192.168.0.136:1400/AlarmClock/Event with SID = uuid:RINCON_7828CA15284201400_sub0000000301 sent renewal with elapsed time = 0.9689 and error = The remote server returned an error: (412) Precondition Failed.

Cheers
Scott

[dcorsus]

Anyone know what what this means in the log & how to fix it??

This is a wired Sonos Play One with no networking issues. Ping times are good. It is one of 10 Sonos speakers. no errors showing for the others.

2019-12-14 11:27:46	Sonos Warning	Unsuccesfull MyUPnPService.SendRenew for ServiceID = http://192.168.0.136:1400/xml/AVTransport1.xml because code 412. Typically means the client had a problem communicating an event and released the subscription. We will try to re-subscribe. Network issue?
2019-12-14 11:27:46	Sonos Warning	Unsuccesfull MyUPnPService.SendRenew for ServiceID = http://192.168.0.136:1400/xml/AVTransport1.xml while sending URL = http://192.168.0.136:1400/MediaRende...ransport/Event with SID = uuid:RINCON_7828CA15284201400_sub0000000303 sent renewal with elapsed time = 0.815 and error = The remote server returned an error: (412) Precondition Failed.
2019-12-14 11:27:43	Sonos Warning	Unsuccesfull MyUPnPService.SendRenew for ServiceID = http://192.168.0.136:1400/xml/AlarmClock1.xml because code 412. Typically means the client had a problem communicating an event and released the subscription. We will try to re-subscribe. Network issue?
2019-12-14 11:27:43	Sonos Warning	Unsuccesfull MyUPnPService.SendRenew for ServiceID = http://192.168.0.136:1400/xml/AlarmClock1.xml while sending URL = http://192.168.0.136:1400/AlarmClock/Event with SID = uuid:RINCON_7828CA15284201400_sub0000000301 sent renewal with elapsed time = 0.9689 and error = The remote server returned an error: (412) Precondition Failed.

Cheers
Scott

Despite a network appearing solid, if a player either receives an error sending an event to the PI or STP makes some configuration changes in your SONOS network, the established eventing subscription is deleted in the player, without the PI knowing of it. When the PI sends out its periodic renewal, the player refuses it and the PI needs to start the subscription process all over. This also means that in this period of silent failure, events from the player are lost. I just realized that the latest version I posted had these errors lowered in severity so I could monitor then, and I forgot to set them back to > "errors only". I'll post a new version soon to fix that.

Having that said, if you currently see a lot of those, something is going on in your network. I would like to point out that pings are just a single packet on connections that carry hundreds of thousands of packets per second and are only useful to see if an end-point is there or not. If you have a horrible network, they may show being dropped but on a local network, they really are only useful for end-point there or not decisions.

Now speaking from own experience, I have a few players in my son's room, together with about a thousand other wifi devices, I can tell when he is in town that I start seeing players drop out, come back, errors 412 etc. and so far I haven't been able to put my finger on it either. That's actually how I began realizing what this error 412 really meant. The players are the farthest away from my sonos hub but when they cut out, other players start cutting out and I suspect this has something do with STP instabilities going on while the Sonos net reconverges, suspect actually some loops but I can't put my finger on it.

I'll post a beta version very soon, an official one take a little longer as it requires an approval from HS.

Dirk

[dcorsus]

Just posted v50 in the beta section of the updater

[ScottRennie]

That makes total sense. Thank you for explaining and fixing it in the Beta!!

Cheers
Scott

[luucelzinga]

Same error 412 over here, can play music but no TTS. v51 installed, but didn't give solution.

[dcorsus]

Same error 412 over here, can play music but no TTS. v51 installed, but didn't give solution.

Have you checked your firewall setting? Will need a lot more info if you want help

[luucelzinga]

Yes, checked FW: Recommanded ports are open and HSPI Sonos .exe is allowed to perform FW.

[dcorsus]

Recommanded ports are open

We are talking about the firewall on your HS PC, right? There are no "recommended ports" for this PI on your PC's FW, they are set to outgoing and incoming allowed.
This is not an exotic VLAN or VM setup, is it?

412 errors: in almost all cases point to a network issue, and this could be an issue BETWEEN Sonos player, as a hard to reach player can cause STP to toggle which in terms messes up established TCP connections for eventing because connections from the PI to players, then to go hop-by-hop through players on Sonosnet. I had a very similar issue with one player just not operating properly, causing quite some issues until I added a second Boost to my network. Type in http://xx.xx.xx.xx:1400/support/review with the IP address of any of your Sonos players and click on Network Matrix to investigate the robustness of your Sonos net. GOOGLE for more info if you see red.

If TTS doesn't work, here are the top x causes:
1/ the PI doesn't receive autonomous events because your FW is not allowing autonomous events to reach the PI. This causes all hell to break lose.
2/ the PI doesn't receive autonomous events because your network has issues (so could be side effect of your error 412). HOWEVER, unless your network is really really bad, in about 5 minutes, the PI re-establishes connection, so I doubt it a bit that this is your issue.
3/ if on Linux, the install is incomplete for the text-to-speech file conversion, which means, this NEVER worked and you need to search on the forum here what to install.
4/ if on Windows, sometimes, the .wav file in the <hs root>\html\Sonos\Announcements file is LOCKED and can't be deleted or overwritten by the PI. Sometimes this is caused because HS is not running as admin and therefore subsequently neither is the PI running as admin, nor can it now write in this subdirectory. Sometime it is locked and it requires a restart of HS or manual delete of the file.

[luucelzinga]

Thanks for your suggestions Dirk.

I’m at Windows Server 2019, no exotic setup. No PI or Linux at all.

I turned of my FW, that works for direct manual starting a wav file at the HS device of a player. Maybe the network traffic is less in that case. I start with troubleshooting with your suggestions. I will reply with my results.