Cannot add W100 and U200 to SmartThings via matter

How on earth are we supposed to add the W100 sensor and U200 door lock, which are connected to Aqara Home via M3 already to Samsung SmartThings? I already obtained the code from each device from the Aqara App instead of the product sticker via Third Party Ecosystem, put in the code to SmartThings, and the add always fails at registering device stage!

Please help!

Did you try both with the numeric code and scanning the QR? Sometimes in SmartThings I have more success with the QR, but that requires another device to display the QR generated by the Aqara app and scan it.

You mean I can’t just copy the code, switch to ST app and add the code?

That’s not what I meant, but given there are more methods to add the device I was sharing my experience. The QR has more comissioning information than the numeric code which could help in case of problems adding a device.

You can also try to add it to another controller like Google Home or Alexa if you have a smart speaker and share it to SmartThings from there. After that you can delete it from Google Home or Alexa if you don’t want the device there.

Again, workarounds, the numeric code should be enough in theory.

1 Like

Tried using the QR Code and still the same.

I should add that ST flashed a pop up saying “Your hub might be in a different network than your Matter device.” Which is technically true as ST is connecting to the hub (mDNS) which in this case is the Aqara App on my phone via wifi, and the device is on the thread network.

ST has no issues adding other aqara matter hubs (G410 and Camera Hub G3), which are bound to the account but no the M3 Hub, using the same methods though. Only when ST trying to add devices already bound to one of the Aqara Hubs will cause this issue.

And this only happens with Aqara Matter devices on the Aqara hubs. I tried doing the same to add a Tapo Matter Plug bound to the M3 Hub (added via matter code from Tapo App which the device initially bounded to). And ST picked it up without issue despite the same warning of different network.

After a couple of days, adding matter devices bound to M3 magically worked today. No clue why…