bpwwer

It looks like you've tried a couple of different things, but the ISY configuration in PG3 isn't correct. When you do a Help -> About from the admin console you get something like this: What shows up for My URL is what you need to configure PG3's current ISY IP with. That will look something like: The ISY on Polisy (IoP) port number is 8080 (or 8443 for secure http) PG2's port number is 80 (or 443 for secure http) PG3's port number is 3000 For IoP, you should only use secure http (port 8443) if you have a valid SSL certificate, issued by a recognized certificate authority.

@4wireE&M Currently, the system has a number of different accounts/passwords none are linked so you have to manually get them all set, which can make the set up confusing. IoP has a username and password PG3 has a username and password Portal has a username and password. Those three accounts are independent but the components do have dependencies. When you configure PG3, you have to configure the ISY that it will communicate with. This is set in the PG3 ISY's -> Edit Current ISY menu. Make sure the proper IoP IP address, IoP username, and IoP password are configured here. If PG3 shows the Ecobee node server installed in one of it's slots, delete that and re-install it. If that doesn't work, post or send me via PM the PG3 log file (from PG3 menu Log->download log) And FYI, when using PG2 or PG3, those programs are what manages the node servers installed on the ISY. You won't need to use the Admin Console's Node Server menu to add nodes.

It will be in a future release.

@CoLongThanks for letting me know it's solved. Checking the IP address was going to be my next suggestion. Based on this issue, I've updated PG3 to do a better job of reporting errors in the log for this type of issue.

PG3 is not able to communicate with the ISY. The first thing I'd try is to reset the ISY password in PG3. Go to the ISY->Edit Current ISY menu in PG3. Enter the ISY password in the password field and save it. If that was the problem then all those errors being reported in the log should stop. When things are working right you won't see any of these: 6/20/2022, 15:59:17 [pg3] error: Error: GET http://192.168.1.116:8080/rest/ns/1/nodes/n001_controller/report/status/SPEED/19.0/48 Failed :: TypeError: Converting circular structure to JSON

There are no errors in the log, the node server appears to be functioning perfectly. Are there any errors in the PG3 log that would indicate that PG3 is having issues communicating with the ISY?

There's nothing in the log (and when set to info, there should be more). So that doesn't tell us anything. Try setting the log level to debug and restarting.

The MagicHome node server currently in the non-production node server store uses flux-led so would probably work.

Just for reference, there are PG3 node servers for other inverters already so it's certainly possible to create one for Sol-Ark. I believe all the existing node servers get data either from the inverter's cloud service or locally over the network. I'm not aware of any node servers that use an rs-232/USB link. You can use a USB hub with Policy if you need more than the 2 available ports. One issue will be that I don't believe node servers have permissions to access the USB ports so that's something that would need to be worked out with UDI to modify the Polisy configuration to allow that.

For PG3, (and even for PG2), the store is cloud based, it always has been. PG3 does make use of the cloud based services to enable more features. However, it is designed to minimize the need to connect to the cloud and to continue running if it fails to connect to the cloud. Features that are dependent on the cloud include the ability to handle subscription based node servers. This is mostly to cover the case where the subscription is about to expire and you renew it. In order to know that the subscription was renewed, it need to contact the portal. Node server updates. Again, to know if a new version of a node server is available, it needs to get updates from the store. It tries to query the store for these updates 3 times a day. When it does successfully query the store, it caches that info locally and will continue to use the locally cached info if it is unable to connect to the store. Similar to new versions, it is possible for node server developers to pass node server specific info to existing installations (think secret keys). During the periodic store queries, it will up date this data if it has changed. Lastly, to process payment for non-free node servers, PG3 must be able to contact the Portal. For free node server, no portal communication is needed. PG3 also uses your portal account info to determine if you are a registered developer and will enable additional features for developers. This doesn't affect non-developers. In theory (I haven't tested this, but if it doesn't work, it's a but) you should be able to refresh the store and then block PG3 from accessing the internet and everything will continue to work. You should be able to start/stop installed node servers and even install new free node servers. You will not be able to purchase node servers. Keep in mind that UI is connecting to PG3 on the Polisy over your local network. So if you unplug the Polisy from the network you won't be able to connect to PG3. But PG3 and node servers not dependent on the network interface should continue to run.

@johnnytYes, confirmed. PG3 supports installing the same node server multiple times and to multiple ISY's. Once you have purchased a license, it is tied the Polisy PG3 is running on. You can then install that node server as many times as you want, on to any ISY that that PG3 is connected to. You could potentially delete PG3 and all it's configuration from the Polisy, re-install it and the license will still be valid. What you can't do, is use that license on a different Polisy (hardware box). The reason the "Target ISY" is shown in the screen shot above is because that dialog box is used for both the purchase and install and when you install, you do so to a specific ISY.

I just changed my password about 5 times without any issues. If it's a database issue, it should show an error in the PG3 log.

Nothing in that log file indicates there's a problem. However, there are restrictions on what characters can be used for node names. It looks like that's the only node that has an '&' in the name so you might want to try removing that.

Plant type is a variable used in the evapotranspiration (ETo) calculation. There are different values for different types of vegetation. 0.26 is a common value for residential environments. You'd have to lookup details on the calculation for more information.

@Michel KohanimIs this something you can do?

Where are you seeing that those node substitution variables should exist on the AERIS node server? Oh, never mind I see, the PG2 version README is displayed from the store link instead of the PG3 version. I've fixed that. The supported substitutions are: ### Current condition node * sys.node.[address].ST (Node sever online) * sys.node.[address].CLITEMP (current temperature) * sys.node.[address].CLIHUM (current humidity) * sys.node.[address].DEWPT (current dew point) * sys.node.[address].BARPRES (current barometric pressure) * sys.node.[address].SPEED (current wind speed) * sys.node.[address].WINDDIR (current wind direction ) * sys.node.[address].DISTANC (current visibility) * sys.node.[address].SOLRAD (current solar radiation) * sys.node.[address].UV (current uv index) * sys.node.[address].GUST (current gust speed) * sys.node.[address].PRECIP (current precipitation accumulation) * sys.node.[address].HEATIX (current heat index temperature) * sys.node.[address].WINDCH (current wind chill temperature) * sys.node.[address].GV2 (current feels like temperature) * sys.node.[address].GV11 (current condition coverage) * sys.node.[address].GV12 (current intensity of conditions) * sys.node.[address].GV13 (current weather conditions) * sys.node.[address].GV14 (current percent cloud coverage) * sys.node.[address].GV15 (current snow depth) ### Forecast node * sys.node.[address].CLIHUM (forecasted humidity) * sys.node.[address].BARPRES (forecasted barometric pressure) * sys.node.[address].UV (forecasted max UV index) * sys.node.[address].SPEED (forecasted wind speed) * sys.node.[address].GUST (forecasted gust speed) * sys.node.[address].PRECIP (forecasted precipitation) * sys.node.[address].POP (forecasted precent chance of precipitation) * sys.node.[address].ETO (calculated ETo for the day) * sys.node.[address].GV19 (day of week forecast is for) * sys.node.[address].GV0 (forecasted high temperature) * sys.node.[address].GV1 (forecasted low temperature) * sys.node.[address].GV7 (forecasted max wind speed) * sys.node.[address].GV8 (forecasted min wind speed) * sys.node.[address].GV11 (forecasted condition coverage) * sys.node.[address].GV12 (forecasted intensity of conditions) * sys.node.[address].GV13 (forecasted weather conditions) * sys.node.[address].GV14 (forecasted percent cloud coverage) * sys.node.[address].GV15 (forecasted snowfall)

The existing ISYInsteon plug-in on HomeSeer should work fine with an ISY on Polisy. From an external communication perspective, they are supposed to be the same. Note however that I have not tested that combination.

There must have been a typo in that URL. I've fixed it so it now points to the correct place. No, it does not work with a Tempest weather station. The WeatherFlow node server is specifically for the WeatherFlow Tempest, Air and Sky weather devices.

If it's not in the PG3 store with the same name (and it's now ST-Inventory instead of ISY-Inventory) or if you don't have a license for the PG3 version, it will skip trying to restore that slot from the PG2 backup.

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.