Re: [Nut-upsdev] Openups patch proposal (KDE, etc.)

2017-07-23 Thread Alphonse
To be honest, most of the NUT development effort is focused on shutting down servers, so there isn't a whole lot of work on the desktop side. Having not used KDE in many years, I hadn't heard of Solid. For anyone else casually interested, this seems to be a good introduction:

Re: [Nut-upsdev] Openups patch proposal

2017-07-23 Thread Charles Lepple
On Jul 22, 2017, at 9:13 AM, Alphonse wrote: > > Note that there is still a 'libusb_get_string: Invalid argument' message into > the log, but only when starting or resuming the system. I should mention that this is now in the master branch as commit e6d77c87d0b0 I added

Re: [Nut-upsdev] Openups patch proposal (KDE, etc.)

2017-07-23 Thread Charles Lepple
On Jul 23, 2017, at 4:50 AM, Alphonse wrote: > > Another point is bugging me: the ups is not repported as a battery in kde nor > in the output of 'solid-hardware list'. > Do you have an idea for this problem? > Thanks! > To be honest, most of the NUT development effort

Re: [Nut-upsdev] Openups patch proposal

2017-07-23 Thread Alphonse
Right, I forgot to mention that the explore mode is not meant to send data to upsd - it just generates debug output. And it is written in the man page... that I do had read! There are a few extra variables that might be read/write, but I don't see the usual ones that translate into commands

Re: [Nut-upsdev] Openups patch proposal

2017-07-22 Thread Charles Lepple
On Jul 22, 2017, at 9:40 AM, Alphonse wrote: > > This is weird (for me): I have added the 'explore' option into the ups > configuration, and restarted the driver, but now it tells that the device is > offline! It is back to normal without this option. > I have attached

Re: [Nut-upsdev] Openups patch proposal

2017-07-22 Thread Alphonse
I don't think that the firmware supported commands when this sub-driver was written. It is certainly something we can check for, using the "explore" mode mentioned in the driver man page: http://networkupstools.org/docs/man/usbhid-ups.html (please stop after 30-60 seconds, and gzip the

Re: [Nut-upsdev] Openups patch proposal

2017-07-22 Thread Alphonse
Charles Lepple a écrit : Thanks for the patch. For reference, what does the rest of the "upsc" output look like for this device? Here it is: $ upsc openups2 Init SSL without certificate database battery.capacity: 100 battery.charge: 100 battery.charge.low: 5 battery.charge.warning: 20

Re: [Nut-upsdev] Openups patch proposal

2017-07-22 Thread Charles Lepple
On Jul 21, 2017, at 3:21 PM, Alphonse wrote: > > Hello, > I have an openups2 ups. It works very well with nut, except two things: > 1) It keeps sending a 'libusb_get_string: invalid argument' message to the > log; > 2) It does not report any command. > > Following >