Potential bug found with apcupsd package (version 0.3.91_8) and configuring it in the webconfigurator (on pfSense Version 2.4.5-RELEASE-p1 on AMD64)
-
I didn't see your original. I think I ran into this also last year. I put "usb" in the USB Type field and it seems fine. I vaguely recall I found that after searching.
As far as reporting, I don't know if the correct answer is to update the HTML to say "usb" instead of "BLANK," or to make the field not required.
If you're programmatically inclined the code is at:
https://github.com/pfsense/FreeBSD-ports/commits/devel/sysutils/pfSense-pkg-apcupsd
Otherwise bugs are at https://redmine.pfsense.org/projects/pfsense-packages -
I didn't see your original. I think I ran into this also last year. I put "usb" in the USB Type field and it seems fine. I vaguely recall I found that after searching.
-- working fine, there is no issue
Redmine issue created:
https://redmine.pfsense.org/issues/11375 -
@viktor_g Define fine?
-
Is it trying to say "enter 'usb' and we'll consider the field blank" as opposed to "leave the field blank for USB connections"?
-
To get it to work with most of the apc ups 'Simple Signalling' USB cables you have to have UPS type blank, as in NULL, nothing written there. Of course there's validation that doesn't let you have a blank entry there.
I've tried filling it with 'usb' and 'BLANK' (the literal string) and they don't make it work. The only way I've gotten it to work thus-far is edit apcupsd.conf either from shell or from the advanced configuration menu, but this isn't preserved across reboots.
Cheers,
JessEdit: Also teamits screenshot is exactly the behaviour I get, and I am not sure how to get the web configurator to accept a null string.,
-
@digitaljessica said in Potential bug found with apcupsd package (version 0.3.91_8) and configuring it in the webconfigurator (on pfSense Version 2.4.5-RELEASE-p1 on AMD64):
apc ups 'Simple Signalling' USB cables
Which model UPSs, do you know? The one I screen capped is a Smart UPS 750. We've set it up on a couple of BR-700s I think (or similar smaller BR models). All using the cable that came with the UPS.
-
@teamits
I personally have Back-UPS ES 700G (UK) UPSes using the 10pin connector that's like a LAN connector but has more pins than an LAN cable. On most of them I'm using the cable that came with them, but since they're a dumb cable, on one of them I have a replacement for it (since it just connects the USB pins to the outer pins of the 10p connector) and the UPS actually has the "USB host" bit.
-
IIRC those are older (?) so maybe that is a difference. It probably comes down to what the code does with "usb" as the type, vs blank as you describe and the instructions say.
Rereading the page a few more times, and considering UPSTYPE and DEVICE are two different columns, it may be saying use these values for the two fields, not "for USB enter blank." Device=(blank) is in fact what I have:
-
@teamits
Oh that's clear as mud.
In the apcupsd.conf you usually just say "UPS: usb" and leave the type blank, which is what it looks like it says on the web configurator page.
Writing "usb" in type now has fixed it. It didn't before so I don't get it. Maybe someone should change that hint to say to write usb there if you're using usb, rather than the table that looks like "for usb specify blank".
-
It's made more confusing because like my screenshot shows it looks like "UPSTYPEDEVICE" with the columns squished together. Perhaps change those columns to "Enter in UPS Type field:" and "Enter in Device field:" or similar? Or move that table to a new row above both fields so it doesn't look like it's talking about only the USB Type field.
-
@digitaljessica Try entering a space in the USB Type field. For some reason that passes input validation and allows you to save the config settings.