@bdarcus Yes funny you should say about the user / pass settings in nut config. @suman and I had discussed hiding / auto dealing with these but I’m afraid I just didn’t get around to it and so they are left open. In the standalone mode they could be auto generated as they are only for intra nut function. Don’t use a regular user just follow the mouse over suggestions and go with some nonsense user and pass. I will try and sort this in a future pull request.
As for if you should try out the built in nut config or stick with what’s working for you now then that’s down really to how curious you are. As you say the nut driver for your particular UPS model is a generic one and apparently as per the NUT Hardware compatibility list it only shows as 2 our of 5 stars due to no manufacturer participation but on the other hand there are successful reports of older NUT releases retrieving info successfully, ie heres a couple of CP1000PFCLCD info dumps via “upsc ups” commands.
If you do decide to take the plunge then remember to first “yum remove” the rpm package you put in before configuring and enabling the nut service, you might also have to reboot after the yum remove, just to be safe.
As it stands there is little immediate advantage in using the built in nut, except maybe email notifications, but that should change over time. Although I would hazard a guess that if it does work for you it will be easier to configure. Also if you use netserver mode (but get standalone mode working first) you can use fancy desktop apps to monitor you ups over the network. If you also power other machines on the network and the network itself from this UPS you could even have them all shutdown automatically followed shortly after by Rockstor by running nut clients on them and Rockstor’s nut in netserver mode as master. You might like that; you have 600W to play with there so keep an eye on load.
So short of it is if this is critical leave as is as it’s working but otherwise it would be great to know how you get on. Though maybe in a specific new thread so we don’t clutter this one up.