Had the trial version earlier this year and it discovered all of my Sonos speakers. Went to use today and realized I never purchased the license and since I can't apply the license to the existing install, I uninstalled ST-Sonos and then reinstalled with license version( (Just paid for), however it now won't discover my speakers and when I select disover, this is the error in the log: 2025-10-25 13:57:10 error: NS: undefined. I decided I might as well upgrade from 5.91 to 6.0 while at it in hopes it may resolve, however it didn't and no amount of uninstalling or reinstalling ST-Sonos afterwards will allow the nodes to sync. When I look on the backend, it doesn't look to be deploying properly as the node directory is missing (Screenshot attached - ST-Sonos is in Slot 10). I tried following bmercier's resolution here: https://forum.universal-devices.com/topic/42744-demo-worked-fine-purchased-version-does-not/ however since I didn't have a deployment directory, there wasn't anywhere to install. I also can access the Sonos API at localhost:5005. Any idea what might be wrong?

24 minutes ago, Hunter Aviator said:

when I select disover, this is the error in the log: 2025-10-25 13:57:10 error: NS: undefined.

When I look on the backend, it doesn't look to be deploying properly as the node directory is missing (Screenshot attached - ST-Sonos is in Slot 10).

I think that UDI broke a bunch of plug-ins with an update. Errors that start with "error: NS:" are coming from the interface library that the plug-in uses to interface with PG3x. That library is maintained by UDI but I'm not sure they actually test to make sure it works when they release updates.

The deployment directory is "000db95608c0_10" so you'd have to do an "ls -la 000db95608c0_10" what files/directories where created when it was installed.

THank you. I see in the install.log there are some errors and it indicates there is a newer version of npm, however i'm not inclined to attempt to install that myself unless UDI thinks that may help

install.log

I don't think the warnings in the install log are significant. It looks like the plug-in got installed correctly. I still suspect that it's the interface file that needs updating by UDI. I sent a message to them, requesting that they look into it.

There have been other reports of issues running the node.js based plug-ins and I am unable to start them as well. These were all running fine before whatever update broke them.

Awesome - thanks Bob!

Re-reviewing this, it does look like the sonos-http-api may not be running. Or may not have been running when the plug-in started.

Have you tried simply stopping and then starting the plug-in?

When I installed it, the first time it tried to start I got errors like what you posted, but after restarting it, it seemed to work fine. Of course I have no Sonos devices so it doesn't actually discover anything, but it did create the control node and didn't have any errors in the log.