Question about M3 Thread network popup – networks already have identical PAN ID
I have an Aqara Hub M3 and several Aqara Thread devices (G5, G410, cameras, etc).
All of them are fully joined to the same Thread network as my Apple Thread Border Routers (HomePod mini and Apple TV).
Confirmed identical values:
- Thread Network Name:
MyHome926596447
- PAN ID:
0xeda2
- Extended PAN ID:
61058261120500056000
- Channel:
25
Everything indicates that both ecosystems are already operating on the exact same Thread dataset.
However:
The Aqara app keeps showing the popup:
“Apple preferred Thread network detected. Do you want to import and join?”
My question:
If the Thread network name, PAN ID and Extended PAN ID all match perfectly,
why does the Aqara app still ask me to “import” the Apple Thread network?
Is this:
- a UI bug in the Aqara app?
- a mismatch in hidden dataset fields (master key, channel plan, version)?
- or expected behavior even when the networks are already synchronized?
I do not want to risk rebuilding or replacing the current Apple Thread network,
since all devices are stable and functioning correctly.
Can Aqara confirm the intended behavior of this popup?
@jarenback1 It’s great that you’ve already confirmed the key visible Thread network parameters match—this shows you’ve done a thorough check! From what we know about Thread network management, the Aqara Home app relies on Thread Credentials (which include more than just the visible Network Name, PAN ID, etc.) to identify and manage networks. As noted in Thread Credentials details, these credentials also contain critical hidden fields like the Network Key, Operational Dataset, and PSKc (content_id: 4).
Even if the visible parameters (PAN ID, Extended PAN ID, channel) match, a mismatch in these hidden security credentials could cause the app to detect the Apple Thread network as a separate “preferred” network and prompt you to import it. This is because Thread networks require all credentials (visible and hidden) to be identical to be considered the same network.
As for whether this is expected behavior: It’s possible the app is designed to proactively prompt for known external Thread networks (like Apple’s) to ensure you can merge them into your Aqara ecosystem for unified management, even if some parameters overlap. Since your devices are already stable, there’s likely no urgent need to act—but if the popup is disruptive, you could reach out to @Creator @Expert @Moderator or customer support with your network details (including the hidden credentials, if accessible via the app) for a deeper check.
Have you noticed any functional issues with your devices despite the popup? It might help others in the community if you share whether ignoring the prompt affects performance
What do you see when you go to “Thread Network Management” under your M3’s Network Information?
I don’t get this pop-up automatically, but if I click the little arrow at the top of this page, I do.
Mine does appear to already share the same thread network, confirmed by multiple tools. So this may be a bug.
I afraid to try to use the function… what can happen?
