Im also having difficulties, strange thing is that when I add aqara fp2 through smartthings app, and look at the logs, discovery never even starts, instead for some reason my smartthings hub on Samsung S90C tv is trying to do bose discovery… looking at logcat logs, i cant see any lines about aqara driver, however it is listed as one of the drivers available.
2024-10-20T13:38:00.542979314+03:00 INFO bose Created dispatcher [SecretDataDispatcher]bose that had no handlers
2024-10-20T13:38:00.544869410+03:00 TRACE bose Setup driver bose with Secret Data handlers:
SecretDataDispatcher: bose
default_handlers:
child_dispatchers:
2024-10-20T13:38:00.546413070+03:00 INFO bose Starting bose driver
2024-10-20T13:38:00.548136255+03:00 DEBUG bose driver device thread event handled
2024-10-20T13:38:00.549123886+03:00 TRACE bose Received event with handler driver_lifecycle
2024-10-20T13:38:00.549933334+03:00 INFO bose received driver startupState: {"hub_zigbee_id":"sMfe//4D+zQ=","hub_node_id":null,"hub_ipv4":"192.168.1.3"}
2024-10-20T13:38:00.550970931+03:00 TRACE bose Received event with handler discovery
2024-10-20T13:38:00.551735132+03:00 TRACE bose Received event with handler environment_info
2024-10-20T13:38:00.552739201+03:00 INFO bose Starting discovery
2024-10-20T13:38:00.553510157+03:00 TRACE bose disco| starting discovery cosock task
2024-10-20T13:38:00.554383814+03:00 TRACE bose disco| inserting search id: scan
2024-10-20T13:38:01.562362533+03:00 TRACE bose disco| done waiting for search ids, sending ssdp discovery message
2024-10-20T13:38:01.644104436+03:00 DEBUG bose disco| response from http://192.168.1.4:4004/description.xml isnt a bose device: Linux/5.4.242-android12-9-gee0822034e3b UPnP/1.0 CyberLinkJava/3.0
2024-10-20T13:38:01.835269394+03:00 DEBUG bose disco| response from http://192.168.1.12:4004/description.xml isnt a bose device: Linux/5.4.242-android12-9-gee0822034e3b UPnP/1.0 CyberLinkJava/3.0
2024-10-20T13:38:04.659895128+03:00 INFO bose disco| response window ended, 0 found
If I select that, there is nothing in the logs. I only get some output when I select all. (Hit enter at the point in your screenshot without typing anything)
Make sure that your SmartThings hub and the FP2 are in the same network. Check the router settings if client separation/isolation is enabled - it shouldn’t.
Oh and the FP2 must be added and configured in the Aqara Home app first. But I’m sure you already know that.
I can confirm that I too am having issues connecting the FP2 sensor to SmartThings. My ST hub is my Samsung S95C tv and everything is on the same network (UniFi APs) and single VLAN. No client isolation is enabled.
I too have reset the FP2 every way as described in this thread with no luck in it being detected by ST when joining it.
I can also confirm that I see no output from the SmartThings CLI tool logcat command shown in this thread when monitoring the Aqara driver (1). Like other users I only see output from logcat when monitoring the other drivers e.g., SONOS.
I can confirm that I have tried every combination of steps described in this thread multiple times, all with no luck in getting the sensor connected to ST.
The only difference I can see is that I am not seeing anything on the ST cli logcat output for the Aqara driver which is making me think it could be the tv based hub not seeing the advertisement packets from the sensor?
I have tried, removed both sonos and bose drivers, started log output - using all drivers, as expected, no change - logcat doesnt log anything when I start Aqara FP2 pairing using the suggested pairing method:
It looks like your hub is also a TV (OLED)? This is common to my scenario in that we are both using the ST hub functionality in our TVs and both not seeing the advertisements on the logcat output.
gediminasstrelciunas@MAC-GKF99QPX4H ~ % smartthings edge:drivers:logcat
using previously specified default hub labeled "Hub - 77" OLED" (3a4084b9-e20d-4a78-a4d9-4ef5c5caad18)
› Warning: The authenticity of 192.168.1.6:9495 can't be established. Certificate fingerprint is 83:4E:D1:8C:C5:B6:C0:5C:7C:B1:88:AD:A2:42:C1:E0:CB:8D:97:F2
? Are you sure you want to continue connecting? Yes
› Warning: Permanently added 192.168.1.6:9495 to the list of known hubs.
────────────────────────────────────────────────────────────────
# Driver Id Name
────────────────────────────────────────────────────────────────
1 01976eca-e7ff-4d1b-91db-9c980ce668d7 Aqara Presence Sensor
2 4eb5b19a-7bbc-452f-859b-c6d7d857b2da Harman Luxury
3 7beb8bc2-8dfa-45c2-8fdb-7373d4597b12 JBL
4 cd898d81-6c27-4d27-a529-dfadc8caae5a Philips Hue
5 dbe192cb-f6a1-4369-a843-d1c42e5c91ba SamsungAudio
────────────────────────────────────────────────────────────────
6 d9c3f8b8-c3c3-4b77-9ddd-01d08102c84b Wemo
────────────────────────────────────────────────────────────────
? Select a driver. all
connecting... connected
Hi, @Andreas_Roedl
Let me catch up on the conversation and also ask about the support of this type of driver on Family hubs to see if it could be the reason.
I’ll get back to you once I know more
Has anyone been able to get this to work on a mesh home network?
I am stuck on the “prepare your device” page within SmartThings app even after the following:
Installing the Aqara FP2 driver
Updating the FP2 firmware to 1.2.8
Removing and readding the device in Aqara Home app
I wonder if my Eero network is causing issues. I have a Smarthing Hub connected to the Eero router (hardwired)
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
I’ll report your issue separately but I need the same information as above but include the steps you followed to install the device in SmartThings as well, please.
When you follow the steps above, those logs are uploaded to a SmartThings server that only certain team members can access. Or, are you referring to the Driver logs?
If you have them you can email them to build@smartthings.com to add them to the report just in case.
