Ross Posted March 29, 2023 Posted March 29, 2023 @bpwwer Hi Bob, I came home tonight and my ST-Sonos had failed. Per your gracious request, I'm attaching the log package. After I downloaded the log package, a simple Restart "fixed" it. No hurry necessary and thank you, Ross ST-Sonos_3-28-2023_84229-PM.zip
carealtor Posted March 29, 2023 Posted March 29, 2023 Mine fails every 3 days or so, almost like clockwork. I've sent a few log packages to @simplextechbut have so far received no response. I just looked and it is failed again. Full disclosure, I have been having networking issues in general at my house for a couple months now. Everything worked great for years and now a few devices are just giving me fits. Most notably, Ecobee. Just can't put my finger on where the issue is. ST-Sonos_3-29-2023_80751-AM.zip
Ross Posted March 29, 2023 Author Posted March 29, 2023 @carealtor Per @bpwwer in another thread, @simplextech has stopped supporting this NS; but Bob is trying to support it and asked for the log the next time it crashed. I'm not sure how often mine fails, but it may do it at regular intervals. It seems like every 3-7 days. I'll note it next time. I don't have any network issues, but I do have intermittent internet issues all-the-time. Perhaps Sonos loses connectivity to its cloud and that causes the NS to fail? This is my only NS (of 8-10) that fails. Regards, Ross 1
bpwwer Posted March 29, 2023 Posted March 29, 2023 The good news is that both of you are seeing exactly the same issue. The bad news is I have no idea how to fix it. It appears to be that something Sonos is sending out a notification related to group volume or group mute, but the group has no members. This triggers an exception in the library which then gets trapped by the node server. So I'm guessing the real problem is somewhere in the library which isn't something I can change. I don't know if this is enough information for the library owner to debug/fix, but I'll create an issue for it. 1
Ross Posted March 29, 2023 Author Posted March 29, 2023 @bpwwer Just curious: when is Sonos sending out the notification? Is it while I'm playing music or just before/after? Will you please tell me the time it failed? If you can clip the line that shows the failure, I can look at the log myself in the future. It seems to "become failed" when I'm not using Sonos which is 98% of the day. I can always stop the music via the NS, but sometimes I can't start it due to the failure. I have 2 groups and all of my speakers are in one or the other (Living Room or Office). However, I group them in the Sonos App. My program tells the NS to play a speaker (rather than a group), and since the speakers are grouped via the app, all of those in the group play. Maybe I need to specify the group via programming. BTW, since this might be out of our control, this is a good situation for wanting to create a program to restart the NS once a day! Thank you, Ross
bpwwer Posted March 29, 2023 Posted March 29, 2023 The author of the library responded and said this is likely caused by the group coordinator player dropping or being demoted. He think it might be a bug so there's hope. From your log @Ross, it happened at about 3:32 in the morning. @carealtor, yours happened at about 8:46 at night. Maybe once you stop the speaker, it takes a while to timeout and then the speaker is demoted from the coordinator and the next volume notification for the group then fails. 1 1
carealtor Posted March 31, 2023 Posted March 31, 2023 @bpwwer I could be wrong, but I seem to remember something in the forum some time ago that it was hoped that the 2 Sonos nodeservers would be combined into one. Is that in the works by any chance? Seems really odd to have 2 of them.
bpwwer Posted March 31, 2023 Posted March 31, 2023 I don't recall any discussion about merging them, but then I didn't really follow discussions about them since I don't have any Sonos devices. So it's somewhat strange that I've ended up maintaining both. Both use different programming languages with different libraries so they can't really be merged. If there's a difference in feature sets, one could be updated to include all the feature of the other making one more desirable than the other, but I don't have information on the feature sets. At this point, ST-Sonos is likely to be better maintained simply because it's not free.
bpwwer Posted March 31, 2023 Posted March 31, 2023 An update on the bug. " a player drops and a topology change event occurs. If a topology change occurred which changes system.zones, but the group this thing was in did not get updated in a timely manner for some reason, then that is exactly the behavior you would expect." So there are two possible ways this bug could be triggered. A fix has been proposed. I'll keep monitoring it and update the node server as soon as a fix is available.
Ross Posted March 31, 2023 Author Posted March 31, 2023 (edited) @bpwwer Thanks for the update. I have no idea what it means which means I'm probably a long way from writing my first NS. @carealtor I can't remember the differences in the 2 Sonos NSs; however, I remember being frustrated with the Sonos NS and was very glad when ST-Sonos came on the PG3 scene. I won't bore you with the details, but I have >50 playlists. I press a keypad button or click a link in a Google Sheet and a state variable changes which triggers Sonos to shuffle and play the playlist. The other NS couldn't do that, if I recall. Edited March 31, 2023 by Ross Specified what kind of button.
lilyoyo1 Posted March 31, 2023 Posted March 31, 2023 19 hours ago, carealtor said: @bpwwer I could be wrong, but I seem to remember something in the forum some time ago that it was hoped that the 2 Sonos nodeservers would be combined into one. Is that in the works by any chance? Seems really odd to have 2 of them. The free nodeserver just allows you to control your speakers and provides status of your devices. The st Sonos version adds your playlists, favorites, and voice TTS
carealtor Posted April 3, 2023 Posted April 3, 2023 On 3/31/2023 at 9:22 AM, bpwwer said: Both use different programming languages with different libraries so they can't really be merged. Well. as an end user, I was referring to a merging of features and only having one NS for Sonos. I wouldn't know anything about the programming languages. On 3/31/2023 at 1:34 PM, Ross said: I can't remember the differences in the 2 Sonos NSs; however, I remember being frustrated with the Sonos NS and was very glad when ST-Sonos came on the PG3 scene. I won't bore you with the details, but I have >50 playlists. I press a keypad button or click a link in a Google Sheet and a state variable changes which triggers Sonos to shuffle and play the playlist. The other NS couldn't do that, if I recall. That's pretty much how I remember it too. This was before the structure to charge for Nodeservers was implemented. On 3/31/2023 at 9:25 AM, bpwwer said: A fix has been proposed. I'll keep monitoring it and update the node server as soon as a fix is available. That's some great positive news. Thanks for looking into this.
matthewjocko Posted May 27, 2023 Posted May 27, 2023 Having this issue as well. The node server fails about every 1-2 weeks and a restart fixes it temporarily. Attached my logs below if it is of any help. ST-Sonos_5-27-2023_121009-AM.zip
carealtor Posted May 27, 2023 Posted May 27, 2023 Interestingly, mine has now been rock solid for several weeks now.
bpwwer Posted May 27, 2023 Posted May 27, 2023 12 hours ago, matthewjocko said: Having this issue as well. The node server fails about every 1-2 weeks and a restart fixes it temporarily. Attached my logs below if it is of any help. From the log it looks like your Sonos is refusing the connection attempt from the node server. After a few tries, the node server gives up and aborts. So it looks more like a Sonos problem than a node server problem.
Ross Posted May 28, 2023 Author Posted May 28, 2023 12 hours ago, carealtor said: Interestingly, mine has now been rock solid for several weeks now. My ST-Sonos NS fails about once a week or even longer now (it failed either today or yesterday), but it's not every 3 days when I started this topic. @bpwwer In your 2nd March 31 post above, you mention that you'll be monitoring the situation. I assume you haven't seen anything since then? If not, would you kindly prompt whomever it was you were engaging to get a status update? Thank you! Ross 1
bpwwer Posted May 28, 2023 Posted May 28, 2023 12 hours ago, Ross said: @bpwwer In your 2nd March 31 post above, you mention that you'll be monitoring the situation. I assume you haven't seen anything since then? If not, would you kindly prompt whomever it was you were engaging to get a status update? Thank you! Ross Yes, I've been monitoring it. There is a proposed fix, but the code base hasn't been changed since 2019 so I'm not real hopeful anyone will actually do something with it. I may have to fork the code and make the fix myself. That's something I can look at doing in a couple of weeks. 1
bpwwer Posted August 13, 2023 Posted August 13, 2023 I had some time so I did some work to make a version with the fix applied. Version 1.0.10 is in the store now and has the proposed fix for the recalculateGroupVolume() crash. I have no way to test this, but the node server does install and run for me. 1
Recommended Posts