NUT?

dennypage

I see references to NUT being available in 2.3, but it doesn't show up in available packages on my 2.3 units. The only place I see it is in my 2.3.1 test system. It this being held for 2.3.1?

dennypage

Hmm… I also see pfBlockerNG version 2.0.14 on the test system, but 2.0.12 on the production systems.

Gertjan

Your pfSense can't connect to the pfSense site where the available packages are listed ?

I upgraded pfBlockerNG 2.0.14 a couple of say ago.
Installed NUT this morning - from the available package list.

dennypage

The problem appears to be specific to the factory images. The factory package list on firmware.netgate.com:

https://firmware.netgate.com/pkg/pfSense_factory-v2_3_0_amd64-pfSense_factory-v2_3_0/packagesite.txz

Does not have NUT and still has pfBlockerNG 2.0.12.

jimp

At the moment we still have to manually merge things over to factory on all branches, it's not something we have safely automated yet. Next time we sync that over it'll show up.

dennypage

Thanks Jim. Appreciate an update when time permits.

jimp

I just merged things over, they're building now, may be up any moment now (or already), or shortly.

dennypage

Wow. Faster than I expected! Many thanks!

dennypage

I see pfBlockerNG updated to 2.0.14, but NUT is still missing. Yes, I'll wait longer. :)

dennypage

And there it is.

Thank you Jim.

Ramosel

@jimp:

I just merged things over, they're building now, may be up any moment now (or already), or shortly.

Thanks Jim!

I only use NUT locally for shutdown control but its still been a missing link to complete conversion to 2.3
Hopefully it will eventually get updated to include more common UPS models… I still have to cheat it to recognize the unit I use.

FWIW, the dashboard widget reports all the correct text but no color in the bar graph for status on charge and load.

dennypage

Rather than add more UPS models to the selection list, I think it make more sense to move away from using UPS model names and use NUT driver names instead. There really are far too many UPS models to attempt to make it practical to maintain a list here.

There are nearly a 1000 UPS models currently listed in the NUT hardware database:

http://networkupstools.org/stable-hcl.html

but only 51 drivers needed to cover the entire lot.

Ramosel

@dennypage:

http://networkupstools.org/stable-hcl.html

but only 51 drivers needed to cover the entire lot.

Sounds like the better solution…
Thanks for the memory jog, I did check the model I have vs. the model I'm telling NUT I have and its the same driver so I think that is why its working... sorta.

Just FYI if anyone working on the Dashboard Widget is reading...
On the Services/NUT/UPS Status I see all fields populated and bar graphs working. On the Dashboard Widget bar graphs are not filling and status is missing.

NUT1.jpg_thumb

NUT2.png_thumb

dennypage

My widget shows status and battery charge correctly. It doesn't show load, but the UPS attached to doesn't report load. From the model in your pics I'm guessing that you have a Tripp Lite ECO850LCD? If so, I have one in shipping and should be able test with it on Friday.

Btw, have you cleared your browser cache?

Ramosel

@dennypage:

My widget shows status and battery charge correctly. It doesn't show load, but the UPS attached to doesn't report load. From the model in your pics I'm guessing that you have a Tripp Lite ECO850LCD? If so, I have one in shipping and should be able test with it on Friday.

Btw, have you cleared your browser cache?

Actually Its a CyberPower model 850LCD. I don't know, is the same box marketed as a Tripp Lite??? They look very similar but not exactly the same. Maybe the same Chinese guts. To get it to work I use the "APC Back-UPS ES USB" and "auto (USB only)" settings. So the ECO850LCD model field is being read through the driver (usbhid-ups). It is not being provided.

Yes, have cleared cache.

dennypage

I'm pretty sure that Tripp Lite and Cyberpower are not the same units. I've only had a couple of Cyberpower units, a CP750LCD which died, and a CP1500PFCLCD which is still in operation.

If you want to see what the driver is actually reading from the unit, you can run the upsc command like so:
```
upsc upsname


where upsname is the name you gave the ups in the NUT configuration page.

You might find that the unit is simply reporting incorrect information. My CP1500PFCLCD for instance, always reports an output voltage of 136-139, which is known to be bogus. Other people report problems with battery voltage reporting, although mine appears to be correct.

More info can be found here:

  [http://networkupstools.org/ddl/](http://networkupstools.org/ddl/)

Ramosel

@dennypage:

If you want to see what the driver is actually reading from the unit, you can run the upsc command like so:
```
upsc upsname

Thanks, for some reason I had it in my head it was upsd <upsname>
and it all shows valid data

And don't ask me why… now the widget is showing full data display.

Oh, and I too am a Marvin fan!

Rick</upsname>