search

hassio-addons / addon-nut

Network UPS Tools - Home Assistant Community Add-ons
https://addons.community
MIT License
188 stars 36 forks source link

Wrong Output Voltage value #358

Closed KameDomotics closed 4 months ago

KameDomotics commented 6 months ago

Output Voltage sensor reports an incorrect value.

Expected behavior

The Output Voltage sensor should report a value between 230 and 240 V.

Actual behavior

Actually this sensor reports an incorrect value of 7 - 9 V maximum

HW and SW information:

Home Assistant Core 2024.5.1 Home Assistant OS 12.2 UPS Model Cyber Power PR1500LCDRT2U

Other Details

By manually installing an old version (0.110 dev), the Output Voltage sensor works correctly, displaying a correct value. IMG_8165

By installing the latest version (0.113) officially from Supervisor, the Output Voltage sensor shows the wrong value.

Add-On Setup

IMG_8166

Finally, with the latest versions of Home Assistant Core (from 2024.4.4) this error appears continuously: IMG_8167

sinclairpaul commented 6 months ago

Although it appears you are logging an issue with the integration, I don't see why this would occur as the version of NUT hasn't changed. It would be great if you could try the various versions after so we could narrow down the commit that caused this.

The errors you pasted are to do with your local copy of the addon.

KameDomotics commented 6 months ago

Although it appears you are logging an issue with the integration, I don't see why this would occur as the version of NUT hasn't changed. It would be great if you could try the various versions after so we could narrow down the commit that caused this.

The errors you pasted are to do with your local copy of the addon.

The latest working version is probably 0.10.0 but I'm not sure, I don't know which one I installed.

The error instead is probably caused by version 12.2 of Hass OS and the old version of the Nut add-on.

sinclairpaul commented 6 months ago

Thanks, though it isn't very descriptive, unless we can nail down the version that caused the issue I doubt there can be much done here. As the issue is specific to the hardware you run, it is tricky to reproduce.

github-actions[bot] commented 5 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!