mike_ws Posted January 4, 2023 Posted January 4, 2023 I'm attempting to install the ST-Sonos NS after updating to PG3x version 3.1.17 on my Eisy. I'm seeing the following error message in the NS log: 2023-01-03 17:44:21 error: POLY: uncaughtException: spawn node ENOENT Error: spawn node ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Log files attached. ST-Sonos_1-3-2023_60617-PM.zip
auger66 Posted January 4, 2023 Posted January 4, 2023 same same. And "Current Status: Disconnected" on the ISY Dashboard page. It was disconnected on 3.1.16 also, but I never had any logs on 16.
bcdavis75 Posted January 4, 2023 Posted January 4, 2023 I am also finding my Sonos NS in a failed state about once a day now. Log attached. ST-Sonos_1-3-2023_114314-PM.zip
bpwwer Posted January 4, 2023 Posted January 4, 2023 16 hours ago, mike_ws said: I'm attempting to install the ST-Sonos NS after updating to PG3x version 3.1.17 on my Eisy. I'm seeing the following error message in the NS log: 2023-01-03 17:44:21 error: POLY: uncaughtException: spawn node ENOENT Error: spawn node ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Log files attached. ST-Sonos_1-3-2023_60617-PM.zip 31.83 kB · 0 downloads This looks like it's a problem with the node server or maybe a problem with PG3x installing a node.js based node server. I'm unable to test at the moment but will look into this as soon as I can.
bpwwer Posted January 4, 2023 Posted January 4, 2023 13 hours ago, bcdavis75 said: I am also finding my Sonos NS in a failed state about once a day now. Log attached. ST-Sonos_1-3-2023_114314-PM.zip 29.67 kB · 0 downloads From your PG3 log, it looks like PG3 is unable to communicate with the IoX. Most likely because the port number is wrong: [ECONNREFUSED] :: 8.726716ms - https://192.168.0.80:8443/rest/profiles/ns/0/connection This should be 8080. PG3 can't use the secure connection because it doesn't trust the self-signed certificate in the ISY.
auger66 Posted January 6, 2023 Posted January 6, 2023 (edited) Updated to 3.1.18 and reinstalled ST-Sonos node server on eisy. Still disconnected. Logs are the same as the OP. Edited January 6, 2023 by auger66
Ross Posted January 6, 2023 Posted January 6, 2023 7 hours ago, auger66 said: Updated to 3.1.18 and reinstalled ST-Sonos node server on eisy. Still disconnected. Logs are the same as the OP. @auger66 Simplextech (creator of the NS) has stated that he doesn't check the forums regularly. However, if you send him a DM requesting that he look at this topic, he will do so. He did that for me for my pseudo-problem last week that ended up being something wonky with my speakers. Ross 1
bpwwer Posted January 6, 2023 Posted January 6, 2023 As soon as I get a chance, I'm going to look into this. Given the reports, it may be some incompatibility between the node server and PG3x. 1
bcdavis75 Posted January 7, 2023 Posted January 7, 2023 On 1/4/2023 at 1:07 PM, bpwwer said: From your PG3 log, it looks like PG3 is unable to communicate with the IoX. Most likely because the port number is wrong: [ECONNREFUSED] :: 8.726716ms - https://192.168.0.80:8443/rest/profiles/ns/0/connection This should be 8080. PG3 can't use the secure connection because it doesn't trust the self-signed certificate in the ISY. I'm confused by this. in PG3, if I go under Edit Current ISY, it says Port 8080. Restarting the NS, as usual, gets everything running again for a while... but then it will randomly fail again.
bcdavis75 Posted January 26, 2023 Posted January 26, 2023 Hi all. this node server is still failing for me several times a week. Its seems to have gotten worse lately. @bpwwer thanks for you response above but wanted to make sure you saw my reply. Is anyone else having this issue with this frequencey?
Ross Posted January 26, 2023 Posted January 26, 2023 6 hours ago, bcdavis75 said: Hi all. this node server is still failing for me several times a week. Its seems to have gotten worse lately. @bpwwer thanks for you response above but wanted to make sure you saw my reply. Is anyone else having this issue with this frequencey? I had a failed NS issue. I stopped the NS, unplugged my Sonos speakers, then plugged them all back in and started the NS. It then worked and has worked since. I was changing playlists really quickly via an ISY program I wrote (testing it) and I feel that broke it (but I don't know for sure and I haven't pushed it since). So, do the off/on thing and see if it connects and stays connected before you actually do anything with it ISY-wise.
Recommended Posts