<div dir="ltr"><div>Cheers,</div><div><br></div><div>  What NUT version is involved? Per `nut-driver@ups1` I suppose it is some v2.8.x, and reports like <a href="https://github.com/networkupstools/nut/pull/638">https://github.com/networkupstools/nut/pull/638</a> and <a href="https://github.com/networkupstools/nut/issues/674">https://github.com/networkupstools/nut/issues/674</a> suggest the needed support was merged before v2.8.0, so that should suffice.</div><div>
<div><br></div><div>  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.</div><div><br></div><div>  One of those discussions starts with a "<code class="gmail-notranslate">Device not supported</code>" 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 <a href="https://github.com/networkupstools/nut/pull/638#issuecomment-443558510">https://github.com/networkupstools/nut/pull/638#issuecomment-443558510</a> - notably there's a sleep involved before the device returns valid info; maybe your device or its firmware needs a longer one or something?</div>

<br></div><div>  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 <a href="https://github.com/networkupstools/nut/pull/638/changes#diff-cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-R696">https://github.com/networkupstools/nut/pull/638/changes#diff-cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-R696</a></div><div><br></div><div>  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. 
<pre class="gmail-notranslate"><code class="gmail-notranslate">nutdrv_qx -a ups1 -d 1 -DDDDDD</code></pre>

</div><div>  If there would be a long wall of text, maybe follow up with that as a new GitHub issue?</div><div><br></div><div>Hope this helps,</div><div>Jim Klimov</div><div><br></div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Dec 17, 2025 at 8:23 AM Stephen Davies via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">According to the support list, the Digitech 650VA UPS is supported but <br>
when I try to connect to my unit, I get:<br>
nut-driver@ups1[357464]: Device not supported!<br>
<br>
My ips.conf has:<br>
[ups1]<br>
driver = nutdrv_qx<br>
port = auto<br>
vendorid=0001<br>
productid=0000<br>
protocol=hunnox<br>
novendor<br>
noscanlangid<br>
<br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>