Rysz

Please raise the UPS Debug Level (not the monitor level) to 6 and restart the UPS with that to see the error. Then upload the NUT Debug Package (found in NUT Settings) here.

It's included in the OS now.

If it's after an update, it's usually kernel (USB driver) related, check this post for information: https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/?do=findComment&comment=1350269

Fair, for a new system you're probably better off doing that as it can test all memory as opposed to the plugin.

Please post a screenshot of the page where you're getting the error and include how much RAM you have installed.

It's normal it says some packages were not found during the uninstall process. If you're unsure you can reboot the server to ensure any leftover files are gone (but there shouldn't be any).

The UPS does know, it's just that this specific UPS series may report it differently than (most) others so the driver doesn't know what to do. 😉 In any case, if you don't have a power outage at that time - it's calibrating, if you do - it's on battery, and either of the flags tell the driver what's what.

NUT will shutdown your containers and VMs as part of the regular shutdown. It will not do that just because the system is on battery (prior to initiating shutdown). If you want to do that you'd have to use the scripting hooks (in GUI configuration editor) or NUT Actions. It's not supported in the GUI, but can be done in manual configuration mode. It's been on the roadmap for a long while, but it's a large effort and not many are asking for it. OL+DISCHRG usually means on battery or calibrating, some UPS like to expose it like that. The flags allow NUT to show the UPS as OB (on battery) or CAL (calibrating) instead when in this state. It ultimately depends on what your UPS is really doing when it's in this state, then you decide on which flag to use.

Just click on the "Preclear" button as you normally would, and choose "Verify Signature" instead.

It's under "Array-specific Settings" - "SnapRAID Maintenance - Schedule".

Python 3.14 and the uv package manager are now included.

You can edit the UseLogging parameter in the configuration file (in DVM settings). You'll have to restart the service afterwards.

This is a feature that is definitely planned before the v1.0.0 release. In fact all the latest updates contain changes paving the way for this very feature. It's definitely going to be a lot of work, but I want to implement that kind of update command. 😉

Those of you who have problems with NUT 2.8.5, please post logs and which UPS model you're using. Ideally raise the "UPS Driver Debug Level" to the highest level (6) before capturing logs. This can help get those problems fixed for future versions, older backends won't be around forever.

I agree with this take. I don't think that disclosure is the holy grail open-source projects make it out to be. What it does is give maintainers a shallow mechanism to weed out obviously unqualified pull requests without needing to waste their time or creating friction among the other contributors. I don't think this approach translates well to an application store ecosystem, at least not without the issues mentioned above. At the end of the day, disclosure works only as long as people actually disclose something - but in my experience the worst code is usually the one that's not disclosed.