bpwwer

Mosquitto does have the ability to log to a file, I think with different levels of verbosity but you'd have look at the documentation on how to configure that.

Unfortunately not. Did you attempt to log in after opening the javascript console? If not try logging in with the console open. You may have to scroll up to see all of it outputs. I'm looking for an error message related to "/auth". The errors in the screen shot are "normal", in that it is trying to use information it gets from PG3 to format the menus, but because it isn't logged in, it doesn't have that info from PG3 yet.

The first step is to get things working with MQTT Explorer as that will mean everything is configured properly. You need to have a MQTT broker running somewhere. Either on the RPi that is running the solar-assistant software of on the Polisy/eisy. Running a MQTT broker on the Polisy/eisy can get confusing because each is already running a broker but the default running brokers are configured to only work with PG3(x). On the Polisy, PG3 has a built-in MQTT broker, but you can't use it. However, you can install the Mosquitto broker and run that along side the PG3 built-in broker. On the eisy, Mosquitto is already installed and running for PG3x, but it is also configured so that only PG3x can use it. I'm not sure if you can install another copy of Mosquitto for your own use or not. What hardware are you using and what have you tried so far?

I wasn't sure if logging out/back in would solve this. Guess not. That's strange that it works from one computer but not another. If you open the javascript console (developer tools) on the one that's not working is there any more details on the error?

The PG3 UI authenticates directly with the PG3 server which is a separate account/password from anything else. The PG3x UI authenticates using the IoX account/password and also has to authenticate with the MQTT broker to establish a connection with the PG3x server. So while the UI looks the same, how it works is very different. The changes are an attempt to both improve security of PG3/node servers and consolidate the IoX/PG3 accounts to simplify it a bit.

The portal authentication has a fairly short time period before it expires. Once it expires, the UI will pop up a warning saying it has expired and in most cases it should auto refresh the authentication with the portal. Portal authentication and authentication with the PG3x server are different and shouldn't be effecting each other.

Log out and then log back in. The problem is that the browser has cached information that is preventing it from connecting to PG3(x). The UI running on the browser thinks that you are logged in but it keeps sending old authentication information to the server and server rejects it. Without a connection to the server you don't get any information from the server (IoX configuration, node servers installed, etc. and the UI can't send anything to server (edited IoX configuration info, etc). When you switch to another computer or browser, the UI has no cached authentication info.

Do you have the option to log out on the menu? If so, try that and then try to log in again.

Do you have other node servers working correctly?

What version of PG3 are you running?

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.

Just for reference. The error means that the configuration of the node server on the IoX (when you go to Node Servers -> Configure -> slot # -> <node server>) has an incorrect password. When PG3 installs the node server on the IoX, it sets the password to an encrypted token, when the IoX sends a command to PG3/node server, PG3 checks that password to see if matches and if it doesn't, it throws that error. Normally, this would mean that the node servers was installed on the IoX by a different PG3**. ** PG3 creates a unique identifier when it creates it's database for the first time. Removing the database and restarting PG3 will create a new unique identifier and this will also cause the authentication to fail.

I have no idea. The MQTT stuff is all handled by standard Python modules.

Portal access is unlikely to be the cause of your issues. You'll need Portal access to purchase node servers or verify node server licenses, but you're not to that point yet. PG3x has two components, the UI running on the browser and the server running on eisy. The can't connect to server is the UI saying it can't connect to the PG3x server. You can't do anything if it's not connected. So yes, that needs to be resolved before you can restore. In general, with PG3x, you don't need to configure the IoX/ISY unless you want to manage node servers on something other than the local eisy. Once the PG3x server side starts, it will pre-populate the IoX config with the local IoX. It appears the PG3x server side is not running, the question is why? PG3x has a dependency on UDX and the local IoX, if one of those aren't running, then PG3x won't be able to start. At this point, it is probably best to reboot the eisy and see if that clears it all up. If it doesn't, then we need to use OS level tools to look at what is happening when PG3x tries to start. If you are comfortable with ssh'ing into the eisy you cat do something like sudo tail -f /var/log/messages which will show the system log messages. PG3x startup messages will be there and it should be repeating the same set of messages every minute or so. If PG3x is crashing, it will show the crash, if the local IoX isn't started, it will show that in the log before aborting. CTRL-C will stop the log display. If you're not comfortable with that, submit a ticket and support will probably have to remote into the eisy to determine what's going on.

The WeatherBit servers aren't sending any data when the node server requests it. Possibly you exceeded your daily limit for requests. iTach is failing to create a secure connection to PG3x. If the system is having issues responding to interactive actions (like log/elk actions, etc) it may mean that there is something going on the OS level that is impacting the node servers.

What does the WeatherBit log show? System memory is not a issue with eisy.

non-free node servers can have the license migrated to the eisy (I believe the portal migration process does migrate the licenses too). But if the licenses are not migrated, then they should still install, they just won't run. And if they won't run, they may not show up in the admin console but should still be visible in the PG3 dashboard. To get a trial license, you'd have to request one via the store, it won't automatically try to get a trial license.

After. Restore the IoX first, then migrate the PG3 node servers. If you migrate node servers to eisy, then restore IoX from Polisy, it will overwrite the node server config on the eisy. Re-restoring/migration node servers would then need to be repeated.

What does the node server log show? Any errors there?

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.

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.

I'll update the announcement to try and make that more clear.

For now, yes.

Hello Everyone, This is the support thread for PG3x v3.1.17 - v3.1.21

Hello all, We are very happy to introduce PG3x v3.1.22 for eisy. This is a minor update to 3.1.21. The eisy is using a new version of Polyglot version three called PG3x. PG3x has infrastructure changes to make node servers (and PG3x) more secure. Both PG3 and PG3x have the same feature set with the exception of a feature in PG3x that allows migration of node servers from PG3 to PG3x. For now, Polisy users should remain on PG3 and eisy users will use PG3x. This fixes a number of bugs in the original PG3x 3.1.16 release and adds the ability to migrate from Polisy/PG3. To upgrade PG3x: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you may need to restart PG3x. From PG3x UI select System-> Restart Polyglot 3x. Once PG3x has restarted, reload /refresh the browser page. Migrating from Polisy/PG3 Make a PG3 backup on the Polisy. From the PG3 UI select System -> Backup/Restore -> Backup. This will download a backup file Restore the PG3 backup on eisy. From the PG3x UI select System -> Backup/Restore -> Migrate from PG3 backup. Select the Polisy PG3 backup file and when the button changes to "Restore" click it. Depending on how many node servers need to be migrated it can take a while. The UI should pop up messages showing the status as it migrates node servers. There are some limitations to the migration process. Only one IoX device can be migrated. If your Polisy was connected to more than one IoX device (say the local IoP and an i994), the migration process will only migrate one of these and it will use whichever one shows up first when it does it's database query. This will remove any previously installed node servers in PG3x and possibly overwrite them with a node server from the backup. You should start this process with no node servers installed. Any node servers on the Polisy that were installed from the "Local" store will fail to properly migrate (applies mostly to developers). All node servers will be left in the "Stopped" state. You will need to manually start each node server after the migration. Changelog for 3.1.22 - Rebuild package to work with Node version 19.5 Changelog for 3.1.21 - Don't loop over non-existent nodes when displaying node details in UI - Add ability to handle system upgrade messages and display a notice in the UI when the system is being upgraded. - quote password when sending to pg3.ops. Fixes issue with passwords containing special characters like '$$' - Try and trap network errors when verifying node servers installed on IoX. - Fix typo in log message. - Fix bug that caused dashboard to ignore "un-managed" node servers. Changelog for 3.1.20 - Fix minor bug in UI where we tried to use settings before they were set. - remove debugging messages. - Return status = 500 , and error if authentication crashes - Revamp verify node servers behavior. PG3x will now try to make the IoX match what is in it's database to better keep IoX and PG3x synced on what node servers are installed. - Fix IoX auto discover to not overwrite existing entry's username/password. - Change how the UI authenticates with the MQTT broker. This should resolve issues with logging and and bring back the ability to use multiple browsers to access PG3x at the same time. - Stop printing the mqtt frontend password in the log - Quote the user name so that it now works if the name has space characters. Changelog for 3.1.18 - Pass the correct structure to installProfile. Fixes profile files not being sent to IoX on node server install. - Allow 127.0.0.1 for IoX node config ip address. Stops PG3 from replacing the localhost IP with network IP on node server verification. Changelog for 3.1.17 - Change the IP address written to the IoX node server configuration to use 127.0.0.1. - Fix typo status should be stats in checkLicense. Caused licence check to fail for some purchased node servers. - Change ISY to IoX throughout the UI. - Always route reinstall through nsinfo, specifically fixes issues when re-installing via the purchases page. - add logging and pg3_install fixes to get permissions correct after install of node server. - fix typo in error message, puchase should be purchase. - Update database to indicate we've migrated to PG3x. - Add ability to migrate from PG3 backup. - Enable check for PG3 node server migration on start. - Add count of node servers re-installed to reinstallNS response. - Add ability to re-install all node servers via the System menu. - Handle alert and reinstallNS messages. - Add pg3x flag to global settings. - Don't update node name to 'undefined' - Remove "Running on Polisy" from footer. - Make node server verification errors more verbose. - Run update check every 12 hours. - Check for updates of PG3x. Support thread: