Hi, I tried your suggestion, but I receive this message: “Cannot read property ‘ownContent’ of undefined”. Do you know wat is going wrong?
It seems that the QNAP ist not responding the correct XML.
Please can you activate the Log in the app settings? Then try to add the NAS.
Go back to app settings, copy the log and send it via PM, please. I’ll take a look at it. I hope I can see what the QNAP is responding and what could be the reason of this error message.
Thanks.
Hello @rln1965,
I found a possible reason why the dialog is showing this message.
I think, the login with your user is ok, but the NAS is not returning all neccessary data. A possible reason are missing rights.
I have some questions to be able to reproduce this situation and to handle it - showing a correct error message.
- The IP and port is correct (the QTS port where you get the login page in a browser)?
- What righs has your QNAP Homey user? Is this user assigned to the admin group? If not, this could be the reason of a valid login but error getting system data.
Many thanks
Hello again,
I could reporoduce the issue. In the pairing dialog, missing user right could occour this error message.
To prevent the message, the new app version will show an empty device list instead - and a hint in the pairing dialog about user definition.
To get your app to work, please assign your new user to the admin group.
Open the user editor, select the group assignment:
Add this group:
Save your changes.
Now you should be able to add the NAS to Homey.
Hi Ronny,
I added homey to the administrators group, but now I get this message: “Could not find that PairSession”.
Rob.
(Attachment image001.emz is missing)
(Attachment oledata.mso is missing)
The session timed out (by Homey itself).
Please close all pairing dialogs and start again. Then it should work.
Hi Ronny,
It works!
Thanks!
Bye, Rob.
Hi Ronny,
I tried the wake-on-lan function, but it doesn’t work. With Qfinder PRO it works just fine.
Any ideas?
Thanks!
Rob.
Hi, have you added one of your ether adapters as device to Homey? The app needs to know the MAC, and that`s stored in the eth device.
See the information in the flow (question mark).
In the mobile app:
In the WebApp:
Just add the Eth interface to Homey:
Because it stores the MAC which is needed for WoL.
Hi Ronny,
That did the trick, many thanks!
Flow trigger for NAS availability/unavailability added including flow tag for unavailability reason.
So you can get an information via push message if your NAS got offline.
Available in Version 1.0.6 (currently test version until approval).
Could someone with 2 QNAP connected to Homey confirm this issue, please?
I have only one to test.
Screenshots from the two NAS sensor views would be nice. Even if the data for each NAS is correct.
Many thanks.
Hi Ronny. Is there a way to put the qnap to sleep or even shutdown to save energy
Br Mark
Hi Mark,
it’s not possible with the used webservice.
I would suggest to use the Homey SSH app like Daniel:
Thanks for your quick reply.
I will give it a try
br Mark
I’ve seen some error reports caused by missing data in the ethernet device reports.
The new version 1.0.12 (currently test version) has some further checks to clear the depending capabilities.
If you are affected (seen app crashes in app detail page), please try the test version for now. It will be pushed to live channel soon.
Hi Ronny, is it possible for you to implant a when card that triggers when QNAP send a notification to me from notifications center?
Hi, I haven’t found any documentation about such WebAPI data. I think the WebAPI only supports system data, no app specific data. So current answer is “no”