upsAdvBatteryChargerStatus floatCharging is not an error

Ok, changed in r13823.

These links are not helpful: they do not refer to setups supported by the manufacturer, and using them as they do may inevitably lead to errors.

Actually i wanted to tell you that the vendor himself says: floatCharging is a normal state. not a warning, not an alert.

Anyway, there is difference in states.
this condition is "warning".. not normal and not alert at same time.

"warning" value means that something is not quite normal in your electrical system.

It seems to me that your question was originally about something else.
If you want to exclude this condition from alerts, you can do it differently.
Show your alert conditions, I will tell you how you can eliminate this state.

Hi Mike,

Thank you for your research. I just spoke with the manufacturer on the phone, and they assured me that this behavior is normal for an online UPS of this type and is not a fault condition. The float voltage is below the charging voltage, so the battery won't be damaged like in the forum posts you linked. Therefore, I maintain that "'event' => 'ok'" should be the case for the situation mentioned above.

Best regards, Helge

in this state battery is "killed".
https://www.candlepowerforums.com/threads/constant-float-charging-a-lead-acid-battery.325385/

It's seems still should be in warning state..

https://nissandiesel.dyndns.org/viewtopic.php?t=2891

Probably I do not sure, what this mean on this hardware.
MIB do not have description for this state.

Describe please

General questions and device support can be discussed in our Discord channel, click here to join.

Please make and attach additional information about the device:

• full snmp dump from device:

  snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk

  snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

  If device not support SNMP version 2c, replace -v2c with -v1.

• If you have problems with discovery or poller processes, please do and attach these debugs:

  ./discovery.php -d -h <device>

  ./poller.php -d -h <device>

• additionally attach device and/or vendor specific MIB files

This comment is added automatically.