NUT Status message

[adm2k]

I was doing a test of the battery in my UPS this morning and when I plugged the UPS back into AC I see this message "OL CHRG" but I don't see any thing in the settings.yaml for it. Just wondering where it comes from.

This my yaml for status:

• field:
  apcmain:
  ups.status
  label: Status
  format: text
  remap:
  - value: "OL"
  to: On AC
  - value: "OB"
  to: On BATT

Many thanks!

al

[adm2k]

Never mind :)

I found it in the JSON target:

{"server_version": "2.8.0", "server_address": "192.168.86.24", "server_port": 3493, "apcmain": {"description": "Description unavailable", "battery.charge": "99", "battery.charge.low": "10", "battery.charge.warning": "50", "battery.date": "2001/09/25", "battery.mfr.date": "2022/04/30", "battery.runtime": "2676", "battery.runtime.low": "120", "battery.type": "PbAc", "battery.voltage": "13.6", "battery.voltage.nominal": "12.0", "device.mfr": "American Power Conversion", "device.model": "Back-UPS ES 600M1", "device.serial": "4B2217P05773 ", "device.type": "ups", "driver.name": "usbhid-ups", "driver.parameter.bus": "002", "driver.parameter.pollfreq": "30", "driver.parameter.pollinterval": "1", "driver.parameter.port": "auto", "driver.parameter.product": "Back-UPS ES 600M1 FW:928.a9 .D USB FW:a9", "driver.parameter.productid": "0002", "driver.parameter.serial": "4B2217P05773", "driver.parameter.synchronous": "auto", "driver.parameter.vendor": "American Power Conversion", "driver.parameter.vendorid": "051D", "driver.version": "2.8.0", "driver.version.data": "APC HID 0.98", "driver.version.internal": "0.47", "driver.version.usb": "libusb-1.0.26 (API: 0x1000109)", "input.sensitivity": "medium", "input.transfer.high": "139", "input.transfer.low": "92", "input.voltage": "120.0", "input.voltage.nominal": "120", "ups.beeper.status": "enabled", "ups.delay.shutdown": "20", "ups.firmware": "928.a9 .D", "ups.firmware.aux": "a9 ", "ups.load": "15", "ups.mfr": "American Power Conversion", "ups.mfr.date": "2022/04/30", "ups.model": "Back-UPS ES 600M1", "ups.productid": "0002", "ups.realpower.nominal": "330", "ups.serial": "4B2217P05773 ", "ups.status": "OL CHRG", "ups.test.result": "No test initiated", "ups.timer.reboot": "0", "ups.timer.shutdown": "-1", "ups.vendorid": "051d"}}

[ArthurMitchell42]

Yes, this is where we get in to slightly mirky territory. What is sent as 'status' is a string and each manufacturer (and sometimes each model of UPS) has a way of doing things. In this case the UPS is telling us that it is power on and charging the battery after an outage.
There are a number of ways of responding to this. In HomePage we could have an extended set of remap: to: causes but that would be verbose. When NUTCase is providing data to Prometheus it splits the operating modes down as follows:
Hence all the possible options are presented 'in parallel'

# TYPE nut_ups_status stateset
# UNIT nut_ups_status 
# HELP nut_ups_status UPS status. Check for a specific status with the "status" label. ("ups.status")
nut_ups_status{ups="ups",status="OL"} 1
nut_ups_status{ups="ups",status="OB"} 0
nut_ups_status{ups="ups",status="LB"} 0
nut_ups_status{ups="ups",status="CHRG"} 0
nut_ups_status{ups="ups",status="RB"} 0
nut_ups_status{ups="ups",status="FSD"} 0
nut_ups_status{ups="ups",status="BYPASS"} 0
nut_ups_status{ups="ups",status="SD"} 0
nut_ups_status{ups="ups",status="CP"} 0
nut_ups_status{ups="ups",status="BOOST"} 0
nut_ups_status{ups="ups",status="OFF"} 0

You can see this output by changing the requested endpoint from /json to /metrics
The way I favour at the moment is to use the variable refactoring feature I'm testing out right now. This would work with the JSON endpoint and I'm thinking about making a hybrid string on operating condition.

My slight concern about this is that the space for strings in HomePage is limited making it look clumsy. It would be nice to see HomePage expand their customapi widget to support things like colour, variability in the fields or test conditions but as it's an edge feature of their system I doubt they would want to spend time on it.

I hope to try and push a beta container to DockerHub this weekend to try this out.
I'll post a link on this thread when it's ready.

[adm2k]

Thank you for the clear explanation! Look forward to your updates...

al