TerraMaster Forum

Hello,
1. UPS: Powercom WOW-750U. https://pcm.ru/product/pcm-wow-300u-37371/
2. TNAS: F4-424.
3. When using TOS 7, it is detected as a HID UPS Battery. When setting "shutdown after 1 minute," everything works normally. The TNAS turns off.
4. When using TOS 7, there are no issues.

Марка и модель ИБП:APC Back - UPS pro 550 совместимс NAS TerraMaster F4-424? вчера свет выключили на день. так он нас не отключил, хотя я выставил 5 минут. разрядился полностью. сегодня свет выключили на час. я уже сам выключил NAS TerraMaster F4-424. когда дали свет ИБП ЕГО НЕ ВКЛЮЧИЛ. Вот мне и посоветовали спросить тут. Сам я пенсионер и сам не могу понять.

Stepan61 wrote: ↑29 Jan 2026, 02:30

Мы не тестировали эту модель. Вы можете попробовать обновить с помощью патча из этого поста и посмотреть, будет ли это работать нормально. Кстати, какая версия TOS у вас сейчас запущена?

We haven't tested this model. You can try updating with the patch from this post and see if it works properly. By the way, what version of TOS are you currently running?

Hello,

Thank you for your reply and for providing the link to the forum article.

I followed the recommendations from the article, however the issue seems to be related to how TOS manages the NUT configuration files.

My UPS is **ExeGate SpecialPro UNB-3000**, which uses a USB interface with the following identifiers:

VendorID: **0925**
ProductID: **1234**
Manufacturer: **RICHCOMM**
Product: **UPS USB Mon V2.0**

The default configuration created by TOS uses the driver:

```
driver = richcomm_usb
```

However, this driver does not work with this UPS.

After manual testing, I found a configuration that successfully detects and communicates with the UPS using the **nutdrv_qx** driver with the **armac / megatec protocol**.

Example configuration:

```
[nutdev-usb1]
driver = nutdrv_qx
port = auto

vendorid = 0925
productid = 1234
vendor = "RICHCOMM"
product = "UPS USB Mon V2.0"

subdriver = armac
protocol = megatec
pollinterval = 5
ignorelb
```

When I start the driver manually:

```
/lib/nut/nutdrv_qx -a nutdev-usb1 -DDDD
```

the UPS is detected successfully and responds correctly to commands (Q1 / I). The driver continuously receives valid telemetry from the UPS.

However, the problem is that **TOS automatically overwrites `/etc/nut/ups.conf` during reboot**, restoring the default configuration with the `richcomm_usb` driver.

Because of this behavior, it is impossible to persist the working configuration.

Could you please advise:

1. Is there a supported way to **persist custom NUT configurations** in TOS?
2. Is it possible to configure TOS to use **nutdrv_qx instead of richcomm_usb** for this device?
3. Is there a configuration file or service that **regenerates `/etc/nut/ups.conf` during boot** that I could override?

Based on my tests, the UPS works correctly with NUT when configured manually, so the issue seems to be related only to how TOS generates the configuration.

I can provide full logs or run additional diagnostics if needed.

Thank you.

Best regards

1. CyberPower VP1600ELCD
2. F4-423 (USB connected) and F5-221 (NUT network-client)
3. Plug and Play, Both NAS see the UPS
4. No problems (will update later if any)

[My UPS + TNAS Experience]
1. UPS brand + model:
EATON Ellipse PRO 650 (ELP650FR)
2. TNAS model:
TerraMaster F4-425 Plus (TOS 6.0.794)
3. My setup / connected devices:
TerraMaster F4-425 Plus (4-bay NAS)
Home internet router / ISP router
USB connection between UPS and NAS for automatic shutdown
4. Experience:
The UPS is recognized correctly by TerraMaster via USB. Everything works properly with power outage notifications and safe shutdown. I mainly use it to protect my NAS and router from sudden power loss.
5. Battery runtime:
Estimated runtime depends on load, but for NAS + router it should be enough time for safe shutdown and short power outages.
6. Problems / shortcomings:
No major issues noticed so far.
7. Useful tips:
USB connection is recommended because TerraMaster can detect power outages and safely shut down the NAS automatically.
8. Purchase channel:
Media Expert (Poland)

Izya12 wrote: ↑11 Mar 2026, 13:12

Hi
do you find any solution for the `/etc/nut/ups.conf` that is overwritten by TOS?
I have the same problem with Vultech UPS?
Many thanks in advance.
Bye

angelor wrote: ↑22 Jun 2026, 16:21

Izya12 wrote: ↑11 Mar 2026, 13:12

Hi
do you find any solution for the `/etc/nut/ups.conf` that is overwritten by TOS?
I have the same problem with Vultech UPS?
Many thanks in advance.
Bye

мне ответили так:
```
We indeed cannot achieve persistence; this is by design. Enabling or disabling through our system interface will overwrite the configuration file, which is the current logic. To avoid overwriting, you can bypass the interface and manually set the UPS configuration, then restart the NUT service.
The issue of overwriting on every reboot is caused by the system’s use of udev rules—any USB insertion triggers an overwrite. Since the system’s USB detection is also used by the storage module, changing the rules is not being considered for now.
If you want to use it this way, you can delete this file: /etc/udev/rules.d/63-upsconf.rules.
```