Still issue with nut-server nut-client

[dudesplace]

I get this:

sudo systemctl status nut-monitor.service
garuda-inspiron3670 nut-monitor[80106]: Communications with UPS qnapups@192.168.1.8:3493 established
Apr 27 13:35:53 garuda-inspiron3670 nut-monitor[98149]: Network UPS Tools upsmon 2.8.2
Apr 27 13:36:34 garuda-inspiron3670 systemd[1]: nut-monitor.service: Supervising process 80106 which is not our child. We'll most likely not notice when it exits.

But still don’t see any indication it’s staying connected when I leave terminal.
On other distro’s nut-monitor adds app icon in apps and can add as a startup application.
And I also don’t see it in my conky’s IP open ports connected like in others..
When I do a upsc qnapups@192.168.1.8 in terminal I get the expected outputs from it.

battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: 2001/09/25
battery.mfr.date: 2024/08/30
battery.runtime: 1263
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.1
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Back-UPS XS 1500M
device.serial: 5B2435TB3663  
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS1
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: APC HID 0.96
driver.version.internal: 0.41
input.sensitivity: medium
input.transfer.high: 136
input.transfer.low: 88
input.voltage: 118.0
input.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 947.d13 .D
ups.firmware.aux: d13     
ups.load: 29
ups.mfr: American Power Conversion
ups.mfr.date: 2024/08/30
ups.model: Back-UPS XS 1500M
ups.productid: 0002
ups.realpower.nominal: 900
ups.serial: 5B2435TB3663  
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

Is there supposed to be a GUI for it?

[SGS]

Make sure you have done the following before you post:

• Search the web and forums
• Read How to search for solutions the right way | Garuda Linux wiki
• Read FAQ and Tutorials Table of Contents

Issue still unresolved? Then:

• ONE issue per topic.
• Describe your issue in detail. The more we know, the better we can help
• Show us the results of your searches, and what you’ve tried

• After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)

• Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text

Without garuda-inxi this request will be moved to 4xx Client Error > 412 Precondition Failed