UGREEN US3000-UPS sub-driver problem

[Railnolds]

Hello everyone. I got my hands on this UPS - UGREEN US3000-UPS.

On the seller's page, one of the users posted the settings for the NAT server, which allowed him to receive information from this UPS. I tried to install the server in the Proxmox environment, but I get messages that the device driver does not support this subdriver parameter. Please tell me what I'm doing wrong? Perhaps someone has encountered such a UPS and knows how to connect it to a server.

[jimklimov]

Are the instruction screenshots from that site? Did you follow them, specifically to build a modern NUT version?

The subdriver option for usbhid-ups is a recent addition, so if you are using distro packages - that code may be not there yet (packages tend to lag years behind actual projects).

[Railnolds]

Are the instruction screenshots from that site? Did you follow them, specifically to build a modern NUT version?

The subdriver option for usbhid-ups is a recent addition, so if you are using distro packages - that code may be not there yet (packages tend to lag years behind actual projects).

Thank you for your reply. No, I installed NAT with a regular command "apt install nut"and then applied the settings shown in the screenshot. But I'm not very good at Linux, so I may have missed something that's why the driver doesn't see the subdriver.
The screenshot was provided by one of the buyers. Apparently, he managed to set up the server and showed how he did it.

[Railnolds]

Did you follow them, specifically to build a modern NUT version?

You were right. Indeed, if to compile the version as shown on the screen, everything will work. Thanks for pointing in the right direction. Now everything works!!
These are the parameters that the UPS transmits. Not much, but enough for information, at least the battery charge level.

[jlcs-es]

Hi @Railnolds could you share a link to those instructions. I am happy to see this device has been added to the kanban, but I don't know how long it will take.

Thank you!

[jimklimov]

The mentioned instructions are in text screenshot of first post.

Generally see https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests

[Railnolds]

Hi @Railnolds could you share a link to those instructions. I am happy to see this device has been added to the kanban, but I don't know how long it will take.

Thank you!

Hi, Jim.
I posted the instructions in the form of screenshots in the first post, I had no other information. But I made a detailed instruction for myself, which contains step-by-step installation in Proxmox. It is in Russian, but I think if you understand Linux, you will be able to understand what needs to be done. Try it. I believe you can do it!

NUT UGREEN US3000.pdf

It is also possible that Arduino subdrivers have already been added to the latest version of NUT, so there is no need to compile the server manually, as I did. But this information has not been verified by me personally.

[Firefishy]

Anyone been able to extract the firmware update for the UGREEN US3000 from the NAS firmware updates? Any tips appreciated.

[uniquoo]

I've updated my UPS3000 firmware to version 3.3_1.2 via the original UGREEN-UI prior to formatting the system and switching to Proxmox.

After installing and configurating nut, i see no battery charge. UGREEN probably patched the ability to read the values with the latest driver?

[root@ /etc/nut]# upsc ups@localhost
Init SSL without certificate database
device.mfr: UGREEN
device.model: US3000
device.serial: DC600
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: ffff
driver.parameter.subdriver: Arduino
driver.parameter.synchronous: auto
driver.parameter.vendorid: 2b89
driver.state: quiet
driver.version: 2.8.1
driver.version.data: Arduino HID 0.2
driver.version.internal: 0.52
driver.version.usb: libusb-1.0.28 (API: 0x100010a)
ups.delay.shutdown: 20
ups.delay.start: 30
ups.mfr: UGREEN
ups.model: US3000
ups.productid: ffff
ups.serial: DC600
ups.status: OB
ups.timer.reboot: 0
ups.timer.shutdown: 0
ups.timer.start: 0
ups.vendorid: 2b89

Update: Probably because i've used the distributor packaged nut version of Debian Trixie which is

[root@]# apt-cache show nut
Package: nut
Version: 2.8.1-5

I'll revalidate with a newer version. Sorry for not checking prior...

[jimklimov]

@uniquoo : yes, the version seems to make a difference - battery.* were added to drivers/arduino-hid.c after v2.8.1 release.

For a custom build, see e.g. https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests