search for: mqtt

Tom via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: >>That makes sense. So you'll have input voltage, output voltage, and >>output current I would guess. You might consider a nodemcu (ESP8266) >>publishing via MQTT to reduce power and use of unobtainium. > > Yes, that is exactly what I was planning to instrument. Maybe battery > voltage too if I can access it. I thought it might be useful to be able to > see the open circuit battery voltage while charging, I dunno. Actually, given that the outp...

But... I cheated. I looked at some projects on Github that do this and they usually link to the NUT and MQTT libraries. While I've done that in the past, more recently I delegated the actual publishing to the Mosquitto client `mosquitto_pub` thinking much more thought has gone into that than anything I would code. And for this task, I find the output of `upsc` to be easily parsable and again, more tho...

I'm using the python-libvirt library and finding that I cannot get .destroy() or .shutdown() to work. https://github.com/simora/docker-libvirt-flask/blob/cba6041b47bdf4ccb3b9506a0379cf8c788a9a57/root/app/mqtt.py#L96 That is the line in my code. .create() works fine and using virsh in the docker container works fine to destroy the domain as well. This is based on ubuntu bionic in a docker container with the libvirt socket and such made available. .create() works, listing works and virsh works so permis...

On Sat, Aug 22, 2020 at 10:32:09AM -0400, Jeremy Markle wrote: > I'm using the python-libvirt library and finding that I cannot get > .destroy() or .shutdown() to work. > > https://github.com/simora/docker-libvirt-flask/blob/cba6041b47bdf4ccb3b9506a0379cf8c788a9a57/root/app/mqtt.py#L96 Your code has alot of "< 0" checks. This is the C API behaviour to return -1 on error. In python we raise exceptions on error. so you try try/except to catch them Daniel

...2020 at 10:32:09AM -0400, Jeremy Markle wrote: > > I'm using the python-libvirt library and finding that I cannot get > > .destroy() or .shutdown() to work. > > > > > https://github.com/simora/docker-libvirt-flask/blob/cba6041b47bdf4ccb3b9506a0379cf8c788a9a57/root/app/mqtt.py#L96 > > Your code has alot of "< 0" checks. This is the C API behaviour to return > -1 > on error. In python we raise exceptions on error. so you try try/except to > catch them > > Daniel > >

My $0.02: LB is baked in to nut behavior. So if a UPS doesn't report LB, then it makes sense to synthesize it. Synthetic LB is the cleanest fix at the earlier processing point. One could have a config that is basically synthetic-lowbatt-percent that generates LB if (as Jim says) on battery, not calibrating, and batt% <= that. One could have a similar config

Good Morning, I am working on setting up a 12V DC UPS that will power a NAS and a router for a few hours. It contains some lithium-ion batteries, and a BMS to control charging. Since it is just a dumb box with batteries, it has no intelligence to inform the NAS of its status. This is where NUT comes in... I would like to incorporate a Raspberry Pi NUT server into this scheme. The Rpi can