a week ago
Hi everyone,
I’m running into a persistent issue between my TP-Link Deco account and Google Home, and I’m wondering if anyone else has experienced the same problem.
🔹 Background
I previously had a Deco BE65 Pro, which I replaced with a Deco BE95.
The old device was removed from my TP-Link account (I no longer own it).
However, every time I reconnect my TP-Link account to Google Home, the old BE65 Pro still appears, along with my two BE95 units.
🔹 What I’ve already tried
Deleted the old BE65 network in the TP-Link Deco app
Unlinked and relinked the TP-Link service in Google Home
Cleared cache and reinstalled the Google Home app
Tried syncing from multiple devices (iPhone, Android, etc.)
Despite all this, the BE65 Pro keeps coming back after the TP-Link account is linked again.
Even deleting and reinstalling the Google Home app doesn’t fix the issue.
🔹 Analysis
It seems the issue might be caused by a stale cloud sync cache on Google’s side.
When I reconnect TP-Link, Google appears to reuse outdated device data instead of fetching the current list directly from TP-Link’s servers.
🔹 What I’m trying to find out
Has anyone successfully removed a ghost device (from an old TP-Link network) from Google Home?
Is there any way to force Google Home to refresh the linked data with TP-Link?
Can Google Support manually reset or clear this integration on my account?
Thanks in advance to anyone who has run into this before or has insights to share 🙏
It’s a small issue, but it’s frustrating to keep seeing a device that no longer exists in my Google Home setup!
Answered! Go to the Recommended Answer.
2 hours ago
I wanted to share the final resolution in case it helps others who may experience the same issue.
After multiple tests and exchanges with TP-Link Support, the problem was finally resolved. The old Deco BE65 Pro (which I no longer owned) kept reappearing in my linked services because it was still bound to my TP-Link Cloud account, even though it had been removed from the Deco app.
TP-Link Support escalated the case to their engineering team, who manually unbound the old device from my TP-Link Cloud account.
Once they did that, I relinked my account and only my current Deco BE95 devices appeared — no more “ghost” device.
Key takeaways:
Removing a device from the Deco app does not always unbind it from the TP-Link Cloud backend.
Clearing the app cache or reinstalling the app does not fix this.
The solution required TP-Link Support to manually unbind the old device from my cloud account.
After that, everything synchronized correctly with my current devices.
Thanks to everyone who tried to help. Hopefully this helps someone facing the same situation.
Tuesday
Hi @Sebastrem,
Thank you for posting in the community. I'm sorry to hear that you're running into this persistent problem. I understand that it must be frustrating to see the old TP-Link Deco device keep reappearing in your Google Home, even though you’ve correctly removed it and relinked the account. I appreciate you confirming the troubleshooting steps you have tried. I'm happy to assist.
To gather the necessary information, please answer the following questions:
I'll be waiting for your reply.
Best regards,
Derick.
Wednesday
Hi, and thank you for your reply.
Yes, my Google Home app is up to date, and I’ve already tried reinstalling it several times on different devices (both Android and iOS) — the issue remains the same.
Here are my answers:
App version: Latest version (confirmed via Play Store).
Removal process: I unlinked TP-Link from Google Home completely using the “Manage accounts > Linked services” option, then relinked my TP-Link ID.
Sync issue: After relinking, the old Deco BE65 Pro device still reappears, even though it no longer exists in my TP-Link account or Deco app.
Google accounts: Only one Google account is used on all devices.
In TP-Link app: The BE65 Pro is gone — only my two BE95 units are active and visible.
Control via Assistant: The ghost BE65 Pro does not respond to any command. It’s just listed among the linked devices.
Cloud sync toggle: Yes, I tried turning cloud sync off and on again, and even clearing cache/data — it doesn’t change anything.
It really seems that Google Home is keeping a cached version of the TP-Link device list and not refreshing it when relinking the account.
Deleting and reinstalling the app doesn’t fix it either.
My case is also currently escalated to TP-Link’s engineering team for further investigation. They haven’t confirmed the source of the issue yet, but since the old device no longer exists in my TP-Link account, it may point to a synchronization or caching problem on the Google Home side.
I’d appreciate it if this could be escalated to the Google engineering team as well for review.
Thanks again for your help!
Wednesday
Hi there!
Thank you for your reply. I appreciate the information; the next troubleshooting step we should consider is deleting and then recreating your current Google Home structure. Since this solution requires you to relink all your devices, could you confirm how many devices are currently set up in your Google Home structure?
I'll be waiting for your reply.
Best regards,
Derick.
Thursday
Hi, and thank you for the follow-up.
I currently have aroun 15 devices connected in my Google Home structure, thermostats, lights, smart speaker and my TP-Link Deco system.
Before proceeding, I just want to confirm something:
If I delete and recreate my Google Home structure, will it force a full resync with the TP-Link cloud and clear any cached data on Google’s side?
I want to avoid rebuilding everything if the same “ghost” device might reappear after relinking my TP-Link account.
Thanks again for your help and clarification before I try this step.
Best regards,
2 hours ago
I wanted to share the final resolution in case it helps others who may experience the same issue.
After multiple tests and exchanges with TP-Link Support, the problem was finally resolved. The old Deco BE65 Pro (which I no longer owned) kept reappearing in my linked services because it was still bound to my TP-Link Cloud account, even though it had been removed from the Deco app.
TP-Link Support escalated the case to their engineering team, who manually unbound the old device from my TP-Link Cloud account.
Once they did that, I relinked my account and only my current Deco BE95 devices appeared — no more “ghost” device.
Key takeaways:
Removing a device from the Deco app does not always unbind it from the TP-Link Cloud backend.
Clearing the app cache or reinstalling the app does not fix this.
The solution required TP-Link Support to manually unbind the old device from my cloud account.
After that, everything synchronized correctly with my current devices.
Thanks to everyone who tried to help. Hopefully this helps someone facing the same situation.