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.

On 1/3/2026 at 10:22 PM, bpwwer said:

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.

Thanks for the reply. I appreciate you looking into it. Unfortunately, I'm no closer to resolution though. @simplextech any assistance would be greatly appreciated.

@simplextech handed the plug-in off to me, he is no longer working on or supporting the plug-ins he wrote. I attempt to maintain them now.

Like I said, from the log, it looks like the plug-in is working correctly so the problem likely lies outside the plug-in's control.

It could be that the JishiAPI server is not running. That seems unlikely if you're getting updates from the speakers. You can check that it's running using a browser and going to http://<polisy/eisy IP address>:5005 This will bring up a Sonos API page with information about the JishiAPI. Including information on how you can send commands from the browser. If this doesn't come up in the browser then the server isn't running and we can try and debug the reason for that.

It could be that the JishiAPI server isn't able to communicate with the speakers. You can test this by using the instructions above and attempt to send commands via the browser to the speaker. If that's failing, the error may give us some information as to why.

The process of sending commands via the plug-in is pretty simple

1. IoX sends a command to the plug-in. This typically has the node(address), command, and possibly a value.

2. The interface layer looks at the node address in the command and forwards it to the that node.

3. The plug-in parses the command and value out of the message sent and executes the command

   1. For the PLAY command, it uses the JishiAPI to send the proper http request to the Jishi server

   2. Sends a status update back to IoX

In your log, I see all of those steps happening and no errors being reported for any of them.