Goodday, I’m trying to connect the Deco to the Homey app. The Homey pro has a cable internet connection. The cable for internet is inserted in the main Deco device. The Homey pro and the Deco device are sharing the same IP adres. I’ve tried to connect, tried to start over etcetera.
Hm i had a similair issue while connecting to my M9+/X50 network last week. For some reason it seems it’s not taking the password while i’ve confirmed it to be the correct pwd by logging into the Deco webgui. Sometimes it shows incorrect pwd and sometimes it just closes the addition interface. I’ve moved on without adding it.
I have the same issue with brand new Deco BE85.
Report: 05b526cc-626c-4c56-a915-84766b11213c
I have issues with Deco M9 and M5 devices. Provided the correct credentials but screen returns to logon again.
Report: d37df1cd-5d20-40df-afa2-bccd6a8086a1
Using version 1.4.69 on Homey Pro 2026
This doesn’t seem to work for my BE65 network. It only sees my device while connected to the master node.
I double checked if I really used the “joined/left the Mesh” trigger. 
Anything else I can do to fix the flow?
Hello. Been trying for a while now to get the deco Homey app to connect to my XE75 Pro without success. I have followed some advice in this thread both from Mathias (developer) and others such as:
- Setting up a new manager account for my deco router and only using this in my TP-link Deco App (i.e. the routers own admin app), only using the main admin account for the Homey app.
- Disabling MFA for main admin account (seems only to affect the mobile app though, as the web interface works without MFA regardless)
- Trying different addresses such as the IP (192.168.68.1 in my system) as well as tplinkdeco.net.
- Making sure I have both the Tplink Deco app as well as any web sessions logged out and closed ( as I now use a separate management account for the app this should not affect the Homey app but just to be safe).
- Re-starting as well as re-installing the Homey Deco app.
I have made some progress, as I have moved from ”wrong credentials” or ”unknown login method” errors to a state where the app seems to accept my credentials without error messages,
However, I still can’t get the connection to work. I just throws me back to the device selection screen.
My credentials works fine for the web. However the XE75 Pro demands an SSL connection and gives a private certificate warning which you have to accept. I don’t know if this is a problem for the app?
Can’t really think of anything else to try, besides factory resetting my Deco router, which I am doubtful would help as I get access through the web ok.
Has anyone got the app working with XE75 Pro?
What was actually broken — v1.4.70 is on Test
First: thank you. Fifty-eight reports came in between mid-August and now — forum posts, emails, screenshots, browser console output and diagnostic logs. I don’t own most of the Deco models involved, so your logs were the entire diagnosis. Several of you sent one, got no reply, and sent another. Sorry about that.
I went through all of them properly. Short version: the login was never the problem. In every diagnostic log I have, the app logs in successfully, fetches the full node list from the router, and builds all the devices correctly — and then the pairing screen closes anyway. What looked like one big “it doesn’t work” turned out to be several unrelated bugs, across twelve Deco model families and five different Homey models. It was never about your hardware.
1. Pairing bounced back with no error — and there were two causes, not one
This is the one nearly all of you hit: enter the IP and password, press Log in, the window flickers, and you’re back on the add-device screen. Nothing added, no message. On some setups you couldn’t even reopen the login screen without restarting the app.
Cause one — Homey’s built-in login screen. The app was using Homey’s standard login template. Its own script calls two methods, Homey.getCurrentView() and Homey.error(), that don’t exist on every Homey client. One of you opened the browser console during web pairing and sent me this:
TypeError: Homey.getCurrentView is not a function
TypeError: Homey.error is not a function
That single paste is what cracked it. The template crashes the instant you press Log in, so the screen never moves on — while the app behind it has already logged in and has your node list ready. And because the crash happens inside the error-display path too, no message could ever be shown. Hence “it just closes, without any message”, which a dozen of you described in almost identical words.
The app now has its own login screen that assumes nothing about which methods a given Homey client provides, and shows errors in its own interface.
Cause two — a node reporting incomplete data. One diagnostic log showed a router returning a satellite with no IP, hardware version, firmware version or hardware ID. The app passed those straight through into the device settings, Homey can’t store an undefined setting, and the whole app process fell over while adding devices. That’s the app restart some of you saw, and it’s why a few people described it as a crash rather than a bounce.
These two are completely independent and produce identical symptoms. Fixing only the first would have left a share of you with exactly the same experience — which is precisely what would have happened if that second log hadn’t come in. Both are fixed.
2. The app was locking you out of your own router
Some of you got “another session is already active”, closed the Deco app everywhere, logged out of the web interface, even created a separate Manager account because the error message told you to — and got the same error. One of you rebooted every Deco and Homey itself first. That advice was wrong, and I’m sorry for the wild goose chase.
A diagnostic log finally showed what the router actually replies:
{"result":{"failureCount":10,"attemptsAllowed":0},"error_code":-5003}
That is not a session limit. That is your Deco’s own brute-force protection, blocking logins after ten failed attempts. The app didn’t recognise the code, so it moved on to the next login format, spent another attempt, eventually collected a 403, reported that as “session limit” — and then retried on a schedule, refreshing the very block it was waiting out. A rebooted router doesn’t clear that counter, which is why rebooting everything didn’t help either.
It also explains the reports where the app said the password was wrong while the same password signed you in at tplinkdeco.net in a browser.
The app now recognises the lockout, stops immediately, and tells you to wait instead of retrying. The Manager-account advice is gone.
If you’re stuck in this right now: stop pressing Log in. Wait about 15 minutes without touching it, then try once. Every extra attempt restarts the timer.
3. The app was putting far too much load on your router
A few of you reported your internet going down repeatedly, and one went to the trouble of A/B-testing it: network rock solid with the app disabled for days, down within half an hour of switching it back on. Someone else had reported the same on a different model six months earlier and worked around it by raising the refresh interval. You were right, and I should have taken it seriously sooner.
Three things were wrong. A reachability check ran before every login that cost about ten seconds and whose result was never used for anything. Failed reconnections retried in a tight loop with no pause, so a router that was struggling never got a chance to recover. And every node in your mesh polled within a few seconds of every other one, so the router took the whole mesh’s worth of requests in one burst each cycle.
The useless check is gone, failed reconnections now back off (30 seconds, doubling, up to ten minutes), each node’s polling is spread across the whole interval instead of bunched together, and the minimum interval is now 15 seconds with a 30-second default — the old default of 10 seconds was too aggressive, and the old minimum of 1 second should never have been allowed.
This is better, not finished. The app should also share one session per mesh rather than one per node. That’s next.
4. Smaller things you reported, now fixed
- Decos showing stale values — including “WAN disconnected” on a working network. Devices now show as unavailable instead of presenting old data as if it were live.
- Presence flickering offline/online every minute on a device that hadn’t moved.
- Homey showing the wrong node as the main Deco after you swapped units.
- The “Login failed” screen sitting on “Loading…” and never showing what was tried — which quietly cost me the diagnosis on at least one unsupported firmware.
- The presence widget showing nothing but a spinner.
- The login screen not saying what to type. Three of you entered your email address, your Wi-Fi network name, or Homey’s own IP — all reasonable readings of a box that asks for a value and a password. It now says what it wants, and rejects the obvious mistakes before spending one of your router’s ten login attempts.
- The password hint claimed the Deco app has a separate local admin password. TP-Link’s own support pages say otherwise, and I can’t currently confirm which is true for which model. It now says something you can verify yourself: the same password that signs you in at tplinkdeco.net in a browser.
On “Timeout after 30000ms”
Homey gives the pairing login about 30 seconds. The app was burning a chunk of that before the first login request even went out — roughly 14 seconds of it — which this release removes. That helps a lot in normal cases.
But I want to be straight about it: the worst case is still not bounded. If you have a large mesh and see that timeout while pairing quietly succeeds in the background anyway, that’s this, it’s known, and it’s on the list. Tell me and I’ll prioritise it.
One more thing — please read this if you sent me a log
Two of the diagnostic logs you sent contained your router password in clear text. One log line wasn’t redacting it. That’s fixed, and redaction now happens centrally so that particular class of mistake can’t recur.
I have not stored those passwords and they are not in my notes or in the repository. But I would rather tell you than not: if it makes you more comfortable, change your Deco password.
Which version do I need?
- v1.4.69 (currently on Live): does NOT contain any of this. If you’ve read somewhere that this was fixed and you’re still on Live, that’s why it still fails for you. There was an unfinished draft of this work visible on GitHub for a while, which I think is where that impression came from. It’s closed now.
- v1.4.70 — Test channel: https://homey.app/a/net.tornbloms.deco/test/
I’d like this confirmed by a few of you before it goes Live. If you install it, please reply with your Deco model, your firmware version, and whether pairing completed. If it fails, send a diagnostic report right afterwards (More → Apps → TP-Link Deco → Diagnostics) and post the report ID here.
Particularly useful to hear from: anyone on a BE68 mesh, anyone who was getting the “session already active” message, anyone whose network was going unstable, and anyone with six or more nodes.
Still broken, and I’d rather say so
- Homey (Early 2019): the app doesn’t start at all — it fails during initialisation with a capability conflict. The crash report doesn’t say which capability, and I’d only be guessing. If that’s you, a diagnostic report would genuinely help.
- Decos not reconnecting after you reboot the router, where removing and re-adding the device is the only fix. I wrote a fix for this and then threw it away: it would have cleared the shared session for every node in the mesh, which risks causing the very overload described in section 3. I’d rather leave a known bug in place than trade it for a worse one.
- LTE data on X50-5G still isn’t detected.
On what this app can and can’t promise
A few messages have carried an expectation that things get fixed on request, so let me be straight about how this actually works.
This is a hobby project and I have one Deco mesh. Everything from BE68 to M4R to X50-5G is supported based on protocol documentation and on logs people send me. I can’t reproduce a fault on hardware I don’t own, and I can’t test firmware I’ve never seen. When TP-Link changes something in a firmware update — which they do — I find out because one of you tells me.
So: reports with a diagnostic log get fixed. Reports without one usually can’t be. That isn’t me pushing work back onto you; the entire content of this release came from logs and one browser console paste. It’s genuinely the only way this works for models I’ll never hold.
Thanks for the patience, and for the reports. Fifty-eight of them is a lot of people taking time to help.
I am really happy to see some progress here! Thank you so much.
However, I am still unable to login to my X55, as nothing happens when I press Log In at the App’s login-page.
Diagnostics report 09f5cce4-d198-440e-b313-15f2b43099db
Deco FW 1.8.0 Build 25102213 Rel. 43970
Also, as stated in the report, link in your post gives v.1.4.71, not 1.4.70. Assuming it is intentional, but FYI just in case.
Thanks! I’m settling in to sort a few bits across different projects this evening. There’s a new 1.4.72 release that adds extra logging around pairing and a few other areas – please give it a go and send me any diagnostics. When you create a ticket, do pop a quick note in the field so I can see what the logs are showing and what issue you’ve spotted.
Nope.
App Version 1.4.72
Deco X50(1.0) | 1.8.0 Build 25102213 Rel. 43970
In web browser/ webapp, I can’t type in url or password.
In app nothing happen when press login
BE65 pro exact the same problem.
Hey Mathias, thanks for spending so much time on this hobby. And thanks for your very transparent explanation to users like me about how the testing and debugging process works in the real world.
I was very excited to see that you were trying to bring this app back to life. Unfortunately I fell at the first fence. Here are the steps:
- I installed your test version 1.4.72
- I clicked to add device
- When prompted, I added my IP address of the main Deco, and my password.
- When I click Login, nothing happens. No error message. Literally nothing.
And that’s it. All I can do is reverse out. I’ve restarted my Homey Pro but this didn’t make any difference.
I’m using a Homey Pro 24 and I have 5 decos: 3 XE75 Pro, 2 X10.
Any other information I can send you?
1.4.72 is completely broken. I am not able to enter the IP and password. Clears out every half a second…
Browser: Edge (desktop)
On Android it is not happening, but Log In button does nothing.
1.4.72 was just a trial run. We’ve now released 1.4.73, and I’d be really grateful if you could test it for me. Please send over your diagnostics – whether everything goes well or something goes wrong – and do try to be as detailed as possible in your feedback.
I have now released 1.4.73, and I’d be really grateful if you could test it for me.
Hi @MathiasT
Thank you for your awesome work! I do get past the login screen(1.4.73), although it gives me a warning about a login which the app doesnt have seen before? Quite a cryptic description, I did make a diagnistic report for you:
6b6da19d-8936-4ac9-907d-d6cf5788ce51
I’m using Deco XE75 Pro
Hi @MathiasT,
I am able to sign in now and add my two BE85 devices.
Anyway, I have sent you a diagnostic report: 8c427c82-b61f-45fc-958a-0c68b6784f2f
Here is my note: Sign in works now! Right after it found both of my BE85 (master and slave). It shows as a note the connected clients, but there is no way to add clients as a Homey device (possibly as intended). However, other app (Netgear) allowed me to add connected computer and that way to get more info about that client and to send Wake on LAN packet.
I don’t know what is possible, but more detailed connection properties would be welcome.
BTW there are two buttons (Sign In and Continue) on the first screen, I have used the Sign In one.
Thank you, Mathias. This seems to work much better with the latest test build (1.4.73). I connected the whole system (2 BE85 devices and 2 BE65 devices with a mixed wired and wireless backhaul). Created some test flows and checked the values. Very good job!
Hi, I connected all 5 of my Deco’s successfully using 1.4.73. Everything seems to be working 100%. Thanks for all the hard work.
