Re: [Nut-upsuser] UPS shuts down on NUT boot with low battery [APS Back-UPS RS 550G]
Thanks for the reply. However these two FAQ are unfortunately not describing the situation. - The first issue is that NUT switches off the UPS upon reboot on low battery (not that it dies because of low battery) - The second issue is that the UPS does not recognise being online again (not that the PC does not restart) Sent from my iPhone > On 11 Jun 2019, at 02:03, Charles Lepple wrote: > >> On Jun 10, 2019, at 2:32 PM, Marc Finns wrote: >> >> Hello, I read all FAQ and other sources but I could not find this situation, >> so I thought of asking the experts. >> I successfully configured a Raspberry NUT server to control my UPS that >> powers several devices (NUC with ESXI VMs, Synology NAS etc). >> All works well in principle, but I have the following behaviours that I >> could not find described anywhere. >>• When power returns after the system has shuts down because of battery >> flat, all restarts immediately. However, as soon as NUT server reboots, it >> switches the UPS to battery till it dies – even if line is present > > This is FAQ #49: > https://networkupstools.org/docs/FAQ.html#_my_ups_powers_up_immediately_after_a_power_failure_instead_of_waiting_for_the_batteries_to_recharge > >>• If power returns after the system has started the shutdown sequence, >> the UPS does not return to AC mode and stays on battery till it dies. > > This is FAQ #51: > > https://networkupstools.org/docs/FAQ.html#_the_power_came_back_during_the_shutdown_but_before_the_ups_power_off_now_the_ups_does_not_reboot_and_my_computer_stays_off_how_can_i_fix_that > > These are subtle edge cases, but apparently a lot of entry-level UPS models > omit the interface to control these two situations. As mentioned in both of > the FAQ explanations, you can work around this in software, or you can sell > the UPS to someone who annoys you, and look for one that provides the > "battery.charge.restart" NUT variable (Minimum battery level for UPS restart > after power-off) and the "shutdown.return" instant command. > > In both cases, we have tried to collect NUT variable dumps and command > listings from NUT users here: https://networkupstools.org/ddl/ > > Note that this information is best-effort, and sometimes vendors change the > underlying firmware without changing the model name. There is no substitute > for testing when it comes to shutdown procedures, unfortunately. > > (If you get an error from the mailing list about the message size, please try > turning off HTML posting, and gzip any log files.) > >> >> Therefore, behaviour (1) creates a dangerous endless loop where power >> returns, all boots, after 30 sec power is brutally cut, and so on. The net >> result is that I already killed a disk. >> Please note: I never had this behaviour when I used the Synology as network >> UPS server. >> Is anyone having the same / having a suggestion? >> Thanks a million. Marc. >> >> Hardware: Raspberry PI >> OS name and version: Raspbian (Linux raspberrypi 4.19.42-v7+ #1219 SMP Tue >> May 14 21:20:58 BST 2019 armv7l GNU/Linux) >> NUT version 2.7.4 installed from repo >> UPS: APS Back-UPS RS 550G >> Driver configuration: >> [ups] >>driver = usbhid-ups >>port = auto >>desc = "Back-UPS RS 550G" >> ignorelb >> override.battery.charge.low = 20 >> override.battery.runtime.low = 200 >> pollfreq = 15 >> >> Output of /lib/nut/usbhid-ups -DD -a ups >> Network UPS Tools - Generic HID driver 0.41 (2.7.4) >> USB communication driver 0.33 >> 0.00 debug level is '2' >> 0.004536 upsdrv_initups... >> 0.006506 Checking device (051D/0002) (001/004) >> 0.009744 - VendorID: 051d >> 0.009826 - ProductID: 0002 >> 0.010240 - Manufacturer: American Power Conversion >> 0.010866 - Product: Back-UPS RS 550G FW:857.L5 .I USB FW:L5 >> 0.011214 - Serial Number: 3B1547X04970 >> 0.011271 - Bus: 001 >> 0.011768 - Device release number: 0090 >> 0.011822 Trying to match device >> 0.012248 Device matches >> 0.013822 HID descriptor length 1134 >> 0.016761 Report Descriptor size = 1134 >> 0.019750 Using subdriver: APC HID 0.96 >> 0.019824 112 HID objects found >> 0.020801 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, >> Offset: 0, Size: 8, Value: 2 >> 0.021529 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: >> 0x02, Offset: 0, Size: 8, Value: 3 >> 0.022404 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, >> ReportID: 0x03, Offset: 0, Size: 8, Value: 4 >> 0.023913 Path: UPS.PowerSummary.iOEMInformation, Type: Feature, >> ReportID: 0x04, Offset: 0, Size: 8, Value: 1 >> 0.025154 Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID: >> 0x05, Offset: 0, Size: 8, Value: 1 >> 0.026405 Path: UPS.PowerSummary.Charging, Type: Input, ReportID: 0x06, >> Offset: 0, Size: 8, Value: 1 >> 0.027244 Path: UPS.PowerSummary.Charging, Type: Feature, ReportID: 0
Re: [Nut-upsuser] UPS shuts down on NUT boot with low battery [APS Back-UPS RS 550G]
On Jun 10, 2019, at 2:32 PM, Marc Finns wrote: > > Hello, I read all FAQ and other sources but I could not find this situation, > so I thought of asking the experts. > I successfully configured a Raspberry NUT server to control my UPS that > powers several devices (NUC with ESXI VMs, Synology NAS etc). > All works well in principle, but I have the following behaviours that I could > not find described anywhere. > • When power returns after the system has shuts down because of battery > flat, all restarts immediately. However, as soon as NUT server reboots, it > switches the UPS to battery till it dies – even if line is present This is FAQ #49: https://networkupstools.org/docs/FAQ.html#_my_ups_powers_up_immediately_after_a_power_failure_instead_of_waiting_for_the_batteries_to_recharge > • If power returns after the system has started the shutdown sequence, > the UPS does not return to AC mode and stays on battery till it dies. This is FAQ #51: https://networkupstools.org/docs/FAQ.html#_the_power_came_back_during_the_shutdown_but_before_the_ups_power_off_now_the_ups_does_not_reboot_and_my_computer_stays_off_how_can_i_fix_that These are subtle edge cases, but apparently a lot of entry-level UPS models omit the interface to control these two situations. As mentioned in both of the FAQ explanations, you can work around this in software, or you can sell the UPS to someone who annoys you, and look for one that provides the "battery.charge.restart" NUT variable (Minimum battery level for UPS restart after power-off) and the "shutdown.return" instant command. In both cases, we have tried to collect NUT variable dumps and command listings from NUT users here: https://networkupstools.org/ddl/ Note that this information is best-effort, and sometimes vendors change the underlying firmware without changing the model name. There is no substitute for testing when it comes to shutdown procedures, unfortunately. (If you get an error from the mailing list about the message size, please try turning off HTML posting, and gzip any log files.) > > Therefore, behaviour (1) creates a dangerous endless loop where power > returns, all boots, after 30 sec power is brutally cut, and so on. The net > result is that I already killed a disk. > Please note: I never had this behaviour when I used the Synology as network > UPS server. > Is anyone having the same / having a suggestion? > Thanks a million. Marc. > > Hardware: Raspberry PI > OS name and version: Raspbian (Linux raspberrypi 4.19.42-v7+ #1219 SMP Tue > May 14 21:20:58 BST 2019 armv7l GNU/Linux) > NUT version 2.7.4 installed from repo > UPS: APS Back-UPS RS 550G > Driver configuration: > [ups] > driver = usbhid-ups > port = auto > desc = "Back-UPS RS 550G" >ignorelb >override.battery.charge.low = 20 >override.battery.runtime.low = 200 >pollfreq = 15 > > Output of /lib/nut/usbhid-ups -DD -a ups > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 >0.00 debug level is '2' >0.004536 upsdrv_initups... >0.006506 Checking device (051D/0002) (001/004) >0.009744 - VendorID: 051d >0.009826 - ProductID: 0002 >0.010240 - Manufacturer: American Power Conversion >0.010866 - Product: Back-UPS RS 550G FW:857.L5 .I USB FW:L5 >0.011214 - Serial Number: 3B1547X04970 >0.011271 - Bus: 001 >0.011768 - Device release number: 0090 >0.011822 Trying to match device >0.012248 Device matches >0.013822 HID descriptor length 1134 >0.016761 Report Descriptor size = 1134 >0.019750 Using subdriver: APC HID 0.96 >0.019824 112 HID objects found >0.020801 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, > Offset: 0, Size: 8, Value: 2 >0.021529 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: > 0x02, Offset: 0, Size: 8, Value: 3 >0.022404 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, > ReportID: 0x03, Offset: 0, Size: 8, Value: 4 >0.023913 Path: UPS.PowerSummary.iOEMInformation, Type: Feature, > ReportID: 0x04, Offset: 0, Size: 8, Value: 1 >0.025154 Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID: > 0x05, Offset: 0, Size: 8, Value: 1 >0.026405 Path: UPS.PowerSummary.Charging, Type: Input, ReportID: 0x06, > Offset: 0, Size: 8, Value: 1 >0.027244 Path: UPS.PowerSummary.Charging, Type: Feature, ReportID: 0x06, > Offset: 0, Size: 8, Value: 1 >0.028082 Path: UPS.PowerSummary.Discharging, Type: Input, ReportID: > 0x06, Offset: 8, Size: 8, Value: 0 >0.028965 Path: UPS.PowerSummary.Discharging, Type: Feature, ReportID: > 0x06, Offset: 8, Size: 8, Value: 0 >0.029785 Path: UPS.PowerSummary.APCStatusFlag, Type: Input, ReportID: > 0x06, Offset: 16, Size: 8, Value: 8 >0.030618 Path: UPS.PowerSummary.APCStatusFlag, Type: Feature, ReportID: > 0x06, Offset: 16, Siz
