You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Appears that due to the version being pinned to NUT 2.8.0-7 if I am reading correctly. Wanted to take advantage of apc_modbus over TCP as I have a UPS that only supports one specific management card and I don't have a way to add direct connections like RS232, USB, etc. The SNMP drivers in NUT also for whatever reason don't seem to fully understand that this is a split-phase (2 phase) UPS (model SURTD5000RMXLP3U) which is very uncommon and thus not all statistics are being reported correctly, which in turn shows incorrect information.
When I go to configure apc_modbus as driver with porttype:tcp and port:[hostname] the add-on crashes with "Can't start /lib/nut/apc_modbus: No such file or directory"
Expected behavior
Newer version and support for apc_modbus
Actual behavior
Add-on crashes following NUT documentation for apc_modbus with "Can't start /lib/nut/apc_modbus: No such file or directory"
That is fair, but with that said - before I open another issue, can the documentation be updated to reflect that it tracks the Debian stable version, thus actual features/function may be behind the NUT developers as their stable version is showing as 2.8.2?
The majority of users would not understand what that meant, so I doubt there is much value. For more technical users you can look at the Dockerfile to see the sources.
Problem/Motivation
Appears that due to the version being pinned to NUT 2.8.0-7 if I am reading correctly. Wanted to take advantage of apc_modbus over TCP as I have a UPS that only supports one specific management card and I don't have a way to add direct connections like RS232, USB, etc. The SNMP drivers in NUT also for whatever reason don't seem to fully understand that this is a split-phase (2 phase) UPS (model SURTD5000RMXLP3U) which is very uncommon and thus not all statistics are being reported correctly, which in turn shows incorrect information.
When I go to configure apc_modbus as driver with porttype:tcp and port:[hostname] the add-on crashes with "Can't start /lib/nut/apc_modbus: No such file or directory"
Expected behavior
Newer version and support for apc_modbus
Actual behavior
Add-on crashes following NUT documentation for apc_modbus with "Can't start /lib/nut/apc_modbus: No such file or directory"
Steps to reproduce
Use configuration settings as follows:
error is shown in logs:
Proposed changes
Update version. Ensure support for apc_modbus
Was specifically pointed to this PR.
The text was updated successfully, but these errors were encountered: