bpwwer

As mentioned in other threads, neither PG2 or PG3 were designed to allow migration so the process is not good. "Unmanaged" means that some other instance of Polyglot installed and is managing those node servers. In your case, it's the PG2 instance that installed and is managing them. You don't need to do the install after purchasing the PG3 versions. To restore from a PG2 backup you just need to have the license, you don't need, or even want the node servers to be installed before doing the restore. The restore will do the installation. If the restore from PG2 backup works, it will install the PG3 into the same slot and update the ISY so that it works with the PG3 version and not the PG2 version. However, PG2 doesn't know this happened and still thinks it is managing those node servers as well. Like I said above, PG2 was never designed to allow this and you're basically making PG3 steal the node server control from PG2. From this point forward, you should not use PG2. You can also use PG2 to delete the node server(s) first, then PG2 won't being trying to control the node server/ISY. Once restored with PG3, it should work, but you may have to do some manual fixing as there's no guarantee that the PG3 is exactly like the PG2. The PG3 configuration could be different and the nodes create by the PG3 version could be different. It varies depending on the node server.

"Unmanaged" means that it was installed by a different instance of Polyglot. Only the instance that installed the node server can manage the node server. By your description, it sounds like you have two Polyglot installations (PG2 and PG3 maybe?) If that's not the case, you'll have to explain how you got your system into this state so we can figure out the next steps.

No idea, I don't know anything about this node server, sorry.

Yes, but it backs up all lighting type devices and restores all lighting type devices. You can't work with just a subset of devices. Although that would be a nice enhancement.

Yes, the free accounts do have limits, typically on the number of requests that can be made in a 24hr period. I don't remember what those limits are for the various services but I did try to set the default polling intervals to be high enough to not hit those limits. It is the poll intervals set in the node server that define how often it makes requests to the service. ISY programs won't trigger additional requests.

The instructions are referring to the PG3 custom parameters configuration, not ISY variables. You enter this in configuration section of node details for the node server on the PG3 user interface.

It should be in the store now.

PG3 (and PG2 actually) is really 2 separate components. There's the server component that interacts with the node servers and the ISYs and there's the frontend, or User Interface (UI) component that you interact with. The server component code runs on the Polisy in the background. The UI component runs in your Browser. In general, the versions should match. When a release it built, it updates the version number for both components. If they don't match, the most likely reason is because a new version was installed but the Polisy is still running the old version of the server component. The latest version of PG3 will tell you this and prompt you to restart PG3 to get the latest version installed on your Polisy running.

RA3 uses the Lutron LEAP protocol which is not publicly available. There are folks working to reverse engineer it. It really comes down to whether or not Lutron is willing to work with UDI or the reverse engineering efforts can provide a stable working library. RA3 does not require a licensed installed to install. Lutron makes the training classes available to anyone and once take, you are free to buy and install RA3 products. No, the Lutron processes/bridges can communicate over your local network via LEAP (or LIP) protocol. Their app has cloud dependencies, but node servers would not (at least the current ones for PG2 do not).

Ok,

I don't know what else to tell you. The Roku documentation lists the following as supported keypresses: Home Rev Fwd Play Select Left Right Down Up Back InstantReplay Info Backspace Search Enter It also supports querying and launching installed apps. That's it.

If you're not planning to use PG2 or need to see the configurations for the node servers there, you can simply delete the node servers from the ISY. From the admin console go to Node Servers -> Configure -> <slot> -> click the Delete button. PG3 may take a few minutes to recognize that it's gone from the ISY but after 5 minutes or so, the unmanaged entry should go away and the slot is now free to install a node server.

Unless it's a Roku TV, no. the node server only controls Roku devices.

No, it was written to work with this device: https://www.amazon.com/Connects-Electric-Metering-Burlington-Mountain/dp/B084T6HGNR/ref=sr_1_3?crid=3BJIJ2RUPH2JR&keywords=emporia+vue&qid=1652393069&sprefix=emporia+vue%2Caps%2C139&sr=8-3

I think version 2.0.2 will resolve it. However, you should also update PG3, you're running an out-of-date version.

Hmm, I did port it last October. I have no idea if works at this point, but I guess I should check and then release it.

It's display the "Main" channel data for both of those. So that kindof implies that your charger is considered the main channel for daily data? I don't really know. The only device I have has only the "Main" channel.

It's not getting valid data. How often are you polling for data? It looks like about 90 seconds from the log. I believe you can only make a limited number of queries per day and if you have it set to 90 seconds, it may only be able to get data for a few hours before you've used up the day's allocation. When I was testing it, I used shortPoll = 240 and longPoll=1200 to try and keep under the limit.

Try version 1.0.4. It should be better.

The store only updates automatically a couple of times a day. You can manually refresh the listing using the "Refresh Store" button. It's in the Production store.

Refresh the store and restart the node server. It should install version 2.0.1 and I believe that will fix the problem.

Yup, that helps. I just uploaded version 2.0.1 of the Roku node server to the store. Refresh the store and then restart the node server and see if that adds your Master Bedroom Roku.

I just pushed out version 1.0.3 of this node server. I think I managed to work around the problem with the library.

If the version numbers match and it's saying it needs to be restarted, just re-loading the browser should fix it. Apparently 3.0.62 does not equal 3.0.62 sometimes. I suspect that the old version is cached somewhere and that's why it does that, but it should be comparing the same values it's displaying.

No, there's nothing wrong with the node server, one of the python libraries it depends on won't install on a Polisy. I'll see if something can be done to get the library supported on the Polisy.