Metric does not show on Topbar and Notification Attachment

[Slebby]

Hello, I recently update to the latest version (v0.2.0) with raspberry pi 5 image (dartsteven/nutify:latest-raspberrypi5-arm64).

The information on the Top bar is not showing an information and it also not showing on the ntfy notification attachments as well. I have tried reinstall it and check the logs but it seems there is not any error in log it self.

The topbar

The notification attachment

[DartSteven]

Please attach the logs and follow this format when reporting the issue:

Environment: Docker + image tag/version
Profile: Single/Multi
Topology: <selected topology>
Symptom: <what is failing>
Expected: <what should happen>
When started: <date/time>
Recent changes: <what changed before issue>
TopBar active target: <target name>
Logs (first error): <paste>
Tried already: <checks/fixes performed>

If you want to enable logging directly from Bash, add the following under environment in your docker-compose.yml, then restart the stack:

- LOG=true
- LOG_LEVEL=DEBUG
- LOG_WERKZEUG=true
- ENABLE_LOG_STARTUP=Y

[Slebby]

Environment: Docker version 29.3.0, build 5927d80 + dartsteven/nutify:latest-raspberrypi5-arm64
Profile: Single
Topology: Network Server
Symptom: Metric would not show on the Topbar for web version and the notification (ntfy) attachment is not showing any metric
Expected: Metric should show proper status and number on the Topbar and attachment in notification (ntfy)
When started: 03/04/2026
Recent changes: 0.2.0 Changelog
TopBar active target: eaton_3S_ups
Logs (first error): No Error found in the log files

logs_2026-04-03T12_58_38.362Z.zip

Tried already: Reinstall, use the default configuration during setup.

[DartSteven]

Could you send me your JSON output from this endpoint: http://your-ip:5050/api/ups/json ?

[Slebby]

here is the output that it gave me:

{
  "timestamp": "2026-04-05 20:48:34 AEST",
  "ups_data": {
    "battery_charge": 100.0,
    "battery_charge_low": 20.0,
    "battery_runtime": 3072.0,
    "battery_type": "PbAc",
    "device_mfr": "EATON",
    "device_model": "Eaton 3S 850",
    "device_serial": "Blank",
    "device_type": "ups",
    "device_usb_version": "USB",
    "driver_debug": 0.0,
    "driver_flag_allow_killpower": 0.0,
    "driver_name": "usbhid-ups",
    "driver_parameter_interrupt_pipe_no_events_tolerance": -1.0,
    "driver_parameter_pollfreq": 30.0,
    "driver_parameter_pollinterval": 2.0,
    "driver_parameter_port": "auto",
    "driver_parameter_product": "Eaton 3S",
    "driver_parameter_productid": "FFFF",
    "driver_parameter_serial": "Blank",
    "driver_parameter_synchronous": "auto",
    "driver_parameter_vendor": "EATON",
    "driver_parameter_vendorid": 463.0,
    "driver_state": "quiet",
    "driver_version": "2.8.4",
    "driver_version_data": "MGE HID 1.55",
    "driver_version_internal": 0.67,
    "driver_version_usb": "libusb-1.0.26 (API: 0x01000109)",
    "input_transfer_high": 276.0,
    "input_transfer_low": 192.0,
    "outlet_1_desc": "PowerShare Outlet 1",
    "outlet_1_id": 1.0,
    "outlet_1_protect_status": "protected",
    "outlet_1_status": "on",
    "outlet_1_switchable": "no",
    "outlet_desc": "Main Outlet",
    "outlet_id": 0.0,
    "outlet_switchable": "yes",
    "output_frequency_nominal": 50.0,
    "output_voltage": 230.0,
    "output_voltage_nominal": 240.0,
    "ups_beeper_status": "disabled",
    "ups_delay_shutdown": 20.0,
    "ups_delay_start": 30.0,
    "ups_firmware": "02.08.001",
    "ups_load": 6.0,
    "ups_mfr": "EATON",
    "ups_model": "Eaton 3S 850",
    "ups_power_nominal": 850.0,
    "ups_productid": "ffff",
    "ups_realpower": 41.0,
    "ups_serial": "Blank",
    "ups_status": "OL CHRG",
    "ups_timer_shutdown": -1.0,
    "ups_timer_start": -1.0,
    "ups_type": "offline / line interactive",
    "ups_vendorid": 463.0
  }
}

Here is the file if you needed: ups_data_20260405_204834.json

[DartSteven]

How did you end up with those values? Did you manually change the polling during the setup wizard or later in the options?

    "driver_parameter_pollfreq": 30.0,
    "driver_parameter_pollinterval": 2.0,

[Slebby]

nope, I did not change anything regarding to those values, I just select the auto-detect as I used USB to connect to my ups and change something in upsd.users file. other than that I did not change anything during the setup and afterward.

[DartSteven]

Could you try setting it to 1 second? Go here:
System->Advanced->Nut Manager->Edit->Polling Interval (seconds) -> 1 -> Save Target
and
System->Advanced->Configuration->ups.conf

    pollinterval = 1
    pollfreq = 1

[Slebby]

The first one is already set to 1 Second. This is the default values.

---

The second one, those variables are not exist in the file. So I added those to the file and add some comment to avoid the confusion.

---

Checked the JSON output and it seems to setup correctly.

{
  "timestamp": "2026-04-06 18:29:41 AEST",
  "ups_data": {
    "battery_charge": 100.0,
    "battery_charge_low": 20.0,
    "battery_runtime": 3072.0,
    "battery_type": "PbAc",
    "device_mfr": "EATON",
    "device_model": "Eaton 3S 850",
    "device_serial": "Blank",
    "device_type": "ups",
    "device_usb_version": "USB",
    "driver_debug": 0.0,
    "driver_flag_allow_killpower": 0.0,
    "driver_name": "usbhid-ups",
    "driver_parameter_interrupt_pipe_no_events_tolerance": -1.0,
    "driver_parameter_pollfreq": 1.0,
    "driver_parameter_pollinterval": 1.0,
    "driver_parameter_port": "auto",
    "driver_parameter_product": "Eaton 3S",
    "driver_parameter_productid": "FFFF",
    "driver_parameter_serial": "Blank",
    "driver_parameter_synchronous": "auto",
    "driver_parameter_vendor": "EATON",
    "driver_parameter_vendorid": 463.0,
    "driver_state": "updateinfo",
    "driver_version": "2.8.4",
    "driver_version_data": "MGE HID 1.55",
    "driver_version_internal": 0.67,
    "driver_version_usb": "libusb-1.0.26 (API: 0x01000109)",
    "input_transfer_high": 276.0,
    "input_transfer_low": 192.0,
    "outlet_1_desc": "PowerShare Outlet 1",
    "outlet_1_id": 1.0,
    "outlet_1_protect_status": "protected",
    "outlet_1_status": "on",
    "outlet_1_switchable": "no",
    "outlet_desc": "Main Outlet",
    "outlet_id": 0.0,
    "outlet_switchable": "yes",
    "output_frequency_nominal": 50.0,
    "output_voltage": 230.0,
    "output_voltage_nominal": 240.0,
    "ups_beeper_status": "disabled",
    "ups_delay_shutdown": 20.0,
    "ups_delay_start": 30.0,
    "ups_firmware": "02.08.001",
    "ups_load": 6.0,
    "ups_mfr": "EATON",
    "ups_model": "Eaton 3S 850",
    "ups_power_nominal": 850.0,
    "ups_productid": "ffff",
    "ups_realpower": 41.0,
    "ups_serial": "Blank",
    "ups_status": "OL CHRG",
    "ups_timer_shutdown": -1.0,
    "ups_timer_start": -1.0,
    "ups_type": "offline / line interactive",
    "ups_vendorid": 463.0
  }
}

I waited around 4-5 minutes to let the poll thing works. but the issues are still persist.

---

Upon checking the log again there is an error regarding to the origin. I used traefik for reverse proxy the dashboard, is it possible that this is the issue? I doubt that this would be an issue.

[DartSteven]

You hadn’t mentioned that you were behind a reverse proxy :)
Yes, that could be the issue. Are you able to test it without the proxy?

[Slebby]

Yeah, It was working behind reverse proxy on previous version before so I thought that was not a problem. Sorry about that.

I tested without the proxy, The top bar shows the metrics now. But the metrics on the notification attachment is still not showing.

[DartSteven]

Okay, that makes things clearer now. Yes, those are definitely API endpoints that require authentication.

Also, I’ve just noticed that the Raspberry version for 64-bit has some issues. Even though the code is identical, a few Python packages end up being different versions because the same ones available on amd64 are not always available there.

[Slebby]

Is it possible for you to make the API endpoint works with reverse proxy or that would be depends on how I setup the reverse proxy.

Also, do you want me to test anything else?

[DartSteven]

It depends on how your reverse proxy is configured. The API endpoint can work through a reverse proxy, but the necessary setup has to be done on your side in the reverse proxy configuration.