[Nut-upsdev] [HCL] Armac Office 1000E USB compatibility issue (VID:0925 PID:1234, richcomm_usb, nutdrv_qx)
Andries
wijk1718 at protonmail.com
Tue Aug 26 17:46:49 BST 2025
I am writing to report a compatibility issue with my Armac Office 1000E UPS (USB ID 0925:1234) under TrueNAS using the latest NUT 2.8.0 package and to request support or advice for its integration with Network UPS Tools.
Device Details:
Model: Armac Office 1000E
Manufacturer: Armac
USB Vendor ID: 0925
USB Product ID: 1234
Detected in lsusb as: Lakeview Research UPS USB Mon V2.0
Platform and Software:
NAS: TrueNAS Scale (latest, August 2025)
NUT version: 2.8.0, driver path: /usr/local/libexec/nut/
Tried drivers: richcomm_usb, nutdrv_qx (with various subdrivers), blazer_usb, genericups
udev and permissions:
udev rule for device:
ATTR{idVendor}=="0925", ATTR{idProduct}=="1234", MODE="664", GROUP="nut"
USB device file:
crw-rw-r-- 1 root nut ... /dev/bus/usb/001/002
NUT runtime directory:
/var/run/nut exists, owned by root:nut, permissions 770
NUT user:
uid=122(nut) gid=126(nut) groups=126(nut),20(dialout)
Driver attempts and errors:
richcomm_usb:
USB device [0925:1234] matches, but driver callback failed: Entity not found
nutdrv_qx with subdriver=armac/q1, vendorid/productid:
Device not supported! Driver failed to start (exit status=1)
or
Subdriver 'q1' not found! Driver failed to start (exit status=1)
blazer_usb with all recommended options:
Could not open any HID devices: insufficient permissions on everything
What I've verified:
Device is detected properly with lsusb and correct permissions.
All recommended auxiliary ups.conf parameters (port=auto, vendorid, productid, subdriver variants).
No kernel driver (usbhid, serial) seems to be blocking access.
Tried power-cycling, different ports, and cables.
No success with any listed subdriver in nutdrv_qx, including auto-detect.
Referenced the NUT stable HCL, which lists Armac R/2000I/PSW (USB ID 0925:1234) as supported with nutdrv_qx, but my Office 1000E does not work.
TrueNAS’s NUT build reports most subdrivers as "not found".
Any advice or guidance on progressing support for this model would be greatly appreciated.
With kind regards,
Andries
Sent from Proton Mail Android
More information about the Nut-upsdev
mailing list