simplextech

No the question was if you had a previous version of ST-Inventory running making this an upgrade to that pre-existing NS or if this was a new install. Is the Polisy new? Is it up to date? Do you have any other NS running, specifically any other Simplex Technology NS defined with ST in the beginning of the name. The error in the log is clear that the Polyglot API is not current which would cause the NS to fail on startup. What is unknown is why this would crash the entire ISY as you have stated it did.

I'm afraid I don't know how a NS is crashing the whole ISY. I recommend you opening a ticket with UD support about the ISY crashes. The log however does show that the Node.js Polyglot API is not a current version and needs to be updated. Were you running ST-Inventory before and then updated to the newer version? If so then it would seem that the Polyglot API is not being updated on NS updates or installs which is a problem outside of a single NS.

I'm not sure. I'll have to look.

This should be possible through programs.

That is interesting. Please do send me a private message and attach the log file to the message. Do you have any other Sonos players besides the Roam?

It is what it is. It's a inventory list of the nodes and devices within your ISY. Common use by many was to know how many nodes were in their ISY994i and whether they were close or over the node limit. If they were they knew what was now causing node add failures and they could upgrade to the ISY Pro. Knowing how many devices of different types is just a metric that many find useful or interesting. The error log entries was added from a request as it is good to know and then clear the log so it doesn't continue consuming system space.

Looks like the speaker was not available (likely after the firmware update/reboot) and at the same time (during the restart) a connection failed. I thought I had caught everything around the speaker restarts. Looks like something is not being caught.

They need to be placed on the file system on Polisy. Example: /var/polyglot/pg3/ns/00:0d:b9:4e:37:d0_4/node-sonos-http-api/static/clips Replace the Node Server 00:0d:b9:4e:37:d0_4 with the location that matches your installation.

Sounds good to me.

Interesting. This gives me a thought that perhaps there should be a forum for Node Server requests? @Geddy any thoughts on this?

Two of the errors (log level) are debugs that I left in and should remove. The other "error" related to the Node not found is because of the async nature of changes/things happening and the nodes not being created/existing just yet. Things have to "catch up". Initial "status" of the Nodes is set when they receive information related to them. So not all nodes will have any information if nothing has happened from that Node/Speaker yet.

I'm not aware of any native Sonos capability for 'fade to off'. Might be able to simulate one with a program or could be a simulated addition that could be done within the NS code and taking fade time as a configuration parameter and lower the volume at pre-defined increment until it hits 0....

Welcome. I went through and changed all nodes to report proper status (ST) for those that like looking at the overall system status from the primary ISY node in Admin Console

Do you have a Personal Weather Station or plan on getting one? If you do then use a NS based around your PWS. If not then use a NS based around a Weather service you prefer. @bpwwer is the defacto "Weather Man"

Lutron does not make any z-wave or wifi switches. Are you perhaps confused with Leviton?

I can confirm this as I do speak with Doug semi-regularly and I did ping him after I saw a post on here about issues with support and delays. Doug is a good guy and just getting his feet wet here in the forum so play nice guys!

It's great to see you here @Doug Roberson. I'm sure a presence from Shelly will go far within the community.

I worked with @Michel Kohanimthis afternoon and tried running a manual update but both failed in my case. He's sending me something in the mail. Not sure if it's a pin connected flasher for the chip or a new Polisy. It'll be a surprise ?

@larryllix yeah sounds familiar. Likely same old chip as I have one of the very early release Polisy boxes.

Just ran an update as I do whenever a new PG3 is released. The follow packages were included: Installed packages to be UPGRADED: isy: 5.4.0_5 -> 5.4.1_1 [udi] npm: 8.4.0 -> 8.5.2 [udi] pciids: 20220128 -> 20220225 [udi] pg3: 3.0.44 -> 3.0.45 [udi] py38-distro: 1.6.0 -> 1.7.0 [udi] py38-typing-extensions: 4.0.1 -> 4.1.1 [udi] udx: 2.6.0_2 -> 2.6.0_7 [udi] After the install Polisy went into a reboot loop. It would startup, I could login...few minutes and it would just reboot and give the lovely beep during boot.... annoying BEEP. Powered off from console. So far the only resolution I've seen is open a ticket and a remote session?

In-Line relays are plentiful with Z-Wave https://www.thesmartesthouse.com/collections/z-wave-relays

I'm aware that the NS is not installing or updating. The update has no functionality just a version change trying to work out problems with the NS store. There is a store problem with production vs beta packages in the store. Before it was delivering the beta package even for production installs and now it's not delivering any package. The UD developer working on this was informed last night.

It's going to take me some time to move devices around and setup a test environment for RA2 Select again. I also don't think this should be continued in this thread under this sub-forum.

The preferred method for any life/safety devices are to use a security panel. A common favorite is Elk. If you do not have a security panel or don't want to purchase one the next option would be Z-Wave Smoke detectors. The current (only?) Z-Wave smoke detector is the First Alert ZCOMBO which is a Smoke/CO detector. I in fact have several of the First Alert ZCOMBO that I've recently retired as they were replaced with Smoke detectors connected to my Elk panel.

v1.0.6 Updated Node.js PolyInterface Log Level selection from UI now works User configuration values are no longer necessary. v1.0.2 Typo correction in a message v1.0.1 Bug fix for ISY returning /CONF/NET/RES.CFG not found for network resources URL v1.0.0 Initial release of ISY Inventory (now ST-Inventory) for Polyglot 3