ZTE Starry MAX and BE3600Pro+: wired mesh first, wireless mesh second

This ACWiFi article answers a practical question: can the ZTE Starry MAX mesh with the Starry BE3600Pro+ kit? I classify it as a serial/network guide rather than a teardown; it also has a different purpose from the BE3600Pro+ hardware article already on the blog.¹

Build the wired mesh

If the BE3600Pro+ is fresh from the box, connect a LAN port on the Starry MAX, acting as the main router, to the WAN port of the node with Ethernet. The system should create a wired mesh automatically. In the ZTE Smart Life app, open 组网管理 and confirm that the method 有线 is shown.

Pair the node near the main router first and move it to its final position afterward. I still verify the firmware and compatibility list because being in the same ecosystem does not guarantee that every hardware revision will pair.

Unplugging the cable: wireless mesh and self-healing

ACWiFi records that removing the cable makes the system switch to wireless mesh. In that example, the lost cable is treated as a link failure and self-healing changes the backhaul so the network can continue. That is different from a simple repeater/bridge, but I inspect the app after unplugging to ensure the node did not become standalone.

Wireless mesh does not have one fixed “half speed” formula, but backhaul and clients compete for radio airtime and can share a channel. Wired backhaul is normally the more stable choice; wireless is for places where Ethernet or fiber cannot be installed. During renovation, I prefer to wire more locations.

Choose by topology

• Cable between floors: main LAN to node WAN, then prefer wired mesh.
• No cable: pair near the main router, confirm wireless mesh, then re-measure RSSI and throughput at the final location.
• Roaming requirements: verify k/v/r support, firmware, and the app's node state.
• Do not treat the source's purchase links or promotions as current specifications; those details change.

Conclusion

The source supports using the Starry MAX and BE3600Pro+ as a mesh pair, with wired mesh first and wireless mesh as the fallback. I do not promise a particular speed: channel, distance, walls, firmware, and client count still determine the result.

Sources