Why discovery is finding my Synology NAS? And also a Ugreen NAS I've already set up? #171
Replies: 2 comments 4 replies
-
|
Coud you please try this fix from another report? At least the multiple discovery should be gone then; not sure about the Syno discovery though. /tom |
Beta Was this translation helpful? Give feedback.
-
|
For detecting the Synology NAS, I think it's because we're listening for the And the Synology is putting that out too. I'll try the fix for discovery - thanks! |
Beta Was this translation helpful? Give feedback.
-
|
So, I assume for a 'clean' implementation I will have to make an UGOS API call here. If it passes through and is answered properly, we have a UGreen device. Possibly I'll just poll the NAS serial number for better identification. (I was trying to avoid caling the API during the stage of discovery, as this comes with other problems, but possibly there is no way around this.) /tom Edit: Nope, there is no known way to make an API poll that delivers the serial # without authentication data (which are not available yet at this stage of discovery). The only valid call without having a token (which requires authentication data) seems this one: |
Beta Was this translation helpful? Give feedback.
-
|
Ok, done - see here. :) /tom |
Beta Was this translation helpful? Give feedback.
-
|
Ah amazing - nice work thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi mattjgalloway, just a quick follow-up: Did the recent changes solve the issues for you? /tom |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The integration is finding my Synology NAS and showing it to me as a discovered device. Also it's showing me the already set up NAS (by IP address).
I can just ignore these superfluous things, but both are surprising and potentially bugs worth fixing?
Beta Was this translation helpful? Give feedback.
All reactions