【已解决】设备型号识别错误造成ups无法连接

bluskai

设备环境：N150物理机，通过USB链接Back-UPS BK650M2-CH

BUG现象：在系统界面可以看到识别了UPS，但是当选定UPS时，提示UPS设备不存在，请刷新后重试。

背景：因为飞牛推出了1.0，就想着重新安装了一下系统。安装之前同样的主机、同样的链接方法，可以正常识别并使用。安装时未移动主机、也未插拔过线缆。重新安装系统后，出现了不能正常链接UPS的问题。尝试了关闭、重启飞牛，重启UPS，重新插拔线缆，还是不行。

出现频率：必现

飞牛技术同学

新版本有优化类似的情况 更新到最新的版本再试试

bluskai

飞牛技术同学 发表于 2025-12-4 18:12
新版本有优化类似的情况 更新到最新的版本再试试

已更新到1.1.4，还是同样的提示，需要我提供什么样的log信息帮助定位bug吗?

bluskai

usb设备信息

$ sudo lsusb -v -d 051d:0002
Bus 003 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x051d American Power Conversion
  idProduct          0x0002 Uninterruptible Power Supply
  bcdDevice            1.06
  iManufacturer           1 American Power Conversion
  iProduct                2 Back-UPS BK650M2-CH FW:29***3G -29***4G 
  iSerial                 3 9B2******845
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0022
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     745
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0006  1x 6 bytes
        bInterval              10
Device Status:     0x0002
  (Bus Powered)
  Remote Wakeup Enabled

nut配置文件信息：

$ sudo cat /etc/nut/ups.conf
#省略了一大段注释
maxretry = 3
[1248261]
driver                           = "usbhid-ups"
port                             = "auto"
vendorid                         = "051D"
vendor                           = "American Power Conversion"
productid                        = "0002"
product                          = "Back-UPS BK650M2-CH FW:01****45-29***4G"
serial                           = "9B2******845"
bus                              = "003"
override.x.additional.devicetype = "USB"

nut-server运行信息：

$ sudo systemctl status nut-server
● nut-server.service - Network UPS Tools - power devices information server
     Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-12-05 09:38:00 CST; 2h 33min ago
   Main PID: 7536 (upsd)
      Tasks: 1 (limit: 37974)
     Memory: 904.0K
        CPU: 892ms
     CGroup: /system.slice/nut-server.service
             **─7536 /lib/nut/upsd -F

Dec 05 11:48:08 N150 nut-server[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 11:48:08 N150 upsd[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 11:53:09 N150 nut-server[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 11:53:09 N150 upsd[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 11:58:09 N150 nut-server[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 11:58:09 N150 upsd[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 12:03:10 N150 nut-server[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 12:03:10 N150 upsd[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 12:08:10 N150 nut-server[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory
Dec 05 12:08:10 N150 upsd[7536]: Can't connect to UPS [1248261] (usbhid-ups-1248261): No such file or directory

bluskai

补充nut-scanner的信息

$ sudo nut-scanner
Scanning USB bus.
No start IP, skipping NUT bus (old connect method)
Scanning NUT bus (avahi method).
[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "051D"
        productid = "0002"
        product = "Back-UPS BK650M2-CH FW:29***3G -29***4G"
        serial = "9B2******845"
        vendor = "American Power Conversion"
        bus = "003"

飞牛技术同学

bluskai 发表于 2025-12-5 12:04
已更新到1.1.4，还是同样的提示，需要我提供什么样的log信息帮助定位bug吗? ...

私信提供一下微信联系方式吧 我让技术远程排查看看

bluskai

问题已经解决！分享一下解决感悟。

首先感谢飞牛的技术人员，周五晚上都六点半了，还在帮我排查，你们辛苦了。

说一下自己理解的错误原因：

1. 从USB信息可以看到型号信息是 Back-UPS BK650M2-CH FW:29***3G -29***4G

sudo lsusb -v -d 051d:0002
iProduct  2 Back-UPS BK650M2-CH FW:29***3G -29***4G

2. 但是，此时nut配置文件中显示的型号确是 Back-UPS BK650M2-CH FW:01****45-29***4G

$ sudo cat /etc/nut/ups.conf
product  = "Back-UPS BK650M2-CH FW:01****45-29***4G"

3. 由于这两处的型号不同，所以就造成了ups一直无法正确添加。解决方法也很暴力，直接在 ups.conf文件中删掉 product = "Back-UPS BK650M2-CH FW:01****45-29***4G"这一行配置。

以上为我自己的理解分析，相关问题的朋友可以参考一下。

• 后续翻看截图，发现一开始截图就反应出来了型号识别有问题。