-
-
Notifications
You must be signed in to change notification settings - Fork 351
NUT HCL and DDL
For browsing, see:
- HCL look-up, and
- DDL look-up
For reporting your device into the library, see DDL reporting how-to and comments in https://github.com/networkupstools/nut/blob/master/data/driver.list.in HCL source file.
If you post a NUT-DDL pull request, a check-list would be presented to help you score all the points. PR approach also tends to have a much faster turn-around with maintainers who just have to review and merge the submitted contributions, than "unstructured" reports which have to be copied into a checkout of the repository and tend to have lower priority than other requests.
The NUT HCL/DDL project helps keep track of this effort. Many original reports are tagged in the NUT issue tracker:
Welcome to the Network UPS Tools (NUT) project Wiki, and feel free to contribute tricks and insights.
While there are several good entries in the menu, ones referenced most frequently in issue discussions include:
- Building NUT for in-place upgrades or non-disruptive tests and Using NIT (NUT Integration Test suite) sandbox
- Technicalities: Customizing (NUT) config files and scripts delivered by packaging
- Links to distribution packaging recipes and repository sections
- Troubleshooting
upsdrvctldrivers not starting ("insufficient permissions on everything" or "Can't claim USB device [VVVV:PPPP]@0/0: Entity not found") possibly due to nut-driver-enumerator (NDE) services having been there before you with NUT 2.8.x - Changing NUT daemon debug verbosity
- Building NUT integration for Home Assistant
- Running NUT in an LXC container
- Troubleshooting eventual disconnections (Data stale) and CyberPower Systems (CPS) know-how
- NUT for Windows
- NUT HCL and DDL
- Code contributions, PRs, PGP and DCO
- NUT CI farm
Also keep in mind the documentation links from NUT website and the FAQ in particular.