11 responses

  1. Toby
    2025/07/21

    I receive the following error message with the modification of PowerManagerNUT-x86_64-1.0.2-SynologyDS923+.spk. What did I wrong?

    Installation completed successfully.1. 环境配置成功
    1. Environment setup successful

    Scanning USB bus.
    [nutdev-usb1]
    driver = “usbhid-ups”
    port = “auto”
    vendorid = “3746”
    productid = “FFFF”
    product = “EF-UPS-RIVER 3 Plus”
    serial = “********serial showing up here**********”
    vendor = “EcoFlow”
    # bus = “001”
    # device = “003”
    # busport = “003”
    2. nut-scanner 执行成功,成功扫描到 EcoFlow UPS 设备
    2. nut-scanner executed successfully, EcoFlow UPS device detected

    Using subdriver: ECOFLOW HID 0.1
    Network UPS Tools – Generic HID driver 0.53 (2.8.2)
    USB communication driver (libusb 1.0) 0.47
    nut_libusb_get_string: Invalid parameter
    using ‘battery.charge’ to set battery low state
    using ‘battery.runtime’ to set battery low state
    Network UPS Tools – UPS driver controller 2.8.2
    default driverpath = /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/bin
    start_driver driverpath = /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/bin
    3. upsdrvctl 执行成功
    3. upsdrvctl executed successfully

    fopen /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/var/state/ups/upsd.pid: No such file or directory
    Could not find PID file ‘/volume1/@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/var/state/ups/upsd.pid’ to see if previous upsd instance is already running!
    /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/etc/upsd.conf is world readable
    listening on 0.0.0.0 port 3493
    /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas is world readable
    Connected to UPS [nutdev1]: usbhid-ups-nutdev1
    Found 1 UPS defined in ups.conf
    /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/etc/upsd.users is world readable
    4. upsd 执行成功
    4. upsd executed successfully

    Error: Unknown UPS
    错误:未知错误(upsc),请尝试重新执行脚本
    Error: Unknown error (upsc), please try running the script again

    Reply

    • albert
      2025/07/21

      It seems the service already started successfully. Could you try to run “upsc ups@localhost:3493” in Synology NAS’s terminal to verify ? Or you can run “upsc ups@[NAS-IP-ADDRESS]” from any linux/unix machine to verify.

      Reply

      • Anonymous
        2025/08/07

        I get same error

        Reply

  2. Keith
    2025/07/22

    So I also had to:
    # 1. Update ups.conf to change [nutdev1] to [ups]
    sudo sed -i ‘s/[nutdev1]/[ups]/’ /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/etc/ups.conf

    # 2. Update upsmon.conf to change the MONITOR line
    sudo sed -i ‘s/nutdev1@127.0.0.1:3496/ups@127.0.0.1:3493/’ /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/etc/upsmon.conf

    # 3. Restart the PowerManagerNUT service
    cd /volume1/@appstore/PowerManagerNUT/usr/local/bin/nas && sudo ./run.sh

    Then I checked this:

    admin@syno:/volume1/@appstore/PowerManagerNUT/usr/local/bin/nas$ upsc ups@localhost:3493
    battery.charge: 92
    battery.charge.low: 10
    battery.runtime: 2075
    battery.runtime.low: -1
    battery.type:
    device.mfr: EcoFlow
    device.model: EF-UPS-RIVER 3 Plus

    Success!

    I couldn’t figure out a way to Start/Stop in Package Center.

    Thanks for writing this up!

    Reply

    • Marek
      2025/08/14

      Thank you for adding this, Keith. It helped me to successfully restart the service. Unfortunately, I still get an connection error when I try to configure UPS in the DSM control panel.

      Any ideas how to solve this?

      Reply

    • Anonymous
      2025/08/14

      Thank you for your preliminary work! After running “upsc ups@localhost:3493” in Synology NAS’s terminal I got this output:
      battery.charge: 80
      battery.charge.low: 20
      battery.runtime: 1867
      battery.runtime.low: -1
      battery.type:
      device.mfr: EcoFlow
      device.model: EF-UPS-RIVER 3 Plus
      device.serial: R631ZEBAWH1A0612
      device.type: ups
      driver.debug: 0
      driver.flag.allow_killpower: 0
      driver.flag.ignorelb: enabled
      driver.name: usbhid-ups
      driver.parameter.override.battery.runtime.low: -1
      driver.parameter.pollfreq: 1
      driver.parameter.pollinterval: 2
      driver.parameter.port: auto
      driver.parameter.synchronous: auto
      driver.parameter.usb_hid_ep_in: 1
      driver.parameter.usb_hid_ep_out: 1
      driver.state: updateinfo
      driver.version: 2.8.2
      driver.version.data: ECOFLOW HID 0.1
      driver.version.internal: 0.53
      driver.version.usb: libusb-1.0.26 (API: 0x1000109)
      outlet.1.status: on
      ups.beeper.status: enabled
      ups.delay.shutdown: 20
      ups.mfr: EcoFlow
      ups.model: EF-UPS-RIVER 3 Plus
      ups.productid: ffff
      ups.realpower.nominal: 286
      ups.serial: R631ZEBAWH1A0612
      ups.status: OL
      ups.timer.reboot: -1
      ups.timer.shutdown: -1
      ups.vendorid: 3746

      Like Marek I get the message “Connection to network ups server is not possible”
      So what’s the problem?

      Reply

      • Anonymous
        2025/08/15

        I got it. I had a wrong network-ups-server IP in DSM ups.

        Reply

  3. Marek
    2025/08/21

    After restarting the PowerManagerNUT service several times, it is working now. Thanks a lot for the helpful information on this page!

    Reply

  4. Anonymous
    2025/09/19

    For anyone following this article, I also had to make one additional change.

    Modify ups.conf

    Path:
    sudo vi /volume1/\@appstore/PowerManagerNUT/usr/local/bin/nas/x86_64-pc-linux-gnu-nut-server/etc/ups.conf

    Change this line:

    [nutdev1]

    To:

    [ups]

    Reply

    • albert
      2025/10/17

      Thank you for your comment! I have updated the post to include this change.

      Reply

  5. Anonymous
    2025/11/09

    If I have Synology SA6400, is it possible somehow to support river3 for my nas? Do I need to buy ecoflow as ups or it won’t work with my nas. What do you think?

    Reply

Leave a Reply

Back to top
Language:
mobile desktop