similar to: Designing a Raspberry Pi "UPS"

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining

I was able to make NUT and my Powercom SPIDER UPS (USB port) work under the Raspberry Pi Desktop (Debian). Everything works in VMware Workstation 15 Player. But my Raspberry Pi 3b + (with raspbian last version) doesn’t work with the same UPS, and with same NUT configuration. Raspberry sees the UPS, but the driver does not cling. Here is the response of Raspberry 3b + to some commands. pi at

2015-06-04 13:04 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > On Sat, 2015-05-30 at 18:51 +0200, Arnaud Quette wrote: > > > > > > 2015-05-29 14:09 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > > > On Fri, 2015-05-29 at 13:59 +0200, Arnaud Quette wrote: > > > > Hi Richard and the list, > > > > > > > >

2015-05-29 14:09 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > On Fri, 2015-05-29 at 13:59 +0200, Arnaud Quette wrote: > > Hi Richard and the list, > > > > you'll find attached a patch for 95-upower-hid.rules, which adds: > > - the "usbmisc" filtering, as added in your repo, > > - more comments, including one that points at your UPower

Everything runs fine for several hours, then communication is lost and nut doesn't reestablish communication on its own. Running sudo upsdrvctl stop then sudo upsdrvctl start reestablishes communication. OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux Nut Version: 2.7.2-4 Nut Installation Method: apt Device: CyberPower PR1500LCD Uses ? ? Generic

2015-06-08 13:06 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > On Mon, 2015-06-08 at 09:45 +0200, Arnaud Quette wrote: > > > > > > 2015-06-04 13:04 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > > > On Sat, 2015-05-30 at 18:51 +0200, Arnaud Quette wrote: > > > > > > > > > > > > 2015-05-29 14:09 GMT+02:00

This was very helpful for me, thank you! On Sat, Oct 24, 2020 at 9:06 AM Charles Lepple <clepple at gmail.com> wrote: > The easiest way to tell if upsd is working is to run "upsc -l" on the same > system, which will list the NUT UPS names, and then run e.g. "upsc mge" > (replacing "mge" with the name returned by "upsc -l") > Here was the

I've tried several recipes found with google, but hal likes to grab the USB ups before nut can get it. There are a number of klugey workarounds, like turn off port power until ready to start nut (so that hal doesn't see the UPS). Or killall hal-addon-hid-ups before starting nut. Here is one of recipes I googled: https://github.com/sdgathman/trippfix/blob/master/halpolicy.fdi It

On Sun, 27 Oct 2019, EP wrote: > I can't imagine that's the way cyberpower wants their unit to work. With this > behavior the unit does exactly the opposite of what it is built for. It > doesn't protect your equipment. It will destroy it because the server which > was just shutted down cleanly will boot again on a battery-powererd ups. What > a crap. > > But I

Hi Richard and the list, you'll find attached a patch for 95-upower-hid.rules, which adds: - the "usbmisc" filtering, as added in your repo, - more comments, including one that points at your UPower repo, - 3 new manufacturers (Minibox, iDowell and Powerware) - a bunch of new devices (7 HP, 1 APC, 1 TrippLite, 2 PowerCOM and 2 Liebert) cheers, Arnaud -- Eaton Data Center

On May 29, 2015, at 8:09 AM, Bastien Nocera <hadess at hadess.net> wrote: > It would also be useful to include a full URL to the NUT Perl script > (to a git repository perhaps), so people don't need to check out the > full repo to update it. I'm not sure how useful the nut-usbinfo.pl script will be without the NUT repository: it scans the NUT source files for certain

Ha! I got several on and off list requests for details, so I'll give a bunch of details here and then maybe I can move this to a wiki page others can help edit. WARNING! WARNING! WARNING! Be careful! My implementation required opening up high power components, and dealing with 120VAC mains power and high currents on 12VDC. If you decide to tackle any of this yourself, you need to understand

Looks very great, thanks for writing this! I gather you'd port this to the Wiki page you've started, too? A couple of comments: > So I run a NUT server on a Raspberry PI which is connected via USB to my DIY-NAS Arduino. DIY-UPS? > See drivers/arduino-hid.c for the list of supported IDs... Since NUT v2.8.1 [PR #1369], the `usbhid-ups` driver allows the user to specify a

On Thursday 29 October 2020 22:12:00 Charles Lepple wrote: > On Oct 28, 2020, at 9:56 PM, Gene Heskett <gheskett at shentel.net> wrote: > > Which looks very incomplete to me. OTOH, its not a very big UPS but > > neither is the pi. I have tested that, and it shuts off long before > > it outouts a LB signal. > > Which part looks incomplete, the variables or the

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does

I was able to make NUT and my Powercom SPIDER UPS (USB port) work under the Raspberry Pi Desktop (Debian). Everything works in VMware Workstation 15 Player. But my Raspberry Pi 3b + (with raspbian) doesn’t work with the same UPS, and with same NUT configuration. Raspberry sees the UPS, but the driver does not cling. Here is the response of Raspberry 3b + to some commands. pi at raspberrypi:~

I installed the NUT under the latest Ubuntu Mate for Raspberry. The driver immediately earned with my UPS (Powercom SPD-850U). But my happiness was not long. After the first restart of Raspberry, the NUT did not start. It is treated by reconnecting the USB connector. Reconnection has to be performed after each reboot of Raspberry. The USB permissions for the "nut" group and priority

On Fri, 2015-05-29 at 14:09 +0200, Bastien Nocera wrote: > On Fri, 2015-05-29 at 13:59 +0200, Arnaud Quette wrote: > > Hi Richard and the list, > > > > you'll find attached a patch for 95-upower-hid.rules, which adds: > > - the "usbmisc" filtering, as added in your repo, > > - more comments, including one that points at your UPower repo, > > -

Hi, I'm building a DIY UPS for a Raspberry Pi using a 12V SLA battery, charger, and an off the shelf 5V regulator. To monitor the battery level I'd like to use an Arduino or similar type device. Since the Arduino can have a serial over USB connection with the Pi I'd like to implement a protocol that can be used with NUT. Does anyone know if something like this has already been done?

On 5/16/24 08:59, Jim Klimov via Nut-upsuser wrote: > I agree with earlier posters, such documentation can help future > tinkerers. There is probably more than just one to hold the hand and > walk through the ordeals :) > > Perhaps a new page at https://github.com/networkupstools/nut/wiki > <https://github.com/networkupstools/nut/wiki> can be a good location... >