>> 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 output)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 the requested log. -------------- next part -------------- A non-text attachment was scrubbed... Name: usbhid-ups-openups2.log.gz Type: application/gzip Size: 2980 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20170722/23c4178e/attachment.bin>
On Jul 22, 2017, at 9:40 AM, Alphonse <alphsteiner at gmail.com> 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 the requested log.Right, I forgot to mention that the explore mode is not meant to send data to upsd - it just generates debug output. There are a few extra variables that might be read/write, but I don't see the usual ones that translate into commands (such as UPS.BatterySystem.Battery.Test or UPS.PowerSummary.DelayBeforeShutdown). Thanks for sending the upsc output.
> 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 (such as UPS.BatterySystem.Battery.Test or UPS.PowerSummary.DelayBeforeShutdown). > > Thanks for sending the upsc output.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!