NAS won't shutdown from NUT master

I am trying to configure my NAS to get shutdown by command from my NUT server, I have tried many things and variations, including renaming my server / adding a dummy-ups named [qnapups] and adding admin/123456 user, or changing the configs exactly as done in this blog:
https://www.dalbert.net/qnap-nas/
but I can’t get my NAS to be shutdown.

Currently after following each step in blog above (changing the MONITOR command on the NAS to match the correct username/password and add a dummy-ups named qnapups in master), I have a working connection under Control Panel-> External device-> UPS with my server ID as supposed to, and also by running upsc myups@<ip> from ssh, I get the UPS data, But no signal seems to affect it.

However when sending shutdown signal with

 upsmon -c fsd

on master, only the other clients are being shutdown, not the NAS.

I can’t get this intractable NAS to shutdown, (I have tried before a pure ssh approch, and it was worse.)

my /etc/config/ups/upsmon.conf on NAS:

RUN_AS_USER admin            
MONITOR qnapnas@<ip> 1 monuser secret slave
MINSUPPLIES 0                
# NAS is a client (if it is NOT powering other devices)
SHUTDOWNCMD "/sbin/shutdown -h +0"
FINALDELAY 0     

(other files are as untouched)

As said, both upsc myups@ip (real ups) and upsc qnapups@ip (dummy-ups) work as expected, it just doesn’t perform shutdown, and so with:

upscmd -u monuser -p secret qnapups@ip load.off
OK
upscmd -u monuser -p secret qnapups@ip driver.killpower
OK

Nothing get’s it to shutdown

I don’t have any logs, and as far as I understand, there isn’t acutal full verion of NUT client on this thing, so it doesn’t really work as expected with all log files.

I can’t figure out even how to debug local shutdown test, as upsmon -c fsd doesn’t work on the NAS:

[~] # sudo upsmon -c fsd
Network UPS Tools upsmon 2.7.4
kill: No such process

Any help would be appricated!

Model: TS-832PX
Software: QTS 5.0.1 2376

Could you please try setting up the NUT Slave via our UI? Or is there a particular reason why you can’t set it up directly through the UI?

Regarding the issue with using a command, I’ll be forwarding that to our internal team for analysis. Thanks for the report!

Finally, it strarted obeying the BL status and starts the timer defined in the UI, it wasn’t working before (maybe needed a roboot apart form apply button)
but I want to trigger an FSD at given moment, I don’t want a nattery event timer, I set it in the UI to 100 minutes so it won’t distub.
I want it to obey upsmon -fsd from master, which is not currently
I could do it with dummy-ups and give 0 minutes timer, but UI won’t let me.