bpwwer

Unauthorized means just that. You've entered a username or password that is not correct. PG3x uses the IoX to authenticate so the usernames and passwords are the same as the ones configured in the Admin Console. Whatever you use to log in to the Admin Console is what you use to log into PG3.

If it's working with UDMobile but not the Admin console, then it's probably not the node server. It still seems like the Admin console hasn't read the node definitions and thus, doesn't know how to represent the nodes. You could enable the Java console and see if the admin console is throwing any errors when it loads. Based on my understanding, UDMobile uses formatted values from the IoX so to get those, the IoX needs access to the node definitions. That means that IoX has the proper definitions and for some reason the admin console is not able to get them from the IoX. It appears that the node server is working correctly. So if the Java console doesn't provide any info, you'll have to open a support ticket.

At this point, we have not been able to identify the root cause for the missing files. The current recommended solution is to migrate to PG3x, and yes, it works on a Polisy. There are instructions on the wiki https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide under the heading "Upgrading to PG3x"

When PG3x process a login request, it sends back either a success or fail message that will pop up on the screen. If you're not getting that (I.E. nothing happens when you press login). That indicates that PG3x was not able to get a response when it tried to authenticate your login and thus has nothing to pass back to the browser. If you have not yet updated the system, I'd recommend that you first do a "Upgrade Packages" from the admin console's configuration tab. Depending on what all needs to be updated, this can take 15 or more minutes. After the system has been upgraded, it will need to reboot. Either reboot the system from the admin console's configuration tab or pull the power wait 10 seconds and re-apply power. If your system is up-to-date, then it may just need a reboot.

So far, all of the reported issues involving missing files on install have happened on PG3. After migrating to PG3x, the issue no longer happens. We have been unable to determine the root cause. So the current recommendation is to migrate to PG3x.

Have you restarted the admin console since installing the node server? Every time you install a new node server, you have to restart the admin console so that it read the information from the node server that describes how to display the nodes. Otherwise you end up with random/incorrect info displayed for the nodes.

I already checked the node server store database and everything looked fine. What is currently in the store database for Bond is just the one perpetual purchase option. @Goose66 if you pull up the production Bond entry from your developer list, what do you see for options? I've not heard of a case where the submission fails to include a purchase option, but that doesn't mean it can't happen.

Can you post/pm me the URL? If the server isn't responding at all to the query, yeah, I can't fix that in the node server. But I can check the query and make sure the node server is creating an invalid query.

What version of PG3 are you running? It looks like a file didn't get installed that is required for the node server to run. There have been a couple of case where PG3 (not PG3x) fails to install all of the node server file. We have not been able to determine the root cause of this issue and the current work around is to migrate to PG3x. If you are already running PG3x, then please try a re-install. If you continue to get this error then this would be the first case where this has occurred on PG3x.

Yes, you can ignore it, but unless you're actually trying to debug an issue, it's best to leave the log level at info or even error

What do you get if you load that URL listed in the log snippet above into your browser? Can you post or PM me the results? Also, it would help to see the full log, including the node server startup so restart the node server, download the log and PM it to me.

I gave your profile files a pretty good going through and I missed it too.

There is probably an error in one of the profile files that is preventing the AC from fully parsing the node. Looking at your profile files, I don't see anything wrong. The best way to double check is to start the admin console with the java console active, any parse errors will be reported there.

The "Pool thermostat" even though it's a child node will show up as a separate node in the program dropdown. The dropdown doesn't support displaying the hierarchy, it just list the nodes; parent or child.

go into the log page and download the log package. PM me with the log package .zip file

What version of PG3 are you running? Is there anything in the log that would indicate why it's not able to get data from the tempest?

The duplicated lines is just because PG3 has multiple streams open to the log file, reloading the page in the browser should close those and resolve that. Try enabling debug log level to see if provides more information on why the queries are failing.

Usually that means you've exceeded the number of queries allowed for you plan. It seems like some of these services have been making that limit lower over time. It will usually reset on a daily basis so you might want to reduce how often you poll and wait a day.

I need to try and reproduce it.

Thanks for the details. That really does help. The node servers are verified every 5 minutes so that's probably not related, just that it is what you'll see in the log when PG3 is mostly idle. But the reconnecting to MQTT broker is related. That's saying that the network connection between the MQTT broker and PG3 dropped for some reason and it had to reconnect. Most likely , that also means that the network connection between each node server and the MQTT broker also dropped and it's each node server's connection dropping and reconnecting that is causing the notifications. Since the MQTT broker is a separate system service communicating with node servers and PG3 over the network, can you think of anything on your network that would be causing network disruptions on a 8 hour frequency?

Realize that currently, the PG3 backup/restore doesn't handle the fact that the IoX may also be changing so creating a backup of eisy and trying to restore to a Polisy (or another eisy) doesn't fully work. The backup/restore processes were written with the assumption that PG3 was pointing to a ISY994 and that if you replaced the Polisy, you'd still want to new Polisy to point to the same ISY994 (this was all done before IoP/IoX existed and hasn't been updated since). Fixing this is on the todo list.

Doing a restore will simply try to re-install all node servers so I wouldn't expect it to behave any different. Since it will re-install all node servers it's possible that it could cause this same issue with other node servers. So I'd say more risk of of making things worse instead of better.

If it is only one of many node servers then it is likely something happening with the node server. Node server will attempt to re-connect to PG3 automatically if the connection drops so you may not notice anything wrong, but this will now trigger notifications to UDMobile. In this case, you should see a "failed" notification followed by a 'connected" notification. If you are seeing notifications for all node servers at the same time, it is likely PG3 that has crashed. PG3 will automatically restart so again, you may not be seeing any other indication of a problem but when PG3 crashes, it will attempt to stop all node servers before restarting and both the stopping and restarting of the node servers will trigger the notifications. In this case you should see "disconnected" notifications followed by "connected" notifications. In either case, this is an indication that something is wrong. Node servers shouldn't randomly disconnect and PG3 shouldn't randomly crash. If you just don't care because things seem to be working fine, you can disable the notifications by going to the System -> Notifications page and disable PG3 notifications.

Yes, it is strange. I installed it here fine and then re-installed it and still fine. I've had another report of the same problem, different node server.

Yes, the missing file would be the problem. Try installing (re-install) it again.