search for: hu_flag_semi_stat

...mit", NULL, - "%.0f", HU_FLAG_OK, NULL }, /* Read only */ + /* the following is writeable for the Back-UPS ES 650 */ + { "battery.charge.low", ST_FLAG_RW | ST_FLAG_STRING, 5, "UPS.PowerSummary.RemainingCapacityLimit", NULL, + "%.0f", HU_FLAG_OK | HU_FLAG_SEMI_STATIC, NULL }, { "battery.charge.warning", ST_FLAG_STRING, 5, "UPS.PowerSummary.WarningCapacityLimit", NULL, "%.0f", HU_FLAG_OK, NULL }, /* Read only */ { "battery.runtime", 0, 0, "UPS.PowerSummary.RunTimeToEmpty", NULL, "%.0f", HU_FLAG_...

...mit", NULL, - "%.0f", HU_FLAG_OK, NULL }, /* Read only */ + /* the following is writeable for the Back-UPS ES 650 */ + { "battery.charge.low", ST_FLAG_RW | ST_FLAG_STRING, 5, "UPS.PowerSummary.RemainingCapacityLimit", NULL, + "%.0f", HU_FLAG_OK | HU_FLAG_SEMI_STATIC, NULL }, { "battery.charge.warning", ST_FLAG_STRING, 5, "UPS.PowerSummary.WarningCapacityLimit", NULL, "%.0f", HU_FLAG_OK, NULL }, /* Read only */ { "battery.runtime", 0, 0, "UPS.PowerSummary.RunTimeToEmpty", NULL, "%.0f", HU_FLAG_...

...y-1 errors." -- https://twitter.com/secretGeek/status/7269997868 It seems like the NUT usbhid-ups driver is a little overzealous when it comes to caching UPS values associated with NUT variables: it is not refreshing certain variables unless they were changed through NUT. This is due to the HU_FLAG_SEMI_STATIC flag here (so other similarly-marked variables would be affected as well): https://github.com/networkupstools/nut/blob/master/drivers/apc-hid.c#L309 If you stop and start the driver, it should refresh. I created an issue on Github so we don't forget: https://github.com/networkupstools/nut/i...

...T_FLAG_STRING, 5, "UPS.PowerSummary.RemainingCapacityLimit", NULL, - "%.0f", HU_FLAG_OK, NULL }, /* Read only */ + { "battery.charge.low", ST_FLAG_RW | ST_FLAG_STRING, 5, "UPS.PowerSummary.RemainingCapacityLimit", NULL, + "%.0f", HU_FLAG_OK | HU_FLAG_SEMI_STATIC, NULL }, { "battery.runtime", 0, 0, "UPS.PowerSummary.RunTimeToEmpty", NULL, "%.0f", HU_FLAG_OK, NULL }, { "battery.voltage", 0, 0, "UPS.PowerSummary.Voltage", NULL, "%.1f", HU_FLAG_OK, NULL }, { "battery.voltage.nominal&q...

...g to 'mge-hid.c': /* Output page */ { "output.voltage", 0, 0, "UPS.PowerConverter.Output.Voltage", NULL, "%.1f", 0, NULL }, { "output.voltage.nominal", ST_FLAG_RW | ST_FLAG_STRING, 5, "UPS.Flow.[4].ConfigVoltage", NULL, "%.0f", HU_FLAG_SEMI_STATIC, NULL }, + { "output.voltage.nominal", 0, 0, "UPS.PowerSummary.ConfigVoltage", NULL, "%.0f", HU_FLAG_STATIC, NULL }, { "output.current", 0, 0, "UPS.PowerConverter.Output.Current", NULL, "%.2f", 0, NULL }, { "output.powerfactor&quo...

...mapping function for Belkin/Liebert since their boolean True value is often 1e-7 instead of 1. I would recommend checking the values to make sure that they match the labels, but static attributes such as CapacityMode, DesignCapacity, FullChargeCapacity and Rechargeable can get a HU_FLAG_STATIC or HU_FLAG_SEMI_STATIC flag (see drivers/usbhid-ups.h) so that the driver does not waste time polling them. Some values like iManufacturer, iProduct and iSerialNumber are likely duplicates of the values in the USB device descriptor, and do not need to be included. >>> >> Which part of the website? >...

...efore use usbfs: process 19862 (hald-addon-usbh) did not claim interface 0 before use My question: is this due to my kernel version, the version of my libusb (libusb-0.1.12-5.1), or do I need a more up-to-date version of drivers/libusb.c? When I make a change to a HID variable that is marked as HU_FLAG_SEMI_STATIC using upsrw (e.g. battery.charge.low), the value is changed in the device (and shows changed with e.g. upsc), but the hal side never knows about the change (e.g. when looking at the hal data with hal-device-manager). I believe this is because the variable "data_has_changed" in the h...

Hi folks, I have a curious issue I'm trying to understand. I'll give my problem description first, then suggested metadata below. My setup is as shown in http://networkupstools.org/docs/user-manual.chunked/images/advanced.png, where my UPS is connected to my NAS via USB, and other computers as well as the NAS are powered by the UPS. As a test, I configured the NAS to enter safe mode,

Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the