bpwwer

Once you migrate the licenses, it should be good.

No, unmanaged means it thinks something else is controlling the node servers in a specific slot. Migrating should have updated everything but it sounds like the IoX didn't get updated. You can do the migration again, it doesn't hurt to re-run it. The lack of license should prevent the node servers from running but they should be 'managed', not 'unmanaged'.

Ok, if I understand correctly, what you need to do is simply delete the PG2 node servers from the IoP, correct? My recommendation is to go through the 'unmanaged' node servers one by one and do the following: 1. From admin console Node Servers -> Configuration -> <slot> -> delete. This will delete the PG2 node server from the IoP. PG3 should then see that the slot is now free (may take a few minutes or log out of PG3 and log back in. 2. Install the PG3 node server into that slot. However, if you have scenes and programs configured for that node server, you may want to try and re-install the PG3 version instead. So skip step #1 and when installing the PG3 version, select the re-install option. It should install the PG3 version and if possible, it will attempt to keep the same nodes with the scenes and/or programs intact.

That implies that the username or password for the i994 as configured in PG2 is incorrect. (maybe it got reset somehow). Try re-entering them in PG2's ISY configuration and save. The reason you're getting the error and the node server's are being deleted is because PG2 can't communicate with the i994.

PG3x has more external system level dependencies than PG3. When doing an update, most of those dependencies are also shutdown and restarted. If any of the external dependencies don't restart, then PG3x won't start. We don't have a good way for users to check all the systems so for now, power cycling the eisy is probably the best way to reset everything.

If this is a new eisy, you should first update the system. Go to the Admin Console, select the Configuration tab and select the Upgrade Packages button. This can take some time depending on how much needs to be updated, it could take as long as 30 minutes. Also, PG3 uses a self-signed certificate so the browser will flag that as not secure and you have to explicitly trust it's certificate to get the page to load. I can't tell from your post what is happening. "This site cannot be reached" is typically because the PG3 isn't running, but I don't know where "client ID is not valid" is coming from. That could be related to the certificates.

Looks like Emporia changed the API slightly. I updated the node server and it should work now. Version 1.0.23

@RossI didn't write the node server, I believe @xKingdid. I converted it from a PG2 node server to PG3 node server.

It sound like the IoX service didn't start back up after the upgrade. PG3x needs to the IoX service to be running or it can't start. Can you start the admin console from the IoX finder?

No. @xKing just needs to fix the requirements file so it uses the working version of the library it needs.

@glarsenThe node servers that are written in node.js need to be updated to work with PG3x. I've updated ST-Inventory but haven't had time to update the others yet.

If you're using PG3x on eisy, there's a bug that's preventing it from restarting node servers on start up. It's been identified and resolved so the fix will be included in the next release.

The problem is that the node server didn't really stop when PG3 told it to. So it's still running. And because it's still running PG3 won't let you start it again. If you're familiar with Unix commands, you can ssh to the Polisy and kill off the running copy. Then use PG3 to start it. Otherwise, restarting PG3 should also kill it. If not, a reboot of the Polisy will for sure.

@garybixlerBased on that info, PG3x is trying to verify the node servers installed on the IoX, it does that every 5 minutes. While it was doing that, the IoX device refused the connection, causing the exception. I'll see if I can trap that exception since that shouldn't cause PG3x to shutdown. But since it's happening around the same time every day, is there something happening on the IoX at that time that would make it too busy to accept connections from PG3x?

The node server's not starting on restart is a bug. I'm looking into it. @garybixlerYour log shows that some type of network error occurred that PG3 was unable to handle, so it shutdown. it doesn't provide any information on what may have caused the error or what PG3 was trying to do when the error occurred. Was there anything in the log prior to the exception that may help? Is it happening at the same time every day?

That's the IoX's uuid '_' slot number so it would be specific to your setup. From the eisy's ssh command line you can do ls -l /var/polyglot/pg3/ns to see how each installed node server is represented.

It should be at 5 minute intervals, not 30 seconds. But I've seen it do something like this before where the timer doesn't wait for the specified time. I wasn't seeing it happen at 30 second intervals, but I'm going upgrade everything and check again.

3.1.16 is the latest version of PG3 for Polisy 3.1.20 is the latest version of PG3x for eisy

That's strange. A node server shouldn't be able to effect that connection. Can you try installing it again? If it does the same thing, capture the node server and PG3 log and post or pm it to me.

Release nodes are published and the 3.1.20 package should be available now.

So it actually works! I wasn't sure if the notification of new versions was working. I added that recently as I thought it might help notify folks about new updates. I guess I need to be better about finishing the packaging process when I create a new release now. The code is available, but the eisy package hasn't been updated yet to install it.

The data reported by the node server is what the Ambient servers report. There's no conversion happening in the node server.

Double check that the ISY configuration is correct. To connect to the ISY running on the Polisy you should have the IP address set to 127.0.0.1:8080 and re-enter the username and password. The PG3 log should show why it is unable to connect to the ISY instance but it most likely either a wrong IP/port or wrong password.

Yes, both my eisy and Polisy leave the other network settings blank when using DHCP. Only the IP address is shown.

PG3x can only migrate the node servers, not the licenses. The licenses need to be migrated through the portal. If you log into your portal account and select migrate under the Select Tools -> Maintenance -> Migrate to there's an option to migrate the licenses from the Polisy to the eisy.