Thanks for the feedback.
The NUT vwersion is 2.8.2.1.
I am in the process of building a new Rocky Linux 10 server after my old
Centos 7 server died.
The old box used upsSmart to access the UPS but that relies on an X
server and does not work on ocky 10.
One of the errors from your suggested test is:
Can't open /run/nut/nutdrv_qx-ups1: No such file or directory
I had "langid_fix=0x0409" in ups.conf but nut-driver complained so I
removed it.
Cheers,
Stephen
On 17/12/25 18:47, Jim Klimov wrote:
Cheers,
What NUT version is involved? Per `nut-driver@ups1` I suppose it is
some v2.8.x, and reports like https://github.com/networkupstools/nut/
pull/638 <https://github.com/networkupstools/nut/pull/638> and https://
github.com/networkupstools/nut/issues/674 <https://github.com/
networkupstools/nut/issues/674> suggest the needed support was merged
before v2.8.0, so that should suffice.
It may well be that the manufacturer moved on and stamped the same
label onto a completely unrelated device (or firmware), these things
sadly tend to happen as products evolve.
One of those discussions starts with a "|Device not supported|"
initially, but then it gets found "after opening and then closing the
OEM software" (UPSmart), and apparently by the end of the ticket they
got it working right away. The new hunnox subdriver introduced in PR 638
changed the initialization to work with that, per https://github.com/
networkupstools/nut/pull/638#issuecomment-443558510 <https://github.com/
networkupstools/nut/pull/638#issuecomment-443558510> - notably there's a
sleep involved before the device returns valid info; maybe your device
or its firmware needs a longer one or something?
Compared to settings in those tickets and HCL, your setup misses a
`langid_fix=0x0409` line, not sure if that makes the difference. This
seems to be a hardcoded default in hunnox_protocol() initializer at
https://github.com/networkupstools/nut/pull/638/changes#diff-
cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-
R696 <https://github.com/networkupstools/nut/pull/638/changes#diff-
cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-R696>
Can you start the driver with higher verbosity to collect what/how it
probes of the device, and how that fails (with what errors), e.g.
|nutdrv_qx -a ups1 -d 1 -DDDDDD|
If there would be a long wall of text, maybe follow up with that as a
new GitHub issue?
Hope this helps,
Jim Klimov
On Wed, Dec 17, 2025 at 8:23 AM Stephen Davies via Nut-upsuser <nut-
[email protected] <mailto:nut-upsuser@alioth-
lists.debian.net>> wrote:
According to the support list, the Digitech 650VA UPS is supported but
when I try to connect to my unit, I get:
nut-driver@ups1[357464]: Device not supported!
My ips.conf has:
[ups1]
driver = nutdrv_qx
port = auto
vendorid=0001
productid=0000
protocol=hunnox
novendor
noscanlangid
_______________________________________________
Nut-upsuser mailing list
[email protected] <mailto:Nut-upsuser@alioth-
lists.debian.net>
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser>
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
