search

nutdotnet / WinNUT-Client

WinForms-based client for monitoring your Uninterruptible Power Supply (UPS) connected to a Network UPS Tools (NUT) server.
GNU General Public License v3.0
209 stars 19 forks source link

CPS wrong output voltage #101

Open Fr0stX76 opened 1 year ago

Fr0stX76 commented 1 year ago

Hi,

I have the wrong output voltage for my CP1500PFCLCD in WiNUT. It display 137v instead of the expected 121-122v (Canada)

Searching online I found out that it is a known bug that seems to originate from usbhid-ups. It has been documented on other software git and forum:

https://github.com/networkupstools/nut/issues/1338

https://github.com/networkupstools/nut/issues/581

https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-June/010685.html

And fixed https://github.com/networkupstools/nut/issues/439#issuecomment-1213568961

Is there anything that can be done to implement a similar fix/workaround?

gbakeman commented 1 year ago

Hi @DfrostX ,

I'm just grasping why the issue is occurring from reading those threads. It sounds like the value is being reported incorrectly to NUT's software, or it's interpreting a value incorrectly... I'm not quite sure which. Either way, we can only rely on what the NUT server reports to us when we query the server. Perhaps WinNUT could do a trick where we look at the reported UPS model, then from there either subtract 32 from the reported voltage like someone else said, or just ignore the value entirely. WinNUT is currently programmed to substitute default values when an important parameter is missing (which I don't think is very good practice) so that may be another option.

Fr0stX76 commented 1 year ago

From what I read it was fixed in NUT 2.8.0

In my case WiNut is reading from a Synology NAS with the UPS connected via USB. So I guess the issue lies with the NAS driver. I think the fix would need to come from Synology. I will open a ticket with them and see. Not having much hope of it being fixed

gbakeman commented 1 year ago

... I guess the issue lies with the NAS driver. I think the fix would need to come from Synology.

I'm afraid that may be the case. If I understood the issue better, I might have been able to make a workaround. Synology seems to pop up here with odd bugs, so hopefully they're on it. Let's leave this bug open until you can confirm a fix.

Grumpy-Old-Engineer commented 1 week ago

I've got exactly the same problem.... and I just updated to DSM 7.2.2. Did Synology ever say anything positive, or indicate that they would do anything?

SHC22 commented 1 week ago

Dear all, I have the opposite display: input voltage and output voltage should be approx. 230V (Europe), but the output voltage only shows 210V. The correct voltage is displayed on the device.

Synology DS423+, DS7, APC Back-UPS RS 1500G

grafik

gbakeman commented 1 week ago

@SHC22 It sounds like you're experiencing a combination of this issue and #136. The gauges will display their minimum value if the true variable is unavailable. I'd suggest calibrating to the minimum of 0V then it should display properly.

@Grumpy-Old-Engineer Best wishes that you find a good answer. I'd also suggest posting in the Synology Community and/or contacting the NUT people for help.

SHC22 commented 1 week ago

@gbakeman Maybe I made a mistake but if I calibrate it "0" then it shows "0". And additionally the battery voltage is at minimum, too.

(sorry for not posting the screenshot in English language - I couldn't find the language-switch quickly)

grafik

gbakeman commented 1 week ago

@SHC22 No mistake on your part! Your NUT server does not provide battery voltage or output voltage (confirm in File -> UPS Variables). This will require further troubleshooting. There are a few issues and discussions here on the topic, but essentially you may need to update your NUT server and/or change to a different driver.

gbakeman commented 1 week ago

All,

If anyone is experiencing this bug on a Synology device, @Grumpy-Old-Engineer has confirmed that Synology is running old software but an update from them is uncertain at this point. I'd encourage anyone experiencing this problem to use an updated instance of the NUT/upsd server software in a different environment (container, package, etc.) until either Synology releases an update or it becomes apparent that WinNUT needs a workaround.

Grumpy-Old-Engineer commented 5 days ago

The follow-up response I received from Synology was not good:

I have received an update from our Senior Engineers, and they won't be able to upgrade the current NUT Version. However, they recommend to submit a feature request so it can be taken in consideration and update it in future DSM Versions.

I've successfully submitted this request on your behalf. I can't guarantee any kind of timeline for when this might be implemented, but in the meantime you can sign up to be automatically notified of DSM, SRM, and application updates by email to see if we implement the feature in future updates: https://account.synology.com/

After signing into your Synology Account, go to Profile->Newsletters to subscribe to emails from the relevant category. If there is a different feature you would like to request in the future you can put in a request through the following form without the need for a support ticket: https://www.synology.com/form/inquiry/feature

Please do not submit this request again as all requests go to the same location.

Maybe if everyone with an UPS issue on Synology submits a request to have the 12 year old version of the driver DSM is using replaced with the current version we might get some kind of result.

gbakeman commented 5 days ago

Thanks for the update @Grumpy-Old-Engineer. I'll see if I can submit a request on my own Syno account.