I just went through setting up Hub Ping and a System Start piston to deal with power outages; proper shutdown and restart.
Then I snoop around this morning looking at old posts and low there is this
I have a wired APC and this would have saved me all that piddling around.
That's all the source, I couldn't find an installable exe there.
FWIW, this is good work and I certainly don't mean to crap in your thread, but if I had a Pi, NAS, or other KVM besides my Win10 running VBox (for ES cookie server), I'd probably get NUT Server going with the latest single device driver below.
You needed to open the releases section on the right-hand side of the link @arnb provided. I am using 0.5.0 rc6 from 2018. There is a setup exe in the list of assets.
I guess I'm still a little confused about a few things with the UPS monitor driver.
I can see many attributes in the driver in RM, but only a few (states) are exposed in the driver (and usable on a tile). Why aren't all the attributes exposed in the driver?
The attributes that are shown when the driver is selected in rule manager don't align well with the attributes showing in apcupsd or returned to the driver from the PC. Which one exactly is TIMELEFT?
Make sure you have the device selected on the left, and I did notice that you need to select the device before selecting the template, i.e. if I chose the Attribute template then selected the device, I still saw a reduced attribute list. If I unselected the template and selected it again (which the device still selected, I then saw the correct list.
Do you see something like this list in the Device Edit page?
Ultimately I'll leave this one for the developer to answer, but in the end if the driver does not include code to interpret the piece of data, it won't automatically appear. You should request an update to the driver / VBS script if there is something you are after.
I do not see all those states. It's never shown more than 3 or 4 states in the driver.
Between this and the java errors still in the driver when events are returned from the PC and all the other issues, I'm not sure I'm going to pursue trying to get this working. There's too much effort for too little benefit for me at this time.
It looks like you don't have a NOMPOWER value in APC so the parse is getting tripped up on it. Try just commenting out line 259 (put double slashes at the beginning of the line '//').
I agree with @FriedCheese2006, the NOMPOWER element is not in the Debug input message. Line 259 should be commented out on your system, then try again. There is a status element value of "" so hopefully it will work.