Hi TP-Link Community and TP-Link Staff,
I'm experiencing a critical bug with EasyMesh Ethernet Backhaul that causes complete network failure after power outages. I've seen similar reports from other users but this issue remains unresolved in the latest firmware. I'm hoping TP-Link can prioritize a fix.

My Setup
Main Router:
Archer AX72 Pro V1.0
Firmware: 1.4.5 Build 20250928 rel.17568
Satellite Routers:

• Satellite 1: Archer AX72 Pro V1.0, FW 1.4.5 Build 20250928
• Satellite 2: Archer AX58 V1.0, FW 1.5.2 Build 20250812
• Satellite 3: Archer AX58 V1.0, FW 1.5.2 Build 20250812

Topology: Main Router → TP-Link LS105G Switch → All 3 Satellites (Ethernet backhaul, 10-30m cables)
All firmware up to date.

The Problem
When a power outage affects all routers simultaneously, the EasyMesh network completely fails to recover automatically. This happens EVERY time we have a power outage (approximately every 3 months).
What happens after power is restored:
Main Router (AX72 Pro):
All LEDs green except Internet LED (sometimes red/orange)
Tether App shows NO satellite devices, or satellites briefly appear then disappear
EasyMesh page shows empty or unstable satellite list
Satellite Routers (both AX72 Pro and AX58):
WiFi LEDs constantly cycling on/off (crash loop behavior)
Internet LED cycling red/on/off
WiFi completely unusable - devices connect then immediately disconnect
Ethernet-connected devices extremely slow and unstable
Result: The entire network is down. Family can't work, smart devices doesn't function.

The ONLY Way to Fix It
I have to manually restart routers in a specific order:

1. Turn OFF all routers (main + all 3 satellites)
2. Turn ON main router → wait until fully operational (all LEDs stable green, WiFi working)
3. Turn ON Satellite 1 → wait until fully operational
4. Turn ON Satellite 2 → wait until fully operational
5. Turn ON Satellite 3 → wait until fully operational

This takes ~30 minutes every time there's a power outage.
If I don't follow this exact sequence (main first, then satellites one by one), the network stays broken.

Why This is a Firmware Bug
When all routers boot at the same time (normal after power outage):

1. Satellites try to connect to EasyMesh before the main router is ready
2. Ethernet backhaul detection fails
3. Satellites try to fall back to WiFi backhaul, but that's not ready either
4. WiFi modules enter crash loop
5. Network becomes unusable

The firmware doesn't handle simultaneous boot properly - it requires the main router to fully initialize before satellites can join.

Other Users Have the Same Issue
I found several forum posts with the exact same problem:
@MCP1's post (October 2023) (https://community.tp-link.com/en/home/forum/topic/629630) - AX72 + AX10:
"Ethernet backhaul kind of works, but ONLY if you ALWAYS restart both routers together after the initial setup, first the AX72 and then the AX10. If you restart just one of them, or in the wrong order, the network (wired & wireless) becomes extremely slow until you reboot both in the sequence AX72->AX10."
@PedroBG's post (February 2024) (https://community.tp-link.com/en/home/forum/topic/593722?sortDir=DESC&page=12) - AX72 Pro + 3× AX53:
"Once a power outage happens, the network stability is lost after power is reestablished."
This detailed bug report (https://community.tp-link.com/en/home/forum/topic/820342) - AX55 + AX10: Documents the same boot synchronization failure.
This has been reported since October 2023 across multiple models (AX72, AX72 Pro, AX58, AX53, AX10, AX55) and still isn't fixed.

What I've Already Tried
✅ Updated all routers to latest firmware → problem persists
✅ Tested different firmware versions → problem persists
✅ Factory reset and rebuilt EasyMesh → problem persists
✅ Using official TP-Link switch (LS105G)
✅ Verified all cables working properly
This is NOT a cable issue, switch issue, or configuration issue. It's a firmware bug.

What TP-Link Should Fix
The firmware needs to handle boot synchronization properly:

• Add a startup delay on satellites so the main router can initialize first (60-90 seconds)
• Add retry logic when Ethernet backhaul connection fails
• Don't crash WiFi modules when initial mesh connection fails
• Add self-healing to recover from boot race conditions

Request for TP-Link Team
@Kevin_Z   @Sunshine 
Can you please acknowledge this is a known bug?
Is there a firmware fix in development?
What's the timeline for a fix?
Is there any workaround besides manual sequential boot?

This severely impacts the reliability of EasyMesh Ethernet Backhaul - a feature that's marketed as enterprise-grade but fails on every power cycle.

Impact
Every power outage = ~30 minutes of manual work to restore network
Family impact: Work disruption, no internet access, smart devices
Makes EasyMesh Ethernet Backhaul unreliable for real-world use

Thanks for any help!