Added support for LYONN CTB-800V #230

marianojan · 2015-08-22T18:23:07Z

Small protocol validation change to add support for the protocol used by the LYONN CTB-800V UPS.

MAINTAINER NOTE: While this PR was not merged as such, its/follow-up commits were - e.g. 62b5e25 (bumping subdriver version to 0.06) ... but later overridden by 618ecb7 (ver 0.10), in particular losing support for the two-char last token, it seems... So I am not sure if this model and its protocol dialect remains supported by the driver as of NUT v2.8.2.

Small protocol validation change to add support for the protocol used by the LYONN CTB-800V UPS.

zykh · 2015-08-22T21:37:37Z

drivers/nutdrv_qx_voltronic-qs-hex.c

@@ -75,6 +75,7 @@ static item_t	voltronic_qs_hex_qx2nut[] = {
 	/* Query UPS for status
 	 * > [QS\r]
 	 * < [#6C01 35 6C01 35 03 519A 1312D0 E6 1E 00001001\r]	(after being preprocessed)
+	 *   [#6901 6c 6802 6c 00 5fd7 12c000 e4 1e 00001001 02] (this is the answer of the LYONN CTB-800v)


The answer should be CR-terminated (and I'd prefer the following bracket-enclosed comment to be separated by a tab and the comment on the previous line to be aligned with it):

* < [#6C01 35 6C01 35 03 519A 1312D0 E6 1E 00001001\r] (after being preprocessed) * [#6901 6c 6802 6c 00 5fd7 12c000 e4 1e 00001001 02\r] (this is the answer of the LYONN CTB-800v)

zykh · 2015-08-22T21:41:54Z

Thanks for the patch.

Apart from the in-source comments, just a couple of things:

Are the length of the answer and the number of tokens always the same?
If so, I would prefer the check to be a bit more strict, like this:

if (
    token < 10 ||
    token > 11 ||
    (token == 10 && strlen(refined) != 46) ||
    (token == 11 && strlen(refined) != 48)
) {

Did you have a chance to understand what the final token means?
Remember to increase version number.

Also, can you provide ups{c,cmd,rw} output?
Do all the values look correct and correctly scaled?
Do the commands work as expected?

zykh · 2015-08-22T21:56:19Z

oops.. forgot a thing...

Commit message, in order to give it some context, should read something like this:

nutdrv_qx: add support for LYONN CTB-800V

Small protocol validation change in 'voltronic-qs-hex' subdriver to add support for the protocol used by the LYONN CTB-800V UPS.

marianojan · 2015-08-23T15:43:42Z

Thank you for the suggestions! I will correct the issues.

The length of the answer and the number of tokens are always the same. I will correct the check to be more strict as per your recommendation.
I've been doing some tests but couldn't figure what the final "02" means. It seems to be a fixed number.

The ups{c,cmd,rw} output should be pushed to nut-ddl? here in a comment? somewhere else?

The values all look correct. The device has a screen and the reported values are the same. I checked with a tester also, and the voltages are correct. I couldn't fully test the load percentage yet, but it seems correct.

I tested the commands. The load can be turned immediately off, and the delayed shutdown commands work as expected. The test also works ok. The only thing that doesn't work is the load.on. It seems that when the load is turned off, the UPS shuts down itself (or the communication circuits).

Thanks again for all the comments and suggestions, I'm fairly new to helping in Open Source projects, so any comments (and a little bit of patience) are greatly appreciated.

zykh · 2015-08-24T23:29:46Z

The ups{c,cmd,rw} output should be pushed to nut-ddl? here in a comment?

Wherever you prefer, but if you decide to go DDL, then make sure to:

use the right syntax;
report your above comments (load.on/load.off), possibly tagging load.on as BAD;
adopt the right name;
follow the commit message pattern already in place.

Small protocol validation change in 'voltronic-qs-hex' subdriver to add support for the protocol used by the LYONN CTB-800V UPS.

Protocol: 'voltronic-qs-hex' Reference: networkupstools#230

zykh · 2015-10-06T22:01:17Z

@marianojan, sorry for the long hiatus - I didn't notice your new commit. It's now merged.
I'm closing this PR, if/when you want to report your ups{c,cmd,rw} data either open a new pull request on nut-ddl or mail the list.

marianojan · 2015-10-07T02:35:05Z

@zykh nevermind! I also forgot about the data. I will open a pull request in a few days.
Have a nice day! And thanks for all your help.

Notable changes: * GPLv2 or GPLv3 as license; * c++ lang addition; * upsdrvctl moved from libexec/ to sbin/ (thanks systemd), reflect this change in rc.d script; * the timeout patch (patch-ab) has been implemented differently, but an error message has been left out. Move it to patch-snmp-error-msg.c; * tiff buildlink3 for ups-nut-cgi required (in addition to gd). Changelog: (lengthy -- if truncated please refer to): http://www.networkupstools.org/source/2.7/ChangeLog 2016-03-09 Arnaud Quette <[email protected]> * configure.ac: Fix autoreconf on Debian For some reason, Automake doesn't search the current directory correctly when searching for helper scripts, when 'nut' is running as a git-submodule, as it is the case with the website repository * configure.ac: update version to 2.7.4 * drivers/apc-ats-mib.c: snmp-ups: add APC ATS input.source * drivers/snmp-ups.c: snmp-ups: fix the matching OID tests For both sysOID and classic methods, we used to test one of the two OIDs provided in the mib2nut structures. However, these two OIDs (oid_pwr_status and oid_auto_check) tend to be redundant and confusing. Replace these matching by an extraction of {ups,device}.model * drivers/nut-libfreeipmi.c: nut-ipmipsu: fix compilation warnings * NEWS, UPGRADING, docs/FAQ.txt, docs/net-protocol.txt, docs/new- drivers.txt, docs/nut-names.txt, docs/nutdrv_qx-subdrivers.txt, docs/packager-guide.txt, docs/snmp-subdrivers.txt, lib/README, scripts/augeas/README: Fix spelling and typo errors Following the spell-checking scope expansion, do a spell-checking pass * docs/documentation.txt: Update documentation as per the new devices scope * docs/features.txt, docs/user-manual.txt: Update documentation as per the new devices scope * docs/Makefile.am: Expand spell-checking scope Add more documents, outside of the docs/ directory Closes: https://github.com/networkupstools/nut/issues/222 2016-03-08 Arnaud Quette <[email protected]> * configure.ac, tools/Makefile.am, tools/driver-list-format.sh: Check driver.list[.in] format at make dist time Instead of checking driver.list.in at configure time, move the checking and modification into a script that is called at make dist time. The script can also be called manually, and will try to fix both driver.list.in and driver.list 2016-03-07 Arnaud Quette <[email protected]> * drivers/powerware-mib.c: Remove an erroneous test This was made test the enumerated values registration in snmp-ups, and should not have been committed * data/driver.list.in: HCL: APC ATS AP7724 supported by snmp-ups These Automatic Transfer Switch should be supported by snmp-ups, however this was not tested at all Reference: https://github.com/networkupstools/nut/issues/260 * NEWS, UPGRADING: Update for release 2.7.4 * drivers/Makefile.am, drivers/apc-ats-mib.c, drivers/apc-ats-mib.h, drivers/snmp-ups.c: snmp-ups: support APC Automatic Transfer Switch Following the recent extension of NUT scope and variable namespace, to support Automatic Transfer Switch (ATS), implement SNMP support for APC ATS (with help from "maaboo" through github) Reference: https://github.com/networkupstools/nut/issues/260 2016-03-04 Arnaud Quette <[email protected]> * drivers/baytech-mib.c, drivers/bestpower-mib.c, drivers/compaq- mib.c, drivers/cyberpower-mib.c, drivers/eaton-mib.c, drivers/mge- mib.c, drivers/netvision-mib.c, drivers/powerware-mib.c, drivers /raritan-pdu-mib.c: snmp-ups: fix mib2nut structures Non existent OIDs, for testing MIB selection, must be expressed as NULL and not as empty string ("") for the algorithm to work 2016-03-03 Daniele Pezzini <[email protected]> * docs/download.txt: docs: update several download links 2016-03-03 Arnaud Quette <[email protected]> * docs/man/upsrw.txt, docs/net-protocol.txt: Clarification on NUMBER type float values Clarify a bit more documentation on how to express float values, when using upsrw. That is to say, using decimal (base 10) english-based representation, so using a dot, in non-scientific notation. So hexadecimal, exponents, and comma for thousands separator are forbiden * clients/upsrw.c, docs/net-protocol.txt, server/netget.c: Prefer NUMBER to NUMERIC for variable type As per discussion on the Github pull request, NUMBER would be more suitable than NUMERIC 2015-11-22 Daniele Pezzini <[email protected]> * drivers/nutdrv_qx.c: nutdrv_qx: increase timeouts in 'sgs' USB subdriver Apparently the previously used timeouts in the 'sgs' USB subdriver were not always enough, so increase them. 2015-11-11 Daniele Pezzini <[email protected]> * data/driver.list.in: HCL: various TS Shara UPSes supported by nutdrv_qx Protocol: 'megatec' USB subdriver: 'sgs' * drivers/nutdrv_qx.c: nutdrv_qx: make sure 'sgs' USB subdriver uses only what it reads Since, in 'sgs' USB subdriver, we read only 8 bytes at a time and we expect the first byte to tell us the length of the data that follows, make sure we don't use more than what we read from the device in case the first byte is not what we expect it to be. 2015-03-04 Daniele Pezzini <[email protected]> * drivers/nutdrv_qx.c: nutdrv_qx: increase verbosity of 'sgs' USB subdriver In 'sgs' USB subdriver: - be more verbose when debugging, - always print the return code when dealing with an error. 2014-01-31 Daniele Pezzini <[email protected]> * docs/man/nutdrv_qx.txt: nutdrv_qx: update man page for new 'sgs' USB subdriver 2014-01-31 Ronaldo Yamada <[email protected]> * drivers/nutdrv_qx.c: nutdrv_qx: add new 'sgs' USB subdriver to support TS Shara units 2016-03-02 Arnaud Quette <[email protected]> * data/driver.list.in: HCL: added Eaton Powerware 9125-5000g Supported with the additional USB card, with the bcmxcp_usb driver * docs/man/upsrw.txt, docs/net-protocol.txt: Clarification on NUMERIC type float values Clarify documentation on how to express float values, when using upsrw. That is to say, using decimal english- based representation, so using a dot * drivers/mge-xml.c: netxml-ups: fix Eaton XML published data Some raw protocol data were wrongly published, and are now commented. Also add some R/W flags to ambient thresholds Closes: https://github.com/networkupstools/nut/issues/201 * tools/nut-scanner/nut-scanner.c: nut-scanner: fix thread attachment Add a test to have the right thread waiting for the scan to be complete (patch from Michal Hlavinka, Red Hat) * configure.ac, tools/nut-scanner/nutscan-init.c, tools/nut- scanner/scan_avahi.c, tools/nut-scanner/scan_ipmi.c, tools/nut- scanner/scan_nut.c, tools/nut-scanner/scan_snmp.c, tools/nut- scanner/scan_usb.c, tools/nut-scanner/scan_xml_http.c: nut-scanner: don't depend on development libraries nut-scanner was previously trying to use directly libXXX.so (libusb-0.1, libfreeipmi, libnetsnmp, libavahi-client, libneon, libupsclient}. However, these files are generally provided by the development packages. nut- scanner now tries to look at some known paths, including the one provided through --libdir, to find the correct libraries Closes: https://github.com/networkupstools/nut/issues/233 2016-03-01 Arnaud Quette <[email protected]> * clients/upsrw.c, docs/net-protocol.txt, server/netget.c: Default to type NUMERIC for variables Any variable that is not STRING, RANGE or ENUM is just a simple numeric value. The protocol documentation (net-protocol.txt) was previously stating that "The default <type>, when omitted, is integer." which was not fully true, since a variable could also be a float. Hence, the wording was changed to advertise this, and that each driver is then responsible for handling values as either integer or float. Moreover, instead of returning a TYPE "UNKNOWN", return "NUMERIC", which is more suitable, and aligned with the NUT protocol specification * tools/nut-snmpinfo.py: SNMP subdriver generator: fix output formatting * tools/nut-snmpinfo.py: SNMP subdriver generator: discard commented lines Discard any commented mib2nut_info_t declaration, which should thus not be taken into account 2016-02-26 Arnaud Quette <[email protected]> * data/driver.list.in, drivers/Makefile.am, drivers/eaton-ats-mib.c, drivers/eaton-ats-mib.h, drivers/snmp-ups.c: snmp-ups: support Eaton Automatic Transfer Switch Following the recent extension of NUT scope and variable namespace, to support Automatic Transfer Switch (ATS), implement SNMP support for Eaton ATS. Note that this device can also be supported through Eaton XML/PDC (XML over HTTP) protocol, supported by the NUT netxml-ups driver * data/cmdvartab, docs/nut-names.txt: Extend namespace for Automatic Transfer Switch (ATS) Extend NUT namespace to support a new type of power device: ATS - Automatic Transfer Switch. These devices are used to setup 2 power systems, such as UPS, to power a single power supply system, and be able to automatically transfer between the input sources in case of failure of the primary one. The added variable are for now limited to 'input.source' and 'input.source.preferred', but may be extended if needed 2016-02-25 C Fraire <[email protected]> * docs/scheduling.txt: Fix docs location of upssched to sbin 2016-02-25 Arnaud Quette <[email protected]> * scripts/subdriver/gen-snmp-subdriver.sh: snmp-ups: add the last missing element in the structure * drivers/apc-mib.c, drivers/bestpower-mib.c, drivers/compaq-mib.c, drivers/cyberpower-mib.c, drivers/delta_ups-mib.c, drivers/huawei- mib.c, drivers/ietf-mib.c, drivers/mge-mib.c, drivers/netvision- mib.c, drivers/powerware-mib.c, drivers/xppc-mib.c, scripts/subdriver/gen-snmp-subdriver.sh: snmp-ups: fix values lookup terminating element The terminating element should really be NULL, and not the string "NULL", as it was originally done, back in 2002 * drivers/snmp-ups.c: snmp-ups: revert order of the NULL/"NULL" test Fix a segfault when doing first the string comparison test * drivers/snmp-ups.c: snmp-ups: register values enumerations Whenever there is a values lookup structure for read/write data, push the values as enumerations for upsrw * drivers/snmp-ups.c: snmp-ups: try to lookup values for numeric elements Numeric elements can also use the value resolution mechanism * drivers/snmp-ups.c: snmp-ups: counter test sysOID with a test OID Some devices have buggy sysOID exposed. Allow to counter test another OID, to be able to select between different mapping structures 2016-02-24 Arnaud Quette <[email protected]> * scripts/subdriver/gen-snmp-subdriver.sh: SNMP subdriver creation script: allow sysOID override Allow to use -s to override buggy sysOID in some device FW. In this case, the sysOID entry in the mib2nut structure should be set to NULL 2016-02-11 Arnaud Quette <[email protected]> * drivers/raritan-pdu-mib.c: snmp-ups: fix macaddr support for Raritan PDU Raritan MIB was fixed to expose macaddr on device.macaddr instead of ups.macaddr * drivers/baytech-mib.c: snmp-ups: fix macaddr support for Baytech PDU Baytech MIB was fixed to expose macaddr on device.macaddr instead of ups.macaddr * drivers/eaton-mib.c: snmp-ups: fix and complete macaddr support for Eaton Eaton G2 and G3 can now expose the MAC address of the device, using device.macaddr. Eaton G1 Aphel was fixed to expose this data on device.macaddr instead of ups.macaddr * drivers/snmp-ups.c: snmp-ups: add support for hexadecimal octet strings * drivers/snmp-ups.c: snmp-ups: fallback for classic MIB detection If the sysOID matching has failed, then snmp-ups uses ups.model to get an OID to test. In case ups.model is not available, fallback to trying to use device.model instead * docs/images/nut_layering.png, docs/images/nut_layering.svg: Refresh and complete NUT architecture diagram 2016-02-08 Arnaud Quette <[email protected]> * drivers/powerware-mib.c: snmp-ups: extend Eaton 3ph outputSource values map Add the new status values for xupsOutputSource (.1.3.6.1.4.1.534.1.4.5.0), that maps to both ups.status and ups.type 2016-02-03 Arnaud Quette <[email protected]> * drivers/powerware-mib.c: snmp-ups: improve support for Eaton 3ph Improve support for temperature and humidity data, including: - ups.temperature now available - fixing ambient.temperature (previously pointing at a wrong OID) - ambient.humidity now available - the following settings now available: * ups.temperature.low * ups.temperature.high * ambient.humidity.high * ambient.humidity.low * ambient.temperature.high * ambient.temperature.low 2016-02-01 Daniele Pezzini <[email protected]> * data/driver.list.in: HCL: various APCUPSD-controlled APC devices via apcupsd-ups Originally reported by GitHub user @Thermionix. Reference: https://github.com/networkupstools/nut/pull/215 2016-01-31 Charles Lepple <[email protected]> * docs/man/nutdrv_atcl_usb.txt: man/nutdrv_atcl_usb: point to nutdrv_qx (fuji) for 0001:0000 Also update best guess for the USB- to-serial converter situation. * docs/FAQ.txt: FAQ: udevadm for fixing permissions 2016-01-30 Charles Lepple <[email protected]> * drivers/nut-libfreeipmi.c: FreeIPMI: do not split function arguments with a conditional Alternate approach to suggestion by Romero B. de S. Malaquias Closes: https://github.com/networkupstools/nut/pull/250 2016-01-24 Charles Lepple <[email protected]> * docs/config-notes.txt: Documentation: fix formatting Put syntax examples in verbatim mode, and remove spaces from ends of lines. * drivers/apc-hid.c: usbhid-ups: handle missing USB strings in APC code Closes: https://github.com/networkupstools/nut/issues/258 Might fix: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1483615 2016-01-23 Charles Lepple <[email protected]> * data/driver.list.in: HCL: added NHS Laser Senoidal 5000VA Source: http://article.gmane.org/gmane.comp.monitoring.nut.devel/7123 Closes: https://github.com/networkupstools/nut/issues/254 2016-01-14 Arnaud Quette <[email protected]> * drivers/snmp-ups.c: snmp-ups: fix staleness detection With some ePDUs or devices using template for outlet and outlet.group, communication loss with the device were not detected, due to the handling mechanism. Simply skipping commands for templates, after the init time, is sufficient to avoid this issue 2016-01-05 Arnaud Quette <[email protected]> * drivers/snmp-ups.c: snmp-ups: improve stale communication recovery Disable the 10 iterations to retry communicating with stale device. This was leading up to 10 x 30 seconds, so 5mn, before being able to get data again * docs/new-drivers.txt, docs/nut-names.txt: Document battery.charger.status This will in time replace the historic CHRG and DISCHRG flags published in ups.status. Closes https://github.com/networkupstools/nut/issues/196 2016-01-03 Charles Lepple <[email protected]> * data/driver.list.in: HCL: Sweex model P220 via blazer_usb Reference: https://github.com/networkupstools/nut/issues/251 2016-01-04 Arnaud Quette <[email protected]> * drivers/ietf-mib.c, drivers/ietf-mib.h, drivers/snmp-ups.c: snmp- ups: add support for Tripplite units on IETF mib These devices expose ".1.3.6.1.4.1.850.1", which could be supported through this specific MIB. For now, just link that to the IETF MIB, to provide a first level of support Reference: https://github.com/networkupstools/nut/issues/171 2015-12-30 Arnaud Quette <[email protected]> * configure.ac: First stab at checking driver.list.in format 2015-12-29 Charles Lepple <[email protected]> * scripts/upower/95-upower-hid.rules: upower: update for AEG 2015-12-29 Arnaud Quette <[email protected]> * drivers/powercom.c: Fix the processing of output voltage for KIN units The processing of output voltage requires to also take into account the line voltage, as reported by Patrik Dufresne. This may still need some further adjustments Reference: https://github.com/networkupstools/nut/issues/187 * drivers/powercom.c: Fix the processing of input voltage for KIN units The processing of input voltage requires to also take into account the line voltage, as reported by Patrik Dufresne. Also bump the driver version to 0.16, since 0.15 was already used, but not set Reference: https://github.com/networkupstools/nut/issues/187 * drivers/mge-hid.c: Fix letter case for AEG USB VendorID The letter case of this VendorID may be important for generated files, such as the udev ones (reported by Charles Lepple) 2015-12-28 Arnaud Quette <[email protected]> * data/driver.list.in, drivers/mge-hid.c: HCL: AEG PROTECT B / NAS supported by usbhid-ups Reference: https://github.com/networkupstools/nut/issues/249 2015-12-17 Daniele Pezzini <[email protected]> * data/driver.list.in: HCL: Legrand Keor Multiplug supported by nutdrv_qx Reference: https://github.com/networkupstools/nut/issues/248 2015-12-09 Andrey Jr. Melnikov <[email protected]> * drivers/bcmxcp_usb.c: Don't call usb_close() after reset 2015-12-08 Andrey Jr. Melnikov <[email protected]> * drivers/bcmxcp_usb.c: Call usb_reset() when driver unable to claim device * drivers/bcmxcp.h, drivers/bcmxcp_usb.c: Refactor get_answer() routine, make it properly deal with multi-packets responses. Lower stack usage. 2015-07-27 Daniele Pezzini <[email protected]> * common/common.c, common/str.c, drivers/bcmxcp.c, drivers/blazer.c, drivers/blazer_ser.c, drivers/blazer_usb.c, drivers/libhid.c, drivers/mge-xml.c, drivers/nutdrv_qx.c, drivers/powerp-bin.c, drivers/powerp-txt.c, drivers/powerpanel.c, drivers/tripplitesu.c, drivers/upscode2.c, include/common.h, include/str.h, server/upsd.c, tools/nut-scanner/scan_usb.c: common: consolidate some string- related functions Move *trim*() functions from common to str. Prepend the 'str_' common prefix. Bailout early if string is NULL or empty. In *trim_m() functions, make sure the string containing characters to be removed is not NULL and bailout early if empty. Add new str_trim[_m]() functions to remove both leading and trailing characters at the same time. Update all the tree accordingly; versioning where appropriate. * common/Makefile.am, common/str.c, include/Makefile.am, include/common.h, include/str.h: common: add some string-related functions 2015-11-10 Charles Lepple <[email protected]> * data/driver.list.in: HCL: Electrys UPS 2500 (nutdrv_qx and blazer_ser) Closes https://github.com/networkupstools/nut/issues/241 * data/driver.list.in: HCL: Eaton E Series DX UPS 1-20 kVA uses blazer_ser Closes https://github.com/networkupstools/nut/issues/238 2015-11-09 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: snmp-ups: add number of outlets in Eaton ePDU groups * docs/nut-names.txt: Add a variable for the number of outlets in a group Added 'outlet.group.n.count' which provides the number of outlets in the outlet group 'n' 2015-11-06 Daniele Pezzini <[email protected]> * drivers/nutdrv_qx_voltronic-qs.c: nutdrv_qx: update 'voltronic-qs' subdriver Since, for devices supported by 'voltronic-qs' subdriver, in reality: - invalid commands or queries are echoed back, - accepted commands are followed by action without any further reply, update the subdriver interface accordingly. Also: - change slightly the way we publish protocol as ups.firmware.aux, - update F's reply examples and some info_type (ratings; output.frequency) in QX to NUT table to reflect reality, - increase version number. 2015-10-19 Daniele Pezzini <[email protected]> * drivers/nutdrv_qx_voltronic-qs-hex.c: nutdrv_qx: improve 'T' protocol support in 'voltronic-qs-hex' subdriver Since the last byte of the reply to the QS query (before the trailing CR) of devices that implement the 'T' protocol holds in reality ratings informations (nominal output frequency/voltage and nominal battery voltage) in its bits, change the 'voltronic-qs-hex' subdriver accordingly. Also: - change slightly the way we publish protocol as ups.firmware.aux, - increase version number. * drivers/nutdrv_qx_voltronic-qs-hex.c: nutdrv_qx: simplify {in,out}put voltage conversion in 'voltronic-qs-hex' In 'voltronic-qs-hex' subdriver, instead of calculating separately the fractional and integer part of input and output voltage, do it at once. Also, increase version number. * drivers/nutdrv_qx_voltronic-qs-hex.c: nutdrv_qx: improve protocol identification in 'voltronic-qs-hex' Since 'V' protocol, in reality, never happens to use the encoded version of the reply to the QS query, but it always uses the plain version already implemented in 'voltronic-qs' subdriver, remove it from the identification process of 'voltronic-qs-hex' subdriver. Also, remove some non-significant entries from the testing table and increase version number. * drivers/nutdrv_qx_voltronic-qs-hex.c: nutdrv_qx: harmonize declarations/definitions in 'voltronic-qs-hex' In 'voltronic-qs- hex' subdriver, the scope of support functions is limited to the subdriver as rightly stated in forward declarations, so correct their definitions to reflect that. Also, increase version number. 2015-10-09 Arnaud Quette <[email protected]> * docs/nut-qa.txt: Reference Black Duck OpenHUB in QA documentation Closes networkupstools/nut#192 2015-10-08 Arnaud Quette <[email protected]> * drivers/snmp-ups.c: snmp-ups: also use __func__ for additional traces * drivers/powerware-mib.c: powerware-mib: more comments for RFC device.event Add more comments on the need to RFC device.event for some data that are currently published under ups.alarm * drivers/powerware-mib.c: snmp-ups: improve Eaton 3-phase UPS alarms reporting Eaton 3phase UPS, using the Powerware MIB, can expose many new alarms. Also use the standard driver "X.YY" versioning, and bump subdriver release to "0.85" * drivers/snmp-ups.c, drivers/snmp-ups.h: snmp-ups: fix and improve the ups.alarms mechanism This mechanism allows to walk a subtree (array) of alarms, composed of OID references. The object referenced should not be accessible, but rather when present, this means that the alarm condition is TRUE. Both ups.status and/or ups.alarm values can be provided * drivers/snmp-ups.c: snmp-ups: fix on some snprintf calls Some snprintf calls are using dynamically allocated variables, which doesn't work with sizeof * drivers/snmp-ups.c: snmp-ups: use __func__ in debug messages * drivers/snmp-ups.c: snmp-ups: nut_snmp_get_oid() returns TRUE on success * drivers/snmp-ups.c: snmp-ups: only use snprintf calls instead of sprintf * drivers/eaton-mib.c, drivers/snmp-ups.c: snmp-ups: simplify handling of other alarms outlet, outlet groups and phase alarms are now using a simplified approach that does not require specific lookup structure to adapt alarm messages. This applies to Eaton ePDU G2/G3 2015-09-22 Arnaud Quette <[email protected]> * drivers/snmp-ups.c: snmp-ups: fix a typo error in debug message Unknown is spelled with an ending N (reported by Evgeny "Jim" Klimov, from Eaton) * drivers/snmp-ups.c: snmp-ups: optimize phase number extraction efficiency Since we know that we are processing an alarm for a phase "Lx", don't use strchr, but simply index (reported by Evgeny "Jim" Klimov, from Eaton) * docs/nut-names.txt, drivers/eaton-mib.c: snmp-ups: use dash- separator for out-of-range For the sake of coherence with other status relative to thresholds, "out of range" frequency status now also use dash as separator, instead of space * drivers/eaton-mib.c: Fix a spelling error in comments * drivers/eaton-mib.c: snmp-ups: fix a typo error on Eaton ePDU G2/G3 MIB Critical is really spelled critical, and not cricital, as used in the various status thresholds value-lookup structures (reported by Evgeny "Jim" Klimov, from Eaton) * data/cmdvartab: Mention the unit for ambient humidity information Add an explicit mention that ambient information related to humidity use the "(percent)" unit * data/cmdvartab, docs/nut-names.txt: Mention the unit for input voltage information Add an explicit mention that input information related to voltage use the "Volts (V)" unit * data/cmdvartab: Mention the unit for ambient temperature information Add an explicit mention that ambient information related to temperature use the "degrees C" unit 2015-09-18 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: snmp-ups: add outlet group identifier for Eaton ePDU Eaton ePDU can now publish the parent group of each outlet * docs/nut-names.txt: Extend outlet collection namespace with group ID An outlet can now publish the group to which it belongs to * drivers/snmp-ups.c: snmp-ups: complete nut_snmp_get_{str,int} These methods now allow to get the value of an OID returned by the source OID (as for the sysOID). In case of failure (non existent OID), the functions return the last part of the returned OID (ex: 1.2.3 => 3) * drivers/snmp-ups.c: snmp-ups: create a nut_snmp_get_oid() function This method allows to get the value of an OID which is also an OID (as for the sysOID), without trying to get the value of the pointed OID. This will allow to use nut_snmp_get_{int,str}() the get the value of the pointed OID 2015-09-17 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: snmp-ups: outlet groups type handling for Eaton ePDU Eaton ePDU can now publish the type of outlet group * docs/nut-names.txt: Extend outlet group collection namespace with type The type of outlet group can now be published, part of the new outlet.group data collection * drivers/eaton-mib.c: snmp-ups: outlet groups commands for Eaton ePDU Eaton ePDU can now handle commands outlet groups, including on, off and reboot (cycle) * drivers/snmp-ups.c: snmp-ups: fix commands handling for outlet groups The su_instcmd() function of snmp-ups is now adapted to support outlet groups * drivers/eaton-mib.c: Advanced outlets groups alarm handling for Eaton ePDU Eaton ePDU can now handle alarms on outlets groups, for voltage and current, relative to the configured thresholds * drivers/snmp-ups.c: snmp-ups: improvements for outlet groups and alarms Improve the code for general template management, including outlets and outlets groups for now, and add alarm management for outlet groups, the same way as for outlets 2015-09-16 Arnaud Quette <[email protected]> * drivers/snmp-ups.c: snmp-ups: fix set variable for outlet groups The setvar() function of snmp-ups is now adapted to support outlet groups * drivers/eaton-mib.c: snmp-ups: outlet groups handling for Eaton ePDU Eaton ePDU can now handle outlet groups, including voltage and current (with thresholds and status relative to the configured thresholds), along with power and realpower. A subsequent commit will address the alarms, settings and commands. Bump subdriver version to 0.30 * drivers/snmp-ups.c: snmp-ups: update debug message The template guestimation function name was changed, but the debug message was left with the old function name 2015-09-15 Arnaud Quette <[email protected]> * docs/nut-names.txt: Extend NUT namespace with outlet.group collection A new data collection, called "outlet.group", is now available. It provides grouped management for a set of outlets. The same principles and data than the outlet collection apply to outlet.group * drivers/snmp-ups.c, drivers/snmp-ups.h: snmp-ups: adapt template mechanisms for outlet groups The template handling mechanisms, originally created for outlets, is now adapted to also manage outlet groups 2015-09-14 root <[email protected]> * docs/nut-names.txt: Add a note on the outlet.count variable 2015-09-14 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: snmp-ups: add nominal input current for Eaton ePDU snmp-ups now provides input.[Lx.]current.nominal for Eaton ePDU G2/G3, both for 1phase and 3phase * drivers/eaton-mib.c: snmp-ups: better input.power handling for Eaton ePDUs Improve the way we declare and process input.power, as previously done for input.realpower, in order to address the variations between Eaton ePDUs G2 and G3 2015-09-11 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: snmp-ups: publish part number for Eaton ePDU device.part was standardized in NUT namespace, so enable the declaration for Eaton ePDU * drivers/eaton-mib.c: snmp-ups: 3-phase alarm handling for Eaton ePDU Eaton ePDU can now handle alarms on 3-phase, currently limited to voltage and current, relative to the configured thresholds * drivers/snmp-ups.c: snmp-ups: implement 3-phase alarm handling snmp-ups now allows to publish 3-phase alarms in ups.alarm, the same way as with outlet. Declaration of such alarms are done using "Lx.alarm". info_lkp_t structures messages are shared templates with outlets, and use the string formats to include the context (outlet or phase) and the number (of the outlet or phase) in alarm messages. These alarms are then published in "ups.alarm", with the standard mechanism for alarm publication * docs/nut-names.txt: Extend 3-phase collection namespace with alarms 3-phase data collection now allows to specify alarms, the same way than with the outlet collection ("outlet.n.alarm"), but using "Lx.alarm" (for example "L1.alarm"). These alarms are then published in "ups.alarm", with the standard mechanism for alarm publication * drivers/eaton-mib.c: Advanced threshold handling for Eaton 3-phase ePDU Eaton ePDU can now handle warning and critical thresholds settings and status for input voltage and current on 3-phase units. Alarms are however still to be implement * docs/nut-names.txt: Extend 3-phase collection namespace with threshold 3-phase data collection now allows to specify low / high warning and critical thresholds for voltage and current. Status relative to the thresholds also exist for these data 2015-09-07 Arnaud Quette <[email protected]> * drivers/snmp-ups.c, drivers/snmp-ups.h: snmp-ups: fix loss of precision when setting values su_setvar() was losing precision when converting and casting the provided values to send to the SNMP agent. As an example, with an OID in millivolt (multiplier set to 0.001), when providing 238 (V) using upsrw, the value sent to the SNMP agent was 237999, so leaking 0.1 volt 2015-09-04 Arnaud Quette <[email protected]> * drivers/dstate.c: Extend ups.alarm internal buffer to 1024 chars Currently, ups.alarm can hold up to 256 chars to expose alarms. With the recent outlet alarms handling addition, the buffer may quickly be to small. Thus, increase to 1024, which may still not be sufficient but already provides a bit more room * drivers/eaton-mib.c: snmp-ups: outlet alarm handling for Eaton ePDU Eaton ePDU can now handle alarms on outlets, currently limited to outlet voltage and current, relative to the configured thresholds * drivers/snmp-ups.c: snmp-ups: implement outlets / PDU alarm handling snmp-ups now allows to publish outlets and PDU alarms in ups.alarm, the same way as with ups.status. Declaration of such alarms are done using the outlet template mechanism ("outlet.%i.alarm"). info_lkp_t structures messages can also use the string formats to include the outlet number in alarm messages. These alarms are then published in "ups.alarm", with the standard mechanism for alarm publication * docs/nut-names.txt: Extend outlet collection namespace with alarms Outlet data collection now allows to specify alarms, using the template definitions ("outlet.n.alarm"). These alarms are then published in "ups.alarm", with the standard mechanism for alarm publication 2015-09-02 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: snmp-ups: outlet threshold handling for Eaton ePDU Eaton ePDU can now handle warning and critical thresholds settings and status for outlet voltage and current * docs/nut-names.txt: Extend outlet collection namespace with threshold Outlet data collection now allows to specify low / high warning and critical thresholds for voltage and current. Status relative to the thresholds also exist for these data 2015-09-01 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: snmp-ups: alarms handling for Eaton ePDU Eaton ePDU can now publish alarms, related to input status (voltage, frequency and current) and ambient status (temperature and humidity). Note that alarms are still published under ups.alarms, though these should belong to either pdu.alarms or better device.alarms * drivers/eaton-mib.c: Advanced input threshold handling for Eaton ePDU Eaton ePDU can now handle warning and critical thresholds settings and status for input voltage and current, along with the frequency status * data/cmdvartab, docs/nut-names.txt: Extend input collection namespace with threshold Input data collection now allows to specify low / high warning and critical thresholds for voltage and current. Status relative to the thresholds also exist for these data, and for the frequency 2015-08-31 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: snmp-ups: ambient dry contacts support for Eaton ePDU Eaton ambient modules, connected on ePDU, now publish the status of the connected dry contacts sensors * data/cmdvartab, docs/nut-names.txt: Extend ambient collection namespace with dry contacts Ambient data collection now allow to specify dry contacts sensor status * drivers/eaton-mib.c: snmp-ups: fix Eaton Pulizzi Switched PDU multiplier As per the previous commit, to well handle integer RW variables * drivers/eaton-mib.c: snmp-ups: ambient threshold handling for Eaton ePDU Eaton ePDU can now handle warning and critical thresholds and status for both humidity and temperature * data/cmdvartab, docs/nut-names.txt: Extend ambient collection namespace with threshold Ambient data collection now allow to specify warning and critical thresholds * drivers/eaton-mib.c: snmp-ups: publish presence of Eaton ambient sensor Publish the actual presence of ambient sensor for Eaton ePDU G2 and G3 * data/cmdvartab, docs/nut-names.txt: Publish the actual presence of an ambient sensor A new data was created (ambient.present) to publish the actual presence of an ambient sensor 2015-10-06 Charles Lepple <[email protected]> * data/driver.list.in: HCL: Asium P700, Micropower LCD 1000 and Eaton 5E1100iUSB 2015-10-06 Daniele Pezzini <[email protected]> * data/driver.list.in: HCL: LYONN CTB-800V supported by nutdrv_qx Protocol: 'voltronic-qs-hex' Reference: https://github.com/networkupstools/nut/pull/230 2015-08-22 Mariano <[email protected]> * drivers/nutdrv_qx_voltronic-qs-hex.c: nutdrv_qx: add support for LYONN CTB-800V Small protocol validation change in 'voltronic-qs- hex' subdriver to add support for the protocol used by the LYONN CTB-800V UPS. 2015-09-28 Arnaud Quette <[email protected]> * docs/new-drivers.txt: Fix spacing error 2015-09-22 Charles Lepple <[email protected]> * drivers/solis.c, drivers/solis.h: solis: remove additional warnings The "Waiting" flag is always zero, and several other variables were not used. * drivers/solis.c, drivers/solis.h: solis: clean up warnings Comment out unused constants, and add 'static' and 'const' wherever possible. 2015-09-20 Charles Lepple <[email protected]> * drivers/Makefile.am, drivers/solis.c: solis: math fixes As mentioned here: https://github.com/networkupstools/nut/pull/235 2015-09-19 bsalvador <[email protected]> * drivers/solis.c, drivers/solis.h: solis: patch for Microsol Back- Ups BZ1200-BR patch for correct reading for Microsol Back-Ups BZ1200-BR (rebased onto solis_debug branch, and cleaned up whitespace. -- CFL) Closes https://github.com/networkupstools/nut/pull/235 and Closes https://github.com/networkupstools/nut/pull/236 2015-09-16 Arnaud Quette <[email protected]> * data/driver.list.in, docs/man/snmp-ups.txt, drivers/powerware- mib.c, drivers/powerware-mib.h, drivers/snmp-ups.c: snmp-ups: add Eaton Power Xpert Gateway UPS Card This newer generation of SNMP card is used for BladeUPS or other UPS, and is serving the same XUPS MIB, as in the "pw" subdriver * scripts/subdriver/gen-snmp-subdriver.sh: Update SNMP subdriver generation script Complete the documentation, by adding some notes and examples ; Fix the MIBs directories list and the "keep temporary files" option 2015-09-11 Arnaud Quette <[email protected]> * drivers/snmp-ups.c: Improve log/debug output trace 2015-09-08 Charles Lepple <[email protected]> * drivers/solis.c: solis: resync with end-of-packet character (0.64) Suggested by @rpvelloso in https://github.com/networkupstools/nut/i ssues/231#issuecomment-134795747 Note that the driver could possibly get out-of-sync after initial detection. 2015-09-07 Charles Lepple <[email protected]> * docs/man/macosx-ups.txt, drivers/macosx-ups.c: macosx-ups: gracefully handle disconnection of UPS Tested on 10.9.5 and 10.10.5. Returns "data stale" when UPS disappears. 2015-09-07 Arnaud Quette <[email protected]> * drivers/powerware-mib.c: Bump Powerware SNMP subdriver version 2015-09-04 Charles Lepple <[email protected]> * Makefile.am, docs/configure.txt, docs/new-clients.txt, tools/nut- scanner/README: doc: correct remaining `--with-lib` references Credit: Paul Vermeer 2015-09-01 Arnaud Quette <[email protected]> * drivers/snmp-ups.h: Minor updates to TODO comments * drivers/snmp-ups.c: Implement ups.alarm for SNMP snmp-ups now allows to publish alarms in ups.alarm, the same way as with ups.status 2015-08-31 Arnaud Quette <[email protected]> * drivers/snmp-ups.c: Proper handling of integer RW variables RW variables were previously supposed to always be strings. Thus, the multiplier (using the info_len field) was not applied. Also allow setting float values, not only integer * drivers/snmp-ups.c, drivers/snmp-ups.h: Fix default SNMP retries and timeout The previous patch was using the default values from Net-SNMP, which are set to -1. When the user was not providing overriden values, this was causing the driver to not be able to establish the communication with the device. The default values are now fixed, as per documented (i.e. 5 retries and timeout of 1 second). Also bump the driver version to 0.74 * docs/man/ups.conf.txt, drivers/dstate.c: Make more obvious the socket write failure Document the error that require the use of the 'synchronous' flag. Also use debug level 1 instead of 2 for the debug message 2015-08-23 Charles Lepple <[email protected]> * drivers/solis.c: solis: Add upsdebug*() and upslogx() calls for diagnostics 2015-08-18 Kenny Root <[email protected]> * drivers/powerware-mib.c: Add ups.start.auto for Powerware SNMP Use the IETF UPS MIB to indicate to Powerware devices that it should restart when mains power is applied. * drivers/powerware-mib.c: Fix some indentation problems in PowerWare SNMP * drivers/powerware-mib.c: Add shutdown.return for Powerware SNMP The Powerware MIB supports the concept of shutting down with a delay and then returning when line power is restored. The delay is set to 0 seconds currently. * drivers/powerware-mib.c: Add load.{off,on}.delay for Powerware SNMP The commands to shut down with delay have existed since the first version of the Powerware MIB so add the newer commands "load.off.delay" and "load.on.delay" to aid in shutdown scripts. 2015-08-07 Arnaud Quette <[email protected]> * drivers/dummy-ups.c, drivers/dummy-ups.h: Fix dummy-ups for external value changes dummy-ups allow to change the values of the publicated variables through the standard upsrw tool. This method is handy to script value changes, in a controlled way, compared to the dynamic version (using the TIMER keyword in .dev files), which changes the values in a non controlled way. Bump driver version to 0.14 * m4/nut_check_libnss.m4: Fully check for a working Mozilla NSS Rework the NSS tests so that just having runtime libraries installed is not enough. Moreover, since GNU libc6 also provides a nss.h header, the test now checks for both nss.h and ssl.h Closes networkupstools/nut#184 * docs/download.txt: Fix Red Hat / Fedora packages repository URL 2015-08-03 Tomas Halman <[email protected]> * clients/nutclient.cpp: Problem: nutclient library sometimes reads socket closed by server. Solution: proper read return value evaluation 2015-08-04 Arnaud Quette <[email protected]> * tools/nut-scanner/scan_snmp.c: Fix a crash on a 2nd call to libnutscan on behalf of Tomas Halman, from Eaton Opensource Team 2015-07-24 Nash Kaminski <[email protected]> * drivers/tripplitesu.c: tripplitesu: Fix initialization when tripplite firmware is buggy With some Tripplite SU1000RT2U (and possibly more) UPS's, a firmware bug causes a malformed response to the very first command that is sent after the serial port is opened following a warm or cold boot of the system. My theory is that this related to either the RS232 data lines or handshaking lines being pulled high once the server's UART is powered however I have not determined precisely if this is related to the data line being pulled high or the handshaking lines being asserted. However, I have been able to consistently reproduce the issue where the driver fails to start on the first attempt after a cold/warm boot across 3 different machines and 2 SU1000RT2U UPS's. To workaround this, the initial enumeration is repeated a 2nd time after 300ms(to allow all garbage data to arrive) if the first attempt fails, which allows the driver to consistently startup successfully on the 1st attempt. Closes networkupstools/nut#220 2015-07-24 Tim Smith <[email protected]> * INSTALL.nut: Spelling fixes Spelling fixes and capitalization of SUSE 2015-07-23 Arnaud Quette <[email protected]> * scripts/augeas/nutupsconf.aug.tpl: Update Augeas lens for ups.conf Add the various missing global directives and ups fields 2015-07-20 Daniele Pezzini <[email protected]> * data/driver.list.in: HCL: fix case and spacing 2015-07-18 Daniele Pezzini <[email protected]> * drivers/nutdrv_qx.c: nutdrv_qx: when targeting 'UPS No Ack' consider also the trailing CR In 'fabula' and 'krauler' USB subdrivers, take into account also the trailing CR in the reply while looking for a 'UPS No Ack'. * drivers/nutdrv_qx.c: nutdrv_qx: stay true to return code in 'fabula' USB subdriver In 'fabula' USB subdriver, when reading 'UPS No Ack' from device, since we already mimic a timeout, also empty the reply. 2015-07-11 Charles Lepple <[email protected]> * data/driver.list.in: HCL: Fideltronic INIGO Viper 1200 supported by nutdrv_qx 2015-07-02 Charles Lepple <[email protected]> * drivers/usbhid-ups.c: usbhid-ups: bump version to 0.41 Both the eaton_dual_reportdesc and usbhid_ups_input_vs_feature branches claimed version 0.40, so let's disambiguate the merged version. 2015-07-02 Arnaud Quette <[email protected]> * drivers/libhid.c: Add a debug trace for the number of HID objects found * drivers/hidtypes.h: Fix testing typo MAX_REPORT is really 500 (HID objects), not 50! * drivers/hidparser.c: Report when there are further unprocessed HID objects Following the last commits, and especially the MAX_REPORT one, warn whenever there are remaining HID objects that were not processed. This may serve * drivers/hidtypes.h: Increase the maximum number of HID objects The previous value (300) was causing a trim of the remaining objects. Increase the value to 500, which should give a bit of time * drivers/libshut.c, drivers/libshut.h, drivers/libusb.c, drivers /usb-common.h, drivers/usbhid-ups.c: Add support for Eaton dual HID report descriptor All devices use HID descriptor at index 0. However, some newer Eaton units have a light HID descriptor at index 0, and the full version is at index 1 (in which case, bcdDevice == 0x0202). This dual report descriptor approach is due to the fact that the main report descriptor is now too heavy, and cause some BIOS to hang. A light version is thus provided at the default index, solving this BIOS issues 2015-06-27 Charles Lepple <[email protected]> * drivers/macosx-ups.c: macosx-ups: fix for 10.10 (Yosemite); v1.1 In OS X 10.9 and earlier, IOPSGetPowerSourcesInfo() returned a CFDictionary. In 10.10 it returns a CFArray. Programmers are supposed to use IOPSGetPowerSourceDescription() to gloss over this distinction. However, this does not make it easy to distinguish between a laptop battery and an UPS. So the "port" driver option no longer has any effect. https://developer.apple.com/library/mac/doc umentation/IOKit/Reference/IOPowerSources_header_reference/#//apple _ref/c/func/IOPSGetPowerSourceDescription 2015-06-22 Arnaud Quette <[email protected]> * scripts/upower/95-upower-hid.rules, tools/nut-usbinfo.pl: Update UPower HID rules and generator 2015-06-11 Charles Lepple <[email protected]> * drivers/usbhid-ups.c: usbhid-ups.c: fall back to HID Input type if not a Feature 2015-06-07 Charles Lepple <[email protected]> * drivers/tripplite-hid.c: tripplite-hid.c: device.part is static (version 0.82) 2015-06-04 Daniele Pezzini <[email protected]> * drivers/nutdrv_qx.c: nutdrv_qx: make sure processed item's boundaries are not wrong 2015-04-26 Nick Mayerhofer <[email protected]> * docs/nutdrv_qx-subdrivers.txt, drivers/nutdrv_qx.c, drivers/nutdrv_qx.h: nutdrv_qx: improve documentation for some methods 2015-06-04 Daniele Pezzini <[email protected]> * docs/nutdrv_qx-subdrivers.txt, drivers/nutdrv_qx.c, drivers/nutdrv_qx.h: nutdrv_qx: remove redundant comments and update docs 2015-04-28 Nick Mayerhofer <[email protected]> * drivers/nutdrv_qx_voltronic.c: nutdrv_qx: move var declaration in 'voltronic' subdriver Move variable declaration to fulfill condition '3.3. Portability' of the developer guide. Bump version. * drivers/libhid.c: libhid: replace "flush loop" with memset Move to the C way of setting memory (memset), replacing a for loop with a few anti-patterns in it: - for (...; ; i++) - for (...; i < MAGIC_NUMBER; ...) - for (...) array[i] = 0 2015-05-18 Daniele Pezzini <[email protected]> * docs/nutdrv_qx-subdrivers.txt, drivers/nutdrv_qx.c, drivers/nutdrv_qx.h, drivers/nutdrv_qx_bestups.c, drivers/nutdrv_qx_mecer.c, drivers/nutdrv_qx_megatec-old.c, drivers/nutdrv_qx_megatec.c, drivers/nutdrv_qx_mustek.c, drivers/nutdrv_qx_q1.c, drivers/nutdrv_qx_voltronic-qs-hex.c, drivers/nutdrv_qx_voltronic-qs.c, drivers/nutdrv_qx_voltronic.c, drivers/nutdrv_qx_zinto.c: nutdrv_qx: give subdrivers a last chance to process the command Add (and document) a new function ('preprocess_command()') to preprocess the command to be sent to the device, just before the actual sending and, in case of instant commands/setvars, after the 'preprocess()' function has been triggered (if appropriate). As an example, this function can be useful to add to all commands (both queries and instant commands/setvars) a CRC or to fill the command of a query with some data. Also, in qx_process(), address buf size vs item->answer size earlier. Update all subdrivers accordingly, bump versions. 2015-06-01 Arnaud Quette <[email protected]> * docs/man/snmp-ups.txt, drivers/snmp-ups.c, drivers/snmp-ups.h: Provide access to Net-SNMP timeout and retries Two new extra arguments are now available to allow overriding Net-SNMP number of retries (snmp_retries) and timeout per retry (snmp_timeout). These respectively maps to snmpcmd "-r retries" and "-t timeout" 2015-05-29 Arnaud Quette <[email protected]> * scripts/upower/95-upower-hid.rules: Update UPower HID rules * tools/nut-usbinfo.pl: Fix UPower device matching for recent kernels As per the UPower patch below referenced, hiddev* devices now have class "usbmisc", rather than "usb". See http://cgit.freedesktop.org/upower/commit/rules/95-upower- hid.rules?id=9f31068707fc79744961cea7258b0eb262effbf1 2015-05-28 Arnaud Quette <[email protected]> * tools/nut-scanner/nut-scan.h, tools/nut-scanner/nut-scanner.c, tools/nut-scanner/nutscan-device.c, tools/nut-scanner/nutscan- device.h, tools/nut-scanner/nutscan-display.c, tools/nut-scanner /nutscan-init.c, tools/nut-scanner/nutscan-init.h, tools/nut- scanner/nutscan-ip.c, tools/nut-scanner/nutscan-ip.h, tools/nut- scanner/nutscan-serial.c, tools/nut-scanner/nutscan-serial.h, tools /nut-scanner/scan_avahi.c, tools/nut-scanner/scan_eaton_serial.c, tools/nut-scanner/scan_ipmi.c, tools/nut-scanner/scan_nut.c, tools /nut-scanner/scan_snmp.c, tools/nut-scanner/scan_usb.c, tools/nut- scanner/scan_xml_http.c: Fix legal information on source-code headers Copyright and author were not mentioned as it should be. Most of the nut-scanner copyright belongs to EATON, apart from few parts. Files descriptions are now also in Doxygen format 2015-05-18 Daniele Pezzini <[email protected]> * docs/nutdrv_qx-subdrivers.txt, drivers/nutdrv_qx.c, drivers/nutdrv_qx.h, drivers/nutdrv_qx_bestups.c, drivers /nutdrv_qx_blazer-common.c, drivers/nutdrv_qx_blazer-common.h, drivers/nutdrv_qx_mecer.c, drivers/nutdrv_qx_megatec-old.c, drivers/nutdrv_qx_megatec.c, drivers/nutdrv_qx_mustek.c, drivers/nutdrv_qx_q1.c, drivers/nutdrv_qx_voltronic-qs-hex.c, drivers/nutdrv_qx_voltronic-qs.c, drivers/nutdrv_qx_voltronic.c, drivers/nutdrv_qx_zinto.c: nutdrv_qx: make preprocessed value's size_t a const There's no need to intervene on the passed-to-the- function value of a preprocessed value's size_t, so clarify it is a const. Update all subdrivers accordingly, bump versions. * drivers/nutdrv_qx.c: nutdrv_qx: make sure an answer is not reused if preprocess_answer() fails If an item's preprocess_answer() function fails, the answer should not be considered valid and inherited by the following items with the same command. Therefore, on failure, clear the answer so that the following items are forced to query the device and preprocess the answer anew, if appropriate. 2015-05-13 Arnaud Quette <[email protected]> * docs/download.txt: Update NUT packages for Windows to 2.6.5-6 2015-05-07 Arnaud Quette <[email protected]> * scripts/systemd/nut-server.service.in: Restore systemd relationship with nut-driver service The Requires directive from nut-server to nut-driver was previously removed, since it was preventing upsd from starting whenever one or more drivers, among several, was failing to start. Use the Wants directive, a weaker version of Requires, which will start upsd even if the nut-driver unit fails to start. closes https://github.com/networkupstools/nut/issues/200 2015-04-23 Arnaud Quette <[email protected]> * Makefile.am: Cleanup GPG signature before generation 2015-04-22 Arnaud Quette <[email protected]> * configure.ac: bump version back to 2.7.3.1 * configure.ac: Restore version 2.7.3 for release * docs/security.txt: Missing link reference update The filename of the previous GPG release key was not updated, leading to pointing to the current release key 2015-04-08 Nick Mayerhofer <[email protected]> * docs/nutdrv_qx-subdrivers.txt, drivers/nutdrv_qx.c, drivers/nutdrv_qx.h: nutdrv_qx: clarify docs/inline comments 2015-04-16 Arnaud Quette <[email protected]> * configure.ac: bump version to 2.7.3.1 2015-04-15 Arnaud Quette <[email protected]> * configure.ac: update version to 2.7.3 * docs/security.txt: Update release signature verification The release manager key has change. Update the documentation to reflect it, along with keeping necessary for checking the previous releases * docs/download.txt: Fix formatting issue * NEWS, UPGRADING: Final update for release 2.7.3 Complete the release information for NUT 2.7.3 * docs/maintainer-guide.txt: Store some comments for latter processing 2015-04-10 Arnaud Quette <[email protected]> * drivers/mge-hid.c: Improve Eaton ABM support for USB/HID units As per clarifications from David G. Miller (Eaton ABM expert) and customers request, when ABM is enabled, we now both publish the following as per the ABM information: - the 5 status bits {charging, discharging, floating, resting, off} under battery.charger.status - the 2 historical status bits {CHRG, DISCHRG} under ups.status When ABM is disabled, we just publish the 2 historical status bits {CHRG, DISCHRG} under ups.status, as per UPS.PowerSummary.PresentStatus.{Charging,Discharging}, as done previously 2015-04-02 Arnaud Quette <[email protected]> * conf/ups.conf.sample, docs/man/ups.conf.txt, drivers/dstate.c, drivers/dstate.h, drivers/main.c: Improve synchronous driver flag implementation The previous commit was suffering a number of issues. The present commit fixes these, along with adding more documentation and a better and more understandable implementation code. Thanks to Daniele Pezzini for the thorough review Closes: https://github.com/networkupstools/nut/issues/197 2015-04-01 Arnaud Quette <[email protected]> * docs/man/ups.conf.txt, drivers/dstate.c, drivers/dstate.h, drivers/main.c: Implement synchronous driver flag As per issue #197, NUT drivers work by default in asynchronous mode. This means that all data are pushed by the driver on the communication socket to upsd (Unix socket on Unix, Named pipe on Windows) without waiting for these data to be actually consumed. With some HW, such as ePDUs, that can produce a lot of data, asynchronous mode may cause some congestion, resulting in the socket to be full, and the driver to appear as not connected. By enabling the 'synchronous' flag, the driver will wait for data to be consumed by upsd, prior to publishing more. This can be enabled either globally or per driver. 2015-04-07 Arnaud Quette <[email protected]> * scripts/systemd/nut-server.service.in: Do not Require systemd nut- driver for nut-server Put the Requires=nut-driver.service in comment for nut-server systemd unit file. Thus we don't require drivers to be successfully started! This was a change of behavior compared to init SysV, and could prevent from accessing successfully started drivers, or at least to audit a system Closes: https://github.com/networkupstools/nut/issues/200 2015-04-04 Charles Lepple <[email protected]> * UPGRADING: UPGRADING: mention SSL permissions (#199) * docs/security.txt: NSS SSL documentation Addresses new behavior as part of the NSS forking fix (#199). Formatting and wording fixed as well. 2015-04-04 Émilien Kia <[email protected]> * server/upsd.c: Initialize SSL after deamonize and downgrade to user. Fix issue #190 - upsd: NSS SSL only working in debug mode https://github.com/networkupstools/nut/issues/190 2015-04-02 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: Better input.realpower handling for Eaton ePDUs G2/G3 Improve the way we declare and process input.realpower, in order to address the variations between Eaton ePDUs G2 and G3 2015-03-19 Arnaud Quette <[email protected]> * docs/nut-names.txt: Document new variables and commands addition The variables and commands that were added were not described in the NUT namespace document. These are: input.transfer.delay - battery.energysave.load - battery.energysave.delay - battery.charger.status - outlet.1.shutdown.return - outlet.2.shutdown.return * drivers/bcmxcp.c: Fix the letter case of ABM and outlets status For more coherence with NUT status publication, these status are now lower case * drivers/bcmxcp.c: Add missing Author 2014-10-10 gavrilov-i <[email protected]> * data/cmdvartab, drivers/bcmxcp.c, drivers/bcmxcp.h: drivers/bcmxcp: advanced features Closes: #158 Added setvar function exec result parsing Add command to turn load on after shutdown.stayoff and shutdown.return. Outlet control changed. Outlet control via commands "outlet.n.load.on/off" like in other drivers. Variable outlet.n.staus now only for reading. Some code changes in outlet.n.shutdown.return command - now supporting more than 3 outlets (up to 9). Add descriptions to new and some old variables and commands. Add "bypass.start" command, for enabling bypass. For returning in On-Line mode exec "load.on" command. Additional checks of UPS vars. Now add zero var only if it could be changed. 2015-04-01 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: Workaround input.{power,realpower} for Eaton ePDUs Add variable declarations to handle missing input.{power,realpower} on Eaton ePDUs G2 and G3 1phase. On 3phase, these variables point at SNMP OIDs that sum up the 3 phases information. These OIDs should also be present on 1phase, however it's actually not the case. So simply duplicate the L1 declaration 2015-03-31 Arnaud Quette <[email protected]> * drivers/powerware-mib.c: Implement battery.charger.status for Eaton SNMP This new official variable now replaces the historic 'vendor.specific.abmstatus', as per other similar implementations (in usbhid-ups and bcmxcp drivers) 2015-03-27 Arnaud Quette <[email protected]> * drivers/mge-hid.c: Implement Eaton ABM support for USB/HID units Add support for Eaton Advanced Battery Monitoring, for USB/HID units. Information are provided through the new battery.charger.status. For now, at least, when ABM is enabled, the historic CHRG and DISCHRG flags are not published anymore in ups.status 2015-03-26 Stuart Henderson <[email protected]> * data/driver.list.in, docs/man/snmp-ups.txt, docs/snmp- subdrivers.txt, drivers/Makefile.am, drivers/huawei-mib.c, drivers /huawei-mib.h, drivers/snmp-ups.c: snmp-ups: new subdriver for Huawei "Hi, the [commit] below adds a new subdriver for snmp-ups to support Huawei UPS, based on an observed walk from a UPS5000-E with a few bits filled in from the MIBs (copy at http://junkpile.org/HUAWEI_UPS_MIB/)." http://news.gmane.org/find- root.php?message_id=slrnmh6npf.tg7.stu%40naiad.spacehopper.org 2015-03-25 Daniele Pezzini <[email protected]> * drivers/nutdrv_qx_voltronic.c: nutdrv_qx: add support in 'voltronic' subdriver for P13 protocol 2015-03-24 Arnaud Quette <[email protected]> * drivers/mge-hid.c: Complementary Energy Saving data for Eaton USB devices Add a 2nd HID path for battery.energysave.delay. Depending on the exact device model, different implementations may be used 2015-03-22 Daniele Pezzini <[email protected]> * NEWS: nutdrv_qx: update NEWS about new 'fuji' USB subdriver 2015-03-21 Daniele Pezzini <[email protected]> * drivers/nutdrv_qx.c, drivers/nutdrv_qx.h: nutdrv_qx: typedef testing_t only if TESTING is #defined First reported by GitHub user @nickma82 * docs/man/nutdrv_qx.txt, docs/nutdrv_qx-subdrivers.txt: nutdrv_qx: document 'voltronic-qs-hex' subdriver in man pages * docs/man/nutdrv_qx.txt, drivers/nutdrv_qx_bestups.c, drivers /nutdrv_qx_blazer-common.c, drivers/nutdrv_qx_blazer-common.h, drivers/nutdrv_qx_mecer.c, drivers/nutdrv_qx_megatec-old.c, drivers/nutdrv_qx_megatec.c, drivers/nutdrv_qx_mustek.c, drivers/nutdrv_qx_q1.c, drivers/nutdrv_qx_voltronic-qs-hex.c, drivers/nutdrv_qx_voltronic-qs.c, drivers/nutdrv_qx_zinto.c: nutdrv_qx: add 'ignoresab' flag to support bogus devices Some UPSes incorrectly report the 'Shutdown Active' bit (7th bit of the 'status byte') as always on (=1), consequently making the driver believe the UPS is nearing a shutdown (and, as a result, ups.status always contains FSD). To workaround this issue, add a new 'ignoresab' flag that makes the driver do just what its name tells (IGNORE Status Active Bit) skipping the relative item in qx2nut tables. References: - http://lists.alioth.debian.org/pipermail /nut-upsdev/2015-March/006896.html - https://github.com/networkupstools/nut/issues/195 2015-03-11 Arnaud Quette <[email protected]> * data/cmdvartab, docs/nut-names.txt: Add some new variable names, related to ePDUs Add new variables names, related to ePDUs, such as input.*.load, input.*.realpower and input.*.power * drivers/eaton-mib.c: Minor update to comments 2015-02-04 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: Fix outlet.{power,realpower} data mapping According to the new mapping using the input collection, these two data mapping were targeting at the wrong OIDs. 2015-02-03 Arnaud Quette <[email protected]> * drivers/eaton-mib.c: Fix and complete a bit Eaton ePDUs support Add some new data mapping to improve support for Eaton ePDUs. This commit includes some new NUT data names that requires approval before being merged 2015-03-19 Arnaud Quette <[email protected]> * data/cmdvartab, docs/nut-names.txt, drivers/mge-hid.c: Add more Energy Saving features for Eaton USB devices Add two new Energy Saving features: - battery.energysave.delay: to configure the delay before switching off the UPS if running on battery and load level low (in minutes) - battery.energysave.realpower: to switch off the UPS if running on battery and power consumption on UPS output is lower than this value (expressed in Watts). Note that documentation in nut-names.txt and cmdvartab was limited to difference with an upcoming branch merge, that will add the others * drivers/mge-hid.c: Align Energy Saving variable names Change ups.load.energysave to battery.energysave.load, to be coherent with the latest commit made in the bcmxcp driver 2015-03-10 Arnaud Quette <[email protected]> * data/cmdvartab, drivers/mge-hid.c: Add a new EnergySaving threshold for Eaton UPSs Add 'ups.load.energysave' parameter, to enable energy saving when the power consumption on the UPS output drops below this value (in percent). This new variable however requires to go through the NUT RFC process to get approved 2015-03-19 Arnaud Quette <[email protected]> * tools/Makefile.am: Also distribute nut-ddl-dump.sh helper script 2015-03-18 Daniele Pezzini <[email protected]> * data/driver.list.in: HCL: EUROCASE EA200N 2000VA supported by nutdrv_qx Protocol: 'megatec' USB subdriver: 'fuji' Reference: ht tp://thread.gmane.org/gmane.comp.monitoring.nut.user/8808/focus=908 1 * drivers/nutdrv_qx_bestups.c, drivers/nutdrv_qx_blazer-common.c, drivers/nutdrv_qx_mecer.c, drivers/nutdrv_qx_megatec-old.c, drivers/nutdrv_qx_megatec.c, drivers/nutdrv_qx_mustek.c, drivers/nutdrv_qx_q1.c, drivers/nutdrv_qx_voltronic-qs-hex.c, drivers/nutdrv_qx_voltronic-qs.c, drivers/nutdrv_qx_zinto.c: nutdrv_qx: remove redundancy in blazer-common-dependent subdrivers Since main nutdrv_qx driver already sets an alarm when FSD arises (see nutdrv_qx.c>ups_alarm_set()), there is no need to do so in the various subdrivers. So, in order to prevent a duplicated alarm message, remove all unneeded code from the affected subdrivers (all the ones that depend on nutdrv_qx_blazer-common). 2015-03-17 Daniele Pezzini <[email protected]> * data/driver.list.in: HCL: update Mecer ME-1000-WTU (supported by nutdrv_qx) Tested by @sliverc (Oliver Sauder) on NUT 2.7.1 Reference: https://github.com/networkupstools/nut/issues/148 2015-03-16 Daniele Pezzini <[email protected]> * docs/man/nutdrv_qx.txt: nutdrv_qx: document USB subdrivers' glitches * drivers/nutdrv_qx.c: nutdrv_qx: add workaround in 'fuji' subdriver to support all shutdown.returns As 'fuji' subdriver discards all the commands of more than 3 characters, in order to support 'SnRm' shutdown.returns (and hence the standard 'S.5R0003' shutdown.return with DEFAULT_{ON,OFF}DELAYs) map 'SnRm' shutdown.returns to the corresponding '…

greenpark-code · 2023-12-14T17:30:24Z

In the hardware compatibility list I see mention of the Lyonn CTB-800V associated with driver nutdrv_qx, but I can't find the /etc/nut/ configuration files for this UPS.

Is there a place where I should be searching?

ATM, the connection to the UPS is failing (apcupsd – uninstalled before installing nut – was seeing it, reporting possibly incorrect values, but at least I know that the physical connection via USB cable is working). Of course I'd prefer the networking features of nut over the apcupsd approach.

[EDIT:] Raspberry PI OS 64:

$ uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux

Currently installed:

libneon27-gnutls/oldstable,now 0.31.2-1 arm64 [installed,automatic]
libnutscan1/oldstable,now 2.7.4-13 arm64 [installed,automatic]
libsrt1.4-gnutls/oldstable,now 1.4.2-1.3 arm64 [installed,automatic]
nut-client/oldstable,now 2.7.4-13 arm64 [installed]
nut-server/oldstable,now 2.7.4-13 arm64 [installed]
nut-xml/oldstable,now 2.7.4-13 arm64 [installed]
nut/oldstable,oldstable,now 2.7.4-13 all [installed]

Installed after nut, to cope with nut-scanner error messages about missing libraries (dependence on development libs has already been reported):

libipmimonitoring-dev/oldstable,now 1.6.6-4+deb11u1 arm64 [installed]
libneon27-dev/oldstable,now 0.31.2-1 arm64 [installed]

Such error messages were not issued any more afterwards, yet nut-scanner -U doesn't seem to find anything:

# nut-scanner -U
Scanning USB bus.

^ Nothing more, I only get error messages in journalctl -f until I stop nut server and client, messages such as:

Dec 14 16:03:26 raspberrypi systemd[1]: Failed to start Network UPS Tools - power device driver controller.
Dec 14 16:03:26 raspberrypi upsd[1502]: Can't connect to UPS [Lyonn_CTB800V@raspberrypi] (nutdrv_qx-Lyonn_CTB800V@raspberrypi): No such file or directory
Dec 14 16:03:31 raspberrypi upsmon[1488]: UPS [Lyonn_CTB800V@raspberrypi]: connect failed: Connection failure: Connection refused

( ^ The second one "No such file or directory" doesn't specify which file or directory is missing... unless the file name is "nutdrv_qx-Lyonn_CTB800V@raspberrypi".)

When I restart nut-server and nut-client, on the console:

Broadcast message from nut@raspberrypi (somewhere) (Thu Dec 14 16:03:16 2023): 
                                                                               
Communications with UPS Lyonn_CTB800V@raspberrypi lost                         
                                                                               
                                                                               
Broadcast message from nut@raspberrypi (somewhere) (Thu Dec 14 16:03:21 2023): 
                                                                               
UPS Lyonn_CTB800V@raspberrypi is unavailable

Current content of files in /etc/nut (omitting commented out lines coming with the package):

/etc/nut.conf

MODE=netserver

/etc/ups.conf

# Set maxretry to 3 by default, this should mitigate race with slow devices:
maxretry = 3

# https://www.howtoraspberry.com/2020/11/how-to-monitor-ups-with-raspberry-pi/
[Lyonn_CTB800V@raspberrypi]
# driver = usbhid-ups
# driver = blazer_usb
# https://networkupstools.org/stable-hcl.html says CTB-800V => nutdrv_qx (however, they don't provide settings for the Lyonn CTB-800V, although it's on the compatibility list.
# They provide settings for the Lyonn CTB-1200 => driver blazer_usb).
driver = nutdrv_qx
port = auto
desc = "Lyonn CTB-800V"

/etc/upsd.conf nothing, I'm clueless on this one ATM.

/etc/upsd.users

[upsadmin]
password = myPassInClear
upsmon master

/etc/upsmon.conf

MONITOR Lyonn_CTB800V@raspberrypi 1 upsadmin myPassInClear master

If somebody has nut working with this UPS, sharing the config files – or the place where I should look for them – would be much appreciated.

jimklimov · 2023-12-14T22:53:12Z

@greenpark-code : Did nut-driver service (or similar) report any errors?

I don't think I've seen [Lyonn_CTB800V@raspberrypi] sort of names in ups.conf. Even if it does not reject the @ character when recognizing a device, it is likely to be a problem for clients that break the string by the first such char - e.g. if you upsc or upsmon some Lyonn_CTB800V@raspberrypi@somehostname.

Normally the name in ups.conf is short like [Lyonn_CTB800V] and the @somehostname is used by (remote) clients.

greenpark-code · 2023-12-20T05:40:13Z

@jimklimov Thanks a lot for replying, I've modified that string and I've been trying other changes, with no success so far.

With journalctl -f I see the following lines when connecting the UPS:

Dec 20 02:03:47 raspberrypi kernel: usb 1-1.4: new full-speed USB device number 4 using xhci_hcd
Dec 20 02:03:47 raspberrypi kernel: usb 1-1.4: New USB device found, idVendor=09d6, idProduct=0001, bcdDevice= 1.10
Dec 20 02:03:47 raspberrypi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 20 02:03:47 raspberrypi kernel: usb 1-1.4: Product: UPS
Dec 20 02:03:47 raspberrypi kernel: usb 1-1.4: Manufacturer: KSTAR
Dec 20 02:03:47 raspberrypi kernel: usb 1-1.4: SerialNumber: KHID0
Dec 20 02:03:47 raspberrypi kernel: hid-generic 0003:09D6:0001.0002: hiddev96,hidraw0: USB HID v1.00 Device [KSTAR UPS] on usb-0000:01:00.0-1.4/input0
Dec 20 02:03:47 raspberrypi mtp-probe[1359]: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4"
Dec 20 02:03:47 raspberrypi mtp-probe[1359]: bus: 1, device: 4 was not an MTP device
Dec 20 02:03:47 raspberrypi mtp-probe[1361]: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4"
Dec 20 02:03:47 raspberrypi mtp-probe[1361]: bus: 1, device: 4 was not an MTP device

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 09d6:0001 KSTAR UPS
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

What should I put as port, not to leave it as 'auto'?

$ sudo systemctl reload-or-restart nut-server => with journalctl -f in another terminal window I'm seeing what follows:

Dec 20 02:37:06 raspberrypi sudo[1844]: pam_unix(sudo:session): session opened for user root(uid=0) by air(uid=1000)
Dec 20 02:37:06 raspberrypi systemd[1]: Starting Network UPS Tools - power device driver controller...
Dec 20 02:37:06 raspberrypi upsdrvctl[1848]: Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4)
Dec 20 02:37:06 raspberrypi upsdrvctl[1848]: USB communication driver 0.33
Dec 20 02:37:06 raspberrypi upsdrvctl[1848]: No supported devices found. Please check your device availability with 'lsusb'
Dec 20 02:37:06 raspberrypi upsdrvctl[1848]: and make sure you have an up-to-date version of NUT. If this does not help,
Dec 20 02:37:06 raspberrypi upsdrvctl[1848]: try running the driver with at least 'subdriver', 'vendorid' and 'productid'
Dec 20 02:37:06 raspberrypi upsdrvctl[1848]: options specified. Please refer to the man page for details about these options
Dec 20 02:37:06 raspberrypi upsdrvctl[1848]: (man 8 nutdrv_qx).
Dec 20 02:37:06 raspberrypi upsdrvctl[1847]: Driver failed to start (exit status=1)
Dec 20 02:37:11 raspberrypi upsdrvctl[1850]: Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4)
Dec 20 02:37:11 raspberrypi upsdrvctl[1850]: USB communication driver 0.33
Dec 20 02:37:11 raspberrypi upsdrvctl[1850]: No supported devices found. Please check your device availability with 'lsusb'
Dec 20 02:37:11 raspberrypi upsdrvctl[1850]: and make sure you have an up-to-date version of NUT. If this does not help,
Dec 20 02:37:11 raspberrypi upsdrvctl[1850]: try running the driver with at least 'subdriver', 'vendorid' and 'productid'
Dec 20 02:37:11 raspberrypi upsdrvctl[1850]: options specified. Please refer to the man page for details about these options
Dec 20 02:37:11 raspberrypi upsdrvctl[1850]: (man 8 nutdrv_qx).
Dec 20 02:37:11 raspberrypi upsdrvctl[1847]: Driver failed to start (exit status=1)
Dec 20 02:37:17 raspberrypi upsdrvctl[1851]: Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4)
Dec 20 02:37:17 raspberrypi upsdrvctl[1851]: USB communication driver 0.33
Dec 20 02:37:17 raspberrypi upsdrvctl[1851]: No supported devices found. Please check your device availability with 'lsusb'
Dec 20 02:37:17 raspberrypi upsdrvctl[1851]: and make sure you have an up-to-date version of NUT. If this does not help,
Dec 20 02:37:17 raspberrypi upsdrvctl[1851]: try running the driver with at least 'subdriver', 'vendorid' and 'productid'
Dec 20 02:37:17 raspberrypi upsdrvctl[1851]: options specified. Please refer to the man page for details about these options
Dec 20 02:37:17 raspberrypi upsdrvctl[1851]: (man 8 nutdrv_qx).
Dec 20 02:37:17 raspberrypi upsdrvctl[1847]: Driver failed to start (exit status=1)
Dec 20 02:37:17 raspberrypi upsdrvctl[1847]: Network UPS Tools - UPS driver controller 2.7.4
Dec 20 02:37:17 raspberrypi systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE
Dec 20 02:37:17 raspberrypi systemd[1]: nut-driver.service: Failed with result 'exit-code'.
Dec 20 02:37:17 raspberrypi systemd[1]: Failed to start Network UPS Tools - power device driver controller.
Dec 20 02:37:17 raspberrypi systemd[1]: Starting Network UPS Tools - power devices information server...
Dec 20 02:37:17 raspberrypi upsd[1852]: fopen /run/nut/upsd.pid: No such file or directory
Dec 20 02:37:17 raspberrypi upsd[1852]: listening on 127.0.0.1 port 3493
Dec 20 02:37:17 raspberrypi upsd[1852]: listening on 127.0.0.1 port 3493
Dec 20 02:37:17 raspberrypi upsd[1852]: listening on ::1 port 3493
Dec 20 02:37:17 raspberrypi upsd[1852]: listening on ::1 port 3493
Dec 20 02:37:17 raspberrypi upsd[1852]: Can't connect to UPS [Lyonn_CTB800V] (nutdrv_qx-Lyonn_CTB800V): No such file or directory
Dec 20 02:37:17 raspberrypi upsd[1852]: Can't connect to UPS [Lyonn_CTB800V] (nutdrv_qx-Lyonn_CTB800V): No such file or directory
Dec 20 02:37:17 raspberrypi upsd[1854]: Startup successful
Dec 20 02:37:17 raspberrypi systemd[1]: Started Network UPS Tools - power devices information server.
Dec 20 02:37:17 raspberrypi sudo[1844]: pam_unix(sudo:session): session closed for user root

jimklimov · 2023-12-20T09:44:42Z

If 09d6 is your UPS vendor ID, I'm sad to say such is not mentioned even in current NUT sources.

You can try specifying the vendorid=09d6 and productid=0001 in the ups.conf section, in case nutdrv_qx can pick a subdriver for it.

You can also try building a newer NUT version (see wiki about in-place builds and tests) - there you can also vary subdriver option for usbhid-ups newly.

The port=auto for USB-capable drivers is a placeholder. The value is ignored and device is found by whatever libusb enumerates. The nutdrv_qx may be a bit special in that it supports serial conbections also, and some /dev/ttyUSB0 is fair game for that (if the chip is a USB-serial translator), but no vendor/product id is in play then.

greenpark-code · 2023-12-20T19:11:55Z

You can try specifying the vendorid=09d6 and productid=0001 in the ups.conf section, in case nutdrv_qx can pick a subdriver for it.

Thank you again, I did that (tried with ' = ' and '=' and sometimes I still see a message inviting to retry after having set up at least subdriver, vendorid and productid, but I guess it's a generic message not necessarily implying that such settings haven't been found in ups.conf [specifying "if you haven't already given those values" might make it less ambiguous, or directly "please check your ups.conf and see if you have specified subdriver, vendorid and productid"]).

I've been trying nutdrv_qx and blazer_usb with all the respectively available subdriver options.
When I don't get an error about the subdriver not having been found, I'm seeing this one:

Can't claim USB device [09d6:0001]: could not detach kernel driver from interface 0: Operation not permitted

It's unclear to me what "Operation not permitted" is about.

I'm launching as root:

systemctl start nut-server

It's USB, not ethernet, so the ufw firewall is not implied AFAIK.

==========

As for building from source:

It would be great if there were a section in the readme doc – as you find in most projects here on github – with title "Building from source" with the list of dependencies and the few commands that usually are sufficient to build from source.

https://www.truenas.com/community/threads/ups-lyonn-ctb-800v-connection-refused.62475/

This user managed to use blazer_usb with a Lyonn CTB-800V but how he did that is still a mystery to me, he doesn't share the content of his /etc/nut files, this page in NUT's official website https://networkupstools.org/ddl/Lyonn/CTB-1200.html does NOT report the content of files in /etc/nut/ either.

I might be a bit stressed / in a hurry (buying this UPS is also part of ad honorem goals), however my impression so far about nut's documentation is that there are explanations about plenty of aspects BUT it's not evident where to look for concise info on how to get things done, meaning, just my opinion, that the community of contributors should possibly be invited to always also share the whole set of their /etc/nut files when succeeding in getting nut to work with a particular UPS brand+model.

jimklimov · 2023-12-21T17:42:34Z

There are many pieces about building, at least for users and for developers, including docs with lists of prerequisites for various platforms and distros. Recent and relatively concise iterations can be seen on our wiki on github (probably go see the one on in-place builds).

As noted, a way to pick subdrivers for usbhid-ups is present since NUT 2.8.1 (a couple of months ago, and your 2.7.4 is almost a decade old soon), otherwise it relies on built-in matching of "this driver knows about this ID pattern" and yours is not known.

For nutdrv_qx retries - which options did you specify? Is ...try running the driver with at least 'subdriver', 'vendorid' and 'productid' message valid (are all 3 present? maybe explicit subdriver was required back then for the unknown device)? UPDATE: saw your update on this now :)

Finally about permissions - normally NUT ships with an udev.rules or similar file (depends on distro USB mgmt stack) which tells the OS to assign certain ownership to device FS nodes for certain USB ID patterns. Yours is unknown so not there - either the setting needs to be extended on your system, or the driver told to remain as user=root (NUT drops privileges by default).

greenpark-code · 2023-12-22T05:30:38Z

Lyonn have a tech service in this zone, I've contacted them, "CTB-800V" includes 4 sub-models with different comm chips, the serial number tells them which sub-model it is, I'll report here how that goes (IMHO the best situation for users [and sells] would be if the whole info were available directly on networkupstools.org).

jimklimov · 2023-12-22T10:31:56Z

@greenpark-code : thanks!

FWIW, the website originates from a bit of scaffolding in a nearby nut-website repo, some in nut-ddl and mostly texts (like FAQ and man pages that could be relevant for this bit) in this nut repo. So as soon as you have info, you can post PR(s) with the update - thanks in advance :)

greenpark-code · 2023-12-26T04:20:38Z

@greenpark-code : thanks!

FWIW, the website originates from a bit of scaffolding in a nearby nut-website repo, some in nut-ddl and mostly texts (like FAQ and man pages that could be relevant for this bit) in this nut repo. So as soon as you have info, you can post PR(s) with the update - thanks in advance :)

Err... should I be seeing links embedded in your last message?

The answer I got before Xmas from their tech service was just mentioning nutdrv_qx and blazer_usb, the drivers with which I had already spent quite a few hours before contacting them, probably without having the proper config in /etc/nut.

I've asked them if this sub-model is an equivalent to some specific model of another brand, so I might find some web page with the complete info on how to get nut working with it.

As I wrote earlier, I'll report here, solved or not.

jimklimov · 2023-12-26T15:51:14Z

No links, sorry - typing while offline (traveling).

…

On Tue, Dec 26, 2023, 05:20 greenpark ***@***.***> wrote: @greenpark-code <https://github.com/greenpark-code> : thanks! FWIW, the website originates from a bit of scaffolding in a nearby nut-website repo, some in nut-ddl and mostly texts (like FAQ and man pages that could be relevant for this bit) in this nut repo. So as soon as you have info, you can post PR(s) with the update - thanks in advance :) Err... should I be seeing links embedded in your last message? The answer I got before Xmas from their tech service was just mentioning nutdrv_qx and blazer_usb, the drivers with which I had already spent quite a few hours *before* contacting them, probably without having the proper config in /etc/nut. I've asked them if this sub-model is an equivalent to some specific model of another brand, so I might find some web page with the complete info on how to get nut working with it. *As I wrote earlier, I'll report here, solved or not.* — Reply to this email directly, view it on GitHub <#230 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMPTFALQKBXV2WNDEQABMTYLJGCBAVCNFSM4BOBVLP2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWHEZDIMRUGU2A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

greenpark-code · 2023-12-28T02:41:19Z

The local tech service guy is a very kind person, but basically:

they don't support open source software, despite the fact that most servers out there are Linux and there's no server without UPS
they have no clue about NUT, although he tried searching for a solution

He mentions that he would contact other customers which use Linux but it's unclear for now which model and sub-model they have.

And talking of sub-model: this one UPS, based on its serial number, is a KSTAR MICROPOWER device.

I've e-mailed KSTAR and I'll report here, good or bad results.

So far, this device is apparently simply not supported (I'm now trying on an AMD64 Ubuntu box just to be sure that the problem is not with the ARM64 binaries):

/etc/nut/ups.conf

driver = blazer_usb
port = auto
vendorid = "09d6"
productid = "0001"
bus = "003"
desc = "Lyonn CTB-800V (KSTAR Micropower submodel)"

/etc/nut/nut.conf

MODE=standalone

NOTICE: I did launch the command recommended here to change the device access permissions
https://devicetests.com/configure-ups-usb-connection-ubuntu-nut-driver

sudo chmod 0666 /dev/bus/usb/003/006

$ sudo upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)
No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 blazer_usb).

(lsusb does show the device as I already reported in a previous post, it's a different usb port on this machine but the same vendor and product ids show up.)

Switched driver to nutdrv_qx

$ sudo upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4)
USB communication driver 0.33
No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 nutdrv_qx).

Switched driver to usbhid-ups

$ sudo upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
No matching HID UPS found
Driver failed to start (exit status=1)

FOR NOW, I'D STRONGLY SUGGEST:

Change this thread title to something like "Lyonn CTB-800V can be DIFFERENT DEVICES, added support for ONE of the sub-models" so nobody else will buy one believing that support for it has been implemented, as it happened to me.
BETTER JUST STAY FAR AWAY FROM LYONN CTB-800V, exactly because you don't know what device you are actually buying and the brand is not actively supporting its connection to NUT.

greenpark-code · 2023-12-30T04:50:51Z

I'm here to share some info which could be useful if anybody in the future will try to get a "Lyonn CTB-800V" working with NUT, and also to ask about something.

The "Lyonn CTB-800V" device for which this thread was originated should be an equivalent of
Voltronic AP Series, a control software for it should exist, called ViewPower

Another device of which a "Lyonn CTB-800V" can be an equivalent is Powercom BNT, software for it should be made by Megatec, called Upsilon and RUPS).

NOTE: Kstar invited me to install Upsilon 2000, and after my first failure report with the version I had found searching, 5.3, they pointed me to their download page with the current version 5.4 https://www.kstar.com/download5/index_10.jhtml which should allow to select USB as the communication type. They included a screen capture in their mail, clearly a configuration dialogue implemented through a Windows GUI.

PROBLEM: That option only exists in their Windows software. The Linux software comes in various flavors, I installed and tried all of them one by one, each one is various version numbers behind the Windows version (2.1 to 3.0) and none allows anything but COM port communications, RS232, there's no way to select USB communications (actually the two oldest versions try to open specifically an xterm-256 colors window in order to show the configuration dialogue, which fails; the dialogue in terminal window is correctly displayed by the other versions and I sent them a screen capture of it, no option to select communication type and switch to USB). That's to say that Kstar answered immediately but their kind input resulted in further time waste. (Besides, the deploy scheme was kind of archaic but installing didn't ruin anything else in this system anyways and I could very easily remove afterwards.)

Another device of which a "Lyonn CTB-800V" can be an equivalent was made by a manufacturer which no longer exists and I have no further information on that.

The "Lyonn CTB-800V" device I bought is actually a KStar Micropower, a standalone software working with it in Linux is KPower (it can be downloaded through this link http://tinyurl.com/5cey6e2f I have no link to a digital signature nor sha256sum or other hash to check integrity / origin, I've launched it anyways).

Beside the fact that it's not open source, it doesn't connect to the UPS unless I call it as root (well if I want it to shutdown the computer it must have root permissions anyways).
I've made a small script to start it, mainly to set the port permissions and to see if I could get rid of a warning this software gives, apparently not justified, about the lack of an environment variable (and I can't but the software sets the var anyways and apparently works just fine, although I haven't tested all the features yet).

#!/bin/bash

runtimeDir="/home/$(logname)/MANINST/KPower"

# sudo chmod 0755 /dev/bus/usb/003
sudo chmod 0666 /dev/bus/usb/003/003

echo ''
lsusb -v -s 003 # just to check viable access to the port, this works without root permissions
echo ''

cd "$runtimeDir"

if [ "$XDG_RUNTIME_DIR" == "" ]
then
	export XDG_RUNTIME_DIR="$runtimeDir"
else
	export XDG_RUNTIME_DIR="$runtimeDir:$XDG_RUNTIME_DIR"
fi

echo "Current value of XDG_RUNTIME_DIR: \"$XDG_RUNTIME_DIR\""
echo ''

sudo ./run.sh

Notice that reading data from the UPS is feasible without root permissions once the above chmod command has been issued:

$ lsusb -v -s 003

Bus 003 Device 003: ID 09d6:0001  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x09d6 
  idProduct          0x0001 
  bcdDevice            1.10
  iManufacturer           1 KSTAR
  iProduct                2 UPS
  iSerial                 3 KHID0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      0 None
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.00
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     655
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
Device Status:     0x0000
  (Bus Powered)

$ ls -l /dev/bus/usb/003/
total 0
crw-rw-r-- 1 root root 189, 256 dic 29 21:55 001
crw-rw-r-- 1 root root 189, 257 dic 29 21:55 002
crw-rw-rw- 1 root root 189, 258 dic 30 01:56 003

PROBLEM: there's no ARM64 version, I couldn't have KPower on a Raspberry PI anyways.

PROBLEM: KPower doesn't seem to allow actions like launching scripts when the main power goes down or comes back or the battery goes lower than a certain level. I don't see, at present, how I could signal the necessity to shut down to other machines, physical or virtual.

(Of course a tiny circuit with an opto-coupler would allow me to detect 220V and its absence and "report" it to the GPIO pins of a raspberry PI, and from it I could warn other machines via networking, but that would not provide me any hint on the level of the battery within the UPS.)

As for having a correct configuarion for NUT for this Kstar Micropower equivalent, the local tech guy, admittedly always giving proof of good will and always showing the best attitude, tried to put pressure on their supplier, alas with no success.

(I'll have to buy another UPS soon and of course I'll avoid Kstar and before buying I'll check that the actual device within the box is not X, incognito mode, and that it is one which actually works with NUT.)

QUESTIONS

I'm trying NUT version 2.8.1, current most recent stable, building from source.

Surprise, nutdrv_qx is not taking the same parameters at all, no vendorid, no productid, no port = auto, no subdriver (possibly replaced by protocol).

I'm trying these lines in ups.conf

maxretry = 1
[Lyonn_CTB800V]
driver = nutdrv_qx
port = /dev/bus/usb/003/003
desc = "Lyonn CTB-800V (KSTAR Micropower submodel)"

# nutdrv_qx -a Lyonn_CTB800V
Network UPS Tools - Generic Q* Serial driver 0.36 (2.8.1)
tcgetattr(/dev/bus/usb/003/003): Inappropriate ioctl for device
upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it

# upsdrvctl start
Network UPS Tools - UPS driver controller 2.8.1
Network UPS Tools - Generic Q* Serial driver 0.36 (2.8.1)
tcgetattr(/dev/bus/usb/003/003): Inappropriate ioctl for device
upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
Driver failed to start (exit status=1)

I've pasted above the result of lsusb -v -s 003 and it starts by Bus 003 Device 003, am I supposed to give the port in another format?

I don't think this UPS would use serial over USB, anyways just to possibly save some ping pong time, I don't have any /dev/ttyUSB* devices:

# ls -l /dev/tty*
crw-rw-rw- 1 root  tty     5,  0 dic 30 00:03 /dev/tty
crw--w---- 1 root  tty     4,  0 dic 29 21:55 /dev/tty0
crw--w---- 1 gdm   tty     4,  1 dic 29 21:55 /dev/tty1
crw--w---- 1 root  tty     4, 10 dic 29 21:55 /dev/tty10
crw--w---- 1 root  tty     4, 11 dic 29 21:55 /dev/tty11
crw--w---- 1 root  tty     4, 12 dic 29 21:55 /dev/tty12
crw--w---- 1 root  tty     4, 13 dic 29 21:55 /dev/tty13
crw--w---- 1 root  tty     4, 14 dic 29 21:55 /dev/tty14
crw--w---- 1 root  tty     4, 15 dic 29 21:55 /dev/tty15
crw--w---- 1 root  tty     4, 16 dic 29 21:55 /dev/tty16
crw--w---- 1 root  tty     4, 17 dic 29 21:55 /dev/tty17
crw--w---- 1 root  tty     4, 18 dic 29 21:55 /dev/tty18
crw--w---- 1 root  tty     4, 19 dic 29 21:55 /dev/tty19
crw--w---- 1 lemon tty     4,  2 dic 29 21:55 /dev/tty2
crw--w---- 1 root  tty     4, 20 dic 29 21:55 /dev/tty20
crw--w---- 1 root  tty     4, 21 dic 29 21:55 /dev/tty21
crw--w---- 1 root  tty     4, 22 dic 29 21:55 /dev/tty22
crw--w---- 1 root  tty     4, 23 dic 29 21:55 /dev/tty23
crw--w---- 1 root  tty     4, 24 dic 29 21:55 /dev/tty24
crw--w---- 1 root  tty     4, 25 dic 29 21:55 /dev/tty25
crw--w---- 1 root  tty     4, 26 dic 29 21:55 /dev/tty26
crw--w---- 1 root  tty     4, 27 dic 29 21:55 /dev/tty27
crw--w---- 1 root  tty     4, 28 dic 29 21:55 /dev/tty28
crw--w---- 1 root  tty     4, 29 dic 29 21:55 /dev/tty29
crw--w---- 1 root  tty     4,  3 dic 29 21:55 /dev/tty3
crw--w---- 1 root  tty     4, 30 dic 29 21:55 /dev/tty30
crw--w---- 1 root  tty     4, 31 dic 29 21:55 /dev/tty31
crw--w---- 1 root  tty     4, 32 dic 29 21:55 /dev/tty32
crw--w---- 1 root  tty     4, 33 dic 29 21:55 /dev/tty33
crw--w---- 1 root  tty     4, 34 dic 29 21:55 /dev/tty34
crw--w---- 1 root  tty     4, 35 dic 29 21:55 /dev/tty35
crw--w---- 1 root  tty     4, 36 dic 29 21:55 /dev/tty36
crw--w---- 1 root  tty     4, 37 dic 29 21:55 /dev/tty37
crw--w---- 1 root  tty     4, 38 dic 29 21:55 /dev/tty38
crw--w---- 1 root  tty     4, 39 dic 29 21:55 /dev/tty39
crw--w---- 1 root  tty     4,  4 dic 29 21:55 /dev/tty4
crw--w---- 1 root  tty     4, 40 dic 29 21:55 /dev/tty40
crw--w---- 1 root  tty     4, 41 dic 29 21:55 /dev/tty41
crw--w---- 1 root  tty     4, 42 dic 29 21:55 /dev/tty42
crw--w---- 1 root  tty     4, 43 dic 29 21:55 /dev/tty43
crw--w---- 1 root  tty     4, 44 dic 29 21:55 /dev/tty44
crw--w---- 1 root  tty     4, 45 dic 29 21:55 /dev/tty45
crw--w---- 1 root  tty     4, 46 dic 29 21:55 /dev/tty46
crw--w---- 1 root  tty     4, 47 dic 29 21:55 /dev/tty47
crw--w---- 1 root  tty     4, 48 dic 29 21:55 /dev/tty48
crw--w---- 1 root  tty     4, 49 dic 29 21:55 /dev/tty49
crw--w---- 1 root  tty     4,  5 dic 29 21:55 /dev/tty5
crw--w---- 1 root  tty     4, 50 dic 29 21:55 /dev/tty50
crw--w---- 1 root  tty     4, 51 dic 29 21:55 /dev/tty51
crw--w---- 1 root  tty     4, 52 dic 29 21:55 /dev/tty52
crw--w---- 1 root  tty     4, 53 dic 29 21:55 /dev/tty53
crw--w---- 1 root  tty     4, 54 dic 29 21:55 /dev/tty54
crw--w---- 1 root  tty     4, 55 dic 29 21:55 /dev/tty55
crw--w---- 1 root  tty     4, 56 dic 29 21:55 /dev/tty56
crw--w---- 1 root  tty     4, 57 dic 29 21:55 /dev/tty57
crw--w---- 1 root  tty     4, 58 dic 29 21:55 /dev/tty58
crw--w---- 1 root  tty     4, 59 dic 29 21:55 /dev/tty59
crw--w---- 1 root  tty     4,  6 dic 29 21:55 /dev/tty6
crw--w---- 1 root  tty     4, 60 dic 29 21:55 /dev/tty60
crw--w---- 1 root  tty     4, 61 dic 29 21:55 /dev/tty61
crw--w---- 1 root  tty     4, 62 dic 29 21:55 /dev/tty62
crw--w---- 1 root  tty     4, 63 dic 29 21:55 /dev/tty63
crw--w---- 1 root  tty     4,  7 dic 29 21:55 /dev/tty7
crw--w---- 1 root  tty     4,  8 dic 29 21:55 /dev/tty8
crw--w---- 1 root  tty     4,  9 dic 29 21:55 /dev/tty9
crw------- 1 root  root    5,  3 dic 29 21:55 /dev/ttyprintk
crw-rw---- 1 root  dialout 4, 64 dic 29 21:55 /dev/ttyS0
crw-rw---- 1 root  dialout 4, 65 dic 29 21:55 /dev/ttyS1
crw-rw---- 1 root  dialout 4, 74 dic 29 21:55 /dev/ttyS10
crw-rw---- 1 root  dialout 4, 75 dic 29 21:55 /dev/ttyS11
crw-rw---- 1 root  dialout 4, 76 dic 29 21:55 /dev/ttyS12
crw-rw---- 1 root  dialout 4, 77 dic 29 21:55 /dev/ttyS13
crw-rw---- 1 root  dialout 4, 78 dic 29 21:55 /dev/ttyS14
crw-rw---- 1 root  dialout 4, 79 dic 29 21:55 /dev/ttyS15
crw-rw---- 1 root  dialout 4, 80 dic 29 21:55 /dev/ttyS16
crw-rw---- 1 root  dialout 4, 81 dic 29 21:55 /dev/ttyS17
crw-rw---- 1 root  dialout 4, 82 dic 29 21:55 /dev/ttyS18
crw-rw---- 1 root  dialout 4, 83 dic 29 21:55 /dev/ttyS19
crw-rw---- 1 root  dialout 4, 66 dic 29 21:55 /dev/ttyS2
crw-rw---- 1 root  dialout 4, 84 dic 29 21:55 /dev/ttyS20
crw-rw---- 1 root  dialout 4, 85 dic 29 21:55 /dev/ttyS21
crw-rw---- 1 root  dialout 4, 86 dic 29 21:55 /dev/ttyS22
crw-rw---- 1 root  dialout 4, 87 dic 29 21:55 /dev/ttyS23
crw-rw---- 1 root  dialout 4, 88 dic 29 21:55 /dev/ttyS24
crw-rw---- 1 root  dialout 4, 89 dic 29 21:55 /dev/ttyS25
crw-rw---- 1 root  dialout 4, 90 dic 29 21:55 /dev/ttyS26
crw-rw---- 1 root  dialout 4, 91 dic 29 21:55 /dev/ttyS27
crw-rw---- 1 root  dialout 4, 92 dic 29 21:55 /dev/ttyS28
crw-rw---- 1 root  dialout 4, 93 dic 29 21:55 /dev/ttyS29
crw-rw---- 1 root  dialout 4, 67 dic 29 21:55 /dev/ttyS3
crw-rw---- 1 root  dialout 4, 94 dic 29 21:55 /dev/ttyS30
crw-rw---- 1 root  dialout 4, 95 dic 29 21:55 /dev/ttyS31
crw-rw---- 1 root  dialout 4, 68 dic 29 21:55 /dev/ttyS4
crw-rw---- 1 root  dialout 4, 69 dic 29 21:55 /dev/ttyS5
crw-rw---- 1 root  dialout 4, 70 dic 29 21:55 /dev/ttyS6
crw-rw---- 1 root  dialout 4, 71 dic 29 21:55 /dev/ttyS7
crw-rw---- 1 root  dialout 4, 72 dic 29 21:55 /dev/ttyS8
crw-rw---- 1 root  dialout 4, 73 dic 29 21:55 /dev/ttyS9

The default path everything gets installed to is
/usr/local/ups/

Quote from docs/config-notes.txt

NOTE: The default path for a source installation is `/usr/local/ups/etc`,
while packaged installation will vary.
For example, `/etc/nut` is used on Debian and derivatives,
while `/etc/ups` or `/etc/upsd` is used on RedHat and derivatives.

Right there it would be a great spot to add info on how to change the installation path, but the info is not there so I searched a bit more...

In configure.ac I found a test which made me think that if any config file was found in /etc/nut then everything would be installed the Debian way.
That code fragment:

        for D in \
            /etc/nut /etc/ups \
            /usr/etc/nut /usr/etc/ups \
            /usr/local/etc/nut /usr/local/etc/ups \
            /usr/local/nut/etc /usr/local/ups/etc \
        ; do
            if test -e "$D/ups.conf" || test -e "$D/upsmon.conf" \
            || ( test -e "$D/upsd.conf" && test -e "$D/upsd.users" ) \
            ; then
                DEPLOYED_SYSCONFDIR="$D"
                break

But that didn't happen.

Finally, I created symlinks:

cd /usr/local/ups/etc/
mkdir ORIGS
mv -i *.sample ORIGS/
mv -i /etc/nut/* .
cd /etc/nut/
ln -s /usr/local/ups/etc/* .
cd /usr/bin/
ln -s /usr/local/ups/bin/* .
cd ../lib
ln -s /usr/local/ups/lib/* .
cd ../libexec/
ln -s /usr/local/ups/libexec/* .
cd ../sbin/
ln -s /usr/local/ups/sbin/* .
cd ../share/
ln -s /usr/local/ups/share/* .
cd man
ln -s /usr/local/ups/share/man/* .
cd man5/
ln -s /usr/local/ups/share/man/man5/* .
cd ../man8
ln -s /usr/local/ups/share/man/man8/* .

A bit of a hack actually, but it should work, right?

# ls /usr/local/ups/bin/
al175         bestuferrups  genericups    microdowell           powercom    tripplitesu
apcsmart      bestups       isbmex        microsol-apc          powerpanel  upsc
apcsmart-old  blazer_ser    ivtscd        netxml-ups            rhino       upscmd
apcupsd-ups   clone         liebert       nutdrv_qx             riello_ser  upscode2
bcmxcp        clone-outlet  liebert-esp2  nutdrv_siemens-sitop  safenet     upslog
belkin        dummy-ups     masterguard   NUT-Monitor           skel        upsrw
belkinunv     etapro        metasys       nut-scanner           sms_ser     upssched-cmd
bestfcom      everups       mge-shut      oneac                 solis       victronups
bestfortress  gamatronic    mge-utalk     optiups               tripplite

There's no usbhid-ups and no blazer_usb (there's a blazer_ser which seems to be for RS232 communication).
Is this correct in NUT version 2.8.1 or should the build give me more files that I'm missing?

jimklimov · 2023-12-30T10:56:47Z

Thanks for the detailed investigation.

On the technical NUT-related parts:

for configure script options, there are --help and docs/configure.txt (IIRC) to detail the settings; most of the path-related ones are standard for autotools, you may want to look at --prefix and --sysconfdir. To emulate the choices made by distro-provided packages, check their recipes. See also about "in-place" build approach in NUT docs or wiki.
Note that if you only have a custom-built NUT without traces of a packaged one, paths are not a great concern beside habit :)
the lack of usb-related drivers (and options in nutdrv_qx) suggests you lack libusb-dev (or equivalent for your distro) or your configure choices excluded it. Check if the configuration summary says whether it detected/selected USB? Check docs/config-prereqs.txt if some chapter matches your platform, to add missing packages.
Currently NUT uses USB device handles as enumerated by libusb (and filtered by vendorid/productid/serial/bus/device/busport options, if given). The port=auto is an ignored stub, because some port must be there in standard driver config.

jimklimov · 2023-12-30T10:58:35Z

Also note the runtime user/group account settings - by default would be nobody. Need to specify if you have dedicated nut ones.

greenpark-code · 2023-12-30T16:49:56Z

Thanks for all the information.

I was actually lacking libusb-dev, now installed.

The following feedback (just as parts of the previous posts) is not meant to be conflictive, it's just meant for you to evaluate what a "tabula rasa" guy ( = totally ignorant about nut) finds when approaching the distribution tarball in order to build from source.

"in-place" would be great.

Quote from docs/configure.txt

For common developer iterations, porting to new platforms, or in-place testing, running the ./ci_build.sh script can be a helpful
one-stop solution.

There is no file with that name in the nut-2.8.1.tar.gz distribution tarball.

Again docs/configure.txt mentions plenty of nice options, e.g.

--enable-keep_nut_report_feature (that could be enabled by default IMHO)
--enable-inplace-runtime

BUT it doesn't show an example call, so it's unclear to which script I should feed these options, maybe to ./configure on the command line, maybe to 'autogen.sh' in case of a git clone... So I have to go looking into 'configure' and see if it would take into account any such parameters... or just try and see what happens. (You know that kind of "I'm a bit lost" feeling that docs are supposed to mitigate or prevent? :D )

Anyways, feeding them to ./configure seems OK:

./configure --enable-keep_nut_report_feature --enable-inplace-runtime
checking for CONFIG_FLAGS... --enable-keep_nut_report_feature --enable-inplace-runtime

No complains followed :D it should be the way to go :D

config.nut_report_feature.log has been produced and build USB drivers: yes

I'll test with the newly built drivers and report.

jimklimov · 2023-12-30T19:56:55Z

Thanks for the feedback, especially about ci_build.sh (although it relies on e.g. autogen.sh which is not supposed to be part of the tarball, historically). I'll ponder this bit.

The configure.txt file documents options for the eponymous script :)

greenpark-code · 2023-12-31T02:12:22Z

Thanks for the feedback, especially about ci_build.sh (although it relies on e.g. autogen.sh which is not supposed to be part of the tarball, historically). I'll ponder this bit.

The configure.txt file documents options for the eponymous script :)

No thanks to you for all the info. Understood about configure.txt!

Best so far

This is the only combination I could test so far which is showing me the UPS online, switches to "on batteries" if I disconnect the UPS from the 220 V power, goes back to "online" when I reconnect.

ups.conf

maxretry = 1
[Lyonn_CTB800V]
driver = usbhid-ups
port = auto
subdriver = "Belkin/Liebert HID 0.18"
vendorid = "09d6"
productid = "0001"
bus = "003"
desc = "Lyonn CTB-800V (KSTAR Micropower submodel)"

Battery charge doesn't always show the correct value, sometimes it shows 0% or 24% (after disconnecting and reconnecting the 220 V power it was showing 100%).

All the other usbhid-ups subdrivers give "on batteries" status when the UPS is receiving the 220 V power (I have snapshots of the monitor app and the server status in case any of it is needed).

After modifying the config file, I was restarting with these commands (probably, stopping the server already stops the driver, however, unsure, I was doing what follows, a tiny script actually):

sudo systemctl stop nut-server

sudo upsdrvctl stop
sudo upsdrvctl start

sudo systemctl reload-or-restart nut-server
# sudo systemctl reload-or-restart nut-client
# sudo systemctl restart nut-monitor

KPower uses USBHID

I'm going to share screenshots of KPower, in its 'Settings' screen you'll see that version info mentions usbhid.
So, usbhid-ups would probably be the way to go, but with a subdriver tailored for the protocol this KStar speaks (go figure, some virtual machine to sniff the USB traffic, maybe, much simpler if the brand KStar, which sells worldwide, stepped in and did the job, but I guess this same situation has been faced with most if not all of the drivers and subdrivers NUT works with).

REMARKABLE to me: that warning I get when starting KPower is identical to the one I get when starting the NUT qt monitor app, but that coincidence might be an irrelevant qt-related detail only related with this system's setup.

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'

The command I use to launch the NUT qt monitor app:

python3 /usr/local/ups/share/nut-monitor/app/NUT-Monitor-py3qt5

As I posted previously, I start KPower through a little script which sets the port permissions (each reboot restores the standard permissions) and queries the bus with lsusb -v -s 003, which is why you see all those lines above the warning, in the terminal window in the following snapshot:

^ NOTICE here "USB HID version: v1.0.2"

Anyways... I've shared the snapshots just in case they are of any interest to anybody, apart the USBHID important point. I don't see how KPower could allow me to call some scripts to signal to other machines, physical or virtual, that they have to shutdown. And in any case I couldn't have it running on ARM64, while nut works via networking and it can be built in lots of platforms, so I'd really like to see a subdriver for this UPS. More caution with the next one, KStar blacklisted.

And this is all for now.

greenpark-code · 2023-12-31T02:45:35Z

P.S.: one last remark.

I can start KPower, stop it, launch NUT and the qt monitor app, the connection to the UPS works (with problems as displayed above).
On the other hand, if I close the qt monitor app, stop nut-server, stop nut-driver (with an error most likely because stopping the server already stops the driver), I can launch KPower but it does not connect to the UPS, I have to reboot for KPower to work again.

greenpark-code · 2023-12-31T02:56:53Z

P.P.S.: I was forgetting to share something which might be significant to somebody.

The output of lsusb -v -s 003 was occasionally much longer than what I posted above. That was possibly happening in between attempts with certain NUT driver+subdriver combinations, or after launching KPower, I didn't dig into how to trigger that situation at will (I was actually querying in that way just to check that port and device were still accessible).

Here it is:

$ lsusb -v -s 003

Bus 003 Device 003: ID 09d6:0001  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x09d6 
  idProduct          0x0001 
  bcdDevice            1.10
  iManufacturer           1 KSTAR
  iProduct                2 UPS
  iSerial                 3 KHID0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      0 None
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.00
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     655
          Report Descriptor: (length is 655)
            Item(Global): Usage Page, data= [ 0x84 ] 132
                            Power Device Page
            Item(Local ): Usage, data= [ 0x04 ] 4
                            UPS
            Item(Main  ): Collection, data= [ 0x01 ] 1
                            Application
            Item(Global): Report ID, data= [ 0x01 ] 1
            Item(Local ): Usage, data= [ 0x30 ] 48
                            Voltage
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x04 ] 4
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
            Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
                            System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
            Item(Global): Unit Exponent, data= [ 0x01 ] 1
                            Unit Exponent: 1
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x35 ] 53
                            Percent Load
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x32 ] 50
                            Frequency
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
            Item(Global): Unit, data= [ 0x01 0xf0 ] 61441
                            System: SI Linear, Unit: Seconds^-1
            Item(Global): Unit Exponent, data= [ 0x01 ] 1
                            Unit Exponent: 1
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x36 ] 54
                            Temperature
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x80 ] 32768
            Item(Global): Logical Maximum, data= [ 0xff 0x7f ] 32767
            Item(Global): Unit, data= [ 0x01 0x00 0x01 0x00 ] 65537
                            System: SI Linear, Unit: Kelvin
            Item(Global): Unit Exponent, data= [ 0x01 ] 1
                            Unit Exponent: 1
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Unit, data= [ 0x00 ] 0
                            System: None, Unit: (None)
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x02 ] 2
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0xff 0x00 0x00 ] 65535
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x73 ] 115
                            Communication Lost
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Local ): Usage, data= [ 0x63 ] 99
                            Voltage out of range
            Item(Local ): Usage, data= [ 0x6f ] 111
                            Buck
            Item(Local ): Usage, data= [ 0x62 ] 98
                            Internal Failure
            Item(Local ): Usage, data= [ 0x72 ] 114
                            Awaiting Power
            Item(Local ): Usage, data= [ 0x58 ] 88
                            Test
            Item(Local ): Usage, data= [ 0x68 ] 104
                            Shutdown Requested
            Item(Local ): Usage, data= [ 0x5a ] 90
                            Audible Alarm Control
            Item(Global): Report Size, data= [ 0x01 ] 1
            Item(Global): Report Count, data= [ 0x09 ] 9
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0x01 ] 1
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Report Size, data= [ 0x07 ] 7
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Main  ): Feature, data= [ 0x03 0x00 ] 3
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Report ID, data= [ 0x02 ] 2
            Item(Local ): Usage, data= [ 0x58 ] 88
                            Test
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0x0a ] 10
            Item(Main  ): Feature, data= [ 0x82 0x00 ] 130
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Report ID, data= [ 0x03 ] 3
            Item(Local ): Usage, data= [ 0x51 ] 81
                            Switch Off Control
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0x0a ] 10
            Item(Main  ): Feature, data= [ 0x82 0x00 ] 130
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Report ID, data= [ 0x04 ] 4
            Item(Local ): Usage, data= [ 0x5a ] 90
                            Audible Alarm Control
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0x0a ] 10
            Item(Main  ): Feature, data= [ 0x82 0x00 ] 130
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Report ID, data= [ 0x05 ] 5
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0x0a ] 10
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x01 0x00 ] 1
            Item(Global): Logical Maximum, data= [ 0x0f 0x27 ] 9999
            Item(Main  ): Feature, data= [ 0x82 0x00 ] 130
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Report ID, data= [ 0x64 ] 100
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x04 ] 4
            Item(Global): Logical Minimum, data= [ 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Report ID, data= [ 0x65 ] 101
            Item(Local ): Usage, data= [ 0x30 ] 48
                            Voltage
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x02 ] 2
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
            Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
                            System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
            Item(Global): Unit Exponent, data= [ 0x05 ] 5
                            Unit Exponent: 5
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x31 ] 49
                            Current
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
            Item(Global): Unit, data= [ 0x01 0x00 0x10 0x00 ] 1048577
                            System: SI Linear, Unit: Ampere
            Item(Global): Unit Exponent, data= [ 0x0e ] 14
                            Unit Exponent: 14
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x32 ] 50
                            Frequency
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
            Item(Global): Unit, data= [ 0x01 0xf0 ] 61441
                            System: SI Linear, Unit: Seconds^-1
            Item(Global): Unit Exponent, data= [ 0x01 ] 1
                            Unit Exponent: 1
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Unit, data= [ 0x00 ] 0
                            System: None, Unit: (None)
            Item(Global): Report ID, data= [ 0x66 ] 102
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x0f ] 15
            Item(Global): Logical Minimum, data= [ 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x0a ] 10
            Item(Global): Logical Minimum, data= [ 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x0a ] 10
            Item(Global): Logical Minimum, data= [ 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Report ID, data= [ 0x67 ] 103
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x6a ] 106
                            Reserved
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x0d ] 13
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Usage Page, data= [ 0x84 ] 132
                            Power Device Page
            Item(Local ): Usage, data= [ 0x24 ] 36
                            Power Summary
            Item(Main  ): Collection, data= [ 0x00 ] 0
                            Physical
            Item(Global): Report ID, data= [ 0x0f ] 15
            Item(Local ): Usage, data= [ 0x24 ] 36
                            Power Summary
            Item(Local ): Usage, data= [ 0x01 ] 1
                            iName
            Item(Local ): Usage, data= [ 0xfe ] 254
                            iProduct
            Item(Local ): Usage, data= [ 0xff ] 255
                            iSerialNumber
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x03 ] 3
            Item(Global): Logical Minimum, data= [ 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Main  ): Feature, data= [ 0x03 0x00 ] 3
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Usage Page, data= [ 0x85 ] 133
                            Battery System Page
            Item(Local ): Usage, data= [ 0x89 ] 137
                            iDeviceChemistry
            Item(Local ): Usage, data= [ 0x8f ] 143
                            iOEMInformation
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x02 ] 2
            Item(Global): Logical Minimum, data= [ 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Main  ): Feature, data= [ 0x03 0x00 ] 3
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Local ): Usage, data= [ 0xd1 ] 209
                            Battery Present
            Item(Local ): Usage, data= [ 0x2c ] 44
                            Capacity Mode
            Item(Local ): Usage, data= [ 0x8b ] 139
                            Rechargeable
            Item(Global): Report Size, data= [ 0x01 ] 1
            Item(Global): Report Count, data= [ 0x03 ] 3
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0x01 ] 1
            Item(Main  ): Feature, data= [ 0x03 0x00 ] 3
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Report Size, data= [ 0x05 ] 5
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Main  ): Feature, data= [ 0x03 0x00 ] 3
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Local ): Usage, data= [ 0x83 ] 131
                            Design Capacity
            Item(Local ): Usage, data= [ 0x8c ] 140
                            Warning Capacity Limit
            Item(Local ): Usage, data= [ 0x29 ] 41
                            Remaining Capacity Limit
            Item(Local ): Usage, data= [ 0x8d ] 141
                            Capacity Granularity 1
            Item(Local ): Usage, data= [ 0x8e ] 142
                            Capacity Granularity 2
            Item(Global): Report Size, data= [ 0x18 ] 24
            Item(Global): Report Count, data= [ 0x05 ] 5
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0xff 0xff 0x00 ] 16777215
            Item(Global): Unit, data= [ 0x01 0xf0 0x10 0x00 ] 1110017
                            System: SI Linear, Unit: Seconds^-1*Ampere
            Item(Global): Unit Exponent, data= [ 0x00 ] 0
                            Unit Exponent: 0
            Item(Main  ): Feature, data= [ 0x03 0x00 ] 3
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Usage Page, data= [ 0x84 ] 132
                            Power Device Page
            Item(Local ): Usage, data= [ 0x40 ] 64
                            Config Voltage
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0xff 0x00 0x00 ] 65535
            Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
                            System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
            Item(Global): Unit Exponent, data= [ 0x05 ] 5
                            Unit Exponent: 5
            Item(Main  ): Feature, data= [ 0x03 0x00 ] 3
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Unit, data= [ 0x00 ] 0
                            System: None, Unit: (None)
            Item(Global): Usage Page, data= [ 0x85 ] 133
                            Battery System Page
            Item(Local ): Usage, data= [ 0x67 ] 103
                            Full Charge Capacity
            Item(Global): Report Size, data= [ 0x18 ] 24
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0xff 0xff 0x00 ] 16777215
            Item(Global): Unit, data= [ 0x01 0xf0 0x10 0x00 ] 1110017
                            System: SI Linear, Unit: Seconds^-1*Ampere
            Item(Global): Unit Exponent, data= [ 0x00 ] 0
                            Unit Exponent: 0
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x66 ] 102
                            Remaining Capacity
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Unit, data= [ 0x00 ] 0
                            System: None, Unit: (None)
            Item(Global): Usage Page, data= [ 0x85 ] 133
                            Battery System Page
            Item(Local ): Usage, data= [ 0xd0 ] 208
                            AC Present
            Item(Local ): Usage, data= [ 0x44 ] 68
                            Charging
            Item(Local ): Usage, data= [ 0x45 ] 69
                            Discharging
            Item(Global): Report Size, data= [ 0x01 ] 1
            Item(Global): Report Count, data= [ 0x03 ] 3
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0x01 ] 1
            Item(Main  ): Feature, data= [ 0x83 0x00 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Report Size, data= [ 0x05 ] 5
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Main  ): Feature, data= [ 0x03 0x00 ] 3
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Local ): Usage, data= [ 0x66 ] 102
                            Remaining Capacity
            Item(Global): Report Size, data= [ 0x18 ] 24
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0xff 0xff 0x00 ] 16777215
            Item(Global): Unit, data= [ 0x01 0xf0 0x10 0x00 ] 1110017
                            System: SI Linear, Unit: Seconds^-1*Ampere
            Item(Global): Unit Exponent, data= [ 0x00 ] 0
                            Unit Exponent: 0
            Item(Main  ): Input, data= [ 0x83 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Global): Unit, data= [ 0x00 ] 0
                            System: None, Unit: (None)
            Item(Local ): Usage, data= [ 0x68 ] 104
                            Run Time To Empty
            Item(Global): Report Size, data= [ 0x10 ] 16
            Item(Global): Report Count, data= [ 0x01 ] 1
            Item(Global): Logical Minimum, data= [ 0x00 0x00 0x00 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0xff 0x00 0x00 ] 65535
            Item(Global): Unit, data= [ 0x01 0x10 ] 4097
                            System: SI Linear, Unit: Seconds
            Item(Global): Unit Exponent, data= [ 0x00 ] 0
                            Unit Exponent: 0
            Item(Main  ): Input, data= [ 0x83 ] 131
                            Constant Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Main  ): End Collection, data=none
            Item(Main  ): End Collection, data=none
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
Device Status:     0x0000
  (Bus Powered)

jimklimov · 2024-12-16T18:56:10Z

@greenpark-code : please check if your device is in fact supported by usbhid-ups per PR #2723 (needs NUT v2.8.2 to pass a subdriver option, or that PR would try it out of the box)?

Added support for LYONN CTB-800V

c39d091

Small protocol validation change to add support for the protocol used by the LYONN CTB-800V UPS.

zykh reviewed Aug 22, 2015
View reviewed changes

nutdrv_qx: add support for LYONN CTB-800V

b155eaf

Small protocol validation change in 'voltronic-qs-hex' subdriver to add support for the protocol used by the LYONN CTB-800V UPS.

zykh added a commit to zykh/nut that referenced this pull request Oct 6, 2015

HCL: LYONN CTB-800V supported by nutdrv_qx

4b29fa0

Protocol: 'voltronic-qs-hex' Reference: networkupstools#230

zykh closed this Oct 6, 2015

sliverc mentioned this pull request Dec 10, 2015

HCL Legrand KEOR MULTIPLUG supported by blazer_usb #248

Closed

jimklimov added the Qx protocol driver Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others label Dec 14, 2023

MAGADE007 mentioned this pull request Feb 11, 2024

Add support for AEG UPS Protect D series, like model D3000, using USB connection #2301

Open

ripf77 mentioned this pull request Mar 28, 2024

blazer_usb failing after apt-get upgrade #2377

Closed

jimklimov mentioned this pull request Dec 16, 2024

usbhid-ups: added support for 0x09d6:0x0001 (KSTAR) UPSes using MGE HID #2723

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Added support for LYONN CTB-800V #230

Added support for LYONN CTB-800V #230

marianojan commented Aug 22, 2015 •

edited by jimklimov

Loading

zykh Aug 22, 2015

zykh commented Aug 22, 2015

zykh commented Aug 22, 2015

marianojan commented Aug 23, 2015

zykh commented Aug 24, 2015

zykh commented Oct 6, 2015

marianojan commented Oct 7, 2015

greenpark-code commented Dec 14, 2023 •

edited

Loading

jimklimov commented Dec 14, 2023 •

edited

Loading

greenpark-code commented Dec 20, 2023 •

edited

Loading

jimklimov commented Dec 20, 2023

greenpark-code commented Dec 20, 2023 •

edited

Loading

jimklimov commented Dec 21, 2023 •

edited

Loading

greenpark-code commented Dec 22, 2023

jimklimov commented Dec 22, 2023

greenpark-code commented Dec 26, 2023

jimklimov commented Dec 26, 2023 via email

greenpark-code commented Dec 28, 2023 •

edited

Loading

greenpark-code commented Dec 30, 2023 •

edited

Loading

jimklimov commented Dec 30, 2023

jimklimov commented Dec 30, 2023

greenpark-code commented Dec 30, 2023 •

edited

Loading

jimklimov commented Dec 30, 2023

greenpark-code commented Dec 31, 2023 •

edited

Loading

greenpark-code commented Dec 31, 2023 •

edited

Loading

greenpark-code commented Dec 31, 2023 •

edited

Loading

jimklimov commented Dec 16, 2024 •

edited

Loading

Added support for LYONN CTB-800V #230

Added support for LYONN CTB-800V #230

Conversation

marianojan commented Aug 22, 2015 • edited by jimklimov Loading

zykh Aug 22, 2015

Choose a reason for hiding this comment

zykh commented Aug 22, 2015

zykh commented Aug 22, 2015

marianojan commented Aug 23, 2015

zykh commented Aug 24, 2015

zykh commented Oct 6, 2015

marianojan commented Oct 7, 2015

greenpark-code commented Dec 14, 2023 • edited Loading

jimklimov commented Dec 14, 2023 • edited Loading

greenpark-code commented Dec 20, 2023 • edited Loading

jimklimov commented Dec 20, 2023

greenpark-code commented Dec 20, 2023 • edited Loading

jimklimov commented Dec 21, 2023 • edited Loading

greenpark-code commented Dec 22, 2023

jimklimov commented Dec 22, 2023

greenpark-code commented Dec 26, 2023

jimklimov commented Dec 26, 2023 via email

greenpark-code commented Dec 28, 2023 • edited Loading

greenpark-code commented Dec 30, 2023 • edited Loading

QUESTIONS

jimklimov commented Dec 30, 2023

jimklimov commented Dec 30, 2023

greenpark-code commented Dec 30, 2023 • edited Loading

jimklimov commented Dec 30, 2023

greenpark-code commented Dec 31, 2023 • edited Loading

Best so far

KPower uses USBHID

greenpark-code commented Dec 31, 2023 • edited Loading

greenpark-code commented Dec 31, 2023 • edited Loading

jimklimov commented Dec 16, 2024 • edited Loading

marianojan commented Aug 22, 2015 •

edited by jimklimov

Loading

greenpark-code commented Dec 14, 2023 •

edited

Loading

jimklimov commented Dec 14, 2023 •

edited

Loading

greenpark-code commented Dec 20, 2023 •

edited

Loading

greenpark-code commented Dec 20, 2023 •

edited

Loading

jimklimov commented Dec 21, 2023 •

edited

Loading

greenpark-code commented Dec 28, 2023 •

edited

Loading

greenpark-code commented Dec 30, 2023 •

edited

Loading

greenpark-code commented Dec 30, 2023 •

edited

Loading

greenpark-code commented Dec 31, 2023 •

edited

Loading

greenpark-code commented Dec 31, 2023 •

edited

Loading

greenpark-code commented Dec 31, 2023 •

edited

Loading

jimklimov commented Dec 16, 2024 •

edited

Loading