Deco X60 V3 offline with green LED and cannot be discovered after reset
Deco X60 V3 offline with green LED and cannot be discovered after reset
Hi everyone,
I have a home network with 10 Deco units all running in Access Point Mode: 6 × Deco M5 and 4 × Deco X60. Everything worked fine for a long time until one of the X60 units started to behave strangely.
Symptom #1 – X60 offline with green LED
- In the Deco app this X60 suddenly showed as “offline”.
- The LED on the unit stayed solid green.
- All clients connected to this X60 lost internet access, while clients on the other Decos worked normally.
- Several normal reboots did not fix it.
Symptom #2 – M5 names reverting
Around the same time, three of my M5 units started losing their custom names in the app. The app sometimes shows them only as “M5”. If the node goes offline for a moment, the custom name comes back, but later it reverts again to “M5”. This is only cosmetic, but I mention it in case it is related.
Factory reset of the problematic X60
Because the X60 stayed offline in the app, I performed a hardware factory reset:
- Pressed and held the reset button on the bottom for about 15 seconds,
- LED turned yellow and then started blinking blue.
Since then I have not been able to add this X60 back to any network.
What happens now
- When in setup mode, the X60 broadcasts its default SSID `Deco_A3F8` (from the sticker).
- I can see and join `Deco_A3F8` from my iPhone without issues.
- However, the Deco app always shows the message “We couldn’t find any new Deco”.
I get exactly the same message in all of these scenarios:
1. Trying to add the X60 as a new node to my existing mesh (X60 placed about 1 meter away from the main Deco and also tested with Ethernet between them).
2. Trying to use this X60 as the main router, connected directly to the modem and using “Create a new network” in the app.
So at the moment I have:
- 3 × Deco X60 and 6 × Deco M5 working normally in Access Point Mode.
- 1 × Deco X60 V3.0 that powers on and broadcasts `Deco_A3F8`, but the Deco app (latest iOS version) never discovers it as a new device.
Questions
- Could this X60 be stuck as “bound” to my previous network/account in the TP-Link cloud and therefore not adoptable again?
- Is there any way for support to check its status from your side or to unbind / reset it remotely?
- From your experience, do these symptoms point to a hardware failure and should I consider an RMA?
Device details
- Model: Deco X60 (US)
- Hardware Version: V3.0
- Default SSID: Deco_A3F8
- App: Deco for iOS on iPhone
I can upload screenshots if needed (offline X60 with green LED, error message “We couldn’t find any new Deco”, Wi-Fi list showing the Deco_A3F8 SSID, etc.).
Thanks in advance,
Gaston
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @David-TP and TP-Link team,
I’m posting here again as a follow-up to my previous messages in this thread, since there has been no further public reply and the situation remains unresolved.
To summarise the current status very briefly:
-
The affected unit is a Deco X60 V3.0 with the abnormal “Deco_25:00” SSID that can no longer be adopted by the Deco app.
-
The device boots, enters setup mode (blue blinking LED), broadcasts Wi-Fi, responds to ping, accepts recovery mode and successfully takes firmware (including 1.0.15, 1.0.13 and later 1.3.0), but still keeps the abnormal SSID and is never discovered by the app.
-
This matches other documented cases with the same “Deco_25:00” symptom described in the community.
In parallel, I have tried for months to contact TP-Link Argentina through every official channel (email soporte.ar@tp-link.com, 0800-888-7808, social media), without any response at all. From a practical standpoint, there is currently no functioning local support in my country.
Given this context, I would really appreciate a clear and official answer from TP-Link on three specific points:
-
Failure classification
How is this “Deco_25:00 / identity / ART / EEPROM corruption” failure mode officially classified by TP-Link? Is it considered strictly “non-repairable hardware failure”, or is it a recoverable identity/storage issue at factory or service-center level?
-
Product lifetime and “natural hardware aging”
In a previous reply (Dec 10), it was mentioned that, after ~3 years of operation, “natural hardware aging” may explain this failure.
I need to know whether TP-Link considers ~3 years to be a normal useful life for Deco devices, where failures of this type are to be expected and replacement is the recommended solution, or whether that wording does not reflect an official position on product lifetime.
-
Support path when local service is not reachable
When the official local service in a country does not respond by email, phone or social media for weeks, what is the official escalation path for customers?
In my case, all answers keep sending me back to “local support”, but local support is effectively not available.
I want to stress that I am not looking for a confrontational exchange. I have invested significantly in the Deco ecosystem (10 units in total) and I simply need transparent, technically grounded and consistent information from the manufacturer so I can decide what to do next and so that other users facing the same “Deco_25:00” pattern can also understand clearly what their real options are.
Thank you in advance for a concrete clarification on these points.
Best regards,
Gaston
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 742
Replies: 11
