bpwwer

The process for PG3 are a bit different, but it's mainly just in how you initially deploy your node server. Developers get access to a "Local" store in PG3 where you can add/remove node server. Once added, the process is a fairly simple install/delete or stop/start depending on how you get the changes to the node server directory. The Polisy supports both NFS and SMB file sharing protocols so it is possible to mount the Polisy's file system to another machine and then edit/copy files as if they were local. There are developers on slack that do this and can help with the setup.

This is what the AERIS documentation says:

Keep in mind that for PG3, the node server license is tied to the hardware. If you try to restore to new hardware, you won't be able to run any of the non-free node servers.

Looks like the node server store entry was messed up. Refresh the store then delete and re-install. It should show all the config parameters.

What do the logs say?

@seacordeanWelcome to node server development. Most of the node server developers are on Slack. That's the best place to ask questions and get answers. You do need to register as a developer with UDI if you have not to get an invitation. PG2 is being deprecated and support is slowly going away. It's find for getting a basic understanding of how node servers work so what you've done isn't wasted time. However, most node servers have been ported to PG3 and most new node server development is happening on PG3. I'm not sure why PyCharm thinks the processor matters. Do they run a component on the client machine? That still may be a problem as the Polisy used FreeBSD as it's operation system. Polisy is an X86 (or really an AMD64) processor. I can't really help you with IDE questions as I just use VIM on the Polisy to do all my development.

How do you feel about generating an API key for me so I see what the API returns and how it works. Blindly making changes to the node server and having you test and report isn't very efficient. I won't intentionally mess with the controls, I mainly want to see the data in the get queries.

Yes, "temperatureUnit" is either "F" or "C" according to something I saw in the API docs. The editor should have two ranges, one for each unit along with the matching UOM. What I find strange is that the targetTemperature (which also doesn't use the correct UOM in the editor) is reported in "F" but is being set in "C" The API isn't real clear on how the API knows which units to use when reporting temperatures. Does the device itself have the ability to specify which units you want it to use?

I can see where that is confusing. The code is also pretty confusing as it doesn't really deal with temperature units at all.

Sorry, made a error in the code. Try version 2.0.2.

Thanks! I believe I've fixed the problem. Refresh the node server store and you should see version 2.0.1 Then restart the node server and it should install the new version. If it still doesn't work, send me a new log.

If no one wants to maintain it, we'll probably have to pull it from the store, or maybe just move it to the non-production store so someone could work on debugging it if they desire. I took a quick look at it and it seems like one of the dependencies isn't installing. This is not uncommon as many of the Python modules are written for Linux and don't include packages specifically for FreeBSD. Sometimes they'll build without any issues on FreeBSD, other times they don't. In this case the build is failing. I didn't dig into why it was failing.

It should be exactly the same as the PG2 version in terms of functionality. If it's not working, please provide logs.

If you restart the node server does it then correctly display the status? After I install the node server it shows disconnected until I restart the node server. This appears to be a race condition within PG3 as it sets the correct (connected) status and then a few seconds later sets it back to disconnected. I think this may be happening for a lot of node servers but may be random depending on the how things get executed in the node server. I'll open a PG3 issue for this.

PurpleAir recently discontinued the API that was being used by the node server. Version 2.0.2 updates the node server to use the current API supported by PurpleAir. The new API requires an API key to access the public sensor data. Anyone can request an API key. To use verson 2.0.2 of the node server, you will first have to send email to contact at purpleair dot com and request a READ API key. Use the API key they proved to configure the node server. A Custom Parameter called "APIKey" (note case) must be created to hold your API Key. You should be able to add this custom parameter after upgrading or delete version 2.0.1 and re-install version 2.0.2 (make note of the sensor ID's you previously configured as you'll need those).

PG3 3.0.62 works with Node 17.x PG3 3.0.63 works with Node 18.x If you update the packages on the Polisy, it should update both PG3 and Node so they are in sync. If you force it to update only one, PG3 will not work. There is no difference between versions 3.0.62 and 3.0.63 other than updating the dependent Node libraries to work with Node 18.x

Hello Everyone, This is the support thread for PG3 v3.0.63

I'm not sure. No one reported any issues when the time change happened last fall. This issue was reported by someone who was messing around with the system time on their Polisy. That's a good point and I'll have to elevate the priority to check that.

I was just about to post here that I pushed out a new version, updated to work with node 18. But I see you noticed. Thanks for letting me know that it's working.

Hello all, We are very happy to introduce PG3 v3.0.63 which is the first production release of PG3. To use the latest version of PG3, you should also be running the latest version of IOP. Follow the instructions in the IOP release announcement to upgrade IOP to the latest version. To upgrade PG3: - In the Admin Console, click on Configuration, Upgrade Packages. After the upgrade is complete you will need to restart PG3. From PG3 select System-> Restart Polyglot 3 Bug fixes: None (This version is identical to release candidate #2 (v3.0.62) Enhancements: Updated to work with Node.js version 18.2 (latest version). Make sure you have (or will have as part of the upgrade) Node.js 18.2 Support Thread:

Yup it does. It appears that PG3 (or rather one of it's dependencies) doesn't work with the new version of Node.js. You'll have try rolling back the version of node to 17.x or wait until I can get PG3 updated to work with node 18.

Looks like it installed correctly. The node server author will have to take a look at it to figure out why it's not working.

You could try deleting and re-install the node server again. It looks like the required "govee-api-laggat" python library didn't get installed. If that doesn't help, then you'll need to post the installation errors from the PG2 or PG3 log file.

Where is it showing "Disconnected"? Is it the Admin Console or the PG3 dashboard or PG3 node details page? If it's the one of the PG3 screens, you may want to just refresh the browser, sometimes the browser caches stuff and what you see is the cached status instead of the current status. If it's the Admin Console, have you re-started it after the latest version of the node server installed? It could be that the Admin Console needs to re-read the profile files to display correctly.

Both versions use the same (now removed) api so neither should be working. I've contacted Purple Air to try and get the information needed to use the new API, I'm waiting to hear back. Based on what I've read in the API documents, it may be a lot more difficult to use with PG2 and even for PG3 will require the main code for the node server to be re-written. I won't know more until they actually respond.