I personally did not need to put this line to get it to work. Based on qfina's post, he/she had the IP of the NUT server (Proxmox host) entered.
Config for Network UPS Tool (NUT) for Prolink
- Thread starter sleeper52
- Start date
@sleeper52 Everything is looking good,,,,
It's so much easier having the Proxmox Host and NUT server on the same IP.
The client-server in the container has blank values for the Input / Output / Load %.
Did I miss something or is this an APC compatibility?
Everything else looks great!
It's so much easier having the Proxmox Host and NUT server on the same IP.
The client-server in the container has blank values for the Input / Output / Load %.
Did I miss something or is this an APC compatibility?
Everything else looks great!
Output: | |
|---|---|
UPS Model: | Smart-UPS_1000 |
Status: | ONLINE |
Runtime: | 01:40:18 |
Battery: | 26.9 V |
Input: |
| battery.charge | : | 98 |
| battery.charge.low | : | 10 |
| battery.charge.warning | : | 50 |
| battery.runtime | : | 5991 |
| battery.runtime.low | : | 150 |
| battery.type | : | PbAc |
| battery.voltage | : | 26.9 |
| battery.voltage.nominal | : | 24.0 |
| device.mfr | : | American Power Conversion |
| device.model | : | Smart-UPS_1000 |
| device.serial | : | AB2109162124 |
| device.type | : | ups |
| driver.name | : | usbhid-ups |
| driver.parameter.pollfreq | : | 30 |
| driver.parameter.pollinterval | : | 15 |
| driver.parameter.port | : | auto |
| driver.parameter.productid | : | 0003 |
| driver.parameter.synchronous | : | auto |
| driver.parameter.vendorid | : | 051D |
| driver.version | : | 2.8.0 |
| driver.version.data | : | APC HID 0.98 |
| driver.version.internal | : | 0.47 |
| driver.version.usb | : | libusb-1.0.26 (API: 0x1000109) |
| ups.beeper.status | : | disabled |
| ups.delay.shutdown | : | 180 |
| ups.firmware | : | UPS 15.5 / ID=1018 |
| ups.mfr | : | American Power Conversion |
| ups.mfr.date | : | 2021/03/03 |
| ups.model | : | Smart-UPS_1000 |
| ups.productid | : | 0003 |
| ups.serial | : | AS2109162124 |
| ups.status | : | OL CHRG |
| ups.timer.reboot | : | -1 |
| ups.timer.shutdown | : | -1 |
| ups.vendorid | : | 051d |
I'm not entirely sure since I don't use an APC UPS. Might want to ask @bigjim63 since he's using one. He also posted his config files so you might want to check those out.
Hi there.
I've got a Tripp Lite AVR900U that I have named as tripplite (instead of your prolink). When I get to step 10 (as quoted above), I get the following:
Code:
Network UPS Tools - UPS driver controller 2.8.0
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Can't claim USB device [09ae:3024]@0/0: Entity not found
Driver failed to start (exit status=1)I've exceeded the breadth of my Google-Fu, so I'm really not sure where the issue is. I'd read in another thread elsewhere that the cable could be the issue so I had already tried to replace that (though Amazon doesn't make it easy to know if you're getting precisely what you need). I'm not sure if I've had NUT functional since I transitioned to VE 8. My upgrade didn't go well, and I'm still putting pieces back together again.
Hi,
What do you get get when u type
nut-scanner -U and typing lsusb?And what does your
nano /etc/nut/ups.conf file look like?
Last edited:
nut-scanner -U
Code:
[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "09AE"
productid = "3024"
product = "AVR900U"
serial = "redacted"
vendor = "Tripp Lite"
bus = "001"lsusb
Code:
Bus 001 Device 011: ID 09ae:3024 Tripp Lite AVR900Unano /etc/nut/ups.conf
Code:
pollinterval = 15
maxretry = 3
offdelay = 180
ondelay = 330
[tripplite]
driver = usbhid-ups
port = auto
desc = "Tripp Lite AVR900U"
# these two are optional
vendorid = 09AE
productid = 3024It doesn't make a difference if I change it there (and elsewhere) to
nutdev1 either.that looks right. I just remembered Techno Tim mention that there is an additional configuration for Tripp Lite UPS devices. Please check this out. I've already set the timestamp to 30:44 where he talks about it. Hopefully this resolves your issue.
Last edited:
Thanks for the share. I remember setting up a rules file (not the exact one specified) but it doesn't seem to have made a difference. I saw...somewhere...in some thread...suggesting powering down the UPS and restarting it so I'll find a quiet time, maybe this weekend, to do that, see if that helps at all.
If you are like me, and you have just ctrl+c ctrl+v the nano commands, there is a typo in step 28.
"nano /etc/nut/upssmon.conf" should be "nano /etc/nut/upsmon.conf" which causes the service "nut-client" to crash in the LXC container.
@SilicaStorm I dont think its necessary, actually I think it's the nut-server to won't start. I didnt put it there and everything is working just fine.
"nano /etc/nut/upssmon.conf" should be "nano /etc/nut/upsmon.conf" which causes the service "nut-client" to crash in the LXC container.
@SilicaStorm I dont think its necessary, actually I think it's the nut-server to won't start. I didnt put it there and everything is working just fine.