NUT Server scanner On Pi Lacks Device Info

July 26, 2024, 12:41

lloyd.b

G'day All, This is a strange one and I'm not sure exactly where it belongs but I think it's more of a Raspberry Pi thing than a NUT thing. (Hopefully). The story so far...I have three UPS's and two of them are identical. The trouble is they do not have any unique information to differentiate between them. I can bypass this on Ubuntu because the nut-scanner utility reports a device ID (based on the port) which I can use to differentiate when writing the config. Alas, Bookworm (and Bullseye) do not seem to provide this information to nut-scanner. It does work if I install Ubuntu server on the Pi but that makes using the GPIO pins difficult and I'd really rather use Bookworm. The difference is that Ubuntu reports like this: [nutdev3] driver = "nutdrv_qx" port = "auto" vendorid = "0665" productid = "5161" product = "USB to Serial" vendor = "Cypress Semiconductor" bus = "002" device = "002" busport = "001" and Bookworm shows the same but without the device or busport entries. I can do without the busport entry but device would be fine. I've tried manually specifying the device ID from the results of lsusb but it doesn't work as I don't think it's aware of a device ID. Is this to do with the implementation of the usb lib stuff in Bookworm or would I need to install something extra on-top? I've scoured google and forums but to no avail as it seems people running it on Rpi have UPS's with serial numbers or other self-defining features. Would be grateful for a poke in the right direction. Cheers, Lloyd.

lloyd.b

Well, I quite understand the lack of replies. It's a very niche area and it's dealing with some software with different attitudes to life! 🙂 I just thought I'd add something to the thread about how I resolved things. It's not the BEST resolution but it will have to do. I took the Eaton UPS from my computer and moved it to the server rack so there are two Eatons (with individual IDs) and one Socomet (vanilla). That works. It's not ideal, as I said, however, I can't see any other way out. There is no easy and reliable way out of this situation. The tricks about allowing duplicates are not completely supported and other ways are not supported across reboots/service-restarts. It's partially my fault, as I've had these 'vanilla' UPS's for quite some years now and have been replacing batteries. You can't expect compatibility out of the ancients! 🙂 This may help some other people, who knows. Happy trails!