Re: [Nut-upsuser] Weekend Puzzle: computer posing as an UPS

Jim Klimov via Nut-upsuser writes: > Did anyone trod these side paths yet, any learnings? :D To me, the answer to power for little things is increasingly POE. I think there are POE ejectors that provide adequate USB-C power. You need 802.3at (POE+) surely, but that's normal these days. ___

Re: [Nut-upsuser] Weekend Puzzle: computer posing as an UPS

Kelly Byrd writes: > With USB-C ports and cables, there are a ton of profiles, I don't know what > the new Pi's support, but likely something like 3A @ 5V, 9V, or 12V over > USB-C Up to the RPI4, I was pretty sure there wasn't PD, just 5V and it drew what it drew, and you hoped that the supply w

Re: [Nut-upsuser] Weekend Puzzle: computer posing as an UPS

Jim Klimov via Nut-upsuser writes: > I am experimenting with a Raspberry Pi, and it is fed from my PC > (Debian-ish Linux) that is in turn protected by an UPS - so runs NUT. > > As far as the Pi is concerned, the bigger computer is its wall power > source (provides the USB socket) and being a

Re: [Nut-upsuser] Question about nut-dependencies

Jim Klimov via Nut-upsuser writes: > Upsmon as such has no need for XML (libneon et al); that would be > nut-scanner and the Eaton NetXML protocol driver. Sure, but it is normal for packaging systems to build the entire project, so that whatever someone wants is available, and thus depend on the

Re: [Nut-upsuser] APC BX ...MI series

Peter Bell writes: > On 20/08/2024 19:18, Greg Troxel wrote: >> People running old versions is a recurring problem for an (unrelated) >> project that I maintain, and I've adopted a policy that bug reports may >> only be filed against the latest formal release or the cu

Re: [Nut-upsuser] APC BX ...MI series

Peter Bell writes: > The problem I had with my BX950MI unit was that it was frequently > reporting off-line, on batt and often not responding to requests from > apcupsd (apcaccess) and then going back online again. However, the > warranty replacement was prompted by a failed battery, apparently >

Re: [Nut-upsuser] Getting Error Using upscmd

Atomic_Sheep via Nut-upsuser writes: > I'm trying to run: > > $ upscmd -l myups > > where myups is the [myups] I provided in ups.conf file. and l is lower > case l. In other words I'm trying to see what commands my UPS > supports. > > I'm using the latest fully updated Raspbian 32bit as a fresh i

Re: [Nut-upsuser] Eco Eclipse 1600 connects via USB put does not put out any data:

Stefan Schumacher via Nut-upsuser writes: > Thanks for the info. Nut runs on bare metal, there is no > virtualization layer. I will have a look at the github post after > writing this post. I have compiled and installed nut 2.8.2 as > suggested. But now I am confused: Where is the usb-hid driver,

Re: [Nut-upsuser] Eco Eclipse 1600 connects via USB put does not put out any data:

Stefan Schumacher via Nut-upsuser writes: > I am using: Debian Bookworm 12.6 with these packages, which were > installed from the official Debian Repository. > ii nut 2.8.0-7 > all network UPS tools - metapackage > ii nut-client 2.8.0-

Re: [Nut-upsuser] Permissions error

Jack McGee writes: >> mythuser@amethi:~$ upsdrvctl start >> Network UPS Tools - UPS driver controller 2.7.4 >> Network UPS Tools - Generic HID driver 0.41 (2.7.4) >> USB communication driver 0.33 >> kill: Operation not permitted >> writepid: fopen /run/nut/usbhid-ups-cyberpowerAmethi.pid: Permiss

Re: [Nut-upsuser] Permissions error

you need to understand what uid/gid you wish to run nut under, and arrange that this uid/gid can open the devices, read the configs, and write the state places. you left out running 'id' before upsdrvctl start to see what the uid/gid is. (followups onlist only please) __

Re: [Nut-upsuser] [Nut-upsdev] RFE to extend "LISTEN" directive to support host-colon-port (as single token)

Tim Dawson writes: > LISTEN 1.2.3.4 2.3.4.5 987 > > is a mess . . . You either need to specify the default port number, or agreed that this method is a mess! But we have "just use multiple listen statements" which is straightforward. I am not really averse to having a format that is a more fa

Re: [Nut-upsuser] [Nut-upsdev] RFE to extend "LISTEN" directive to support host-colon-port (as single token)

Jim Klimov writes: > Just to clarify: using a different port *is* possible since forever, with > `LISTEN host port` (as two arguments to the directive); the question was if > having a way to spell it as one argument as `LISTEN host:port` would solve > some shortcomings/ease adoption more than int

Re: [Nut-upsuser] [Nut-upsdev] RFE to extend "LISTEN" directive to support host-colon-port (as single token)

Jim Klimov via Nut-upsdev writes: > A recent discussion in the issue tracker brought up the idea to allow the > `LISTEN` keyword to also accept a single "host:port" token (e.g. if there > is only one argument, with at least one colon, and the last colon is > followed only by numbers, split it i

Re: [Nut-upsuser] NUT v2.8.2, the Easter Egg Edition

Jim Klimov via Nut-upsuser writes: > A hiccup was reported about validating the tarball signature on some > systems, so it was reissued from another workstation. Please don't worry :) Do you mean the signature was re-issued, which is ok, or that the tarball was re-issued, which is very much not

Re: [Nut-upsuser] Keeping the traffis on or off the list ?

The list appears to have settings enabled: - modify the subject by adding [Nut-upsuser] - add a footer I believe these are controlled by the list administrator, in the same way as reply_goes_to_list. Both of these are, in the eyes of DKIM, attacks on the integrity of the message. I believe

Re: [Nut-upsuser] Keeping the traffis on or off the list ?

I would guess that reply-to is getting added because of header munging. Turn off munging and this all goes away. ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Keeping the traffis on or off the list ?

Reply-To: is about the *author*. On a list, people should "reply all" and include the list, generally, unless they intend to send a private reply. Having Reply-To set to the list violates standards and causes the "reply" MUA action to send a reply to other than the author, violating expectations.

Re: [Nut-upsuser] BUG: KFENCE: memory corruption in free_async+0x1d8/0x1e0

Dirk Schneider via Nut-upsuser writes: > Hi, > > i run NUT on a Raspberry Pi 3 Model B and after the latest OS Update i get > the following Error from KFENCE, the current OS Version is the first with > KFENCE so it possible that this Problem has was always existing. You didn't say what operating

Re: [Nut-upsuser] Should upsd abort if one if LISTEN addresses is not available?

Jim Klimov via Nut-upsuser writes: > Issue https://github.com/networkupstools/nut/issues/723 was brought up > recently, and I've re-verified it with the current codebase that it still > happens. > > The crux of it is that if upsd can LISTEN to some but not all addresses, > it aborts because "

Re: [Nut-upsuser] Spammy notification-tech diagnostic message

Vojtěch Hurčík via Nut-upsuser writes: > Thanks for the reply, it's only reported once per spawned process and > what you say makes perfect sense in this light. A configuration toggle > or environment variable also seems like a good idea, but I'm sure I or > we can also live with the message bein

Re: [Nut-upsuser] My Back-UPS RS 1000 went haywire, any ideas?

Gennadiy Poryev via Nut-upsuser writes: > I took an external voltmeter and made sure that actual input voltage > is around 223 V and is not changing. However, each successive run of > upsc indicated drastically different "input.voltage", arbitrarily > jumping from 160 V to 280 V. Besides this, no

Re: [Nut-upsuser] Do we need both Nut-upsuser and Nut-upsdev ?

Roger Price writes: > I would like to suggest that we merge the two mailing lists > Nut-upsuser and Nut-upsdev. > > 1. Users increasingly post simultaneously to both lists. One list is > sufficient. IMHO it's poor form to post to both, generally, unless it's an annoucement. The only reason to

Re: [Nut-upsuser] [Nut-upsdev] Setting up charge/voltage based shutdowns

Jim Klimov via Nut-upsdev writes: > While looking at https://github.com/networkupstools/nut/issues/2014 > I understood that I am not sure if currently NUT has a standard way of > triggering a shutdown based on remaining charge or runtime, if a > device/driver lacks a `battery.charge.low` settin

Re: [Nut-upsuser] Question on simultaneous IPv4 and IPv6 "any address" listening

Jim Klimov writes: > Thanks to everyone for a fruitful discussion, links and ideas. > > The result is nearing a merge at > https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI > on any platform, including Windows (which behaves funny WRT binding to the > same host:port as ma

Re: [Nut-upsuser] Question on simultaneous IPv4 and IPv6 "any address" listening

Jim Klimov via Nut-upsuser writes: > I've recently found that at least on my test box the `LISTEN *` line had > only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for > `upsd`. Interesting. On one system I checked, I have 4 explicit directives for 127.0.0.1, ::1, and the LA

Re: [Nut-upsuser] Powering off the big stuff first

Dan Langille via Nut-upsuser writes: > I had an idea last week: why shut everything off (in my basement) when > the power goes off (and run time goes below X minutes)? Makes sense to me. I would say after 30s, start to shut off the "not important to keep running" stuff. At least for me, once t

Re: [Nut-upsuser] Accessing: upsstats.cgi Error: no hosts to monitor (check hosts.conf)

Jim Klimov writes: > Not fully true about example configs in docs: man pages for CGI bits have > some :) > > https://github.com/networkupstools/nut/blob/master/docs/man/upsset.conf.txt > https://github.com/networkupstools/nut/blob/master/docs/man/upsstats.cgi.txt > https://github.com/networkupsto

Re: [Nut-upsuser] Accessing: upsstats.cgi Error: no hosts to monitor (check hosts.conf)

Dan Grostick via Nut-upsuser writes: > When Apache starts is complains about not finding the fully qualified domain > name. That seems normal > In the past, upsstats.cgi would just load. I didn’t have to do any Apache2 > configuration. I don’t know what has changed. in general this does need

Re: [Nut-upsuser] Monitoring a remote UPS

Nichole Kaligian via Nut-upsuser writes: > Every guide I'm finding is connecting their NUT server to the UPS directly. > Is there no option to monitor a network-attached UPS? On its IP or > hostname? This was my first assumption when looking at a product called > 'Network UPS Tools', but it seems

Re: [Nut-upsuser] Synthesize low batt (LB) fron SNMP UPS which does not support this?

Willcox David via Nut-upsuser writes: > Hmm, looking at status_commit(), if the UPS actually reported just > “OB", but the “ignorelb” logic kicked in, wouldn’t status_commit() > change it to “OB LB”? And would clients interpret that correctly? Yes, if status_commit is called. But what happens i

Re: [Nut-upsuser] Synthesize low batt (LB) fron SNMP UPS which does not support this?

Willcox David via Nut-upsuser writes: > In status_init(), if “driver.flag.ignorelb” is set in the driver state, the > “ignorelb” flag is set. > In status_set(), if ignorelb is set, and the status being set > (presumably from the UPS) is LB, it’s ignored. In other words, LB > reported by the UPS

Re: [Nut-upsuser] got nut 2.8.1 but despite reinstall, shows 2.7.4

gene heskett writes: > On 5/22/23 07:13, Greg Troxel wrote: >> gene heskett writes: >> >>> Which file in the nut I pulled a month ago, should I start with to get >>> the new version actually running? I still get - -V=2.7.4 >> It is likely that you hav

Re: [Nut-upsuser] got nut 2.8.1 but despite reinstall, shows 2.7.4

gene heskett writes: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 It is likely that you have built new nut but old nut is still on your system. I do a 'sudo make install' to write over the distribution nut (

Re: [Nut-upsuser] Synthesize low batt (LB) fron SNMP UPS which does not support this?

Carsten Aulbert writes: > Hi all, > > On 5/19/23 15:11, Greg Troxel wrote: >>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.

Re: [Nut-upsuser] Synthesize low batt (LB) fron SNMP UPS which does not support this?

I should add that my thinking is in part due to having a python script that does the equivalent of upsc and reports status to Home Assistant over MQTT. If I had a UPS that didn't do LB, I would still want to see LB reported via this mechanism at the right time. With this support in upsmon, that w

Re: [Nut-upsuser] Synthesize low batt (LB) fron SNMP UPS which does not support this?

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)

Re: [Nut-upsuser] Cyberpower BRG1350AVRLCD with powerpanel driver timeouts

Arturo Javier Alejandro Morán Rouzaud via Nut-upsuser writes: > This is my first time using a mailing list, so please let me know if I > missed something. You are doing great! Your message is well-formatted, readable, and on topic. I know nothing about Proxmox and have never used a cyberpower

Re: [Nut-upsuser] Enhanced driver troubleshooting

gene heskett writes: > Jim, would an upgrade to the install on my rpi4b running a medium > sized 80+ yo lathe give me better control over a: > device.mfr: CPS > device.model: CP625HGa > device.type: ups > driver.name: usbhid-ups > driver.parameter.offdelay: 120 > where that offdelay seems hard co

Re: [Nut-upsuser] Vertiv Liebert

Bruce Pleat via Nut-upsuser writes: > Here's the (far less lengthy) output for the Vertiv Liebert: > > device.mfr: Vertiv Co > device.model: Liebert PSA5 > device.serial: 3106602D04C > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval:

Re: [Nut-upsuser] nut server without nut-client/monitor?

Orion Poplawski via Nut-upsuser writes: > To explain the motivation behind my question - I'm looking at tweaking > the Fedora RPMs and noticed that currently the "nut" server package > requires the "nut-client" package to also be installed (though not the > reverse obviously). With some effort w

Re: [Nut-upsuser] nut server without nut-client/monitor?

Orion Poplawski via Nut-upsuser writes: > Would it be at all useful to have just the nut "server" components installed > and running on a machine without a nut-monitor service running? It really depends on your goals and your overall plan. Generally, upsd and drivers just accumulate state and p

Re: [Nut-upsuser] Using 'dummy.ups' for a real application, not just testing...

Tom via Nut-upsuser 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. May

Re: [Nut-upsuser] Using 'dummy.ups' for a real application, not just testing...

Tom via Nut-upsuser writes: > 1. Yes, I plan to use a Raspberry Pi Zero W with an I2C interface wired to > it which can monitor multiple channels of voltage and current. Here is an > example I am considering: > https://www.amazon.com/Comimark-INA3221-Triple-Channel-Current-Voltage/dp/B07X524KSK

Re: [Nut-upsuser] Using 'dummy.ups' for a real application, not just testing...

Tom via Nut-upsuser writes: > 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 stat

Re: [Nut-upsuser] Question about Tripp-Lite UPS life span

Larry Fahnoe via Nut-upsuser writes: > Somewhat off-topic, but seeking some input from other tech folk on > this list. I have a Tripp-Lite SMART 2200 (a white tower that looks > similar to, but predates the black SMART2200NET) that just failed its > monthly battery test so I bought new batteries

[Nut-upsuser] Best Fortress users?

I have 4 Best Fortress LI660 units from 1995 and would like to improve the driver. Before I change things, I'd like to ask: Is anyone else using "bestfortress"? I'll assume "no"; otherwise please email me or post here, and also I'd like to know: Does 'upsdrvctl shutdown' cause poweroff to b

Re: [Nut-upsuser] Problem with Multiple USB UPSs, including multiple apparent CyberPower

Bruce Pleat via Nut-upsuser writes: > I'm using the latest updates to OS and running the latest apt nut packages > in the dist (2.7.x?). Debian 11 has 2.7.4. That's old; 2.8.0 was released in spring of 2022. And git master has a lot of improvements since 2.8.0, and I would therefore recommend

Re: [Nut-upsuser] battery.voltage Powercom Macan MRT-3000

What would be best is if they could just publish a protocol spec, or mail you a copy with permission to add to nut docs. ___ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuse

Re: [Nut-upsuser] battery.voltage Powercom Macan MRT-3000

That makes sense to me. The field needs to be split into bytes. The low byte is the integer part of voltags, and the high part is units of 10 mV. And this is per cell. Probably the unit is measuring the total and then dividing by 36. But volts per cell will have the same interpretation for va

[Nut-upsuser] experience with old Best Fortress? shutdown not seeming delayed

I have several Best "Fortress LI660", manufactured ~1995, which use bestfortress(8). nut has been monitoring two of them just fine for years via a USB/serial adaptor and homemade TXD/RXD/COMMON cable. I am now trying to properly set up LB shutdown and have a few questions. 1) ups.shutdown.delay

Re: [Nut-upsuser] [Nut-upsdev] How verbose should NUT be by default?

Roger Price writes: (I'll politely decline to accept argument by analogy to humans doing real-time safety-critical tasks.) > It seems to me that logging « Network UPS Tools upsd 2.8.0.1 > listening on 127.0.0.1 port 3493 listening on ::1 port 3493 » is also > essential for safe shutdown manageme

Re: [Nut-upsuser] How verbose should NUT be by default?

Jim Klimov via Nut-upsuser writes: > The opposite opinion is that programs should be quiet until asked to > squeak (e.g. by restarting with higher debug verbosity... "that would help > troubleshooting why the rack went down last week, right!" says the sysadmin > me). That's a fair summary but

Re: [Nut-upsuser] UPS driver polling interval

Mike via Nut-upsuser writes: > I have an APC SmartUPS 3000 RM monitored via NUT. I was planning to use > collectd or some such to poll the values (voltage, battery level, etc) > from UPSC. I was just curious as to how oftem that data gets updated? > One thing I'm quite interested in measuring i

Re: [Nut-upsuser] confusion about shutdown

On 1/5/23 3:04 PM, Jim Klimov wrote: https://github.com/networkupstools/nut/pull/1762 (and maybe some of other recent PRs) updated quite a bit here and there, including a configure-time option for default POWERDOWNFLAG value (using legacy defa

Re: [Nut-upsuser] confusion about shutdown

Charles Lepple writes: > On Dec 30, 2022, at 7:42 PM, Greg Troxel wrote: >> >> maybe me, maybe docs. >> >> I have never had auto shutdown set up on netbsd. Mostly I monitor to >> mqtt. But now I'm trying and have multiple confusions. >> >>

Re: [Nut-upsuser] [Nut-upsdev] [networkupstools/nut] Project Release Cycle Plan Needed (Issue #1769)

My thoughts are: we have an infinite number of version numbers it makes sense to, roughly every 6 months to a year, release 2.N+1.0 with whatever has accumulated after a several-week call for testing, even if it's not exciting. 2.N.1 etc. can happen if there's something serious and oth

[Nut-upsuser] confusion about shutdown

maybe me, maybe docs. I have never had auto shutdown set up on netbsd. Mostly I monitor to mqtt. But now I'm trying and have multiple confusions. 1) 'upsdrvctl shutdown' vs 'upscmd shutdown.return' upsdrvctl is about stopping the driver, but lowbatt shutdown wants to send a command. I don't g

Re: [Nut-upsuser] /etc/pki/nssdb is world readable complaint

Orion Poplawski via Nut-upsuser writes: > nut-server/upsd complains that /etc/pki/nssdb is world readable. > However, this is the standard configuration (RedHat/Ubuntu). did upsd complain, or some library it includes? It seems possiblethe issue is not really a nut one. > If keys are present

Re: [Nut-upsuser] APC ups reports "OL DISCHRG" as its normal status, even when plugged into mains

>> 0.430484 ups_status_set: seems that UPS [GamingUPS] is in OL+DISCHRG >> state now. Is it calibrating or do you perhaps want to set >> 'onlinedischarge' option? Some UPS models (e.g. CyberPower UT >> series) emit OL+DISCHRG when offline. I think the first questions are: what is the UPS actua

Re: [Nut-upsuser] ups-server grumpy after updating to Fedora 37

Sam Varshavchik writes: > After updating to Fedora 37 ups-server started having a bad hair day, > spewing this: > > Nov 21 07:03:28 monster.email-scan.com nut-server[1735]: Can't connect > to UPS [nutdev1] (usbhid-ups-nutdev1): No such file or directory > > May or may not be related: there's a w

Re: [Nut-upsuser] APC SmartUPS powercycles when power returns

Andrea Venturoli via Nut-upsuser writes: > I've got an APC SmartUPS 1500: it's connected via USB and I'm using > the usbhid-ups driver. This used to work properly until recently. > > Now, when power goes out it keeps on going on battery potentially for > several minutes, but, the moment line ret

Re: [Nut-upsuser] NUT can't connect to USB UPS on OpenBSD

Glad you got it working. Marc-André Harbec writes: > Also, I found I had to manually start the USB driver. In my case: > `usbhid-ups`. I don't know if it's something that needs to be done on > all platforms (or it's OpenBSD specific), but I haven't read anything > on this in the official docum

Re: [Nut-upsuser] NUT add on for Home Assistant

I did a quick experiment. Machine A runs NetBSD 9, ups-nut 2.8.0, and Home Assistant Core 2022.8.4. It has a ups foo. Note there is no "nut addon" involved, or any "addon" at all. ("addon" is a Home Assistant concept for the Home Assistant OS or Supervisor running progams not from Home Assista

Re: [Nut-upsuser] NUT add on for Home Assistant

"z.kevino--- via Nut-upsuser" writes: > Thanks for the reply. > I was only showing the yaml to make it easier to send to this email > list as I didn’t think a screenshot of the UI would make it > through. The thing to note here is that these UPS are not connected to > the home assistant raspberr

Re: [Nut-upsuser] NUT add on for Home Assistant

"z.kevino--- via Nut-upsuser" writes: > I am able to get the NUT add-on for Home Assistant to act as a client > for one of the UPS units attached to my NUT-server running on another > Raspberry Pi. What I am unable to do is to get it to attach to a > second. I can attach to the second, or the fi

Re: [Nut-upsuser] Where is nut-scanner on raspberry pi?

It turns out that there is a bug in nut about this, in 2.8.0. I checked the pkgsrc package, and it doesn't have nut-scanner. Usually what is packaged is what upstream installs. On digging in, I found that the package did not declare a dependency on libltldl and thus it was not visibile during t

Re: [Nut-upsuser] Where is nut-scanner on raspberry pi?

華敏 座利 via Nut-upsuser writes: > Thanks, I'll check it out. Still would like to know why the documentation > shows there should be a nut-scanner and it doesn't install on raspb o/s. > But I do appreciate the tips on how to find what I need now. Thank you > again ! You are having two problems:

Re: [Nut-upsuser] NUT can't connect to USB UPS on OpenBSD

Charles Lepple via Nut-upsuser writes: > If that fails, I'd recommend using ktrace to find out what is failing, > such that you get the "no USB buses found" error. Definitely. I would actually recommend ktrace first. Then just `kdump | egrep NAMI` will probably find the issue fast. I use nut

Re: [Nut-upsuser] Info on Cyber Power CP1500AVRLCDa

Sorry, I did find the compat list https://networkupstools.org/stable-hcl.html but I'm not really clear where the sort of extended discussion you are providing belongs. (I am sure it's useful.) signature.asc Description: PGP signature ___ Nut-upsuser

Re: [Nut-upsuser] Info on Cyber Power CP1500AVRLCDa

Thanks for posting all those details; they are interesting. I think it would be helpful to publish the config, at least the nut logic part, and the details of cyberpower actual vs documented behavior. (nut github wiki if Jim thinks that makes sense?) Or maybe there is a better place. It seems t

Re: [Nut-upsuser] UPS restart after power-off

I have little useful wisdom, but: Phil Chadwick writes: > I have NUT installed on FreeBSD 13.0-RELEASE-p11. It's installed from a > standard package, derived from nut-2.7.4.tar.gz. That's now out of date; 2.8.0 is out. (I don't have any reason to think that is related to your issue.) > I am

Re: [Nut-upsuser] I-D progress update - ISE comments - NETVER vs PROTVER

Roger Price writes: > On Tue, 19 Apr 2022, Matus UHLAR - fantomas wrote: > >> On 19.04.22 08:56, Roger Price wrote: >>> >>> The problem: the I-D uses PROTVER rather than NETVER, however 2.8.0 >>> only supports NETVER. >>> >>> The argument in favour of PROTVER is that the command is not asking >>

Re: [Nut-upsuser] NEWLINE

Jim Klimov via Nut-upsuser writes: > I believe the code only deals with '\n' character for line-breaks, in > protocol and probably configs. Probably if nut started out as IETF-ish and was mimicking SMTP it would look for \r\n, but it seems obviously unix-ish (seems normal to me!) and is \n. S

Re: [Nut-upsuser] I-D: ISE request for more detail on command STARTTLS

Roger Price writes: > The IETF Independent Submissions Editor (ISE) has asked for more > detail on the command STARTTLS, in particular the use of certificates. That's interesting, given how the overall state of PKI is not particularly about NUT. > I propose saying that NUT 2.8.0 supports the e

Re: [Nut-upsuser] On retiring some terminology

Jim Klimov via Nut-upsuser writes: > That's odd, seems a spam or phish sneaked through to the list. > > NOT from me :) A warning was posted about this on the spamassassin list, about forged phishing/malware sent to opens source lists, which uses an encrypted file on live.com. Note that the from

Re: [Nut-upsuser] ISE review of I-D: deprecate command VER?

Manuel Wolfshant writes: > Not really. Even 2.7.5 is still not out and 2.7.4 was released in sept > 2021 ( according to https://github.com/networkupstools/nut ). No, 2.7.4 was released in 2016. It's just a github artifact; read the "release notes". >> 4. The I-D must also say which protocol

Re: [Nut-upsuser] finding a common abstraction for reporting

[I was going to rely privately to reduce list traffic, but the list instructed me not to do that :-( ] Charles Lepple writes: > On Mar 17, 2022, at 7:26 PM, Greg Troxel wrote: >> >> My script is in the process of being extended to also deal with apcupsd >> and that se

Re: [Nut-upsuser] ISE review of I-D: deprecate command VER?

Matus UHLAR - fantomas writes: > On 20.03.22 16:02, Roger Price wrote: >>I received the following comment from the Independent Submissions Editor >>(ISE): >> >> The command VER is hazardous because it encourages exploiting of >> implementation peculiarities that are not well documented in a >>

Re: [Nut-upsuser] finding a common abstraction for reporting

Jim Klimov writes: > As for "how much NUT" is doing, it depends :) > > For many of the values where mapping tables are involved, it just reads > some number or string from the protocol encapsulation (usb-hid, snmp, > netxml...) and passes it on. However, that entry's mapping may also involve > s

Re: [Nut-upsuser] ISE review of I-D: deprecate command VER?

Manuel Wolfshant writes: > Connected to outlook-com.olc.protection.outlook.com.. > Escape character is '^]'. > 220 VE1EUR03FT022.mail.protection.outlook.com Microsoft ESMTP MAIL > Service ready at Sun, 20 Mar 2022 22:20:44 + > > |_ssl-date: 2022-03-20T22:22:21+00:00; 0s from scanner time. >

Re: [Nut-upsuser] ISE review of I-D: deprecate command VER?

Roger Price writes: > I received the following comment from the Independent Submissions Editor > (ISE): > > The command VER is hazardous because it encourages exploiting of > implementation peculiarities that are not well documented in a > protocol.  The best example of such a failure is the

[Nut-upsuser] finding a common abstraction for reporting

I have been using NUT for a long time, but my UPS farm is very old and homogenous: I have 3 "Best Power Fortress" from about 1995, and there's one at someone else's. (Yes, these really are 27 years old, and yes I have changed the batteries.) They report a bunch of variables, and I have written a

Re: [Nut-upsuser] Smart-UPS 1500 info though usbhid and apcsmart

I'm far from an expert, but I would not really expect serial to work better. I would try to turn on debugging first. However, a UPS not reporting line in and line out voltage seems strange. signature.asc Description: PGP signature ___ Nut-upsuser ma