Thanks for reporting. I found a possible reason. If I’m right, the situation is like this:
pairing dialog: the correct volumes (name) are displayed for the NAS
after pairing, this volume shows the data of the other volume (same volume number, but from the other nas
Is this the behaviour? If yes, that it should be fixed in the next test version.
Added wake-on-lan in version 1.0.1 (currently only testversion until review):
Use the buttons in maintenance view (device settings) of NAS or Ethernet devices.
Use flow action: select the flow of the app and select the NAS you want to wake up.
I haven’t seen API URLs for such actions, only for reading data. So it’s not possible at the moment until I find some other documentations about the QNAP API.
This app uses a Webservice API (XML over http).
I’m not planning to mix this high level access with another low level access like SSH. This will bring security problems (you have to use a user with more rights - and only admin will have SSH access as far as I know) and irritations of port usage (closed or changed SSH port in addition to the default QTS port).
At his point it’s a selection of NAS data and no full remote control.
No only with single step.
Please take a look at the first post…
Best way is to create a new user for Homey with admin group without further rights (apps, folders) and without 2FA.