bpwwer

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.

Is you eisy registered to your UDI Portal account? It needs to be or PG3 won't be able to install node servers.

It's certainly possible that they've changed something in newer Roomba's that breaks the way the node server attempts to access it. Everything related to connecting to Roomba's is based on reverse-engineering how they work as there isn't a public API to do this. Given that it's unable to connect to the Roomba because it is denying the connection attempt, you may need to do something to the Roomba to enable that. Ah, yes, the issue has been reported and it looks like the way to get the password is different for the j7+ and that method is not easily integrated into the node server.

No, the current design is based on the fact that the Roomba broadcast the information needed to connect to it. So the node server has to be able to receive that info to function. This is mostly a function of how the Roomba works, not the node server.

There was more than one. Release notes for 3.1.26 - Fix permissions on node server files after migration from PG3 to PG3x - Add an enhancement to cloudlink support, primarily for the Google Calendar node server - Compress old log files and limit the size of a log file from 100Mb to 30Mb - Fix a submission issue for node server developers.

Just to follow up, I spent some time with @pkauf and this is what we found. Node servers that install from a .zip package are getting installed with some of the files (seems like mostly the Python files) corrupted. The files contents are all there, but the order in the file is wrong. Usually a chunk of the code from the middle of the file ends up at the beginning. This causes the Python interpreter to fail, no surprise. Node servers that install from a git repository are fine. No idea why this is happening. I replaced all the PG3 files on the system and replaced the node.js module that does the unzipping in PG3 with no change. The FreeBSD unzip program works fine unzipping the same files. If anyone has any ideas, let us know.