realies

Changing the switch structure for a key-value array pair wouldn't be increasing processing speed but allowing for further and easier progression of the plugin. Future functionality might allow the user to specify UPS information that they would want to be displayed. This would be easy if the front-end (html and javascript) is isolated from the back-end (php) if both communicate via a REST interface. In practice, nut_status.php would be replying with a json array containing the information and the front-end would be drawing it. Another reason to have the key-value array pair would be if there is more UPS specific rules such as the Eaton one. Another case would be falling back to VA instead of W for the load section of UPS units without real power and a specific estimation rule. All of those would be easier to write and manage outside a switch statement. Happy to prepare a refactor for the aforementioned.

Nice finding, @pwm. I wonder if the value in watts can be estimated for other types of UPS units. There should probably be a fallback to displaying volt-amperes instead of watts if it cannot be estimated.

Since it's not possible to create an issue in the repository, I'm writing one here. Consider parsing the whole output of `upsc ups` to a key-value pair array instead of iterating through the keys and making use-cases for individual keys. This way the output from the ups service would be more easily accessible which eases refactoring and introducing new functionality. Would be exciting to see a separation between the front and back end too. In regards to the above, this should be sufficient to generate the array: exec("/usr/bin/upsc ups 2>/dev/null", $stdout); print_r(array_reduce($stdout, function($carry, $line) { list($key, $value) = explode(":", $line, 2); $carry[trim($key)] = trim($value); return $carry; }, [])); A demo can be seen here.

It seems nut package has been updated to 2.7.5-pre. Is this replacing the old binary and can the update be reflected in the changelog? Update: usbhid-ups stayed 2.7.4, great to see Nominal Power and UPS Load (W) working on Eaton! Update: As discussed in the package repository, ups.power.nominal/100*battery.charge does not produce the expected results. When using Eaton 5E 650i with the NUT v2 plugin, it reports: Nominal Power: 650 UPS Load: 253 UPS Load %: 39 Eaton UPS Companion (attached to a Win10 VM) reports: Output Load: 203W Usage: 39% Looking into the changes made to estimate Eaton's realpower when it is not available, I am proposing a similar change to the NUT v2 plugin until 2.7.5 or newer are deployed without any issues.

Thanks for testing. Could this be reported to the repo? I am currently unable to reproduce, but remember that when the UPS was passed through to a Win10 VM it did reconnect every now and again.

Have the USB resets been addressed? There's some functionality in master that I am hoping to see in unRAID.

This message seems to be constatnly repeating in the logs: ==> /var/log/gitlab/node-exporter/current <== 2017-12-02_11:13:22.15422 time="2017-12-02T11:13:22Z" level=error msg="ERROR: mdadm collector failed after 0.000246s: error parsing mdstatus: error parsing mdline: sbName=/boot/config/super.dat" source="node_exporter.go:95"

With the latest update docker fails with: /usr/bin/docker: Error response from daemon: endpoint with name Netdata already exists in network host. Removing the container and image and re-adding the app does not fix it.

Nextcloud says it's version 12.0.2 and that there is a new version available even after a forced update of the container. Thoughts?

It is a valid workaround.

Removing the container and image (without orphan containers) and reinstalling worked. Although now I think I am having trouble with the built-in https support of 6.4.0.rc9f.

Having issues updating and starting on 6.4.0-rc9f.

Does it mean that if the system is powered off, the ups goes out of power and shuts down, upon the power being restored the computer will not power on? Or is that nothing will power on the computer if power gets restored during the interval of the UPS being still up and the computer being off already?