search for: laurenttaieb

...sudo ./usbhid-ups -a myups3 -DDD>& tracefile Please apologies for the extra length of the traces as most of them are probably irrelevant (I had to cut the main file into multiple chunks): I have zipped the trace as requested. Thanks Laurent De : Nut-upsuser <nut-upsuser-bounces+laurenttaieb=free.fr at alioth-lists.debian.net <mailto:nut-upsuser-bounces+laurenttaieb=free.fr at alioth-lists.debian.net> > au nom de Laurent Taieb via Nut-upsuser <nut-upsuser at alioth-lists.debian.net <mailto:nut-upsuser at alioth-lists.debian.net> > R?pondre ? : "laurenttaieb at...

...services) before starting this one? Does udev, ugen or similar facility have the configuration to hand off this device to NUT run-time user? (BTW, if you are now testing a custom build - was it configured to use same accounts as pre-packaged variant)? On Fri, Mar 24, 2023, 18:46 Laurent Taieb <laurenttaieb at free.fr> wrote: > Hi Jim, > > I have 2 drivers which have launched well connecting 2 APC UPS (both with > usbhid-ups) > > They have both bus & serial set. > > The Eaton is the third one. I have removed serial and bus from the > configuration. > > > &gt...

...ng this one? Does udev, ugen or similar facility have the > configuration to hand off this device to NUT run-time user? (BTW, if you > are now testing a custom build - was it configured to use same accounts as > pre-packaged variant)? > > On Fri, Mar 24, 2023, 18:46 Laurent Taieb <laurenttaieb at free.fr> wrote: > >> Hi Jim, >> >> I have 2 drivers which have launched well connecting 2 APC UPS (both with >> usbhid-ups) >> >> They have both bus & serial set. >> >> The Eaton is the third one. I have removed serial and bus from the &g...

...sion and finally found the issue which was a hidden character staying in the ups.conf file. I rebuilt the file and everything worked out. Issue closed and many thanks for your help. Laurent From: Jim Klimov <jimklimov+nut at gmail.com> Sent: mercredi 29 mars 2023 13:22 To: laurenttaieb at free.fr Cc: nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org> Subject: Re: [Nut-upsuser] Question on EATON UPS Which OS is that? With Linux+systemd, I'd expect systemd to start the drivers (hence blocking the port) and keep logs in the systemd journal (if your packa...

...1 > > 1.041605 [D2] HID descriptor length 481 > > 1.041926 [D2] Unable to get Report descriptor: Resource > temporarily unavailable > > > > Any idea ? > > > > Thanks > > Laurent > > > > *De : *Nut-upsuser <nut-upsuser-bounces+laurenttaieb= > free.fr at alioth-lists.debian.net> au nom de Larry Fahnoe via Nut-upsuser < > nut-upsuser at alioth-lists.debian.net> > *R?pondre ? : *Larry Fahnoe <fahnoe at fahnoetech.com> > *Date : *jeudi 9 mars 2023 ? 18:59 > *? : *nut-upsuser Mailing List <nut-upsuser at l...

...21 10 01 21 01 22 e1 01 1.041566 [D3] HID descriptor length (method 2) 481 1.041605 [D2] HID descriptor length 481 1.041926 [D2] Unable to get Report descriptor: Resource temporarily unavailable Any idea ? Thanks Laurent De : Nut-upsuser <nut-upsuser-bounces+laurenttaieb=free.fr at alioth-lists.debian.net> au nom de Larry Fahnoe via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> R?pondre ? : Larry Fahnoe <fahnoe at fahnoetech.com> Date : jeudi 9 mars 2023 ? 18:59 ? : nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org> Objet...

Is that with both UPSes on same machine? A quick guess would be that insufficient data points to identify the device are configured (vendorid, productid, serial...) in ups.conf, so both drivers connect to the first match. I'd expect them to conflict and one would die or both loop reconnecting, if both are running at once, though. Also, which NUT version? Custom build from GitHub or an

On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: >> The UPS has been defined in ups.conf as: >> >> [myups3] >> >> driver : usbhid-ups >> >> port = auto >> >> vendorid = 0463 >> >> productid = ffff >> >> desc = "5S" >> >> bus

Which OS is that? With Linux+systemd, I'd expect systemd to start the drivers (hence blocking the port) and keep logs in the systemd journal (if your packaging includes nut-driver-enumerator, you may see them with `journalctl -lu nut-driver at myups3`; for older systems just `journalctl -lu nut-driver`), and on others init-scripts added by packaging should do the same to start drivers when

Hi mailing list, I looked at all FAQ and docs and can?t find a solution. I installed but on both Kali Linux and Ubuntu. (For comparison purposes) I?m trying to connect and monitor two UPS APC via usb. One is a back-ups bx1400 which I can see via via upsc. The second one is a more recent one smc 1500ic which when I poke it via upsc returns the data of the bx1400 one. I tried by changing port and

Hi NUT Users, One of my APC UPS is having battery issue and apparently we cannot change battery in that UPS. (not super green?) I have purchased an EATON UPS and added the ref in ups.conf When restarting the driver, I got this error > 0.030612 [D2] Checking device 2 of 10 (0463/FFFF) > 0.287659 [D2] - VendorID: 0463 > 0.287853 [D2] - ProductID: ffff >