NUT and the USB HID driver are broken on FreeBSD because they are using an unsupported legacy API. According to information I got on their mailing list they have implemented the new API, but since they have not tagged a release since 2016, that code has not made it into any FreeBSD package, yet.Your best bet (IMHO) is to get a network card for your UPS if available and use SNMP.
Did you reboot the opnsense? It seems to have to do a reboot with the UPS plugged in to detect it. Then it is using the USBHID as UPS type.It works for me on my CyberPower CST135XLU which is about 3 years old, so don't know why it wouldn't work for you. The key is even on pfsense it requires a reboot.
Quote from: IsaacFL on March 21, 2021, 08:30:28 pmDid you reboot the opnsense? It seems to have to do a reboot with the UPS plugged in to detect it. Then it is using the USBHID as UPS type.It works for me on my CyberPower CST135XLU which is about 3 years old, so don't know why it wouldn't work for you. The key is even on pfsense it requires a reboot.I did reboot. I'm getting errors in the system log as well. When I get back home I'll post up my syslog errors.Sent from my IN2025 using Tapatalk
Dang, unfortunately my ups is USB only, surprised that's been broken so long.
2021-03-21T21:43:01 root[43795] /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut 2021-03-21T21:43:00 upsmon[94899] upsmon parent: read 2021-03-21T21:42:58 upsmon[95263] UPS [CyberPowerUPS]: connect failed: Connection failure: Operation already in progress 2021-03-21T21:42:27 upsmon[95263] UPS [CyberPowerUPS]: connect failed: Connection failure: Operation timed out 2021-03-21T21:42:04 root[81548] /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Quote from: FullyBorked on March 21, 2021, 07:32:40 pmDang, unfortunately my ups is USB only, surprised that's been broken so long. The current version on github seems to work fine, but without a release since 2016 it's almost impossible to update the FreeBSD package.
How can install the version from github?
Any downsides to sideloading like that?
I did a fresh install yesterday and ran into the same issue with my Cyberpower UPS.When I looked into the ups.conf file located at /usr/local/etc/nut, I noticed that opnsense was adding several (3) configs for the ups in the file. I removed the configs that didn't pertain and was left with:# Please don't modify this file as your changes might be overwritten with# the next update.#[CP1500PFCLCD]driver=usbhid-upsport=autoAfter saving and rebooting, it worked. But since there isn't a widget for the UPS like in pfSense, I'm wondering why I wasted so much time mucking with it.
# Please don't modify this file as your changes might be overwritten with# the next update.#MODE=standalone~~
Quote from: genesysguy on March 22, 2021, 04:02:16 pmI did a fresh install yesterday and ran into the same issue with my Cyberpower UPS.When I looked into the ups.conf file located at /usr/local/etc/nut, I noticed that opnsense was adding several (3) configs for the ups in the file. I removed the configs that didn't pertain and was left with:# Please don't modify this file as your changes might be overwritten with# the next update.#[CP1500PFCLCD]driver=usbhid-upsport=autoAfter saving and rebooting, it worked. But since there isn't a widget for the UPS like in pfSense, I'm wondering why I wasted so much time mucking with it.This might explain something too, my config file is pretty much blank.Code: [Select]# Please don't modify this file as your changes might be overwritten with# the next update.#MODE=standalone~~