Closed cromulus closed 3 years ago
Unfortunately you will need to fork and maintain your own copy. The addon installs the debian packages, I'm not keen on maintaining any additional changes outside that for future maintenance reasons (udev rules are part of the package).
Makes good sense. Perhaps a "run configurable init-commands after boot" option, similar to this functionality in the node-red addon?
imho, it's too complicated to try and support, plus looking at the issue linked it doesn't resolve all challenges. My best recommendation would be to try to get the support configured upstream.
Problem/Motivation
I have a TrippLite 3024 and I have gotten it to work with nuts as a standalone daemon running on a dedicated machine. I had to do some finagling of the config.
It does not work by default, however, with this add-on.
Expected behavior
I expect that my UPS will be configured and managed by the addon
Actual behavior
this is the error I receive:
Steps to reproduce
Have a trip-lite 3024, and use this config: devices:
This is the solution I used to get this working on my standalone machine: https://github.com/networkupstools/nut/issues/808