bpwwer

I don't understand what you did with random id's. The nodes listed are device id's not station id's. The station ID is associated with the main "WeatherFlow" node and the sub nodes are all the devices associated with that station (as listed by the WeatherFlow servers). The ISY won't let you delete sub-nodes when they are grouped. You have to first ungroup them then delete them.

It's backing up log files again because the module doesn't provide a way to exclude them. That's why it's so large and because it's so large, it takes longer. It's taking long enough that the connection between PG3 and the node servers fail, moving them all to "Failed" state. You should be able to restart the node servers after the backup is complete. So both libraries that provide the functionality we need fail when the backup gets to a certain size. At this point, I don't have a solution that works.

Looking at the code for the PG2 version, the port is set to 3001. Maybe you changed yours at some point? Try version 4.0.3. I'm still trying to understand the relationship between the various nodes in this node server.

Fixed the problem with the object has not attribute 'parent' in version 4.0.2

That's not really enough information to do any debug with. I'd need the steps you were doing that lead to this and the complete log.

right-click on the node and select delete. The node server will create nodes for all the devices associated with the station ID, so if all of those are associated with the station ID, the node server will re-create them when it restarts.

Try version 4.0.1 just released to store. Refresh the store listing and verify it's showing version 4.0.1 then restart the node server.

The node server to PG3 is now a tri-state value instead of boolean. The states are "Connected", "Disconnected", and "Failed".

Great! glad it's working now.

Might be more correct in version 2.0.2

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?