I am unfortunately still unable to login to my X55. Error message: This Deco’s firmware uses a login format this app hasn’t seen before.
Diagnostics code 9f1d5f6c-2e57-4878-8d27-52d48221a5a9
X55 with FW. 1.8.0 Build 25102213 Rel. 43970
Exact the same here.
269fac57-7882-4150-a840-3496137d5d0c
4 x Deco BE65 pro. Firmware 1.31 rel 23561
App version: 1.4.73 (experimental)
Homey Pro (Early 2023), firmware 13.5.0
The app connects to the Deco system successfully, but no clients are ever listed, the client list is empty everywhere, not just in Flows. This means client-based Flow cards can’t be configured, since there’s nothing to select.
Deco setup:
- BE68 (primary) — firmware 1.3.6
- BE65 — firmware 1.3.3
- BE65 — firmware 1.3.3
- BE25-Outdoor — firmware 1.2.0
What works: Connecting to the Deco system via the experimental app.
What doesn’t: No clients appear anywhere in the app (Flows included), so nothing client-based can be used.
Diagnostic report ID: 15ba0b75-67ed-4614-a3d8-7d2b4718ca34
Hi Tobias, thanks for the detailed report and logs — much appreciated.
I found the root cause: on your setup, every non-master Deco (the 2× BE65 and the BE25-Outdoor) was failing to read back its settings after each app restart, not just right after pairing. The retry logic added in the previous release only waited 6 seconds before giving up, which wasn’t enough in your case — so those devices never got an API connection or polling running at all, which is why no clients ever showed up.
This is fixed in v1.4.77, now published:
The retry window is now up to 30 seconds instead of 6.
That retry no longer blocks the app’s own startup, so even a slow device can’t risk the whole app failing to start.
Could you update to v1.4.77 and let me know if clients now show up correctly after a restart? If it’s still not working, a fresh diagnostic report would help me dig further
Hi and thank you! I confirmed the version, restarted my Homey and then tried to create a flow but couldn’t list any clients. Diagnostic Id a259fb68-9be7-4b22-8e13-60cce75ac0a6
They are all working now. I had to manually go in to each Deco and add the password, then reboot and after that they were all connected. Thanks!
Hi Tobias,
Thanks again — your last message was actually the key piece: the fact that manually re-opening each device’s settings and re-entering the same password fixed it told me exactly where the bug was. It turns out the password wasn’t being saved reliably during pairing itself (while everything else — hostname, model, etc. — saved fine), which is exactly why re-entering it by hand worked.
v1.4.79 is now published and should fix this properly — no manual re-entry needed anymore. If a device’s password ever fails to save during pairing again, the app will now notice and automatically re-save it itself on the next restart.
Since your devices are already working now (after your manual fix), you shouldn’t need to do anything else. But if you ever remove and re-add a Deco in the future, it’d be great if you could let me know whether it comes up working right away on v1.4.79 or later — that’ll confirm the fix holds for new pairings too.
Thanks again for sticking with this and for the detailed reports — you basically solved it for me.
Hi @MathiasT
Thanks again for your tremendous work!
Though i’m still facing issues login on my Deco through the test app 1.4.79, see below error message as soon as I type in my IP adress of the main Deco and the correct password :
dc535760-5b6c-4e1a-aa37-ce048eb68a4b
Is there anything I can try now?
Hi Borssie,
Thanks for the diagnostic report — this confirms what I suspected. Your Deco’s firmware is rejecting all 6 login formats the app currently knows how to try (two different content-types × two body formats × two password encodings), each in a different way, which points to this specific firmware speaking a login protocol the app hasn’t seen before — not a password problem.
To fix this, I need to see exactly what a real, successful login looks like on the wire for your router. Could you capture a HAR file while logging in through the browser?
- Open
http://192.168.68.1(your Deco’s IP) in a desktop browser. - Open DevTools (F12) → Network tab, check Preserve log, and clear anything already listed.
- Log in with your password as you normally would.
- Right-click anywhere in the network request list → Save all as HAR with content (Firefox: “Save All As HAR”; Chrome: use the export/download button above the list).
A couple of notes:
- Please skim the file yourself before sending — the login should be encrypted, but double-check nothing looks like a plaintext password.
- Send it to me directly (not posted publicly) since it’ll contain details about your local network.
Once I have that, I can see exactly which request format your firmware expects and add it to the app. Thanks for your patience — this is the one case we haven’t been able to crack yet, and your HAR should finally let us do it.
Send you an error report.
Hi Mathias, thanks for the app.
I can’t get my Deco mesh added to Homey and I think I’ve narrowed it down to something on the app side, so hopefully this is useful feedback.
Setup:
- Deco BE65, hardware version 2.0 (shown as BE65(2.0) in the web UI)
- Firmware 1.3.2 Build 26040912 Rel. 40631 on both nodes
- 2 nodes, router mode, behind an ISP router (double NAT)
- LAN 192.168.68.1, subnet mask 255.255.252.0
- Homey Pro is on the Deco network at 192.168.68.60
- App version: [VUL IN]
What happens:
I enter the hostname and password and press Log in. There is a short loading spinner, then the pairing dialog closes and returns to the driver selection screen. No error message, and no “new devices found” step. Nothing is added to Homey.
What I’ve already ruled out:
- The password is correct. The same password logs me into the web UI and when I deliberately used a wrong one earlier the app correctly returned “Wrong password (9 attempts remaining)”. So communication with the Deco works.
- No other admin session is active. I log out of the Deco mobile app and the web UI before each attempt.
- Tried 192.168.68.1, http://192.168.68.1 , https://192.168.68.1. Same result each time.
- Tried on both the mobile app and the web app, and restarted the Homey app in between.
- No half-added Deco devices left over in Homey.
My guess is that login succeeds but reading the node list fails on this hardware revision, since the BE65 v2.0 with 2026 firmware may return a different response format. Happy to run any test or grab logs if that helps.
Thanks!
Please try the test app TP-Link Deco | Homey and provide feedback
Thanks you very much! It works now.
@MathiasT Did you have an update regarding the log-in issues I’m facing ?
