nut

nut copied to clipboard

> As for the build log, I suppose most of the error noise about `ups->conn` as an `int` is because of C defaulting: ```` src/nut.c:40:2: error: #error "Unable to determine...

jimklimov

Missing support for the feature in Python bindings For details see https://github.com/networkupstools/nut/issues/656

jimklimov

Missing support for the feature in PERL bindings For details see https://github.com/networkupstools/nut/issues/656

jimklimov

Study the possibility to default to type 'STRING' for variables

3

Quoting @zykh from #265: "I know that most of our vars are numbers and so it's easier to only edit the type for the few string ones, but maybe it...

aquette

We currently have an initial limited support for some SCDs (driver `ivtscd`), but the retrieved and published data is very scarce. Other (newer) devices report more data which could be...

zykh

These devices use a protocol (https://github.com/zykh/nut-website/blob/voltronic-sunny/protocols/voltronic-sunny.txt) which is an evolution of the one used by Voltronic Power UPSes and, as such, `nutdrv_qx` is the best candidate to support them. With...

zykh

Setting input.transfer.high/low fails on CP1500PFCLCD but reports OK

8

I was having trouble setting input.transfer.low and high values. Using the script called out here: https://github.com/jimklimov/nut/commit/4be9a31226d9044bfee21fc9eb69929f0ec409bd I found that input.transfer.high only allows values between 136 and 141 and input.transfer.low only...

dacarson

(follow-up to #616) We now have access to (almost) all the protocols specs for `metasys`-supported devices: - https://github.com/networkupstools/nut-website/commit/66d30c90401ff7929b25e5a87f9299b728f861ea - https://github.com/networkupstools/nut-website/commit/570c1e5e9f1fb4f82abef9359897b5159e88fc50 ...and the `metasys` driver currently only uses a subset of...

zykh

Support building drivers for both libusb-0.1 and libusb-1.0 on systems that have both

1

_As suggested in a comment originally posted by @knuta in https://github.com/networkupstools/nut/issues/300#issuecomment-665450498_ We have the following two requirements which have so far been somewhat at odds: - Some devices cannot function...

jimklimov

All drivers and `nut-scanner` should use `nut_usb_get_string` instead of libusb's `*_simple` and `*_ascii`

1

* Device discovery, where still custom * String data point queries * Copy of the method (or separate `.c`/`.h` file to share) for `nut-scanner`? => Currently solved as a copy,...

jimklimov