similar to: NUT testing for v2.8.3 (hopefully imminent)

So... April 1st came and went, busy with last-minute warnings from a newly set-up NetBSD build agent for the NUT CI farm, as Greg-inspired warnings exposed by the stricter platform kept popping up and biting. Led to some discoveries in toolkits and standards I thought I knew for decades, too. So it was a tad bit annoying, but good overall :) But now we are a day over the hopeful "not more

So... April 1st came and went, busy with last-minute warnings from a newly set-up NetBSD build agent for the NUT CI farm, as Greg-inspired warnings exposed by the stricter platform kept popping up and biting. Led to some discoveries in toolkits and standards I thought I knew for decades, too. So it was a tad bit annoying, but good overall :) But now we are a day over the hopeful "not more

So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim

So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim

Sounds great, thanks! A number of other community members raised a few issues from the RC testing that finally took off, so I guess there will be an rc3 at least... There may also be some issues with upssched as discussed in another mailing list thread and https://github.com/networkupstools/nut/issues/2890 (may be or not be same problem underneath) but I am not ready to investigate that deeply.

Sounds great, thanks! A number of other community members raised a few issues from the RC testing that finally took off, so I guess there will be an rc3 at least... There may also be some issues with upssched as discussed in another mailing list thread and https://github.com/networkupstools/nut/issues/2890 (may be or not be same problem underneath) but I am not ready to investigate that deeply.

Sorry, that was one mishap layered onto another - the "v2.8.3-rc1" tag was supposed to point to the same commit as what I originally hoped was "v2.8.3"... but did not - instead initially pointed to what would land to `master` among its fixes for a cleaner release. Hopefully tags are correctly refined on GitHub repo now, at least. Jim On Tue, Apr 8, 2025 at 2:58?PM Greg

Sorry, that was one mishap layered onto another - the "v2.8.3-rc1" tag was supposed to point to the same commit as what I originally hoped was "v2.8.3"... but did not - instead initially pointed to what would land to `master` among its fixes for a cleaner release. Hopefully tags are correctly refined on GitHub repo now, at least. Jim On Tue, Apr 8, 2025 at 2:58?PM Greg

Hello fellow NUTs :) It is my great pleasure to get a bit of sunshine from other people's work, and announce that the initial pull request for `apc_modbus` NUT driver has recently been merged to the main NUT codebase, so it would be part of an eventual 2.8.1 release. Great thanks go to Axel Gembe for the implementation, and to numerous community members for testing as well as their bug-fix

Hello fellow NUTs :) It is my great pleasure to get a bit of sunshine from other people's work, and announce that the initial pull request for `apc_modbus` NUT driver has recently been merged to the main NUT codebase, so it would be part of an eventual 2.8.1 release. Great thanks go to Axel Gembe for the implementation, and to numerous community members for testing as well as their bug-fix

Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov

Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

Hello there, I don't think that's working,? I have done all your repo but i don't know how it's supposed to work. I have a idea, change vendor id and product id? to make the driver try to connect to the ups, what do you think of that ? With this driver maybe : usbhid-ups FatGear Le 16/09/2023 ? 20:40, Jim Klimov a ?crit?: > It seems the `libmodbus` library or headers were

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. > > https://github.com/networkupstools/nut/pull/2184 > > As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. > > https://github.com/networkupstools/nut/pull/2184 > > As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and

I have an Smart-UPS X 1500 (SMX1500I, USB) USB. I am looking for the APC_MODBUS driver. Thanks James -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20231209/e81b0a7d/attachment-0001.htm>

I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make dist, (on NetBSD 10) and then used that tarball as the source for pkgsrc, built a package, installed it on machine with a Best Fortress (NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT interface code seem fine. So I see no problems. (Of course, I always like there to be a multiday interval from rc to

I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make dist, (on NetBSD 10) and then used that tarball as the source for pkgsrc, built a package, installed it on machine with a Best Fortress (NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT interface code seem fine. So I see no problems. (Of course, I always like there to be a multiday interval from rc to

Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your