I have firmware to setup FP2 in smarthings, but when I search nearby nothings happens? Somebody knows that I missing someting?
Delete the FP2 in the Aqara Home app, re-add it, try again in ST.
Andreas, I have deleted 3 times, my fp2 is chinese version, maybe is something related?
I don’t even know what firmware version you have…
Ah, yes, good advice.
I figured this one is okay to install since it was posted in this thread and no one flagged it as being harmful.
So…
When you delete the FP2 from the Aqara app, does the LED of the FP2 start to flash rapidly?
Yes, rapidly quickly, but does not working! The FP2 and hub is in the same wifi connection, I believe the problem is related to chinese version of my FP2, I can’t connect through Alexa and Google regarding region restrictions. It’s frustating! 
When it’s flashing, you have to add it to the Aqara Home app first, before you can add it to ST.
Try to add it by choosing the device directly - not by scanning:
If this doesn’t work, a logcat would be helpful. Install this on your computer:
And execute it:
smartthings edge:drivers:logcat
Choose the driver, then try to add the device again through the SmartThings app.
Copy & paste the output here.
How do you know that your device is from Mainland China?
I bought my FP2 in aliexpress and does not support alexa and google integration and just work in Aqara app in China server.
Does it have CN in its device name in the Aqara Home app?
ST’s Edge drivers repository on GitHub has three main branches. When new standard drivers are created, or changes to existing drivers are proposed, a pull request is made against the ‘main’ branch. As part of this pull request a temporary channel is automatically created with the proposed new driver in it to allow it to be tested while the pull request is being evaluated.
Once the PR is approved the code gets merged into the ‘main’ branch. Once a week, all being well, (it always used to be a Tuesday, but lately it has often been a Monday) the driver gets rolled up to the ‘beta’ branch where it gets repackaged and assigned to the Beta channel. The next week, again all being well, there is a roll up from ‘beta’ to the ‘production’ branch and the driver is assigned to the default channel.
The default channel is so called because you do not need to explicitly enrol your hubs in it and new drivers are automatically installed on your hub if required, but it is otherwise a channel like the others.
Installing a driver from a channel in the PR is OK if you particularly want to engage in the testing process, but for day to day use you will probably want to reinstall from one of the production channels (beta or default) at some stage as you will potentially be missing out on other changes to the driver. This is because although the various channels may have different version numbers of the ‘same’ driver (which may or may not have identical code), the hub knows what channel the driver was last installed from and only updates that appear in that channel are installed.
I was able to contact aqara customer support last night. By the morning I was able to update to update to version 1.2.8_0006.0086. I’m at work now when I get home I’ll see how good the integration is.
Same, I saw they just pushed the update for me too. 
When I go to Select different driver it has the SmartThings version 2024-10-10, I can just select that right? I don’t need to reinstall?
That sounds right. I could have chosen my words better.