To be honest, most of the NUT development effort is focused on
shutting down servers, so there isn't a whole lot of work on the
desktop side. Having not used KDE in many years, I hadn't heard of Solid.
For anyone else casually interested, this seems to be a good introduction:
http://shubham.chaudhary.xyz/blog/2013/11/09/kde-solid-namespace/
And this bug seems to show that "solid-hardware list" is talking to UPower for
battery information: https://lists.debian.org/debian-qt-kde/2015/03/msg00554.html
Before UPower came along, we had a version of usbhid-ups which was a bridge
between the UPS and DeviceKit Power. It was, unfortunately, an either-or
proposition: you could have the UPS show up in the GUI, or you could have the
traditional NUT upsmon/upsd/driver stack, and all of the network connectivity
of the latter. That bridge code no longer exists.
However someone could probably write a NUT client that does something similar:
connect to a running upsd, and publish UPS information via DBus. I am not
volunteering, but it does sound like an interesting idea.
In the near term, you might consider KNutClient <http://knut.prynych.cz> or
NUT-Monitor <http://www.lestat.st/en/informatique/projets/nut-monitor>.
Thanks for the informations! Actually, I have written a script using
upsc to monitor the ups and handle the important events, but it should
be simpler to use some desktop interface. I hope someone will volunteer
for that; it is beyond my competences.
Anyway, I'd be happy to help by testing patches.
_______________________________________________
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
