PowerWalker VI 650 SH driver support

[schinivision]

Hi. I just wanted to state that the PowerWalker VI 650 SH is not supported by the blazer_usb driver like other PowerWalker Produkts. It works with the usbhid-ups driver.

Tried it out to find the correct driver with a Raspberry PI 3.. Works fine (limited output though but the values like load, state etc. is correct).

Regarding FreeNas 11 it should work with any product that is supported by the usbhid-ups driver.
(still limited information but the crucial information is there)

Output provided from FreeNas 11.0-U3

battery.charge: 100
battery.runtime: 2418
battery.type: PbAc
battery.voltage: 14
device.mfr: PPC
device.model: Offline UPS
device.serial: 000000000
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.internal: 0.41
ups.load: 16
ups.mfr: PPC
ups.model: Offline UPS
ups.productid: ffff
ups.serial: 000000000
ups.status: OL CHRG
ups.vendorid: 06da

Do not know if this should be considered as a issue, Maybe it could be used to update the compatibility list.

Best Regards
Stefan

[clepple]

Thanks! We haven't updated the main website in a while, but we do have an entry for this UPS queued here: http://new.networkupstools.org/ddl/PowerWalker/VI_650_SH.html

If you have problems with stale data, please see the discussion at issue #475.

Is driver.version.data missing from the FreeNAS display? (Odd, but not terribly important.)

[schinivision]

Sorry seems to have been a copy and paste error.

Here is the output from FreeNas 11.0-U3

battery.charge: 100
battery.runtime: 2418
battery.type: PbAc
battery.voltage: 14
device.mfr: PPC
device.model: Offline UPS
device.serial: 000000000
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: Phoenixtec/Liebert HID 0.3
driver.version.internal: 0.41
ups.load: 16
ups.mfr: PPC
ups.model: Offline UPS
ups.productid: ffff
ups.serial: 000000000
ups.status: OL CHRG
ups.vendorid: 06da

Here is the output from FreeNas 11.0-U4

battery.charge: 100
battery.runtime: 2615
battery.type: PbAc
battery.voltage: 14
device.mfr: PPC
device.model: Offline UPS
device.serial: 000000000
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: Phoenixtec/Liebert HID 0.3
driver.version.internal: 0.41
ups.load: 16
ups.mfr: PPC
ups.model: Offline UPS
ups.productid: ffff
ups.serial: 000000000
ups.status: OL CHRG
ups.vendorid: 06da

And here for completeness the output from the PI running Armbian

battery.charge: 100
battery.runtime: 2418
battery.type: PbAc
battery.voltage: 14
device.mfr: PPC
device.model: Offline UPS
device.serial: 000000000
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.7.2
driver.version.data: Liebert HID 0.3
driver.version.internal: 0.38
ups.load: 16
ups.mfr: PPC
ups.model: Offline UPS
ups.productid: ffff
ups.serial: 000000000
ups.status: OL CHRG
ups.vendorid: 06da

All show driver.version.data

Interestingly I didn't found the page for the VI 650 with google 😞 But good to know it is there.
I haven't had time to test the shutdown sequence and the mail reporting till now but I will try to update so it can be added to the page.

BR
Stefan

[schinivision]

(Addition)
UPS Notification works on FreeNas 11.0-U4 so I assume that the shutdown sequence should also work. If the service can detect a change, the service will probably shut down the machine also.

[clepple]

We should probably clarify the information request on the compatibility webpage, but I think the part we're less sure about is whether the system can tell the UPS to power off after shutdown. (Usually the UPS-to-PC notification is pretty solid.)

To that end, what commands are listed if you run upscmd -l? I can't remember if this is built into the FreeNAS GUI, but you could run that command from the Pi and give it the address of the FreeNAS box. I am most interested in the one running NUT 2.7.4, but if the older versions are different, I guess that would be useful to know.

Because new.networkupstools.org redirects to the Buildbot server, and apparently parsing robots.txt after redirects is still a hard problem, we had to restrict web crawlers from indexing that box. (They would try to download every single build log file, which is not terribly useful given how similar they are.) After the next release, I will look at setting up another hostname for the work-in-progress documentation so that it can be picked up by search engines again.

[schinivision]

Hi. Regarding your request for upscmd. I tried to run it in the FreeNas Console and I get a empty list. Also if I try to run this command from any client (PI) the upscmd -l returns an empty list.

FreeNas output:
[xxx@xxx]$ upscmd -l powerwalker
Instant commands supported on UPS [powerwalker]:

PI output
xxx@xxx:~# upscmd -l powerwalker@x.x.x.x
Instant commands supported on UPS [powerwalker]:

So I assume that either the standard config on FreeNas does not support sending commands to the UPS or it does not work.
Any suggestions where I should dig in to on FreeNas to change / look it up? The UI is not very verbose on that and the config files are located somewhere else.. I have to do some research where FreeNas puts them because they are not in /etc/nut/....

[clepple]

Hi. Regarding your request for upscmd. I tried to run it in the FreeNas Console and I get a empty list. Also if I try to run this command from any client (PI) the upscmd -l returns an empty list.

Sounds like the driver does not support any commands with that hardware. It is possible to check for other commands that NUT has not implemented, but that might be tough with FreeNAS.

I have to do some research where FreeNas puts them because they are not in /etc/nut/....

/usr/local/etc/nut ? (that is where they end up in FreeBSD with the default ports tree configuration)

[leshik]

@clepple I have a similar UPS labeled "Syndome Atom LCD-1000". It has the same vid/pid and works only with usbhid-ups. The upscmd -l returns an empty list as in @schinivision case. I'm not on FreeNAS but on full-featured Ubuntu server. What can I do to check for other commands that NUT has not implemented? The important thing to me is to turn off UPS power after the server shutdown so that it could start when the power goes on again.

[clepple]

@leshik please post the output of /lib/nut/usbhid-ups -DD -u root -x explore -x vendorid=XXXX -a UPS (replacing UPS with the name from /etc/nut/ups.conf) as an attachment.

[leshik]

@clepple Here it is:

Network UPS Tools - Generic HID driver 0.38 (2.7.2)
USB communication driver 0.32
   0.000000	debug level is '2'
   0.000761	upsdrv_initups...
   0.015238	Checking device (1D6B/0003) (002/001)
   0.030973	- VendorID: 1d6b
   0.031003	- ProductID: 0003
   0.031011	- Manufacturer: Linux 4.13.0-37-generic xhci-hcd
   0.031019	- Product: xHCI Host Controller
   0.031027	- Serial Number: 0000:00:14.0
   0.031035	- Bus: 002
   0.031045	Trying to match device
   0.031066	Device does not match - skipping
   0.031295	Checking device (06DA/FFFF) (001/004)
   0.036529	- VendorID: 06da
   0.036560	- ProductID: ffff
   0.036569	- Manufacturer: PPC
   0.036577	- Product: Offline UPS
   0.036585	- Serial Number: 000000000
   0.036595	- Bus: 001
   0.036603	Trying to match device
   0.036663	Device matches
   0.038150	HID descriptor length 495
   0.056310	Report Descriptor size = 495
   0.056570	Using subdriver: EXPLORE HID 0.1
   0.057170	Path: UPS.BatterySystem.Battery.Test, Type: Feature, ReportID: 0x24, Offset: 0, Size: 8, Value: 6
   0.057786	Path: UPS.Flow.[4].ConfigApparentPower, Type: Feature, ReportID: 0x74, Offset: 0, Size: 16, Value: 5
   0.058399	Path: UPS.Flow.[4].ConfigFrequency, Type: Feature, ReportID: 0x36, Offset: 0, Size: 8, Value: 50
   0.059014	Path: UPS.Flow.[4].ConfigVoltage, Type: Feature, ReportID: 0x72, Offset: 0, Size: 8, Value: 220
   0.059631	Path: UPS.PowerConverter.ffff0041, Type: Feature, ReportID: 0x4a, Offset: 0, Size: 8, Value: 1
   0.060326	Path: UPS.PowerConverter.Input.[1].Voltage, Type: Feature, ReportID: 0x31, Offset: 0, Size: 16, Value: 229
   0.060889	Path: UPS.PowerConverter.Input.[1].PresentStatus.Boost, Type: Feature, ReportID: 0x2d, Offset: 0, Size: 8, Value: 0
   0.060921	Path: UPS.PowerConverter.Input.[1].PresentStatus.Boost, Type: Input, ReportID: 0x2d, Offset: 0, Size: 8, Value: 0
   0.060938	Path: UPS.PowerConverter.Input.[1].PresentStatus.Buck, Type: Feature, ReportID: 0x2d, Offset: 8, Size: 8, Value: 0
   0.060956	Path: UPS.PowerConverter.Input.[1].PresentStatus.Buck, Type: Input, ReportID: 0x2d, Offset: 8, Size: 8, Value: 0
   0.061589	Path: UPS.PowerConverter.Output.Frequency, Type: Feature, ReportID: 0x42, Offset: 0, Size: 16, Value: 49.8
   0.061622	Path: UPS.PowerConverter.Output.Voltage, Type: Feature, ReportID: 0x42, Offset: 16, Size: 16, Value: 228
   0.062155	Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 2
   0.062718	Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x09, Offset: 0, Size: 32, Value: 0
   0.063364	Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 32, Value: 0
   0.063928	Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x10, Offset: 0, Size: 8, Value: 5
   0.063959	Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x10, Offset: 8, Size: 8, Value: 1
   0.063975	Path: UPS.PowerSummary.ffff00f0, Type: Feature, ReportID: 0x10, Offset: 16, Size: 8, Value: 3
   0.063992	Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x10, Offset: 24, Size: 8, Value: 2
   0.064009	Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x10, Offset: 32, Size: 8, Value: 4
   0.064575	Path: UPS.PowerSummary.ffff00e2, Type: Feature, ReportID: 0xe2, Offset: 0, Size: 8, Value: 4
   0.065127	Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 1
   0.065695	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1
   0.065726	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x01, Offset: 0, Size: 8, Value: 1
   0.065743	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x01, Offset: 8, Size: 8, Value: 0
   0.065761	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x01, Offset: 8, Size: 8, Value: 0
   0.065781	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x01, Offset: 16, Size: 8, Value: 1
   0.065799	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x01, Offset: 16, Size: 8, Value: 1
   0.065820	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x01, Offset: 24, Size: 8, Value: 0
   0.065837	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x01, Offset: 24, Size: 8, Value: 0
   0.065856	Path: UPS.PowerSummary.PresentStatus.Good, Type: Feature, ReportID: 0x01, Offset: 32, Size: 8, Value: 1
   0.065875	Path: UPS.PowerSummary.PresentStatus.Good, Type: Input, ReportID: 0x01, Offset: 32, Size: 8, Value: 1
   0.065895	Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Feature, ReportID: 0x01, Offset: 40, Size: 8, Value: 0
   0.065913	Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Input, ReportID: 0x01, Offset: 40, Size: 8, Value: 0
   0.065934	Path: UPS.PowerSummary.PresentStatus.Overload, Type: Feature, ReportID: 0x01, Offset: 48, Size: 8, Value: 0
   0.065954	Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input, ReportID: 0x01, Offset: 48, Size: 8, Value: 0
   0.066575	Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 8, Value: 100
   0.066637	Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, ReportID: 0x0b, Offset: 8, Size: 8, Value: 1
   0.066661	Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID: 0x0b, Offset: 16, Size: 8, Value: 100
   0.066682	Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x0b, Offset: 24, Size: 8, Value: 2
   0.067336	Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 100
   0.067369	Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x06, Offset: 0, Size: 8, Value: 100
   0.067386	Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x06, Offset: 8, Size: 16, Value: 6954
   0.067405	Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x06, Offset: 8, Size: 16, Value: 6954
   0.067427	Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x07, Offset: 8, Size: 16, Value: 27.7
   0.067474	Report descriptor retrieved (Reportlen = 495)
   0.067491	Found HID device
   0.067505	Detected a UPS: PPC/Offline UPS
   0.067520	find_nut_info: unknown info type: load.off.delay
   0.067533	find_nut_info: unknown info type: load.on.delay
   0.067545	find_nut_info: unknown info type: load.off.delay
   0.067566	upsdrv_initinfo...
   0.067583	upsdrv_updateinfo...
   0.318716	libusb_get_interrupt: Connection timed out
   0.318747	Got 0 HID objects...
   0.318758	Quick update...
   0.318858	dstate_init: sock /var/run/nut/usbhid-ups-ups open on fd 5
   0.318883	upsdrv_updateinfo...
   0.569212	libusb_get_interrupt: Connection timed out
   0.569247	Got 0 HID objects...
   0.569259	Quick update...
   2.320715	upsdrv_updateinfo...
   2.571099	libusb_get_interrupt: Connection timed out
   2.571132	Got 0 HID objects...
   2.571142	Quick update...
   4.322526	upsdrv_updateinfo...
   4.573818	libusb_get_interrupt: Connection timed out

Then the last 4 lines are repeated continuously.

[clepple]

@leshik you should try NUT v2.7.3 or later.

[leshik]

@clepple Ok, here it is – but it doesn't change much:

Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
   0.000000	debug level is '2'
   0.000769	upsdrv_initups...
   0.014808	Checking device (1D6B/0003) (002/001)
   0.030479	- VendorID: 1d6b
   0.030510	- ProductID: 0003
   0.030518	- Manufacturer: Linux 4.13.0-37-generic xhci-hcd
   0.030526	- Product: xHCI Host Controller
   0.030534	- Serial Number: 0000:00:14.0
   0.030541	- Bus: 002
   0.030552	- Device release number: 0413
   0.030578	Trying to match device
   0.030599	Device does not match - skipping
   0.030821	Checking device (06DA/FFFF) (001/004)
   0.036345	- VendorID: 06da
   0.036380	- ProductID: ffff
   0.036388	- Manufacturer: PPC
   0.036396	- Product: Offline UPS
   0.036404	- Serial Number: 000000000
   0.036411	- Bus: 001
   0.036422	- Device release number: 0003
   0.036436	Trying to match device
   0.036492	Device matches
   0.037317	HID descriptor length 495
   0.055508	Report Descriptor size = 495
   0.055802	Using subdriver: EXPLORE HID 0.1
   0.055817	45 HID objects found
   0.056458	Path: UPS.BatterySystem.Battery.Test, Type: Feature, ReportID: 0x24, Offset: 0, Size: 8, Value: 6
   0.057220	Path: UPS.Flow.[4].ConfigApparentPower, Type: Feature, ReportID: 0x74, Offset: 0, Size: 16, Value: 5
   0.057823	Path: UPS.Flow.[4].ConfigFrequency, Type: Feature, ReportID: 0x36, Offset: 0, Size: 8, Value: 50
   0.058406	Path: UPS.Flow.[4].ConfigVoltage, Type: Feature, ReportID: 0x72, Offset: 0, Size: 8, Value: 220
   0.059135	Path: UPS.PowerConverter.ffff0041, Type: Feature, ReportID: 0x4a, Offset: 0, Size: 8, Value: 1
   0.059805	Path: UPS.PowerConverter.Input.[1].Voltage, Type: Feature, ReportID: 0x31, Offset: 0, Size: 16, Value: 235
   0.060419	Path: UPS.PowerConverter.Input.[1].PresentStatus.Boost, Type: Feature, ReportID: 0x2d, Offset: 0, Size: 8, Value: 0
   0.060453	Path: UPS.PowerConverter.Input.[1].PresentStatus.Boost, Type: Input, ReportID: 0x2d, Offset: 0, Size: 8, Value: 0
   0.060469	Path: UPS.PowerConverter.Input.[1].PresentStatus.Buck, Type: Feature, ReportID: 0x2d, Offset: 8, Size: 8, Value: 0
   0.060487	Path: UPS.PowerConverter.Input.[1].PresentStatus.Buck, Type: Input, ReportID: 0x2d, Offset: 8, Size: 8, Value: 0
   0.061175	Path: UPS.PowerConverter.Output.Frequency, Type: Feature, ReportID: 0x42, Offset: 0, Size: 16, Value: 49.8
   0.061210	Path: UPS.PowerConverter.Output.Voltage, Type: Feature, ReportID: 0x42, Offset: 16, Size: 16, Value: 235
   0.061787	Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 2
   0.062411	Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x09, Offset: 0, Size: 32, Value: 0
   0.063086	Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 32, Value: 0
   0.063708	Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x10, Offset: 0, Size: 8, Value: 5
   0.063739	Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x10, Offset: 8, Size: 8, Value: 1
   0.063754	Path: UPS.PowerSummary.ffff00f0, Type: Feature, ReportID: 0x10, Offset: 16, Size: 8, Value: 3
   0.063772	Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x10, Offset: 24, Size: 8, Value: 2
   0.063789	Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x10, Offset: 32, Size: 8, Value: 4
   0.064340	Path: UPS.PowerSummary.ffff00e2, Type: Feature, ReportID: 0xe2, Offset: 0, Size: 8, Value: 4
   0.064893	Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 1
   0.065461	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1
   0.065492	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x01, Offset: 0, Size: 8, Value: 1
   0.065509	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x01, Offset: 8, Size: 8, Value: 0
   0.065529	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x01, Offset: 8, Size: 8, Value: 0
   0.065550	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x01, Offset: 16, Size: 8, Value: 1
   0.065568	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x01, Offset: 16, Size: 8, Value: 1
   0.065589	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x01, Offset: 24, Size: 8, Value: 0
   0.065606	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x01, Offset: 24, Size: 8, Value: 0
   0.065623	Path: UPS.PowerSummary.PresentStatus.Good, Type: Feature, ReportID: 0x01, Offset: 32, Size: 8, Value: 1
   0.065641	Path: UPS.PowerSummary.PresentStatus.Good, Type: Input, ReportID: 0x01, Offset: 32, Size: 8, Value: 1
   0.065661	Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Feature, ReportID: 0x01, Offset: 40, Size: 8, Value: 0
   0.065678	Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Input, ReportID: 0x01, Offset: 40, Size: 8, Value: 0
   0.065701	Path: UPS.PowerSummary.PresentStatus.Overload, Type: Feature, ReportID: 0x01, Offset: 48, Size: 8, Value: 0
   0.065719	Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input, ReportID: 0x01, Offset: 48, Size: 8, Value: 0
   0.066363	Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 8, Value: 100
   0.066394	Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, ReportID: 0x0b, Offset: 8, Size: 8, Value: 1
   0.066410	Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID: 0x0b, Offset: 16, Size: 8, Value: 100
   0.066424	Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x0b, Offset: 24, Size: 8, Value: 2
   0.067120	Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 100
   0.067152	Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x06, Offset: 0, Size: 8, Value: 100
   0.067173	Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x06, Offset: 8, Size: 16, Value: 6954
   0.067189	Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x06, Offset: 8, Size: 16, Value: 6954
   0.067210	Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x07, Offset: 8, Size: 16, Value: 27.1
   0.067243	Report descriptor retrieved (Reportlen = 495)
   0.067255	Found HID device
   0.067267	Detected a UPS: PPC/Offline UPS
   0.067282	find_nut_info: unknown info type: load.off.delay
   0.067297	find_nut_info: unknown info type: load.on.delay
   0.067309	find_nut_info: unknown info type: load.off.delay
   0.067331	upsdrv_initinfo...
   0.067348	upsdrv_updateinfo...
   0.317606	libusb_get_interrupt: Connection timed out
   0.317638	Got 0 HID objects...
   0.317649	Quick update...
   0.317745	dstate_init: sock /var/run/nut/usbhid-ups-ups open on fd 5
   0.317772	upsdrv_updateinfo...
   0.568432	libusb_get_interrupt: Connection timed out
   0.568473	Got 0 HID objects...
   0.568501	Quick update...
   2.319605	upsdrv_updateinfo...
   2.569866	libusb_get_interrupt: Connection timed out
   2.569901	Got 0 HID objects...
   2.569913	Quick update...
   4.321395	upsdrv_updateinfo...
   4.572149	libusb_get_interrupt: Connection timed out
   4.572180	Got 0 HID objects...
   4.572191	Quick update...

[clepple]

Ok, here it is – but it doesn't change much:

sorry, I meant to try "upscmd -l" with a newer version of NUT. There have been some fixes for that USB ID.

[leshik]

@clepple I tried, but no – the list is still empty.