Thanks for the effort you put into this. But I still get a timeout. 3479495a-182b-463a-955d-ba24f4cce32b
are you logged in via web, mobile app at the same time?
You should setup a separate account, all the logs from the past dys show that we have no more sessions and I could not wait nor log these other sessions out.
Troubleshooting: “timout” error
TP-Link Decos only allow one admin login at a time. If you keep getting this error while pairing or repairing, it’s usually because the TP-Link Deco app (or its web admin page) is logged in with the same account elsewhere — on your phone or in a browser tab. Close those and try again. If it happens often, create a separate “Manager” account in the TP-Link Deco app (App → More → Managers) for everyday phone use, and keep your main owner login reserved for Homey.
I am logged out of the Deco app and not logged in anywhere else. Yet, I am still getting a timeout.
68cae066-19e4-453a-9987-11b811cb650b
But did you create a separate account and logged in with that in your app?
I have been testing back and forth on my X50-4G and X50. 1.4.34 (public) and 1.4.46 (Beta). I have updated, removed device in all sorts of combo and I could not reproduce the issues you are seeing. Could a few of you help me with HAR files from the developer Menu on your browsers while you are browsing around on your router.
Please delete the devices, delete the app and install a fresh version, please compare public and beta versions. Send the diags. Trying really to solve this matter some of you are seeing.
Nope. it will not connect to any deco x50. It say “Cannot reach the router at IP X.X.X.X”
And in the TEST Version of the app all I get is timeout 30000ms
What is your exact version of your x50? I have i 1.4.5 Build 20240828 Rel 84587 and it work flawlesly
Hi. All have the same FW/HW.
Main
X50(1.0)
1.8.0 Build 25102213 Rel. 43970
( In TEST App ) if I press continue, I get “cannot read properties of null (reading ‘length’)”
If I press sign in, I get “timeout 30000ms”
Tested on shs and Pro
@Mike_Nono Could you help me with HAR files? I would really like to solve this butt as I dont have your unit im having a hard time here.
What’s the difference on WHEN device disconnected from Deco mesh and the WHEN device in (specific deco router) became online/offline??
Is there some instruction to make the files you want? I can try it tomorrow on my deco’s, so you can take a look at them.
Good question — these are two different triggers and they behave differently on purpose. Here’s the breakdown:
“A client became online/offline” — per Deco node, no delay
This trigger lives on one specific Deco device (one node in your mesh). It checks that node’s own connected-client list every poll cycle and fires the instant a client appears/disappears from it.
The catch: if a device roams from Deco A to Deco B (e.g. you walk from the living room to the bedroom), it briefly disappears from A’s list and shows up on B’s — so A’s trigger fires “offline” even though the device never actually left your home network. It’s a real signal, just scoped to that one node, including normal roaming blips.
Use this when you specifically want to know “is this device connected to this Deco,” not “is this device home.”
“A client joined/left the Deco Mesh” — mesh-wide, debounced
This trigger isn’t tied to a single node — it looks at the combined client list across every Deco in your mesh. “Left” only fires after the client has been missing from the entire mesh for 2 consecutive poll cycles, not just one.
That short grace period is exactly there to absorb the roaming case above: if a device hops from Deco A to Deco B, it’s still present somewhere in the mesh, so “left the mesh” never fires. It only triggers when the device is genuinely gone — not connected to any node.
Use this for “is someone home” / “did this device leave the house” type automations — it won’t false-trigger every time someone walks between rooms.
TL;DR
| Online/offline (per node) | Joined/left the Mesh | |
|---|---|---|
| Scope | One specific Deco | Whole mesh |
| Roaming between nodes | Fires (false “offline” blip) | Ignored — debounced |
| Speed | Immediate, next poll | Up to 2 poll cycles on “left” |
| Best for | “Is this device near this Deco” | “Did this device actually leave/return home” |
If you want to track a device moving between nodes without treating it as offline, there’s also “A client changed Deco node”, which fires specifically for that roaming case.
Thanks for offering to help debug this! Here’s how to capture a HAR file in Chrome — it only takes a couple of minutes:
Capturing a HAR file from your Deco’s web admin
- Log out of the TP-Link Deco app on your phone first (and close any other browser tabs logged into the Deco). We want a clean session.
- Open Google Chrome and go to your Deco’s local address (e.g.
http://192.168.0.1orhttps://192.168.0.1— whatever you normally use to reach it). - Open Chrome DevTools:
- Windows/Linux: press
F12orCtrl+Shift+I - Mac: press
Cmd+Option+I - Or: Chrome menu (⋮) → More tools → Developer tools
- Windows/Linux: press
- Click the Network tab at the top of DevTools.
- Make sure these are both on (checkboxes near the top of the Network panel):
- Preserve log
(so the recording survives page navigation/login) - The red record dot should already be active — if it’s grey, click it once to start recording
- Preserve log
- Click the
(clear) icon to wipe out anything already captured, so we start from a clean slate. - Now actually log in and use the Deco web admin like you normally would — log in, click around (device list, clients, network info), basically trying to capture the whole UI.
- Once you’ve reproduced the issue (or just browsed enough — a minute or two is plenty), go back to the Network tab.
- Right-click anywhere in the list of requests → Save all as HAR with content (the wording is slightly different depending on Chrome version — look for “Export HAR” or the down-arrow
icon at the top of the Network panel). - Save the file somewhere you can find it (it’ll have a
.harextension).
Sending it over
One heads-up before you send it: a HAR file captures your login session with the router, including auth tokens. It’s not your plain password, but please don’t post it publicly in the forum thread — send it to me directly (DM here, or however you’d prefer) rather than attaching it to the public post.
If you can grab one HAR file from a normal login, and ideally one more from whatever’s currently failing for you, that’ll give a much clearer picture of what’s happening on the wire.
Thanks again — this kind of diagnostic is exactly what helps track this down!
Thanks!
I’ll will try to create the files and will contact you after it’s done.
Check your inbox for link.
Send you a message for the HAR file. Hope it’s okay.
