bpwwer

I can't speak to the differences between v1 and v2 as I never used v1. The major change in v3 is a framework that allows third party developers to charge for the node servers they create. In addition v3 is able to manage multiple ISYs instead of just one. It also can also manage multiple copies of the same node server. There are a lot of internal changes to try and improve reliability and make it easier to create node servers.

When it shows the "not connected to server" message, it means that the user interface code running on the browser is not able to connect with the Polyglot instance. Because it is not connected, it is not able to receive any of the configuration information from Polyglot nor is it able send any updated information there to be saved. If refreshing/reloading the browser page doesn't cause it to reconnect, you'll have to look at the logs to figure out why it isn't able to connect. Both the Polyglot log and the browser's console log (developers tools on the browser) should provide some help in determining that.

The latest release is version 2.0.1. This is the first release that supports PG3. The node layout has changed from PG2 versions of the Ambient Weather node servers. You likely need to fix any programs that are based on Ambient Weather data when migrating to PG3. Pulls data from http://www.ambientweather.com and makes it available to the ISY. This node server uses an API Key associated with your ambient weather account to query the ambient weather servers for your weather stations. Supports multiple weather stations with multiple sensors. Nodes will be dynamically created for each station and each sensor attached to the station. The ambient weather servers are polled at the short poll interval (in seconds). The servers do rate limit so it is recommended to poll at a minimum of 60 seconds.

Just to clarify, you're using Polyglot cloud right? Local Polyglot has a drop down selector where you select the slot you want to install to. Or are you saying that feature is broken? And, no, you can't edit existing node server slots. You would have to remove and re-adding to a different slot.

I believe the root cause of this has been determined. It looks like the most recent version of node broke something with host name resolution. Specifically it fails to properly resolve 'localhost' to 127.0.0.1. To resolve the issue in PG3, replace 'localhost' in the ISY configuration IP field with '127.0.0.1' and save it.

I've been able to reproduce the errors by changing the ISY configuration in PG3 to use an incorrect port. You might want to try just re-entering the port number and saving from the ISY/edit current ISY screen in PG3.

Try restarting the ISY. This looks like the same issue reported on Slack and for that case, it appears the ISY is simply refusing connections from PG3.

I believe that most of the devices that @Goose66is talking about never publish an official API. They have an internal API that works with their apps(s) and the node server (or library it uses) has reverse engineered the API. In this case, the manufacturer isn't under any obligation to notify customers when the API changes so the changes do cause a support problem for the node server. I'm not sure what the "right" or "best" answer is for this. Creating node servers using unofficial API's is potentially a headache for the developer and more expensive for the customer. This is probably something we should do a better job of documenting. Knowing the node server uses an unofficial API may deter people from buying that equipment in favor of supporting a different manufacturer that does publish an official API.

True. I believe the very long term plan is to combine ISY and Polyglot so it's just one piece of software and one user interface.

Good question! At a high level, the ISY (standalone or running on Polisy) has an API that node servers use to interact with the ISY. That API hasn't changed and is used by PG2, PG3, and NodeLink (and maybe some other stand alone node servers). PG2, PG3, and NodeLink are all node server managers. They sit between the ISY and node servers. They provide some extra capabilities and handle some of the common tasks that node servers have to do. For example, when a node server is installed, there are some files that describe the nodes that the node server will create. Those files need to be uploaded to the ISY. The node server manager does that so each individual node server doesn't have to have the code to upload it's files. From a high level architecture, PG2 and PG3 are very similar. Both communicate with the ISY in the same way, both have similar user interfaces, and both provide a similar API to interact with the node servers. PG3 supports all the same basic core functionality that PG2 does. The main differences are some new core functionality in PG3, a lot of minor fixes and improvements and an improved API to interact with node servers. Probably the biggest user visible change was adding support for licensed/purchased node servers. A lot of the changes have to do with the internal structure of node servers with the goal to make them easier to write, easier to maintain, and more stable. There were internal design choices in PG2 that made it hard to improve and maintain compatibility. Some of that was tried when PGC was created but we just ended up with bunch of "if running on PGC do this, else do that" code in node servers. Given the scope of the changes, PG3 seemed like the right time to break compatibility to make node servers better going forward.

Currently, the node server license is tied to the Polisy so if you have multiple Polisys, you need multiple licenses. However, you can run multiple copies of the same node server on the same Polisy under one license and one Polisy can manage node servers for multiple ISYs.

As I think I mentioned before, the goal is to have most of the existing PG2 node servers available in PG3, that's one of the gates to moving from a Beta product to a Production product. Whether or not the PG3 version is free, is up to the node server author. Like @Jimbostated, it's slow going because the node server authors are doing the conversion in their spare time. However, realize that you will be able to run both PG2 and PG3 on the Polisy (or PG2 on RPi), so you can continue using the PG2 versions for node servers that haven't been converted and switch over to PG3 versions as they become available and it makes sense to do so. Eventually, support for the PG2 versions will disappear, and how quickly that happens, is again, dependent on the individual node server authors. Because the production release date of PG3 is unknown, I expect to continue providing support (and bug fixes) for my PG2 node server for quite a while. But any new node servers will be PG3 only and new features will be PG3 only.

In no particular order, here's the list of node servers currently available in the PG3 store. Airscape JImBo $10 Airscape Node Server HusqvarnaMower Bob Paauwe $10 Husqvarna Mower: A node server for control of AutoMower Timedata Gordon Larsen $5 An ephemeris nodeserver for Polyglot V3 on Polisy PurpleAir Bob Paauwe $5 Add air quality data to the ISY994 WLED AutomationGeek free Interface between WLED and PG3. AERISWeather Bob Paauwe free Add AERISWeather service weather data to the ISY994 Roku Bob Paauwe $10 Control Roku media devices. PythonTemplate James Milne (Einstein.42) free Template Node Server Example-1 Bob paauwe free Example node server that simply increments a count. This is demonstrating how to create a simple node server that doesn't have a controller node and creates only a device node. WeatherBit Bob Paauwe $5 Add weather data from WeatherBit.io. Includes current conditions and daily forecasts NOAA Bob Paauwe $5 Add weather data to the ISY994 Daikin James Paul $5 Daikin Node Server to control Daikin Mini-Split System AMINEM Steven Bailey $5 / 12month Net Energy Utility Meter for Landis+Gy & Oncor models you can set the devisor in custom parameter nem_oncor. WeatherLink Bob Paauwe $10 Pull weather data from a Davis weather station using WeatherLink Live's local device API. UnifiPresence AutomationGeek $10 UniFi Device Network Presence Detection Example-2 Bob paauwe free Example node server that simply increments a count. This is demonstrating how to create a simple node server that has only a controller node. Climacell Bob Paauwe $5 Add weather data from Tomorrow.io. Includes current conditions and daily forecasts Volumio Bob paauwe $10 Add control of Volumio media players WeatherPoly Bob Paauwe $10 Receive weather data from locally configured station software like meteobridge, Cumulus, WeeWx, acuparse, etc. Example-3 Bob paauwe free Example node server that creates a user specified number of counter child nodes. Twinkly AutomationGeek free Twinkly Light WeatherFlow Bob Paauwe $10 Make WeatherFlow weather station data available to the ISY. BASIRRIGATION Steven Bailey $5 / 12month Universal Devices WiFi Controlled irrigation controller, with optional local camera for up to thirty six (36) irrigation Zones. It utilizes up to six (6) Contemporary Controls BASpi-6u6r or the BASpi-Edge-6u6r. Please see documentation. Backup Bob Paauwe free Save and restore lighting type device status OpenWeatherMap Bob Paauwe $5 Add weather data from OpenWeatherMap.org. Includes current conditions and daily forecasts RainMachine Gordon Larsen $20 Nodeserver for the Green Electronics RainMachine BASPOOL Steven Bailey $15 / 12month Universal Devices Wifi Ethernet Pool Controller using the Contemporary Controls BASpi-6u6r or the BASpi-Edge-6u6r control Devices. You can have up to (6) pools using this Node Server and it is a great fit for a conventional Time Clock controlled pool upgrades. Please see GitHub documentation for details on setup. Acurite James Paul free A Node Server for retrieving AcuRite Access Remote data for AcuRite devices BASGARAGE Steven Bailey $5 / 12month WiFi Controlled Garage door opener momentary push button duplicator, with optional local camera for up to six (6) doors. FlumeWater JimBo $10 FlumeWater Nodeserver VUE Bob paauwe free Monitor your smart meter with Emporia VUE Sense AutomationGeek free Sense Home Energy Monitoring MySmartBlinds AutomationGeek free MySmartBlinds *Only support Blind and required a Bridge* Eagle-200 Bob Paauwe free Smart Home Energy Monitor. Monitor home electricity use. AmbientWeather Bob Paauwe $10 Pull weather data from weather stations connected to Ambient Weather's ambientweather.net servers

Thanks everyone for the info. It was helpful to see that my pricing models seem to be aligned with expectations to most extents. Hopefully other node server authors will see this and get some value from it as well. I do agree about preferring non-subscription pricing, but I can also envision some cases where it could be required. A node server that accesses data from a data service that requires a paid account and a monthly subscription to access the data would mean that monthly subscription cost would need to be passed to the node server purchasers. Otherwise the node server author would end up paying out-of-pocket at some point.

Yes. I've added a couple of PG3 only node servers for integrating with smart meter energy monitors. There might be a couple of others also, I haven't really looked. Most are simple conversion from PG2 to PG3. For some of mine, I've tried to make the PG3 version better in some way to help justify the price. For example, the WeatherFlow node server for PG3 support the forecast data, the PG2 version does not. The PG3 version of the Volumio node server supports multiple Volumio devices, the PG2 version supports only one.

Nailing down a specific date for each milestone is difficult because everyone working on PG3 and porting node servers over is doing so in their spare time. Most people using it today, are doing so simply to port node servers but a couple of people have been doing more 'real-world' testing. I've been running a couple of instances of PG3 for most of this year. We continue to find the occasional bug but overall, it has been stable. But given that I have a lot more insight into the inner workings of it, I probably subconsciously avoid doing things that will cause issues (I.E. I'm a horrible test user). Once we declare beta, it means I'm pretty confident that anyone can use it without major issues. That's also when I expect to get more bug reports as there will be minor issues. As many of you are probably aware, one of the primary reasons for PG3 was to build in the capabilities that allow node server authors to charge and get compensated for their efforts. This is a big change and is also where we're likely to see issues initially. I'm going take this opportunity to try and do some quick market research. Currently, we're seeing prices between free and about $15 per node server with a couple taking advantage of subscription pricing of like $5 a year. I'd like to hear some thoughts on this pricing model.

@asbrilThey are unrelated. Polyglot is a program for managing node servers. PG2 - Polyglot version 2 PG3 - Polyglot version 3 ISY on Polisy is a replacement for the ISY 994i hardware The Polisy hardware is capable of running all three (PG2, PG3, and ISY) applications The 994i hardware is capable of only running the ISY application/firmware

Both PG2 and PG3 can run simultaneously on the Polisy. However, PG3 and PG2 node servers are not compatible. Moving to PG3 will require installing new node servers that are written for PG3. There are no plans to provide an automated migration of node servers. Currently the PG3 node server store has 31 node servers available and the PG2 node server store has 112 node servers available. Work is underway to reduce that gap. PG3 is not yet functionally complete, but it's close. I believe it is about 2 releases away from being moved from an Alpha quality product to a Beta quality product. It will remain beta until all existing node servers (that can be) are available in the PG3 node server store.

Even though you ran the pip3 command, you probably ran it as user "admin" and Polyglot is running as user "polyglot". So when you ran it, it installed the modules but they were installed for user "admin" and when the node server, running as user "polyglot" starts, it still doesn't have access to the modules. I think what you'll need to do is delete the iAquaLink node server (not uninstall, just delete). And then do the Add Nodeserver again to re-add it. That should re-run the install.sh script which will run pip3 again and, hopefully, install the modules so the node server runs. If that doesn't work, then try deleting and uninstalling the node server. If after that, you still have issues, best to open a ticket with UDI.

There are currently multiple versions of Polyglot and multiple versions of the node server store. Regardless of the version, the node servers are installed from the "cloud". Typically, when someone refers to the Polyglot in the cloud, they are not talking about the node servers, but rather the version of Polyglot that runs directly from the "cloud" vs. a version of Polyglot that runs on local hardware (Polisy or RPi). If you're installing node servers on a Polisy running Polyglot, then you are running the node servers locally. Because the "cloud" version of Polyglot and the Polisy version of Polyglot are different, they use different node server stores and they can run different versions of the node server. So an Ecobee node server installed and running from the "cloud" can be different from the Ecobee node server installed and running locally on a Polisy. And that makes a difference when answering questions/supporting the node server. Hopefully, this explanation helps clear that up.

"connected" just means that the node server executable is running (and it runs on the Polisy so that doesn't have anything to do with an ISY being connected or not). Under Settings->Polyglot is where the configuration of the ISY is set. Have you changed that to your new ISY? Polyglot should compare what node servers are installed on the configured ISY with what is in its database and reconcile the two so that only node servers that show up in both places are listed on the dashboard as "Connected/active".

Once polyglot marks a node server as un-managed, it's not really possible to move it back to "managed". Polyglot on startup and periodically while it is running, will query the ISY for the list of installed node servers. If when it does this query, the ISY either doesn't respond or responds with an empty list, it assumes those node servers have been removed from the ISY and removes them from its database. If it was a temporary failure and the next time it queries, it sees the full list from the ISY, it compares that with what's in its database doesn't find a match so marks them as "unmanaged". That's the technical description of how this can happen. I've had it happen many times while working on PG3 and made some changes to PG3 to make it a bit more robust so that if it can't communicate with the ISY it doesn't assume all the node servers have been removed. If you have a Polyglot backup, you can restore that and should be fine. Otherwise, you have to delete the node servers from the ISY and re-install them on Polyglot.

By P3, I'm assuming you mean Polyglot Version 3. No, the ISY 994 hardware is not capable of running any version of Polyglot. PG3 will only run on a Polisy. Polyglot version 3 does support managing node servers on multiple ISY's. However, you need to switch between them as it can only display the dashboard for a single ISY. You could have multiple browser windows open for PG3 and each could show the dashboard for a different ISY.

I just deleted all my node servers running on my ISY/PG3 so now would be the perfect time What is the specific issue with case?

Try re-starting polyglot after setting/saving the ISY info. I've seen this type of issue before and it seems to be related to polyglot getting confused over which ISY it should be using.