Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4943

upsAdvBatteryChargerStatus floatCharging is not an error

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Alerting

    Description

      Hi there,

      imho there is a small definition error in includes/definitions/mibs/apc/powernet-mib.inc.php:

      $config['mibs'][$mib]['states'][$type][4] = [ 'name' => 'floatCharging', 'event' => 'warning' ];

      floatCharging should not generate a warning. 'event' => 'ok' is fine.

      Attachments

        Activity

          [OBS-4943] upsAdvBatteryChargerStatus floatCharging is not an error

          Ok, changed in r13823.

          landy Mike Stupalov added a comment - 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.

          helge.wiethoff@thga.de Helge Wiethoff added a comment - 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.

          helge.wiethoff@thga.de Helge Wiethoff added a comment - 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.

          landy Mike Stupalov added a comment - 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

          helge.wiethoff@thga.de Helge Wiethoff added a comment - 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
          landy Mike Stupalov added a comment - 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

          landy Mike Stupalov added a comment - It's seems still should be in warning state.. https://nissandiesel.dyndns.org/viewtopic.php?t=2891

          People

            landy Mike Stupalov
            helge.wiethoff@thga.de Helge Wiethoff
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: