bpwwer

The node server does have a 30 day trial you can use to test it before purchase. Also, the node server will log info about the devices it doesn't know about and if you send me that info for the Diva I'll have a head start in making it a non-generic device.

I was able to reproduce the problem with ST-Nuheat on that test version. It is an issue with that specific version of PG3 that has been fixed in the latest test version. I know how to update the various packages using the pkg command line, but I'm not sure that's a good idea anymore. I suggest you do an update packages from the IoP configuration page in the admin console and see if that gets you a new version. ideally, it will move you back to the latest production version 3.0.63.

I stopped by a HomeDepot today to see if they had any of the new switches/dimmers but nope, the selection of Caseta devices was very limited.

I believe they will show up as generic switches and generic dimmers. Currently, there's no difference in the node server between a generic device and a known device other than the node type for a generic device says "Generic" and the known device will show the actual model number.

I'm running on my Fedora system using icedTea. Over the years I've had to fiddle with it a bit to keep it working but I don't have any specific recommendations. I'm currently using java-11-openjdk-11.0.13.0.8-2.fc33.x86_64 if that helps at all. My launcher icon on the desktop is configured like this: [Desktop Entry] Version=1.0 Name=ISY Launcher GenericName=Java Web Start Application Comment=This utility finds ISY and launches the correct version of the UI-Admin Console-Dashboard Categories=Network;ISY Launcher;Java;Javaws; Type=Application Icon=/home/bpaauwe/.config/icedtea-web/icons/udlogo.png X-Vendor=Universal Devices- Inc. Exec=/usr/libexec/icedtea-web/javaws --verbose --nosecurity "https://isy.universal-devices.com/launcher/isy.jnlp" > /tmp/isy.log 2>&1 That launches the ISY finder and then I do have to manually add (or load a saved listing) of my ISY/IoP devices as it only seems to ever automatically find one ISY.

Store updated and version 2.0.1 with callback URL changes in README/Config docs.

Use the Refresh Store button to refresh the store listing. Otherwise, it auto updates the list every 8 hours.

Fixed in version 3.0.24 of the node server

Then something happened that caused PG2 to get confused. It's not hard to confuse PG2 so that it no longer thinks it is managing a node server. You can delete the node server from slot 3 from the admin console, as I outlined above.

It's on my list to add RIO support to the PG3 version, just need to find the time.

PG2 node servers will show as unmanaged in PG3 PG3 node servers will show as unmanaged in PG2 That's because they are two different instances of Polyglot and only one instance can manage any given slot on the IoP. To remove a node server, you should use the Polyglot instance that created it to do the remove/delete operation. When you use Polyglot to delete a node server it will remove it both from the IoP and from the Polyglot instance. If you are no longer running the instance of Polyglot that created the node server, you can delete it from the IoP by using the admin console's Node Servers -> Configure -> slot range -> Node server/slot and click on the delete button

I don't really know anything about the Kasa node server but I did take a quick look at the log. It looks like the power outage caused the switches to get assigned new IP addresses and when the node server attempted to re-discover them, something may have failed as there's no more log messages after that until you restarted the node server. It may not be possible given home router reservation limits, but for things like these switches, they'll be more reliable if they always get the same IP address. Handling devices that disappear and then re-appear at different IP address can be tricky to handle properly within the node server.

There are two node servers that support Onkyo control. You might want to try the OnkyoAVR node server instead.

You seem to be asking a couple of different things here so I'll try to answer as best I can. On your local network, there shouldn't be any problem accessing PG3 from an iPad. I just connected to mine using my iPhone and other than the small screen, it worked fine. That being said, you may have to use an unsecured connection (http vs. https) as the iPad probably won't allow you to use the self-signed certificate since it it can't verify it. Using the ISY Finder to connect may always try to use a secure connection. If so, you simply have to type the Polisy's IP address manually into the browser address field (http://<ip address:3000/). Then you mention trying to do it remotely. Right now, PG3 does not provide any method to access it remotely. That's not to say you can't, but you have to know how to configure your network to allow this. You can open port 3000 through your router, however, for security reasons it is never a good idea to open ports. Or you can access your home network via a VPN. Using a VPN is much more secure and once the VPN is configured and connected, you'd access PG3 remotely the same way as if you were on your home network.

This is what I get from the logs: At 9:36 you attempted to restart the ping node server. It failed to restart because it was unable to stop the currently running version. However, the restart attempt seems to have kick-started whatever was blocking it and it seems to start working. At least it sends a bunch of status updates to PG3. At 9:46 you attempt to start the ping node server. Again it fails because it is still running. So it appears that the network outage may have caused the node server to block in such a way that PG3 was unable to stop it. Restarting PG3 causes the OS to attempt to clean up hung node servers, so that is what likely resolved the issue. Yes, I ported the ping node server to PG3, but beyond that, I don't have any other involvement with the node server.

@johnnytYou can run to copies of the Airthings node server in different slots. Your current license allows you to run multiple copies. Weather or not the node server will allow each instance to control a subset of the devices on your account depends on the node server. You may need to create multiple accounts and have each instance use a different account.

Perhaps I can't. It was never part of the node server API to send commands from the ISY to control node servers.

Yes. When the Polisy is restarted, both the IoP and PG3 are started at approximately the same time. One of the first things PG3 does is try to contact the IoP and verify the installed node servers. Even though the IoP startup is fairly quick, it's still possible that it's not ready when PG3 makes this initial query. If that happens (and chances are good that it will), PG3 simply continues on and starts starting node servers. If those node server try to update status on the IoP and the IoP is still not ready, those status updates will also fail. PG3 does periodically verify the node servers installed on the IoP (every 5 minutes). So 5 minutes after all that above has happened, PG3 will again try to verify the node servers on IoP and probably succeed. At this point, everything should be running normally. The next version of PG3 will try to mitigate this. If it fails to connect to the IoP on startup, it will wait until it can connect before it starts the node servers.

It will only report anything if the node server is actually running at the time. Unfortunately, PG3 doesn't have any good way to notify about things like this. It doesn't have a email address nor any way to actually send email. Same for text. The ISY doesn't have any API's that would allow PG3 to route notifications like this through it. All it's left with is to send a notification to the UI, but that only happens if both the UI and the node server is running at the time. And it's possible that it's broken in 3.0.63. I've made hundreds of changes and fixes since then and don't recall if any of those fixes relate to the expiring of trial/subscriptions.

If you're running a trial version (and same applies to a subscription purchase). PG3 will notify you that it is about to expire. At 14 days before it expires it will put a message in the log At 10 days before it expires it will put a message in the log at 5 days before it expires it will put a message in the log and display a notice at 2 days before it expires it will put a message in the log and display a notice After it has expired it will log the fact and display a notice when you try to start the node server For a trial, if you purchase a non-trial license before the trial expires, it will use the purchased license and ignore the trial license and you won't get any notices because you are no longer using the trial license. Now this could be broken, it is very difficult for me to test since the purchasing system won't let me generate trial licenses for my own node servers and once you purchase one and it expires, you can't purchase it again.

I don't disagree with this but there are both pros and cons to each approach. The automatic update "feature" was already part of the PG3 design when I took over development. There has been some discussion with node server developers about this and what may be a better design. However, there are some concerns about how to handle and the priority hasn't been very high compared to all the other issues with PG3. In general, the automatic update of node servers has not been a problem. Certainly there are cases where a bad release happens, but that is typically resolved very quickly. @btreinderssince you don't specify the node server that broke, I don't know what happened.

Not yet. It seems like the packaging system doesn't like to downgrade stuff. I'm trying to get the production version back in the package repository. There is a know issue where you can't install some of the free node servers with 3.1.2, that's a problem with the node server entries in the store so not related to what you're experiencing. There are a couple of fixes in 3.1.2 but most of the changes effect developers only.

Pulling the ISY response times from the PG3 logs isn't that hard. Someone better at unix shell scripting than me could probably whip up a script that dumps just the timestamp and response time into a file that could then be imported into a spreadsheet to graph it. Just seeing how it changes over time may provide some insight like every day at 4pm the response gets slower, then you'd know to look at programs that start at 4pm. PG3 saves 2 weeks worth of daily logs so you do have some historical data available to correlate with other events/logs. You can just dump all the response time entries for the current day with the command line command: grep "ISY Reponse" /var/polyglot/pg3/logs/pg3-current.log Or to just get time and response time grep "ISY Response" /var/polyglot/pg3/logs/pg3-current.log | cut -d ' ' -f 1,2,13 This is from a ssh shell on the Polisy running PG3.

Ok, try version 1.0.4.

@simplextechThe log shows this when trying to install: 8/16/2022, 11:37:50 [pg3] info: [00:0d:b9:59:41:84_1] 'ST-Nuheat' installed into ISY successfully... 8/16/2022, 11:37:50 [pg3] error: NSChild: ST-Nuheat(1) /bin/sh ./install.sh: /bin/sh: cannot open ./install.sh: No such file or directory 8/16/2022, 11:37:50 [pg3] debug: NSChild: ST-Nuheat(1) /bin/sh ./install.sh: exited with cause code: 127 8/16/2022, 11:37:50 [pg3] error: installNs: Error: Non-zero exit code: 127 at ChildProcess.<anonymous> (/var/polyglot/node_modules/@universaldevices/pg3/lib/services/node servers.js:47:30) at ChildProcess.emit (node:events:537:28) at maybeClose (node:internal/child_process:1091:16) at Socket.<anonymous> (node:internal/child_process:449:11) at Socket.emit (node:events:537:28) at Pipe.<anonymous> (node:net:747:14) Then when it tries to start if fails with: ReferenceError: Cannot access 'logger' before initialization at process.<anonymous> (/var/polyglot/pg3/ns/000db9594184_1/st-nuheat.js:1:6746) at process.emit (node:events:537:28) at process._fatalException (node:internal/process/execution:167:25) Node.js v18.5.0 I don't think running version 3.1.2 would cause this, but I've also never tried any node.js node servers on it yet.