-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use ESP Matter APP to connect with matter bridge (con 1 reason 0x213) (CON-914) #755
Comments
@GeeklinkSmart What exactly is the ESP Matter app you are talking about? |
@GeeklinkSmart The ESP Matter app was added as a test app to perform the commissioning, and is not maintained currently. Instead, the ESP RainMaker app is the default app for Matter from Espressif. The iOS app is already updated on the app store to support Matter while the Android app will be updated soon. AFAIK, the bridge device type isn't supported in the app yet. |
@dhrishi now I can use IOS app Home to add it as matter accessory, and the bridge show online ,but the light shows no responed, So I can't control the light in Home app. |
@GeeklinkSmart Does the default BLE Mesh bridge example not work with the Home app? If yes, please create a new issue and provide details about the iOS version. Also, mention if you are doing any changes in your app. I will close this one as the original question is answered. |
You guys should update the instructions in Section 2.3 here, as it still points the reader to the old app, which no longer exists in the App Store. |
@JetForMe Thanks for pointing out, will update the links! |
Now I can use chiptool to connect with the matter bridge and control the light.
But when I use ESP Matter APP to connect with matter bridge ,I scan the QR code ,this is the logs.APP shows timeout after a while
I (28088) chip[DL]: BLE GAP connection established (con 1)
I (28089) chip[DL]: CHIPoBLE advertising stopped
I (29268) chip[DL]: BLE GAP connection terminated (con 1 reason 0x213)
I (29269) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (08:00:27.400) NimBLE: GAP procedure initiated: advertise;
I (08:00:27.407) NimBLE: disc_mode=2
I (08:00:27.411) NimBLE: adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (08:00:27.422) NimBLE:
I (29297) chip[DL]: CHIPoBLE advertising started
I (32586) chip[DL]: Configuring CHIPoBLE advertising (interval 500 ms, connectable)
I (32587) chip[DL]: Device already advertising, stop active advertisement and restart
I (08:00:30.720) NimBLE: GAP procedure initiated: stop advertising.
I (08:00:30.728) NimBLE: GAP procedure initiated: advertise;
I (08:00:30.734) NimBLE: disc_mode=2
I (08:00:30.738) NimBLE: adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=800 adv_itvl_max=800
I (08:00:30.749) NimBLE:
The text was updated successfully, but these errors were encountered: