bpwwer

I guess that makes sense, "not a number" isn't a number so it can't be converted to an integer. In any case, the latest version shouldn't crash if that happens again.

The version in the non-production store is the same, I was using it to test auto-update functions which is why it has a different version number. You can try version 2.0.3 and see if it makes any difference but I don't really think it will. The code that interacts with the roombas is from an external library and there haven't been any changes to that library since version 2.0.2.

I added code to check for that error, report it and continue. If you refresh the store, you should see version 2.0.4 and restart of the node server will install it. It should report an error to the log when it does this. I'd really like to know what Volumio is sending for the volume if you don't mind posting.

I think I see the problem. Try refreshing the store list to make sure it shows version 2.0.1 and then restart the node server

That's strange, I wonder what it's returning for the volume that's not a base 10 number?

@DennisCIt shouldn't be a problem with the latest version of PG3, released today.

Yes, at this point, you'll see the same problem with almost all node servers because it isn't really a problem with the node servers, but a module that they all depend on.

Look like you got lucky. You happened to install a node server(s) that didn't get the latest version of the interface module and that version that did get installed, requires the latest version of pyisy module which is currently broken. The next version of PG3 will try to work around this, but at this point, there's no easy way to fix this. Because Python relies on so many third party modules, if one of those breaks, it causes trouble for everyone using that module and there's nothing configured on the Polisy to let your manually change these packages. I updated the AmbientWeather and NOAA node servers to require the fixed version of the module so you can try refreshing the store and then restarting(starting) one of those node servers and see if that works.

ISY -> edit current ISY menu option in PG3

The log is showing authentication errors connecting to the ISY. Sounds like you don't have the right username or password entered for the ISY.

It looks like the certificate for isy.io has expires and needs to be renewed. We're working on it now.

Sounds like a network/AWS issue. Both versions get the store info from AWS. So either something (firewall) is blocking it, the network route is down for some reason or the AWS for your region is having issues.

No, it doesn't backup the logs. I thought that just not including the logs would be enough to allow all node servers to be backed up, but because they can vary in size I don't really know what the maximum size of a backup could be. Based on your report, I'm guessing that it's not too hard to get a backup too big for the process.

If the backup is too big, it just stops sending without reporting any error or any other indication. I'm not sure what the size limit is, but I'm guessing you're system exceeded it.

Can you turn on debug and send a debug log and configuration?

It only tries to discover if there aren't any saved or you manually start the discovery process.

It will probably work tomorrow Try version 3.0.15, it should get farther, but it seems like there's no historical data so I might have other places where I assume the historical data exists.

It does save the discovered Roombas, but I have no idea if that would work. Seems like your router wouldn't allow that.

There isn't any option to set the IP address manually. That would have to be added.

One of the node server dependencies (PyISY) just releases a new version that is broken. I just pushed out a new version of the node server that will try to roll back to the previous version of PyISY. If you refresh the store, it should show up (version 2.0.5). If you restart the node server it will automatically update to this version.

If that's all your log shows, then it looks like PG3 is unable to start the node server. You can check the PG3 log for errors trying to start the node server.

Node servers in the "Production" store have been vetted and approved. Node servers in the "Beta/Non-Production" store don't have that requirement. The primary purpose is a place for developers to release pre-release or bug fix versions for testing by a limited audience before moving them to the Production store. In general, you should only install a node server from this store if the developer recommends you do so.

I can't get it to run either because of issues in the python libraries that it depends on.

Depends. By default, PG3 will try to connect to an IoP ISY running on the Polisy. If you both that and a standalone 994 ISY, you'll have to add the configuration for the 994 under the ISY menu. It is also possible that it found the ISY, but doesn't have permissions yet to actually log into it and get the existing node information. In this case, you'll need to edit the ISY entry and add the ISY username/password.

I just pushed version 3.0.1 to the node server store. This version should stop it from crashing. Restarting the node server, should auto update it. If that doesn't work, let me know.