ST-Sonos Node Server "Failed"

[Ross]

@simplextech and others:

Bought this earlier today and it worked for several hours (I did get it to play my Christmas music) but it is now "Failed".

I've attached the log.

Absolutly no hurry - i can play the music through the Sonos app in the meantime.

Thanks,

Ross

 

ST-Sonos Failed State 2022-12-24.txt

[auger66]

Unfortunately, I have this happen every two weeks or so. A restart of the Sonos node server always gets it going again for me.

[Ross]

6 hours ago, auger66 said:

Unfortunately, I have this happen every two weeks or so. A restart of the Sonos node server always gets it going again for me.

When I restart (or stop/start - I've tried both), it says Connected for about 3 seconds and then goes back to Failed.  It doesn't appear that anything can be done in Configuration as I have no entries there.

I suppose I can uninstall/install the NS.  I believe I can do it in the same slot and programs won't be affected.  I'll see if anyone chimes in.  I've worked with @simplextech before and he's been very responsive.  This can wait until after the holidays.  

[Bumbershoot]

4 hours ago, Ross said:

I suppose I can uninstall/install the NS.  I believe I can do it in the same slot and programs won't be affected.  I'll see if anyone chimes in. 

In order to get the latest version, I had go through the uninstall/install process, but I found that you don't have to uninstall it at all.  You can reinstall it in the same slot as the current installation. 

Go through the install process, and at the final screen you have the option to install it in the same place it's already installed.  See screenshot.

That might fix it.  There weren't any negative consequences to me.

[Ross]

Thanks @Bumbershoot.  Not that I need to reinstall NSs very often, but this tip is helpful.

Unfortunately, it did not solve my problem.  So, I completely deleted the NS and reinstalled it (losing my links in the process) - and I still have the same problem (Failed).

I'll await a response by @simplextech.

Ross

 

 

[Ross]

Just an update on ST-Sonos Failed.

I uninstalled it completely last night and then reinstalled it this morning (trying the old off-and-on technique).  Same issue - Failed after a few seconds.

I clicked on Download Log and Download Log Package (I'm not sure of the difference) and attached them here.

A recurring theme in the logs are:  "error:  POLY:  Node e1c98da not found".

Maybe I should install it in a different slot?

Thank you for any assistance,

Ross

 

ST-Sonos_12-28-2022_73451-AM.zip ST-Sonos_12-28-2022_73443-AM.zip

[simplextech]

On 12/28/2022 at 10:41 AM, Ross said:

Just an update on ST-Sonos Failed.

I uninstalled it completely last night and then reinstalled it this morning (trying the old off-and-on technique).  Same issue - Failed after a few seconds.

I clicked on Download Log and Download Log Package (I'm not sure of the difference) and attached them here.

A recurring theme in the logs are:  "error:  POLY:  Node e1c98da not found".

Maybe I should install it in a different slot?

Thank you for any assistance,

Ross

 

ST-Sonos_12-28-2022_73451-AM.zip 38.51 kB · 0 downloads ST-Sonos_12-28-2022_73443-AM.zip 878 B · 0 downloads

Thanks for the log packages and the first log.  I took a quick look at them and I have no freaking idea what is going on.  The node.js install is throwing errors for node modules that are not directly even in use by the Node Server. 

What version of PG3 are you running?

What version of Node.js is installed on your Polisy?  (From the command line ssh session) run "node -v" this will output the node.js version.

Top of my head says that something with Node.js is wonky.  Could be Node.js version installed and module compatibility or worst case the jishi node-sonos-http-api used by the node server has some serious compatibility issues with the node.js version.  Dunno yet.

[Ross]

2 hours ago, simplextech said:

Thanks for the log packages and the first log.  I took a quick look at them and I have no freaking idea what is going on.  The node.js install is throwing errors for node modules that are not directly even in use by the Node Server. 

What version of PG3 are you running?

What version of Node.js is installed on your Polisy?  (From the command line ssh session) run "node -v" this will output the node.js version.

Top of my head says that something with Node.js is wonky.  Could be Node.js version installed and module compatibility or worst case the jishi node-sonos-http-api used by the node server has some serious compatibility issues with the node.js version.  Dunno yet.

@simplextech I am running Polisy version 3.1.13 (front-end version is the same).  

I'll need to research how to SSH as I've never done that before.

I am attaching a log (not mine) that @auger66 posted back on May 9th in this thread:  The errors there 
"error: POLY: Node a0a654e not found" are similar to my errors; however, I'm not sure how it was resolved.

Thanks,

Ross

 

 

.  

 

ST-sonos log.txt

[bpwwer]

I believe node 18.2.1 is the latest version on Polisy/eisy

[Ross]

@simplextech To answer your questions, I am running Polisy version 3.1.13 and Frontend Version 3.1.13.  Also, my ISY is 5.3.4.  Following your instructions to get the node.js version, I got v18.7.0.

@bpwwer The node.js version on my Polisy is v18.7.0.

Thanks,

Ross

[Ross]

After upgrading Polisy, learning about putty, SSH-ing, Node.js among other things and researching forums about other node server "Failed" issues and sweating about this for a couple of days, I stumbled upon a great idea.

I unplugged and plugged back in my Sonos speakers and the node server worked again.

Happy New Year,

Ross