About a week ago, the node server stopped working. usually a simple restart sets it straight--but not this time. Today I tried re-installing it all together but no luck. Whats strange is that in the AC, it appears to be registering volume and volume changes correctly and instantaneously. But I cannot send commands to sonos from the AC at all.

Log attached. Any help is appreciated.

ST-Sonos_1-3-2026_24015_PM.zip

I'm not sure. I don't have any Sonos devices so I can't do any debug/testing other than analyzing your log files. Doing that I don't see anything that looks wrong.

At 12:20:45, it looks like you tried to send the PLAY command for the speaker identified by 7ad3b3a. This is from the PG3 log. After the command is sent to the plug-in, there's a message to IoX requesting that it set 7ad3b3a's status for the ST value to 1.

In the plug-in log, there's an error "NS: undefined". This error is coming from the interface between plugins and PG3. I've seen this a lot from ST-Sonos and it seems harmless. But since I can't run the plug-in, I can't debug where in the interface layer it's happening.

The plug-in code for the PLAY command is pretty simple:

call the API's play command for the device
set the ST value to 1

The plug-in uses a third party library, JishiAPI, to communicate with the Sonos devices.

From the logs:

• IoX sends the command to the plug-in

• The plug-in sends the command to the JishiAPI

• The plug-in updates the status

Which is indicates that the plug-in is doing what it is supposed to do.

Now the JishiAPI communicates with the Sonos devices by sending http requests to a server component called node-sonos-http-api/server.js. This component is supposed to be installed when you install the plug-in and started when you start the plug-in. If it is not running, the plug-in would not be able to do any communication with the Sonos devices. You indicate IoX is getting updates from the device which implies this component is started and working.