I recently got the Watcher. When I try to link it to the app via QR, it says “Device Added” but then nothing happens. Watcher is not visible on the homepage as well. I have a similar issue when I try to add it manually. It doesn’t proceed to Configuration step. I tried on three devices to no avail. How can I link the device?
Hi, were you able to solve this problem? Share your experience, I have the same problem.
If it’s a Wi-Fi-enabled Watcher, some networks (like those with captive portals or MAC filtering) block onboarding.
Try using a mobile hotspot for pairing.
You can send the EUI of your device to seeed via [email protected] and they will help you solve your problem!
When I was using the watcher to link the APP, the scanning process kept showing the error message “check eui error”.
Could you please check the EUI in the device settings and send us a photo of the label on your device as well? You can email the information to our technical support team at [email protected] — we will be happy to assist you in resolving this issue.
Hi, if I got problem which email I can use for my questions? [email protected] or [email protected]? Thanks!
Hi there,
And welcome here…
SO, I’m pretty sure the first one, BUT what is the issue maybe someone here can help or answer?
Can you describe what you tried to do and any errors you received ?
Have you looked at the Wiki for Watcher ?
HTH
GL 
PJ 
Not to hijack this person’s question, but I wrote on a different thread yesterday about not being able to get my new Watcher W1A to bind with my phone. I did work through the troubleshooting list, but nothing worked. If you have any tips, I’d be happy to listen! Below is what i posted elsewhere:
I am also having issues with the Watcher I just received from the U.S. warehouse. My account is registered to the world server and my phone and Watcher both are connected to the same 2.4 Ghz wifi network. I granted all permissions and then went back and verified they are good. When I try to add the device, it connects to wifi but then gets stuck on binding. Using a Samsung S24 with Android 16. Thanks.
Hi there,
No problem it’s in the same hood(hijack), so you’re good and we are all here to help,. well some of us. 
So , I’ve seen this issue come up before (including on Discord), 
So I took a closer look and ran it through a proper troubleshooting flow.
(for the lurkers 
= AI disclaimer) but i digress…
In this case, since the device connects to WiFi but stalls during binding, the issue is almost certainly related to one of the following:
- Region/server mismatch between app and device
- Network isolation (router settings like AP isolation)
- Incomplete provisioning state or firmware timing,(it times out too quickly)
A fast way to isolate it:
- Factory reset the device (long press)
- Use a phone hotspot (2.4 GHz) instead of your router
- Log out of the app, clear storage, and re-login (explicitly selecting region)
- Re-attempt pairing
If it works on hotspot, you’ve confirmed it’s a network or router configuration issue, not the device.
if it still fails then, At that point:
- Try a second phone (iOS vs Android)
- Try a different account
- That isolates account vs device vs ecosystem
everything has to be in order on these kind of IOT onboarded device IMO,
Cloud + app + firmware + router (wifi) all must be inline..
sometimes they get halfway provisioned and fail, only a factory reset I have seen is what fixes it. ( I have 2 ) and I’m on record 
liking the device.
I found this info interesting, but Android 16 has some very nice features in the BLE stack I wish, the update to 16 would hit the RAYzer I have , it’s scheduled… 
Android 16 Permissions / BLE Changes
Samsung + latest Android versions can be picky:
- Nearby devices permission
- Location permission (still required for BLE scan)
- Background restrictions
Fix checklist:
- Location ON (not just permission granted)
- Bluetooth ON
- App allowed:
- Location
- Nearby Devices
- Bluetooth
- Disable battery optimization for the app
there was a thread about a timing issue with the time not initially set or date maybe and the TLS thought it was expired or something to that effect the fix was after the reset let it sit on the wifi for a few minutes to let the NTP sync up the clocks & dates, then try pairing again. 
As for the bigger picture—there’s a reason people say:
“Any fool can criticize, condemn, and complain—and most do.” — Dale Carnegie
I prefer solutions that actually work.
HTH
GL PJ:+1:
Quick note on approach: tools don’t replace experience, they extend it. What matters is whether the answer is accurate, testable, and helps solve the problem. That’s the standard I stick to. (you should too!) 
Thanks for the detailed response! I’ll give this a try and let you know if it works.
1 Like
I did several of the steps listed, and finally got it added by manually entering the EUI and Key. Before it was telling me that it was invalid, but it worked this time.
Thanks for the help!
1 Like
Hi there,
Awesome, Glad you got it going. Do us a solid and mark the reply as the solution so others can find it fast.
Thank you , for contributing.
GL PJ