I found the installation of some T2 bulbs a bit tricky, so I thought I’d post some problems I encountered & solutions to help other users. First, I have a Google Mesh WiFi & found that my M100 hub, the bulbs & my iphone had to be on the same access point… several points share the same WiFi but on different channels, so I guess to get it to connect you have to be using the same channel. Secondly, I can’t get Thread to work. It says that it can’t find my Aqara hub on the LAN even though I can see it in my Mac - and yes it is connected via IPv6 that’s needed for Thread. Luckily, I switched to Zigbee & it all connects just fine. It’s annoying that the default set-up is Thread & not Zigbee as it has taken me all day to find that I needed to switch to Zigbee.
@server_montbretias Thanks so much for sharing your T2 bulb setup journey! It’s incredibly helpful for other users to learn from the challenges you faced and the solutions you found—this kind of community sharing makes everyone’s smart home experience smoother.
Your tip about ensuring the M100 hub, bulbs, and iPhone are on the same access point (especially with Google Mesh WiFi’s multi-channel setup) is a great catch—channel consistency can often be overlooked, so that’s a key takeaway for others.
We totally get the frustration with Thread setup! As noted in the T2 bulb FAQ, the device defaults to Thread protocol, but switching to Zigbee is an option during the initial setup via the app. We’re glad Zigbee connected smoothly for you after making that switch—sometimes finding the right protocol fit for your network environment is half the battle.
Thanks again for taking the time to post this—your experience will save others hours of troubleshooting. If you run into more insights or tips in the future, feel free to share them here. The community really appreciates it! 
Go into the M100 settings and confirm that it was joined to your current thread setup and not created it’s own thread network independent from your current setup.
@david Thanks for the great tip, david! You’re absolutely right—ensuring the M100 hub joins the existing Thread network instead of creating a separate one is key for stable connectivity. As noted, connecting all border routers to the same Thread network helps enhance coverage and avoid network fragmentation, which is super helpful for users troubleshooting Thread setup issues like the original poster . Your insight will definitely save others time—keep sharing those smart home hacks!
Hi, but sorry you’ve lost me. I’ve no idea that I had a current thread set-up and I don’t know how it find it… I can’t see anything on ‘Threads’ in the M100 set-up. Sorry, I’m not that IT savvy and simply want to have some smart light bulbs 
Hello Again, well Google Mesh ( certain models ) have build in thread support and potentially this could either be the culprit or the M100, it’s difficult to know your setup.
Thanks, David… I’m starting to get my head round this. If I go to the Aqara app>Accessories>Hub M100> … >Network Info> Thread Network Management> I see NEST-PAN-CC89 which I guess is the Thread coming from my Google Mesh that the M100 is connected to. Is this good or bad? I note that I have to ensure that I make the enquiry from the same AP as otherwise it says ‘Detected that the phone is not on the same local network…’ Anyway, for the moment I’m not able to connect the bulbs using Thread, but Zigbee works great. Do I let ‘sleeping dogs lie’ or is it better to find a solution and connect the bulbs via Thread? Thanks for your help!
Honestly, for the most stable setup I’d carry on with the Aqara Zigbee method, I’m not knocking tread but you get all the options and configurations for the T2 light bulbs and some unavailable in thread mode.
If the lights work well and you have no issues in ZigBee mode then leave it for now would be my advice.
Many thanks, David, I’ll take your advice and stay with Zigbee - much appreciated.