bpwwer

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.

Did you start the ISY software on the Polisy? I don't believe installing it starts it automatically. You can check if it's running with: sudo service status isy If it's not running, you can enable it and start it with: sudo service isy enable sudo service isy start

I see the same thing. While it shows the existing node servers in the tree view, and does allow me to install and delete node servers via Polyglot, it doesn't appear to be reading the profile files for the node servers. They all show up with the light icon and none of the drivers are displayed when selecting a node server. @Michel Kohanimwas a build option for node server support turned off in this build?

No, it will be a separate (different and empty) ISY. Since the ISY software on Polisy doesn't support z-wave yet you won't be able to do much with it at this time. You should be able to connect node servers to it, but the existing Polyglot can only connect to one ISY so you'd need a separate instance of Polyglot (I.E. running on a separate RPi) in addition to your Polisy to do that. I believe you could run PGC based node servers on it if you have a portal account (but I haven't tried). That might be a good thing for someone to test out. As @Michel Kohanimstated when he announced this, he's making it available to get some more wide spread testing, it's not ready for production use. You basically need a separate, non-production, environment to make use of it.

Installing the ISY software on the Polisy gives you another ISY box, independent of any others you own. So unless you move the PLM and re-link all your Insteon devices and re-create all your programs/variables and re-install all your node servers to the new ISY (which I don't recommend you do at this time), you continue to use your existing ISY as you normally would. ISY on Polisy is available to experiment with. On that note, I've installed the ISY software and the latest PG3 software on a Polisy and loaded up a PG3 node server. So far that is all working. It's pretty exciting to see all the components working together and running on one box.

I created something like what you want but it is designed to run full screen in a browser and provides status of mostly node server based devices. But the technique would also work for a small browser window and normal switch/lighting devices as well. I have a web page served from my local web server that makes a websocket connection with the ISY. It monitors that connection for specific events and updates the appropriate elements on the web page with the new values. I believe there is an example of this in the wiki (or maybe the forum) and the ISY itself can host the web page (I think you need the network module). It would also be easy to use this technique to create a desktop app with something like C# in .net (or whatever your language of choice is). The code to do this is pretty simple. WS = open websocket connection to ISY on WS event: # get event details (event type, device, action) if event type is something we care about: if device is one we want to monitor: display new action value for event You probably won't find a pre-existing solution because to do something like in a generic manner means you're going to end up re-writing the admin console / dashboard which is a lot more complicated. Plus, what you want to display and how is probably very specific to your environment. I could give you my javascript/web page, but by the time you modified it for what you wanted, you'd probably have changed almost every line. If you're curious, I did already post screen shot and code at

Starting on Friday, there was a problem with the store. I caused that when I updated something for the local Polyglot store and didn't realize that it would effect PCG. I won't go into the details, but that issue has been resolved. While @Michel Kohanimand I were trying to determine the store problem, we did something to cause the second problem, happening now. Neither of us really understand PGC all that well so we're trying to figure it out as we go. Does anyone know how to enable developer tools on their browser and report what it's doing when it's spinning? The basics are (at least on chrome/opera): - enable Developer Tools on the PGC page. - select the network tab - reload the PGC page I'd like to see the last couple of messages in the console. For me, it hangs after requesting the list of ISYs attached to my account. Something eventually times out and the page loads, but the request for the list of ISYs is taking anywhere from 50 minutes to 20 hours before it returns the list. My list of ISYs contains a Polisy, because that will be required for PG3 and that seems to confuse PGC so I'm curious if what everyone else is seeing is related to the getIsys request or if it's something else that I'm not seeing because I'm special.

I let mine sit there for a while and it eventually populated the ISY menu and seems to be working fine now (unless I refresh the ISY list). I don't think I have access to view/modify anything related to the running cloud instances so I can't do much else at this point.

This sounds similar to what I'm seeing too, I thought it might just be me since I have an "ISY" entry in the database that's special for PG3 testing, but it sounds like other's are having issues getting their ISY entry out of the database too. I'm looking into it.

@thruster999can you re-try connecting again? There were some issues with PGC yesterday that should be resolved now.

The program is evaluated (run) when something in the 'if' part is triggered. at 5:21ish, the dusk/dawn sensor is triggered, the program is run and the if statement evaluates to FALSE (sensor switched off is TRUE but time range is FALSE) so the ELSE clause is executed. at 6:00am the program is run again and the if statement evaluates to FALSE (sensor switched off is FALSE but time range is TRUE) so, again, the ELSE clause is executed. at 9:30am the program is run again and the if statement evaluates to FALSE (sensor switched off is FALSE but time range is TRUE (maybe) so, again, the ELSE clause is executed. The confusion is that the condition is re-evaluated when any of the conditions change, not when all the conditions are TRUE. The conditions control which part of the program is executed (THEN or ELSE), not if the program is run. It sounds like what you might need two programs to accomplish this because you're trying to do a nested condition, but the ISY can't do that. You want: if sensor switch off then if time in range send text else send email On the ISY you can simulate that with: if sensor switched off and time in range then send text if sensor switched off and time outside range then send email

The Polisy Pro is not running Linux, it's running FreeBSD. They are different operating systems. While the hardware (and FreeBSD) are both capable of running a general purpose web server, I don't believe that UDI packages up any of the general purpose web server programs or other related software necessary to run one. Also, if you're using the Polisy to run Polyglot, Polyglot is a custom web server so you'd have to careful not to have anything you install conflict with that. My first question would be why do you want a publicly accessible web server on the Internet? Maintaining a public facing web server is a lot of work and typical home Internet providers prohibit running one because of the load/security issues. To make it accessible, you would also need to purchase a domain name, and configure DNS and have some way to map the your external (possibly changing) IP address to the domain name. If you really need a public facing web site, you're much better off purchasing one from a hosting provider. They end up doing most of the heavy lifting and you just have to create/add the content. Your ISP may even provide some limited web serving for you. If you just want a web server that is only visible to the devices on your local home network, then hosting it on the Arduino is fine (or on a RPi). Security is much less of an issue since only someone logged into your WiFi or router would be able to access it.