Re: CyberPower cp1500PPFCLCD
On 11/14/22 3:35 AM, Stuart Henderson wrote: That is just for APC UPS. I know it's supposed to be just for APC UPSes, but it's my understanding that apcupsd works, at least for some, CyberPower UPSes.
Re: CyberPower cp1500PPFCLCD
On 2022-11-14, ITwrx wrote: > On 11/13/22 12:56 PM, Peter Fraser wrote: >> My sensorsd.conf contains >> >> hw.sensors.upd0.percent0:low=99.00%:command=/etc/ups-shutdown %2 >> >> The 99.00% was to allow me to test it easily >> >> As far as I could tell there is no way to ask sensorsd to only run a program >> when the UPS is not charging and the % left is less than a value. >> >> At this point one of two things happened. Either then upd0 values disappear >> from sysctl or the system dies with no messages, and I have to do a hard >> reset. >> >> Does anyone have any ideas of what is going on and how to fix it. > > I accidentally sent the below to the op directly before. Sorry about that. > >> I just wanted to make sure you know about apcupsd [1]. It may work for your >> UPS, even though it's not APC branded. It's in the OpenBSD repos. >> >> http://www.apcupsd.org/ That is just for APC UPS. There is NUT which has much wider device support, but the original issue seems to be with the USB stack rather than upd and may affect userland software too. -- Please keep replies on the mailing list.
Re: CyberPower cp1500PPFCLCD
Good morning,
p...@thinkage.ca (Peter Fraser), 2022.11.13 (Sun) 19:56 (CET):
> My old UPS dies, it was very old I had been changing batteries on it
> for years. It was so old that it used a serial port for
> communications.
>
> I replace it with a new CyberPower cp1500PPFCLCD.
>
> I connected the USB cable and OpenBSD found
>
[...]
>
> Nov 13 13:21:58 fw sensorsd[42763]: upd0.indicator0: Off, UNKNOWN
> Nov 13 13:21:58 fw sensorsd[42763]: upd0.indicator1: Off, UNKNOWN
> Nov 13 13:21:58 fw sensorsd[42763]: upd0.indicator2: On, UNKNOWN
> Nov 13 13:21:58 fw sensorsd[42763]: upd0.indicator3: Off, UNKNOWN
> Nov 13 13:21:58 fw sensorsd[42763]: upd0.percent0: 100.00%, UNKNOWN
> Nov 13 13:21:58 fw sensorsd[42763]: upd0.percent0: marked invalid
> Nov 13 13:21:58 fw sensorsd[42763]: upd0.percent1: 100.00%, UNKNOWN
> Nov 13 13:21:58 fw sensorsd[42763]: upd0.timedelta0: 11425.00 secs,
> UNKNOWN
> Nov 13 13:23:38 fw sensorsd[20386]: upd0.indicator0: Off, UNKNOWN
> Nov 13 13:23:38 fw sensorsd[20386]: upd0.indicator1: Off, UNKNOWN
> Nov 13 13:23:38 fw sensorsd[20386]: upd0.indicator2: On, UNKNOWN
> Nov 13 13:23:38 fw sensorsd[20386]: upd0.indicator3: Off, UNKNOWN
> Nov 13 13:23:38 fw sensorsd[20386]: upd0.percent0: 100.00%, UNKNOWN
> Nov 13 13:23:38 fw sensorsd[20386]: upd0.percent0: marked invalid
> Nov 13 13:23:38 fw sensorsd[20386]: upd0.percent1: 100.00%, UNKNOWN
> Nov 13 13:23:38 fw sensorsd[20386]: upd0.timedelta0: 11425.00 secs,
> UNKNOWN
>
> My sensorsd.conf contains
>
> hw.sensors.upd0.percent0:low=99.00%:command=/etc/ups-shutdown %2
>
> The 99.00% was to allow me to test it easily
>
> As far as I could tell there is no way to ask sensorsd to only run a
> program when the UPS is not charging and the % left is less than a
> value.
>
> At this point one of two things happened. Either then upd0 values
> disappear from sysctl or the system dies with no messages, and I have
> to do a hard reset.
>
> Does anyone have any ideas of what is going on and how to fix it.
I have one of these CyberPower USV, it works for years already.
Unfortunately it's connected to a windows server where it shows up
as a laptop battery.
What I do with sensorsd(8) on OpenBSD for the upd(4) USVs:
$ cat /etc/sensorsd.conf
hw.sensors.upd0.percent0:low=80:high=100:command=/etc/sensorsd.upd.sh \
%l %n %s %x %t %2 %3 %4
$ cat /etc/sensorsd.upd.sh
#!/bin/sh -e
[[ X"${1}" == X"below" && $(sysctl -n hw.sensors.upd0.indicator5) != \
"On (ACPresent), OK" ]] && shutdown -hp +1
There were long threads on sensorsd(8) in the past.
Marcus
Re: CyberPower cp1500PPFCLCD
On 11/13/22 12:56 PM, Peter Fraser wrote: My sensorsd.conf contains hw.sensors.upd0.percent0:low=99.00%:command=/etc/ups-shutdown %2 The 99.00% was to allow me to test it easily As far as I could tell there is no way to ask sensorsd to only run a program when the UPS is not charging and the % left is less than a value. At this point one of two things happened. Either then upd0 values disappear from sysctl or the system dies with no messages, and I have to do a hard reset. Does anyone have any ideas of what is going on and how to fix it. I accidentally sent the below to the op directly before. Sorry about that. I just wanted to make sure you know about apcupsd [1]. It may work for your UPS, even though it's not APC branded. It's in the OpenBSD repos. http://www.apcupsd.org/
Re: CyberPower cp1500PPFCLCD
On Sun, Nov 13, 2022, at 3:49 PM, Kenneth Hendrickson wrote: > --- On Sunday, November 13, 2022, 01:56:12 PM EST, Peter Fraser > wrote: > >> I replace it with a new CyberPower cp1500PPFCLCD. > > You poor bastard. If this company has anything to do with the > CyberPower PC It does not. https://www.cyberpowersystems.com/ Brian
Re: CyberPower cp1500PPFCLCD
--- On Sunday, November 13, 2022, 01:56:12 PM EST, Peter Fraser wrote: > I replace it with a new CyberPower cp1500PPFCLCD. You poor bastard. If this company has anything to do with the CyberPower PC that I bought a PC from a few years ago, you made a big mistake in buying from them. The motherboard on my PC started failing about 6 months after I bought it. The first video slot failed. Then later, the other video slot failed. In order to "honor their warranty", the company was going to make me go without my computer for 3 months. About a week (or maybe two) to ship it to California, a couple of months for them to repair it and test it, and another week (or maybe two) *at my expense* to ship it back to me. I bought another motherboard and fixed it myself. If you look at the comments online about this company, about half of them say this is the best company ever. The other half are horror stories like mine. I think the first half are all false and astro-turfed. The best response is never to have anything to do with this company ever again, and spread the word about just how horrible they are. Sorry to hear about your horrible experience. PS Don't believe any positive reviews. Nobody goes out of their way to post a positive review when things are working. On the other hand, they will post a negative review when things don't go well. Those are the believable reviews.
CyberPower cp1500PPFCLCD
My old UPS dies, it was very old I had been changing batteries on it for years. It was so old that it used a serial port for communications. I replace it with a new CyberPower cp1500PPFCLCD. I connected the USB cable and OpenBSD found Nov 13 12:29:45 fw /bsd: uhidev0 at uhub0 port 4 configuration 1 interface 0 "CPS CP1500PFCLCDa" rev 2.00/2.00 addr 2 Nov 13 12:29:45 fw /bsd: uhidev0: iclass 3/0, 45 report ids Nov 13 12:29:45 fw /bsd: upd0 at uhidev0 Nov 13 13:00:58 fw /bsd: uhid4 at uhidev4 reportid 1: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid5 at uhidev4 reportid 2: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid6 at uhidev4 reportid 3: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid7 at uhidev4 reportid 4: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid8 at uhidev4 reportid 5: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid9 at uhidev4 reportid 6: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid10 at uhidev4 reportid 7: input=0, output=0, feature=6 Nov 13 13:00:58 fw /bsd: uhid11 at uhidev4 reportid 8: input=5, output=0, feature=5 Nov 13 13:00:58 fw /bsd: uhid12 at uhidev4 reportid 9: input=0, output=0, feature=2 Nov 13 13:00:58 fw /bsd: uhid13 at uhidev4 reportid 10: input=0, output=0, feature=2 Nov 13 13:00:58 fw /bsd: uhid14 at uhidev4 reportid 12: input=1, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid15 at uhidev4 reportid 13: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid16 at uhidev4 reportid 14: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid17 at uhidev4 reportid 15: input=0, output=0, feature=2 Nov 13 13:00:58 fw /bsd: uhid18 at uhidev4 reportid 16: input=4, output=0, feature=4 Nov 13 13:00:58 fw /bsd: uhid19 at uhidev4 reportid 18: input=0, output=0, feature=2 Nov 13 13:00:58 fw /bsd: uhid20 at uhidev4 reportid 19: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid21 at uhidev4 reportid 20: input=1, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid22 at uhidev4 reportid 21: input=0, output=0, feature=2 Nov 13 13:00:58 fw /bsd: uhid23 at uhidev4 reportid 22: input=0, output=0, feature=2 Nov 13 13:00:58 fw /bsd: uhid24 at uhidev4 reportid 24: input=0, output=0, feature=4 Nov 13 13:00:58 fw /bsd: uhid25 at uhidev4 reportid 25: input=2, output=0, feature=2 Nov 13 13:00:58 fw /bsd: uhid26 at uhidev4 reportid 26: input=1, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid27 at uhidev4 reportid 27: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid28 at uhidev4 reportid 28: input=0, output=0, feature=5 Nov 13 13:00:58 fw /bsd: uhid29 at uhidev4 reportid 29: input=2, output=0, feature=2 Nov 13 13:00:58 fw /bsd: uhid30 at uhidev4 reportid 37: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid31 at uhidev4 reportid 38: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid32 at uhidev4 reportid 39: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid33 at uhidev4 reportid 40: input=63, output=0, feature=63 Nov 13 13:00:58 fw /bsd: uhid34 at uhidev4 reportid 41: input=0, output=63, feature=63 Nov 13 13:00:58 fw /bsd: uhid35 at uhidev4 reportid 42: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid36 at uhidev4 reportid 43: input=0, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid37 at uhidev4 reportid 44: input=1, output=0, feature=1 Nov 13 13:00:58 fw /bsd: uhid38 at uhidev4 reportid 45: input=1, output=0, feature=1 Nov 13 13:21:58 fw sensorsd[42763]: upd0.indicator0: Off, UNKNOWN Nov 13 13:21:58 fw sensorsd[42763]: upd0.indicator1: Off, UNKNOWN Nov 13 13:21:58 fw sensorsd[42763]: upd0.indicator2: On, UNKNOWN Nov 13 13:21:58 fw sensorsd[42763]: upd0.indicator3: Off, UNKNOWN Nov 13 13:21:58 fw sensorsd[42763]: upd0.percent0: 100.00%, UNKNOWN Nov 13 13:21:58 fw sensorsd[42763]: upd0.percent0: marked invalid Nov 13 13:21:58 fw sensorsd[42763]: upd0.percent1: 100.00%, UNKNOWN Nov 13 13:21:58 fw sensorsd[42763]: upd0.timedelta0: 11425.00 secs, UNKNOWN Nov 13 13:23:38 fw sensorsd[20386]: upd0.indicator0: Off, UNKNOWN Nov 13 13:23:38 fw sensorsd[20386]: upd0.indicator1: Off, UNKNOWN Nov 13 13:23:38 fw sensorsd[20386]: upd0.indicator2: On, UNKNOWN Nov 13 13:23:38 fw sensorsd[20386]: upd0.indicator3: Off, UNKNOWN Nov 13 13:23:38 fw sensorsd[20386]: upd0.percent0: 100.00%, UNKNOWN Nov 13 13:23:38 fw sensorsd[20386]: upd0.percent0: marked invalid Nov 13 13:23:38 fw sensorsd[20386]: upd0.percent1: 100.00%, UNKNOWN Nov 13 13:23:38 fw sensorsd[20386]: upd0.timedelta0: 11425.00 secs, UNKNOWN Nov 13 13:27:03 fw /bsd: usbd_start_next: error=5 Nov 13 13:27:04 fw /bsd: usbd_free_xfer: xfer=0xfd821f61b690 not free Nov 13 13:29:52 fw syslogd[98754]: exiting on signal 15 My sensorsd.conf contains hw.sensors.upd0.percent0:low=99.00%:command=/etc/ups-shutdown %2 The 99.00% was to allow me to test it easily As far as I could tell there is no way to ask sensorsd to only run a program when the UPS is not charging and the % le
