bpwwer

Have you restarted ST-Inventory? Or you may just be able to do a query on the node. I believe what happened is that when you installed Ring, you also had to enable remote access. When remote access was enabled it restarted the IoX. When IoX restarts, it doesn't remember any of the node server values. ST-Inventory will only send the counts to IoX when they change and most of those values rarely change. It doesn't know that the IoX was restarted and that it needs to send everything again.

Hello all, We are very happy to introduce PG3x v3.1.27 for eisy and Polisy. The eisy is using a new version of Polyglot version three called PG3x. PG3x has infrastructure changes to make node servers (and PG3x) more secure and enable features based on remote access. Polisy users may update their systems to use PG3x if they want access to the new features. PG3 will continue to get updates for the foreseeable future. To upgrade PG3x: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you should restart/reboot the eisy. Do this from the Admin Console, Configuration, Reboot. Once PG3x has restarted, reload /refresh the browser page. Changelog for 3.1.27 - Fix developer API queries. - Add install option to Purchases page and change "(Re)Install" to "Update". - Base call to PG3x cloudlink protocol on UI protocol. - Send notification to UD Mobile for NS connection status - Finish notification support - Add support for incoming POST request from IoX (to handle more complex notifications) - Add clientConnected message API for remote access via Portal. - Remove portal login button from sales report - Clean up login/logout of portal code in html templates. - rework purchase options to provide developers with more control over pricing. - Limit developer sales report to 18 months. - Sort developer sales entries by date - Handle free/trial in developer sales report if no paid options exist. - Update developer sales report to handle changes to API. - rework purchase options to provide developers with more control over pricing. - Log pip output when installing node server. - Add support for push notifications to UD Mobile

Hello Everyone, This is the support thread for PG3x v3.1.27

Hello all, We are very happy to introduce PG3 v3.1.21 with bug fixes and new features, see changelog below. To upgrade PG3: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you will need to restart PG3. From PG3 select System-> Restart Polyglot 3. Once PG3 has restarted, reload /refresh the browser page. Note that in some cases you may be asked to reboot after the upgrade is complete. Changelog for 3.1.21 - Fix developer API queries. - Add install option to Purchases page and change "(Re)Install" to "Update". - Base call to PG3 cloudlink protocol on UI protocol. - Finish notification support - Add support for incoming POST request from IoX (to handle more complex notifications) - Remove log messages for access_token authentication not needed. - Remove debug output from sale report request. - Remove portal login button from sales report - Clean up login/logout of portal code in html templates. - Portal oauth2 re-write. UI should now only ask for portal credentials once. - Limit developer sales report to 18 months. - Sort developer sales entries by date - Handle free/trial in developer sales report if no paid options exist. - Update developer sales report to handle changes to API. - rework purchase options to provide developers with more control over pricing. - Decrease maximum log size and compress old log files. - Add support for push notifications to UD Mobile (for PG3 an Node Servers) - Fix bug in git clone when no branch is specified. - Change text on how to update node server. - Change ISY to IoX in UI

Hello Everyone, This is the support thread for PG3 v3.1.21

I took a look at the RoomieRemote. It doesn't seem all that much different to me. Mostly there is just a difference in focus. eisy/Polisy are more focused on home automation and less on remote control. RoomieRemote is more focused on media remote control. RoomieRemote treats the ISY as a lighting controller and that makes sense. The support things like ecoBee thermostats directly, why would they want to also support an ISY node server for ecoBee thermostats? Doesn't make sense to apply any resources to that. Yes, there are devices that UDI supports via node servers that RoomieRemote doesn't and there are devices that RoomieRemote supports that UDI doesn't. That has more to do with each team applying resources to the support devices that fit with their main focus.

@TRI0N It can be hard to figure out what someone did/didn't do from forum posts so a big thanks for posting the screen shots. With the next release of PG3(x) the purchases page button will display either "Update" or "Install". Update when the node server is installed and Install when it is not. I'm hoping that clears up some of the confusion the exising (re-install) button causes.

What would it take to make UD Mobile compare with Roomie Remote? I.e. can you enumerate specific features/capabilities that UD Mobile doesn't have that Roomie Remote does? Here on this forum, you have the ability to influence UD Mobile development but this forum is not the right place to get Roomie Remote to better support eisy/Polisy.

Node servers have been available for years (4, 5, more?). There were discussions with third party developers and as @Javi said, it is possible to support them. Most developers of third party integrations chose not to. My reasoning was something like this: A HomeSeer thermostat plug-in sells for about $29. There are 4 or 5 different node servers for different thermostats. How much would I have to change for an ISY plug-in that supported 5+ different thermostats to make it worth the effort to provide support for them all? Now try to scale that up to support the 100+ different node servers. I'd have to charge over $3000 for my plug-in and nobody's going to pay that.

If it's not on the dashboard then you haven't installed it. Go to the Node Server Store, select Ring and select Install.

I believe ST-Inventory always logs that error if you don't have any network resources defined. It's not fatal and would have nothing to do with the Ring node server.

Pretty much no third party product that integrates with UDI has ever supported node server nodes. I've written one such product (HomeSeer ISY plug-in) and I don't support node server nodes in that either. While it is possible to do so, it is a lot of work because node server nodes can't really be handled in a common, generic way like Insteon or Z-wave. Each node server creates unique nodes which means unique code on the third party side for each node server. There are over 100 node servers so the effort is high and the payback is currently low.

The authenticate button is on the node server details page.

If you selected re-install to the existing slot, it does not touch the custom parameters so any that were previously entered will remain.** If you delete the node server and then install, it will delete the custom parameters and you will have to re-enter them. ** This is somewhat dependent on the node server as it could clear them all at startup if that was part of it's startup process.

@Michaelv Yes, the latest ISY plugin for HomeSeer does work with the latest eisy and Polisy firmware.

What do you mean everything seems to still be working? Do you mean that node servers are running and updating values in the AC? If that's the case, then have you tried logging out of the UI and logging back in? It's possible that the browser has cached credentials for PG3 and that those don't work for PG3x. PG3x no longer has it's own username/password database and instead authenticates against the IoX username and password as set for the local IoX.

When the UI is disconnected from the server you can't really do anything at all in the UI. Typically, this means that the server (or MQTT broker) isn't running. I would suggest running the upgrade packages from the admin console (even if you already did this) and then rebooting the Polisy.

With changes to allow for different types of purchase options, checking for updates got a lot more complicated as not all node servers have updated to the latest purchase option format in the store. Yes, I'm aware of the issues and how badly it is currently working. Unfortunately , fixing it is not at the top of Michel's priority list for PG3 updates right now.

Ahh, it looks like that data may be available via the Version 2 API, but not the Version 1. The node server current uses the Version 1 API. I have it on my list to convert the node server to use Version 2 of the API, but that's basically a full re-write of the node server and I don't have a time frame yet as to when I'll be able to do that.

The is what the server is sending in response: The plan is restricted and cannot perform this action. Adjust action and try again: endTime cannot be more than 5 days ahead.' It sounds like you're requesting more days of forecast than your plan allows. Reduce the number of forecast days to 5 or less.

Does the node server detect the sensors? If so, do you see anything in the log (probably need debug enabled) showing the data from them? I don't have any Davis equipment so I can only add support for something if I have enough info.

If you set the log level to 'debug' you'll get more information. It will display the actuall http request that it is making for the forecast data and it will display what the server returns. The error message is because the server did not return any forecast data.

From the admin console go to the configuration tab and then the portals tab. It should be obvious if it's registered or not.

I don't believe it is possible to get it working with the node server. The node server will need to be re-designed to work with the j7+.

The license is bound to the Polisy (or eisy) UUID. This is a hardware ID and will be valid as long as you're using that specific Polisy/eisy. If you had 5 i994's, you could install the node server on any/all of them. Once you have the license it's good for installing on the i994 and the later you can install it on the IoX running on the Polisy using the same license. The target ISY/IoX info displayed before you purchase the license isn't really meaningful. PG3 is using the same dialog box for the purchase and for the install, so it's only when installing that the target ISY/IoX means anything. I can see how that might be confusing so I'll see if I can make it less so.