Charles, thanks for the hint. It got me thinking about 'listening on'. Further
investigation revealed that my hosts file was fubar. Correcting it resolved the
issue.
Dan
From: Charles Lepple
Sent: Friday, March 8, 2024 9:04 AM
To: Dan Grostick
Cc: nut-upsuser
On Mar 8, 2024, at 8:22 AM, Dan Grostick via Nut-upsuser
wrote:
>
> I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian
> 12) with success.
>
> When I take that same configuration to a PI 3B running bookworm 32 bit,
> compile from source, use the same files from
On Mar 8, 2024, at 7:07 AM, Roger Price wrote:
>
> Perhaps setting lowbatt = 50 in ups.conf would help.
Roger, good point.
That option is missing in the usbhid-ups man page, so I logged an issue to
remind us to fix that: https://github.com/networkupstools/nut/issues/2356
Since I am used to
I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian
12) with success.
When I take that same configuration to a PI 3B running bookworm 32 bit, compile
from source, use the same files from /etc/nut, I get a 'nut-monitor
ups@localhost Connection refused.
usbhid-ups and
On Mon, 4 Mar 2024, Alan C. Bonnici via Nut-upsuser wrote:
Platform: Proxmox VE 8.1.4
NUT version: Network UPS Tools upsstats 2.8.0
I configured Proxmox and I can pull up the UPS stats.
Typing in `upsrw -l cyberpower@localhost` I get the following:
[battery.charge.low]
Remaining battery level
On Mar 4, 2024, at 3:23 PM, Alan C. Bonnici via Nut-upsuser
wrote:
>
> I would like to push up the shutdown process to initiate when the ups is at
> 50% rather than 10% mainly because there is a need to down other servers.
>
Some UPSes have a limited range for adjusting the LB threshold, or
*Platform: Proxmox VE 8.1.4NUT version: Network UPS Tools upsstats 2.8.0*
I configured Proxmox and I can pull up the UPS stats.
Typing in `*upsrw -l cyberpower@localhost*` I get the following:
*[battery.charge.low]Remaining battery level when UPS switches to LB
