bpwwer

Your question is unclear. There are no changes with how Polyglot interacts with an 994i vs. interacts with an ISY on Polisy. It continues to work as it does today. Over time, the various components will have their support end-of-lifed, but the components themselves should continue to work as is. Eventually the 994i will stop getting firmware updates. Polyglot version 2 is not likely to get any more feature updates. Node servers for PG2 will also likely stop getting feature updates and new node servers will likely be available for PG3 only.

I don't think this effects the current version of PG2, but using 'localhost' isn't working with PG3 (because it isn't resolving correctly with node.js). Using 127.0.0.1 does work. Something to keep in mind if trying out PG3.

Go to the menu item "ISYs" You can try automatic discovery, but if that doesn't find it, just add a new ISY and enter the information for the ISY on Polisy. PG3 can switch between ISY's so if more than one is configured you'll see them all in this menu and can switch between them.

That screenshot indicates it not running. If what @Bumbershoot recommends above doesn't work, make sure it really is installed. sudo pkg install pg3 then if no errors sudo service pg3 start

PG2 is on port 80 or 443(default web port) PG3 is on port 3000 You should be able to use the same URL you use for PG2, but add port 3000. For example if your polisy is at ip address 192.168.1.5 you'd use: PG2 - https://192.168.1.5/ PG3 - https://192.168.1.5:3000/

@asbril Can you be more specific about what you changed? To reset PG3 to it's default: sudo service pg3 stop sudo rm /var/polyglot/pg3/pg3.db sudo service pg3 start That will clear the database. When PG3 starts and no database is present, it will create it with default values.

That's weird. When PG3 starts and the database doesn't exist, it looks at, in order: an environment variable PG3IP (which shouldn't be set) the system's current IP address if those are both blank, it uses the local address 127.0.0.1 Can you post (or pm me) a screen shot of where you're seeing the old IP address and what you get when you run 'ifconfig' on the Polisy?

I don't think just uninstalling and re-installing will solve it as I don't think the uninstall removes the database, but I could be wrong. I haven't tried uninstalling. You can also just remove/move the existing database and restart PG3 if you're comfortable with the Polisy command line. The database is in /var/polyglot/pg3/pg3.db so either remove or move that file and then run sudo services pg3 restart that should re-create the database and populate it with the new IP address.

@sjenkins Is it the PG3 ip address that's showing wrong or the ISY address? Those are two different things in two different menus on PG3. The PG3 IP address is set when PG3 is run for the very first time and there is no mechanism to change it later. The only way is to uninstall PG3 and remove the database so that when it is re-installed it starts with the new/correct IP address. The ISY IP address is configurable using the Edit ISY menu option. Completely unrelated, but we used to go boating on Lake Fenton when I was a kid. I grew up in Grand Blanc. Small world sometimes.

The ISY version issue is a know issue. Restarting everything will probably correct that as I think PG3 only checks that on startup. Changing the Polisy's IP address is not a trivial process. When a node server is installed on the ISY, it includes the IP address of the node server (PG3/Polisy) so that it can send status/commands to the node server. PG3 will also compare the value the ISY has with its own IP to see if it "owns" the node server. If you change the IP on the Polisy without changing the IP for each node server installed on the ISY, PG3 will assume it no longer owns those node servers and will delete them from it's database. Once deleted from the database, the only way to restore would be from a backup or by re-installing the node server after manually removing it from the ISY. Because of this, PG3 isn't designed adapt to it's IP address changing. It checks the IP address when it is first time it is run and saves that IP address in its database. The assumption is is that if you're changing the IP address you are starting over with a new install. Basically, changing the IP address isn't really supported on PG3 and while it may appear to be working fine now, things may fail later that will be hard to debug.

Agree with @Javi about Global Cache. I've used on for years without any issues. I also have a Quatech 4 port device that I use with Russound systems. It might be the specific firmware version, but it seems to give up on dhcp if the dhcp server is down when it tries to renew the lease. This means that I typically have to power cycle it manually after power outages.

Since the Polisy has USB ports, it should be possible to add a USB IR receiver and write a node server to interact with it. Not a direct replacement for the IR support in the 994i/IR but should be able to provide the functional equivalent. And, no, I'm not volunteering to write the node server at this time

The primary goal for PG3 was to provide a platform that allowed for commercial node servers. I.E. a way for third parties to publish and sell node servers. In addition to that it has some user visible new features: Ability to connect with multiple ISY's, not just one. Ability to install multiple copies of a node server. Sorting the node server store list by various columns. Simplified install process. Automatic updates on restart (similar to what PGC does). Additional control of node servers from the GUI (discover, load profile). There has also been a lot of work to revamp the API used by node servers to interact with PG3 so that node servers work a bit better. An example here is how configuration parameters are handled. With the new API it is easy to set the default values for configuration parameters and handle user changes to those dynamically. So you should no longer have node servers that say set xyz and then restart the node server.

I believe PG3 may be installed by default now with the latest updates. Certainly, once it is installed, it can be updated using the standard pkg commands or via the Polyglot (PG2) menu items to update the Polisy. Soon those same menu items will be available on PG3. I've been posting announcements of updated versions (and the changes) to a Slack channel for PG3 node server developers. Seems like more people are interested in it so I'll have to start posting those here as well. Occasionally, the updates to PG3 have broken existing PG3 installations. I've tried hard to minimize this, but it is still a possibility. However, I don't know of any changes on the horizon that would do this. Most of my effort going forward will be to get existing node servers ported to work on PG3.

There are a couple of node servers that make use of specific hardware features of the RPi that won't be ported to PG3 as they just can't work there. Currently, you can use the Polyglot backup process to backup PG2 node servers and use the PG3 restore from PG2 backup to restore them on PG3. However, there are things to note about this process. 1. The node server must exist in the PG3 store. It can't restore node servers that don't exist for PG3. 2. The node server in PG3 must have the same name as the node server in PG2. If the name has changed, it won't be able to find it under the new name. 3. If the node server in PG3 is not a free node server, you'll need a license for the PG3 version or it won't restore. 4. Configuration parameters will only carry over if they are the same. If the PG3 configuration is different, it can't translate.

You can change the password but not the username. Polyglot can only have one user account and currently PG3 doesn't allow you to change that.

It doesn't replace the existing PG2 installation. That remains active. It adds a second dashboard at a slightly different web address. https://<polisy ip>:443/ ==> Your normal PG2 dashboard (or https://<polisy ip>/) https://<polisy ip>:3000/ ==> The PG3 dashboard

Yes, it available with recent Polisy updates. You'll have to install it from the ssh command line. 1. Make sure your Polisy is up-to-date sudo pkg update sudo pkg upgrade 2. Install PG3 sudo pkg install pg3 sudo service pg3 enable sudo service pg3 start Once it is installed, you can access it at https://<your polisy's IP>:3000/ It has the standard default login of 'admin' / 'admin'

No, but given that you aren't paying for any of them, you are always getting what you paid for. I disagree with the conclusion. Do you really expect a single entity to provide better support for 100's of different devices they don't have and don't use than individuals that actually have and use the devices? My experience is that the other controller manufacturers either can't support all the different devices or provide the minimum of support so they can claim they support them. UDI provides a platform and API, the community is currently providing Polyglot and device support. This is changing as UDI takes a more active role in developing and supporting the third party development community. That's an interesting question as the Polisy is really a future ISY product, not the current ISY product. So I believe most folks are taking the "plunge" with Polisy now so they can be better prepared for the future, not based on what it can do today. If you don't want to run pre-release/beta software, the Polisy is really just a nice piece of hardware with Polyglot pre-installed. Both the Polisy and an RPi with Polyglot installed give the ISY the ability to interact with other devices and services beyond the support for Insteon and Z-Wave devices built into the ISY. If you need support any other device/service, then node servers are the only option you have. And I use the term "node servers" specifically because that's a reference to the API that the ISY uses to interact with other devices. Polyglot (on either Polisy or RPi) is a framework that supports many different device node servers. It is community developed and supported and is not well documented. You basically have to install it to see what is available and (as others have pointed out) the documentation for each. NodeLink is another framework that supports device node servers. It was developed by a forum member and you can find more information about it here in the forums. Polyglot Cloud is a cloud version of Polyglot that runs on machines in the cloud instead of a local (Polisy or RPi) hardware device. It supports a subset of the node servers that Polyglot has. In a few cases, there have been individual node servers developed that aren't part of any framework. But I believe most of these have been abandoned in favor of NodeLink or Polyglot. Polyglot version 3 is currently in development and is an evolution of the current Polyglot. The main goal is to provide a better customer experience and allow third party developers to be compensated for their efforts, should they desire. Yes.

Keep in mind that with the current release of Polyglot, all node servers are free. They are mostly developed by individuals that create them for the equipment they own, to do what they want to do. And then they do their best to support others who want to use them in their spare time without any compensation. I state this simply so that you have the right expectations set. That's not to say that the existing node servers aren't good. Most of them are very well written and do what they are intended to do.

To answer the question about running multiple copies of the rainmachine node server on PG3. That is true. PG3 will allow for multiple copies of the same node server to run so you would be able to support both controllers. It is also possible to run two copies of the same node server on PG2, but you would have to manually install one of the copies and give it a different name. When PG2 installs a node server from the store, it uses the node server name as the location to do the installation (hence you can only install it once from the store).

Polyglot is not the only way to install and run node servers, there are others. However, Polyglot is the most used method. You're right in that when using Polyglot, it is managing the installation/removal, starting, stopping, and configuring of node servers. It tires to make that fairly easy. Polyglot version 2.x is designed to work with only one ISY at a time. You can switch it to another, as you've tried, but none of the node server configuration transfers to the new ISY when you do that and you're basically starting over as if it was a new install. Once you switch, Polyglot will remove all the old configuration (from Polyglot, not the old ISY) so you are not able to switch it back to the old ISY without again re-installing the node servers.

Yes, in theory. I believe it can do name resolution for the ISY IP but I haven't tried that. But the connection would have to work both ways. PG3 will connect to the ISY via an IP address/port number. As long as the IP/port is reachable, it will work. But the ISY also needs to communicate with PG3 (mainly to send commands back) so it needs to be to reach the http(s) IP and port that PG3 is using.

Unfortunately, that's not how Polyglot works. A node server is a program that translates data between a device and the ISY. It puts the data in a form that the ISY can consume, and it takes commands from the ISY and puts them in a form that the device understands. Polyglot is designed to help manage node servers and handle some of the common tasks that every node server needs to do. When Polyglot "installs" a node server, what it is really doing is configuring the ISY, setting up communication channels, and starting the node server program running. When Polyglot starts, it queries the ISY for what node servers have been configured there and then sets up the communication channels and starts the node server program running. Once you change the ISY and restart Polyglot, it queries the new ISY for what node servers have been configured. The new ISY doesn't have any node servers configured, so it returns none. Polyglot then thinks everything it has configured has been removed, so it clears all the previously installed node servers. The ISY is considered the definitive source of node server installs, not Polyglot. Unless you have a backup of the Polyglot database or did a backup of the node servers using the Polyglot backup feature, you are going to have to start over and re-install the node servers.

Not with PG2. It can only connect to one ISY. You'd have to run an additional copy of Polyglot on something else like a RPi and have one connected to your old ISY and one connected to the ISY on Polisy. PG3 will be able to do this, but it's not production ready at this point.