Non suported device

[tislar]

Hi,

I have tried connecting my UPS and tring to get it to work with NUT but with no sucess.
Please if you can help.

Here are all data i have.

Only thing that worked on my homeassistant addon is blaser_usb, but no data was shown.

Product:
https://gembird.com/item.aspx?id=7479

LOG from addon:

---

Add-on: Network UPS Tools
Manage battery backup (UPS) devices

Add-on version: 0.17.0
You are running the latest version of this add-on.
System: Home Assistant OS 16.3 (amd64 / generic-x86-64)
Home Assistant Core: 2025.12.4
Home Assistant Supervisor: 2025.12.3

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[14:42:06] INFO: Configuring timezone (Europe/Vienna)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nut.sh
[14:42:07] INFO: Setting mode to netserver...
[14:42:07] INFO: Generating /etc/nut/upsd.users...
[14:42:07] INFO: Configuring user: hassio
[14:42:07] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[14:42:07] INFO: Configuring Device named Energenie...
[14:42:07] INFO: Starting the UPS drivers...
Please note that this driver is deprecated and will not receive
new development. If it works for managing your devices - fine,
but if you are running it to try setting up a new device, please
consider the newer nutdrv_qx instead, which should handle all 'Qx'
protocol variants for NUT. (Please also report if your device works
with this driver, but nutdrv_qx would not actually support it with
any subdriver!)
Supported UPS detected with megatec protocol
Vendor information read in 1 tries
No values provided for battery high/low voltages in ups.conf
Using 'guesstimation' (low: 0.000000, high: 0.000000)!
Battery runtime will not be calculated (runtimecal not set)
WARNING: Needed to fix group access to filesystem socket of this driver, but failed; run the driver with more debugging to see how exactly.
Consumers of the socket, such as upsd data server, can fail to interact with the driver and represent the device: /run/nut/blazer_usb-Energenie
Network UPS Tools - UPS driver controller 2.8.1
cont-init: info: /etc/cont-init.d/nut.sh exited 0
cont-init: info: running /etc/cont-init.d/nutclient.sh
cont-init: info: /etc/cont-init.d/nutclient.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun upsd (no readiness notification)
services-up: info: copying legacy longrun upsmon (no readiness notification)
[14:42:07] INFO: Starting the UPS information server...
0.000000 fopen /run/nut/upsd.pid: No such file or directory
0.000012 Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
0.000209 [D1] debug level is '1'
0.000283 listening on 0.0.0.0 port 3493
0.000379 [D1] Succeeded to become_user(root): now UID=0 GID=0
0.000399 [D1] chdired into statepath /run/nut for driver sockets
0.000497 Connected to UPS [Energenie]: blazer_usb-Energenie
0.000522 Found 1 UPS defined in ups.conf
0.003768 Running as foreground process, not saving a PID file
0.003876 upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
0.003936 upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
0.003972 upsnotify: logged the systemd watchdog situation once, will not spam more about it
[14:42:07] INFO: Starting the UPS monitor and shutdown controller...
0.000000 fopen /run/nut/upsmon.pid: No such file or directory
0.000013 Could not find PID file to see if previous upsmon instance is already running!
0.000128 Using power down flag file /etc/killpower
0.000242 UPS: Energenie@localhost (primary) (power value 1)
0.000284 [D1] debug level is '1'
0.000320 Warning: running as one big root process by request (upsmon -p)
0.000489 [D1] Saving PID 321 into /run/nut/upsmon.pid
Init SSL without certificate database
0.002201 upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
0.003595 upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
0.003609 upsnotify: logged the systemd watchdog situation once, will not spam more about it
0.003613 [D1] Trying to connect to UPS [Energenie@localhost]
0.017861 User upsmonmaster@127.0.0.1 logged into UPS [Energenie]
0.005677 [D1] Logged into UPS Energenie@localhost
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
601.666519 Signal 15: exiting
Network UPS Tools upsmon 2.8.1
601.680454 User upsmonmaster@127.0.0.1 logged out from UPS [Energenie]
601.681025 Signal 15: exiting
601.682220 [D1] driver_free: forgetting UPS [Energenie] (FD 4)
Network UPS Tools upsd 2.8.1

[jimklimov]

On one hand, NUT v2.8.1 is a bit old. Not extremely, but a couple of years behind evolution.

On another, HA and its addon are independent projects, so you may have to ask their communities about getting newer NUT there. Also check our wiki, there was a page about how someone built their own update.

If the ups.conf file is available, feed debug_min 6 into it, so the log could display more details about what it found. Maybe the driver works and it is HA part that does not pass something?..

Oddly, both Gembird and Energenie are names I heard of, but are not seen in NUT drivers nor DDL/HCL; oddly even the issue tracker can't see them. Not my day I guess :)

[Onxr]

@jimklimov

Oddly, both Gembird and Energenie are names I heard of, but are not seen in NUT drivers nor DDL/HCL; oddly even the issue tracker can't see them. Not my day I guess :)

IIRC I also didn't found my UPS when checking supported UPS list. But it works.

@tislar
If I am not wrong HomeAssistant addons are just container and I'm not sure if it uses docker or any other container technology.

Recently I had issues when setting up NUT. When I was looking online I found many user mentioning to use NUT bare metal. To be specific, install NUT on the host os where you have connected your USB. For many this solved the issue. Then you can install NUT in other guest OS or container.

Are you running Home Assistant OS bare metal or a VM ?

[jimklimov]

My take is that in a container it can help with monitoring, but not so much with (bare-metal) shutdown and UPS power off/cycle, power race avoidance, etc.

[tislar]

I am running ha on bare metal. So it is only os running on this machine. I guess I do not have enough of computer knowledge to solve this. I will try to run it on docker container in synology, to see if it funds it. I tried before with built in ups support for synology bit it does not comunicate either, i guess it is not supported.

[Onxr]

I am running ha on bare metal. So it is only os running on this machine. I guess I do not have enough of computer knowledge to solve this. I will try to run it on docker container in synology, to see if it funds it. I tried before with built in ups support for synology bit it does not comunicate either, i guess it is not supported.

If you can, try to install in a host OS for once. No container or VM. If you don't want to install in your in prod hosts then get a ventoy drive and boot into a live USB and test there.