bpwwer

Yes, using 127.0.0.1 (the local address) should be a bit quicker, but probably not something you'd notice.

There are communications both ways between the IoP and PG3. When a node server is installed in a slot on the IoP, part of that configuration is the ip address of PG3 so the IoP can query the node server and send commands to the node server. Since PG3 is designed to support multiple ISY/IoP's it can't assume that the ISY/IoP is on the same host as PG3 so it uses the real IP address for that. Thus if the IP address of PG3 changes after the node servers are installed, that communication channel is broken. The node server will still be able to send updates to the ISY/IoP so it may not be obvious.

It doesn't look like they're measuring the same things. If I enter 20158 in AirNow and check the box for PM2.5 most of those near that area disappear the ones that are left drop in value to below 10. It looks like the sensors you're looking at in AirNow are measuring Ozone. I don't believe the Purple Air monitors can measure Ozone, they are just PM2.5 and PM1.0 monitors. PM2.5 and PM1.0 refer to the size of the particles that the monitor can detect. Even two monitors next to each other in the same physical location will not match exactly. There are a lot of variables that go into calculating a AQI value and most inexpensive (like Purple Air) sensors are not very accurate. Not compared to sensors that cost 10-100x. The Purple Air monitors can give you a good representation of the air quality within a very small radius of the sensor (probably a couple of hundred yards) for the pollutants it can detect. You might want to read through this: https://www2.purpleair.com/community/faq#hc-how-do-purpleair-sensors-compare-to-regulatory-particulate-matter-sensors

Why do you expect them to match? I don't know where the Purple Air sensor is located as I couldn't find it on their map, but the sensor reporting for AirNow seems to be located near the freeway and all the Purple Air sensors I could see on the map are located many miles east of that. Air quality is always much worse near freeways. Also, the AirNow reading seems to be based on PM2.5 and Ozone and I believe the Purple Air sensors just look at PM2.5.

The EPA AQI is probably the equivalent but that site says it's the nearcastAQI. I don't know if nearcastAQI and the EPA AQI use the same formula or not. The EPA AQI Category in the node server corresponds the ranges that the EPA lists (good, moderate, bad, etc.). It looks to be about the same as what's shown on the AirNow site. The Purple Air bases most of this off the PM2.5 level. The Purple Air is reporting that at .7ppm while on AirNow it's listing it as 8 (over 10x as high). Based on that I would expect the AQI values to be different.

It looks like you have a copy of the node server running already so it can't start another. Each installation is assigned an ID, that instance with that ID is only allowed to connect to PG3 at a time, all other attempts are rejected. What probably happened was that when you restarted PG3 after upgrading, it wasn't able to stop the currently running node server for some reason. PG3 does ask each node server to stop when it is stopping but sometimes a node server ignores it and keeps running. Uninstalling and reinstalling will assign a new ID to the new installation. You'll still have two copies running but they'll both be able to connect and you'll probably see duplicate messages in the log and both will be trying to update the nodes on the ISY which could lead to confusion. There are 2 ways to force the original to go away. 1) ssh to the Polisy and run some commands to find the process and manually kill it. 2) reboot the Polisy. If you want to attempt #1 I can provide some examples of how to do that.

Just FYI, there isn't any place on the frontend that shows the connected status of the ISY/IoP. The "connected" badge in the footer represents the frontend UI to backend server connection, not the backend server connection to the ISY. Right now the only way to tell if it is communicating properly with the ISY is by checking the log file. Although adding a connected badge for the ISY isn't a bad idea.

Ah, I think I see part of the problem. It looks like you have two ISY's (or an ISY and an IoP) configured but one of them doesn't have a valid username/password set. That's just making the log file a bit harder to read. The ISY with UUID 00:0d:b9:53:2b:bc and IP address 192.168.0.48:8080 doesn't appear to be configured correctly in PG3 so PG3 is unable to communicate with it. This looks like an IoP UUID. Since it doesn't appear to be able to communicate, it's unclear how any node servers would be working with it. The other looks like an ISY 994 but at a non-standard port 1026. However, it does appear to be communicating with PG3 and it looks like it was able to install the 'Hue' node server per the log. As @JimboAutomatessays, trying to use port 8080 for the hue emulator will cause conflicts with IoP so that to is contributing to the issues.

A 401 error is authentication. So it looks like communication is failing because it can't authenticate with the ISY/IoP. Double check the username and password in PG3 -> ISYs -> Edit Current ISY

@oberkcmake sure you're running the latest version of PG3. There have been a couple of bug fixes since the 3.1.6 version and symptom sounds like one of them.

That's what works for me, but I may have changed some of the restrictions on the polyglot account on my Polisys. I don't know any other way to do that.

@tmorse305If you refresh the store and try re-installing it should work now.

When node servers don't start, the PG3 log will have more information on why they don't start. We just discovered an issue today where if a node server was installed during the early alpha test time frame (before there were multiple node server stores) it can now fail to start because it's missing information in the local database records telling PG3 what node server store it was originally installed from. That's the working theory anyway. If the PG3 log shows a failure with auto update, then it's the same problem. I'm not sure how best to handle this. 1) it's not hard for me to add a check for this condition in PG3 and then assume the node server was installed from the production store. However, there have been other similar changes so it may just fail later because some other piece of info is missing from the database. 2) you can try simply re-installing the node server. With this version of PG3 you can simply click the "install" button in the store for this node server and you will have the option to re-install it to the same slot. This will download the latest version of the node server and update everything. The downside is that it will put the configuration parameters back to the default settings so you have to re-configure the node server. But nothing on the ISY/IoP side will change so programs remain intact.

Looks like the update process failed. This is the second report of this same failure, UDI is looking into why and how to resolve it.

I believe you. I just don't like it when PG3 does something it shouldn't.

Nothing should be able to reset the login credentials except you manually doing that (either through the menus or by running the reset_password command on the command line). The only other way the credentials could be reset would be if the database was removed and re-created. In that case, it would be a lot more than just credentials that would be reset. From the menus, use the Settings -> Profile option to set the credentials

Try upgrading packages again and get version 3.1.8. I think this will resolve the issue. It it still says the node server has expired, try restarting the node server and see if that fixes it.

Try updates packages again and restart with version 3.1.8. If it still says it's expired, restart the node server and pm me the PG3 log

You should be able to attached it to a PM to me. I'm building a new release now that I think will resolve the issue.

@garybixlerThere's another thread about the same problem: So I'll ask you the same question. Did you previously have a trial license before purchasing the perpetual license? I'm wondering if the trial license info is still saved in PG3 and isn't getting updated by perpetual license purchase. There should be some PG3 log messages for checkLicense, seeing those might help some.

Sorry about all the trouble with the update process. That's not something I can do much about, but others are working to make that better. After PG3 3.1.6 was released, a bug was discovered in one of the developer only functions. 3.1.7 fixes that bug but otherwise is identical to 1.0.6. So unless you are a node server developer, there's no reason to update from 3.1.6 to 3.1.7. @MrBillThanks for pointing that out, you're right that text is very confusing and wrong. Since I took over development of PG3, I hadn't bothered to actually look at the text.

The PG3 log file might help. It only checks for an expired license if the expiration data is set and is non-zero. For a perpetual license, it should be either null or zero. Did you activate a trial for these originally? I'm wondering if the query for a license is returning both an expired trial and perpetual and PG3 is using the expired trial license for some reason.

Unfortunately, that's not the way it was designed. PG3 holds no state information for the user interface so it has no knowledge of how many browsers are currently connected to it. When something changes, those changes are pushed to all connected browser clients. While PG3 can manage node servers on multiple ISY/IoP devices, it can only work with one at time. Also, for this specific case it may be desirable for it not to do this, for most other cases it would be far worse. For instance, if you had two browser windows open to the same node server configuration page and you change a configuration parameter on one you'd either be confused or possibly even undo the change if you looked at the other page and it didn't have the correct values for the configuration.

There is a script to reset the PG3 username/password back to admin/admin included in the update. You can only access it via a ssh command line. The following commands should reset the password. sudo su polyglot node /var/polyglot/node_modules/@universaldevices/pg3/bin/password_reset.js exit

It should only say it needs rebooting if the Frontend Version is different from the Version (see below). However, sometimes browser caching can confuse the check. If the two versions are the same, all is good. If the frontend Version is less than Version, reload the page in the browser. If the frontend Version is greater than Version then restart PG3. (in this case it should say needs restart0