-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CPS wrong output voltage #101
Comments
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. |
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 |
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. |
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:
networkupstools/nut#1338
networkupstools/nut#581
https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-June/010685.html
And fixed networkupstools/nut#439 (comment)
Is there anything that can be done to implement a similar fix/workaround?
The text was updated successfully, but these errors were encountered: