Tecnoware Era Plus 2000

[Alfatango12]

I have two ups tecnoware era plus 1500 that works well with both blazer_usb and nutdrv_qx driver. I have also a tecnoware era plus 2000 that works only with nutdrv_qx. The output of upsc for the 1500 looks like this:

battery.charge: 100
battery.voltage: 13.6
battery.voltage.high: 13.00
battery.voltage.low: 10.40
battery.voltage.nominal: 12.0
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: nutdrv_qx
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.state: quiet
driver.version: 2.8.1
driver.version.data: Voltronic-QS 0.09
driver.version.internal: 0.36
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.voltage: 226.5
input.voltage.fault: 226.5
output.current.nominal: 3.0
output.frequency: 50.0
output.frequency.nominal: 50
output.voltage: 226.5
output.voltage.nominal: 230
ups.beeper.status: disabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware.aux: PM-V
ups.load: 30
ups.productid: 5161
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0665

The output of upsc for the 2000 is:

battery.voltage: 27.10
device.type: ups
driver.name: nutdrv_qx
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.version: 2.8.0
driver.version.data: Q1 0.07
driver.version.internal: 0.32
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.frequency: 50.0
input.voltage: 221.8
input.voltage.fault: 221.8
output.voltage: 221.8
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 2
ups.productid: 0000
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0001

As you can see all the battery related "values" aren't shown (especially the battery charge).
Are there a way to get the driver read those values? I don't think it would be so difficult because the ups are basically the same, but with different battery.
I can provide logs and test eventual changes since I have the device.

Edit 1:
When I start with sudo upsdrvctl start on the tecnoware 2000 it seas Can't autodetect number of battery packs [-1/27.00] Battery runtime will not be calculated (runtimecal not set).

[jimklimov]

Can you check if NUT 2.8.1 (or a build of master) behaves differently yet? Maybe #1692 (IIRC OTOH) is related.
UPDATE: #1652 is the relevant one for nutdrv_qx

[Alfatango12]

Oh I've just noticed that on Manjaro Arm (I'm running nut on a rpi) the package version is 2.8.0 and not 2.8.1 as I thought. This evening when I'll be at home I'll try the last version.

[Alfatango12]

Ok so I've installed the latest version from Manjaro testing branch but nothing changed.
Output of sudo upsdrvctl start

Network UPS Tools - UPS driver controller 2.8.1
Network UPS Tools - Generic Q* USB/Serial driver 0.36 (2.8.1)
USB communication driver (libusb 1.0) 0.46
Duplicate driver instance detected (PID file /run/nut/nutdrv_qx-tecnowaremansarda.pid exists)! Terminating other driver!
Using protocol: Q1 0.08
Can't autodetect number of battery packs [-1/27.10]
Battery runtime will not be calculated (runtimecal not set)

and upsc

battery.voltage: 27.1
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: nutdrv_qx
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.state: quiet
driver.version: 2.8.1
driver.version.data: Q1 0.08
driver.version.internal: 0.36
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.frequency: 50.1
input.voltage: 222.3
input.voltage.fault: 222.3
output.voltage: 222.3
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 20
ups.productid: 0000
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0001

[jimklimov]

This seems related to #1652 (relatively recent changes in just this area) and to an extent to #2267 (as a report of similar difference of driver behaviors).

Running the two drivers with raised debug verbosity (see e.g. https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity article) could help discern the issue better.

I think the battery.charge is derived from battery.voltage (unless reported directly by a device), and maybe 27.1V does not fall into any bucket of predefined min/max ranges for auto-detection (e.g. looks to human eye like a nominal 24V as a 2*12V PbAc pack).

FWIW, the report for "1500" model states a 13.6 in similar case (for 2x cells would be ~27.2), so not sure ATM if the value is so "out of range" as to matter here, or is okay in this regard.

Debug log would show some decisions made early in driver init...

[Alfatango12]

Thanks a lot for the responce, I thought that the issue would have been forgotten between other issues. I'm a bit busy this week but I'll definitely dive into it this weekend to provide all the logs.

[DjMayone]

Does the problem with Tecnoware 2000 was solved? I have the same UPS and not reporting too.

[jimklimov]

@DjMayone : did you check with a recent NUT release? What exactly does the driver debug log say?

[DjMayone]

I've added NUT add-on to my homeassistant. UPS is recognized but, in the log, I've a couple of errors:

• Battery runtime will not be calculated (runtimecal not set)
• 0.000000 fopen /run/nut/upsmon.pid: No such file or directory
  0.000022 Could not find PID file to see if previous upsmon instance is already running!

I think Era Plus 2000 is not in NUT database...
Could please help to configure it in the best way?
Thank you!

[jimklimov]

The fopen part is okay - it means no competing older instance of the driver was running. It should be quieter in new NUT builds (currently on master, not in a release yet). With the explanation on second line it is already friendlier than it was for ages before :)

For runtimecal explanation see the driver man page, e.g. at https://networkupstools.org/docs/man/nutdrv_qx.html - not sure how it can be passed from HA configuration (if its YAML limits the keywords or not).