Jammy B

Members
  • Posts

    125
  • Joined

  • Last visited

About Jammy B

  • Birthday 10/25/1984

Converted

  • Gender
    Male
  • Location
    United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jammy B's Achievements

Apprentice

Apprentice (3/14)

15

Reputation

1

Community Answers

  1. thanks for the script. i've put that in as even after adding the nominal voltage in yesterday, NUT failed this morning. will report back tomorrow if the script does the job. thank you for the assistance on all this as always.
  2. its a cheap UPS, its just had new batteries put into it. when they "fail" in a couple years i will look at it then. in the meantime, is there a script i can make/run that runs 5 minutes after startup to restart Nut? odd that the NUT starting issue only started after i removed the battery voltage and nominal voltage in the ups.conf, i might re-instate the nominal voltage today to see if it "cures" the issue, then if need be, reinstate the battery voltages and reduce "on battery" runtime to 1 minute instead of 2 minutes. thanks for looking at it.
  3. no problem, attached. amjam-diagnostics-20240327-1411.zip
  4. hi @Rysz new issue now, Server turns off at midnight each night as per sleep scehdule. at 6am it then turns back on via BIOS alarm. but now NUT will not start. when i go into NUT settings and say "Yes" to Start NUT service. it then starts and runs. i attach diag prior to manually starting NUT and after i have started NUT. what have i busted this time? nut-debug-20240327091949 post.zip nut-debug-20240327091532 pre.zip
  5. [ups] driver = nutdrv_qx port = auto vendorid = 0001 productid = 0000 protocol = hunnox langid_fix = 0x0409 novendor noscanlangid default.battery.voltage.high = 27.50 default.battery.voltage.low = 21.40 default.battery.voltage.nominal = 24.00 default.input.voltage.nominal = 230 runtimecal = 900,100,1800,50 removed: default.battery.voltage.high = 27.50 default.battery.voltage.low = 21.40 default.battery.voltage.nominal = 24.00 Then Nut would not start. changed the attribute to runtime.low and then it loaded. see how that fares i guess.
  6. Good morning! i have now replaced the 2no batteries within the Powercool UPS and it is now functioning correctly. running the UPS directly connected to my laptop via USB and running the software that came with the Powercool doesn't tell me anything about the battery health. As far as it is concerned, the batteries within the unit are fine. now that i have replaced the batteries, the 2 minute process is working fine. What do i need to do [besides remove my custom battery voltages] to enable NUT to accurately read from the UPS? edit to add - the "battery capacity" doesn't change even with new batteries. i think the software is a bit "universal" as it has options to do tests that do not do anything.
  7. yeah its doing a parity check. looks like the power cut has revealed other issues as when i cut the power to the UPS, the UPS just goes off. so i've directly connected to the UPS with a laptop via USB and the battery is 0%. i don't know if its just because it has been flattened and needs time to re-charge or if its f##ked. its only as old as my posts on here asking if NUT could get it! i've disabled sleep/shutdown on the server as it won't finish a Parity check by midnight. when i get back home from work tonight i will have a look at battery % again. worrying part is the SOC on NUT is dictated by the battery voltages i've manually entered. seems i need to do some further investigation on this as NUT won't know the battery is flat either. will update this evening. thanks again.
  8. you are the best! that fixed it and re-instated my old settings. thank you. no notifcations as i wasn't home when it lost power so it couldn't get the messages out. thanks for remembering how "cool" my Powercool was!
  9. running == nut-2.8.1-x86_64-2stable.ssl11 has something been updated to remove the settings on NUT to set Battery level to initiate shutdown (%): Runtime left to initiate shutdown (minutes): Time on battery before shutdown (seconds): as i seem to have lost those options in NUT settings and we have had two power cuts in the last 12 hours and the server has not switched off due to not being told to. i had it set 2 minutes after noticing a power cut, shut down. how do i put that back?
  10. removing those 3 lines of code causes NUT to not function. whilst they aren’t necessarily correct, the config works enough that when on battery it then powers off after 2 minutes. what do you recommend I do next?
  11. no screen on my basic UPS - https://www.cclonline.com/pc-1000va-powercool-smart-ups-1000va-3-x-uk-plug-2-x-iec-rj45-x-2-usb-led-display/ the charging indicator is solid green which means charged and that doesn't change unless i have a powercut or manually kill power to it. it powers my Unraid machine, UDMPRO, switch and CCTV NVR no problem. its never switched off and we don't get many powercuts and when we have its been flawless in signalling the Unraid machine to switch off. its now on 52% charged as well. it was on 3% when i posted this morning is there a setting i might have put in to it that it is reading the wrong thing, but what would increase over time? my 3 year old thread -
  12. i've had NUT running a couple years now and one thing it does i still cannot solve. the UPS runs 24/7. my Unraid server does not, its on from 6am to midnight each day. When Unraid first boots, the battery % is at 0%. some point this afternoon, it have steadily "charged" itself up and got to 100%. i don't understand why it does this when it is 100% already as it is fully charged and on 24/7! any suggestions on what i need to check/alter to make it display correctly? or am i totally misinterpreting something?
  13. i've just seen the reddit post about the current installs expiring 1/1/24. i'm running controller 5.14.23 with 12 or so sites on it. can i migrate to this reborn or do i need to do something else? edit - went for it to 8.0.24. it went without a hitch and is working great. thank you.
  14. Yeah it’s loading up fine. Just normally a blank screen on boot. Only change is updating to 6.11.5