Unstable experience with APC UPs

[marcgarciamarti]

Problem/Motivation

My experience with an APC UPS is bad. The UPS keeps reporting LB very frequently, even though I replaced the battery 1 month ago.

While this could be related to my unit being unhealthy, It looks like the standard nut component has issues with APC UPS: networkupstools/nut#2347. The last post is mine. I echoed the issues reported by other APC owners running the native nut project, because I believe the HA add-on version does implement that native project in a containerized manner.

Expected behavior

I expected to have stable telemetry that I could use to trigger healthy notifications. With my current experience, that is not an option at all.

Actual behavior

APC devices might report unstable telemetry

Steps to reproduce

Configure the integration like this:

users:
  - username: pass
    password: pwd
    instcmds:
      - all
    actions: []
devices:
  - name: apc-cs350
    driver: usbhid-ups
    port: auto
    config:
      - desc = "APC Back-UPS CS350"
      - vendorid = 051d

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[giannoug]

Same issue here. This bug has been reported upstream: networkupstools/nut#2347

Last comment mentions that version 2.8.2 should fix the issue. This addon is using 2.8.0.

[sinclairpaul]

The addon uses the latest version published in the Debian repo's. Building NUT is likely not something we will implement.

If you need the functionality of later versions I would suggest you look at alternate methods of running the software.

[giannoug]

That makes sense. Even Debian unstable doesn't have it yet. Its at 2.8.1.

[giannoug]

Checking with upstream again, it seems that adding "pollonly" to the configuration fixes this issue. Any idea how to achieve that in the addon?

This doesn't seem to work. How can I check the generated configuration file?

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[giannoug]

I'm not sure how and why, but this was fixed for me:

The only change I did was the one I mentioned around the end of May.

[marcgarciamarti]

I'm not sure how and why, but this was fixed for me:

The only change I did was the one I mentioned around the end of May.

Hi there! Thanks! I went ahead and added that option to my config, and the continuous flow of notifications has ceased. It looks like you hit the nail right on its head.
Thanks!!

[giannoug]

It looks like you hit the nail right on its head.

It stopped working for me again, after I tested wether the UPS works. Stuck on 99% OL CHRG 😥