2 Smart UPS W150 WalleCube. Incorrect data

[Keks1975]

Good evening! I can provide the data using the command "usbhid-ups -s test -x port=auto -DDDDDD -d1"I am confused by the incorrect data:
ups.status: ALARM OL
ups.alarm: No battery installed!
battery.mfr.date: OPEN
battery.charge.warning: 5
battery.temperature: 4.09

underlined with a yellow marker in the screenshot

w150.txt

[jimklimov]

Thanks for the debug log. Looking at it, you are using an older NUT v2.8.1 release; the OpenUPS subdriver did not significantly change since then, but other parts of the ecosystem did (not sure quickly if any of that could directly impact the issue though... maybe the LogMin/LogMax fixes?)

In particular, newer (master-branch, not "released" so far) code includes log comparison of how the report descriptor mismatches the mapping table, to help troubleshoot what is missing. If you can experiment with https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests - it might be interesting.

Otherwise, at 285 bytes / 33 entries the HID report of the device is rather small.

battery presence

Seems to be some mis-parsing indeed - the status says "1" which I assume means "yes" (is present):

2.265869	[D2] Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x02, Offset: 171, Size: 1, Value: 1
2.265873	[D5] process_boolean_info: nobattery

Many other values are reported inverted (e.g. !overload) so maybe some inversion got lost here?

• UPDATE: looking at code, seems so.

battery date

0.012458	[D5] hid_lookup_usage: UPS -> 00840004
0.012460	[D5] hid_lookup_usage: PowerSummary -> 00840024
0.012463	[D5] hid_lookup_usage: iOEMInformation -> 0085008f
0.012465	[D4] string_to_path: depth = 3
0.012468	[D3] Report[buf]: (8 bytes) => 01 11 01 02 03 08 09 02
0.012470	[D5] PhyMax = 0, PhyMin = 0, LogMax = 15, LogMin = 0
0.012472	[D5] Unit = 00000000, UnitExp = 0
0.012474	[D5] Exponent = 0
0.012477	[D2] Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID: 0x01, Offset: 40, Size: 8, Value: 9
0.012857	[D5] send_to_all: SETINFO battery.mfr.date "OPEN"

"OPEN" as a date also looks wrong, I suppose this field UPS.PowerSummary.iOEMInformation generally means "some info about/from the device OEM (original equipment manufacturer)", not necessarily related to battery at all. Looking at other subdrivers however, it is usually either not mapped or battery date:

:; git grep iOEMInformation
drivers/arduino-hid.c:  /*{ "battery.mfr.date", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%s", HU_FLAG_STATIC, stringid_conversion},*/
drivers/belkin-hid.c:  { "unmapped.ups.powersummary.ioeminformation", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%s", 0, stringid_conversion },
drivers/cps-hid.c:  { "battery.mfr.date", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%s", 0, stringid_conversion },
drivers/ecoflow-hid.c:  { "experimental.ups.powersummary.ioeminformation", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%s", HU_FLAG_STATIC, stringid_conversion },
drivers/ecoflow-hid.c:  { "unmapped.ups.powersummary.ioeminformation", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%.0f", 0, NULL },
drivers/libhid.c:       { "iOEMInformation",                    0x0085008f },
drivers/openups-hid.c:  {"battery.mfr.date", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%s", HU_FLAG_STATIC, stringid_conversion},
drivers/powercom-hid.c: { "unmapped.ups.powersummary.ioeminformation", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%s", HU_FLAG_STATIC, stringid_conversion },
drivers/tripplite-hid.c:        { "UPS.PowerSummary.iOEMInformation", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%s", HU_FLAG_STATIC, stringid_conversion },

My guess is that on the first device covered by a subdriver that had something reported here, the OEM placed a date into the field, and then it was copy-pasted around.

Technically, NUT defines the *.date data points as "opaque strings" - so there is no expectation of particular structure or format there. In this regard "OPEN" is not wrong, although of course it is meaningless as a date. Probably comes from its "openUPS" firmware roots?

temperature

FWIW the raw data are here:

0.013066	[D5] hid_lookup_usage: UPS -> 00840004
0.013068	[D5] hid_lookup_usage: PowerSummary -> 00840024
0.013070	[D5] hid_lookup_usage: Temperature -> 00840036
0.013072	[D4] string_to_path: depth = 3
0.013075	[D3] Report[buf]: (23 bytes) => 02 41 35 f5 ff 64 64 0a 05 d4 2f 3a 01 98 2f c6
0.013078	[D3]  05 3b 30 25 04 01 0c
0.013080	[D5] PhyMax = 0, PhyMin = 0, LogMax = 65534, LogMin = 0
0.013082	[D5] Unit = 00010001, UnitExp = -2
0.013084	[D5] Exponent = -2
0.013086	[D2] Path: UPS.PowerSummary.Temperature, Type: Feature, ReportID: 0x02, Offset: 80, Size: 16, Value: 3.14
0.013090	[D5] send_to_all: SETINFO battery.temperature "4.43"

2.265601	[D3] Report[buf]: (23 bytes) => 02 41 35 f0 ff 64 64 0a 05 d4 2f 3a 01 bd 2f 25
2.265603	[D3]  04 45 30 52 04 01 0c
2.265605	[D5] PhyMax = 0, PhyMin = 0, LogMax = 65534, LogMin = 0
2.265607	[D5] Unit = 00010001, UnitExp = -2
2.265609	[D5] Exponent = -2
2.265612	[D2] Path: UPS.PowerSummary.Temperature, Type: Feature, ReportID: 0x02, Offset: 80, Size: 16, Value: 3.14

Not quickly sure what is wrong here. The code which converts from raw "3.14" value to ultimate "4.43" can be seen at https://github.com/networkupstools/nut/blob/v2.8.1/drivers/openups-hid.c#L238-L273

Feel free to walk through that code, today I don't have time to drill into it.

All in all, seems like this subdriver worked with some firmware for whoever wrote this, but this firmware is implemented "creatively" with devices seen in the field, so more work is needed (PRs welcome!) to make it work for different devices or openUPS firmware generations.

[Keks1975]

I'm not dragging in the code, I don't understand. NUT v2.8.1 is on Proxmox 9.1.14.
It is possible to install a new OpenUPS subdriver with my version of NUT v2.8.1?

[Keks1975]

Обратите внимание га сриншоте два 4,1°C, а на скриншоте 3 температура 30,9 °C в родном мобильном приложении.

[jimklimov]

How does the native mobile app connect to the UPS? Does it also serve SNMP? Is it phoning back home to vendor portal?

Otherwise (theorizing here), the "3.14" seen in USB raw data may well mean "31.4 *C" with a wrong (10x) factor then, maybe partially due to them reporting a wrong exponent?..

[Keks1975]

UPS подключается к WiFi через мобильное приложение и показывает данные о состоянии. возможно неправильно работает множитель.

[Keks1975]

One more question. when I launch it

root@prox:~# sudo upsdrvctl start
Network UPS Tools - UPS driver controller 2.8.1
Network UPS Tools - Generic HID driver 0.52 (2.8.1)
USB communication driver (libusb 1.0) 0.46
Duplicate driver instance detected (PID file /run/nut/usbhid-ups-w150.pid exists)! Terminating other driver!
Using subdriver: openUPS HID 0.5

Broadcast message from root@prox (somewhere) (Sun Jan 11 14:09:46 2026):

Communications with UPS w150@localhost established

Broadcast message from root@prox (somewhere) (Sun Jan 11 14:09:54 2026):

Communications with UPS w150@localhost lost

Broadcast message from root@prox (somewhere) (Sun Jan 11 14:10:02 2026):

Communications with UPS w150@localhost established

root@prox:~# upsc w150@localhost
Init SSL without certificate database
battery.capacity: 100
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 5
battery.current: 32.745
battery.mfr.date: OPEN
battery.runtime: 12891
battery.temperature: 3.86
battery.type: LiFePO4
battery.voltage: 13.61
device.mfr: WalleCube
device.model: Smart UPS W150
device.serial: E4B32374A1E4
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 15
driver.parameter.port: auto
driver.parameter.product: Smart UPS W150
driver.parameter.productid: D005
driver.parameter.serial: E4B32374A1E4
driver.parameter.synchronous: auto
driver.parameter.vendor: WalleCube
driver.parameter.vendorid: 04D8
driver.state: quiet
driver.version: 2.8.1
driver.version.data: openUPS HID 0.5
driver.version.internal: 0.52
driver.version.usb: libusb-1.0.28 (API: 0x100010a)
input.current: 1.049
input.voltage: 12.58
output.current: 1.141
output.voltage: 12.46
ups.mfr: WalleCube
ups.model: Smart UPS W150
ups.productid: d005
ups.serial: E4B32374A1E4
ups.status: OL
ups.vendorid: 04d8

When starting
at zero, the status is ups.status: OL

after a while, ups appears.status: ALARM OL