-
Notifications
You must be signed in to change notification settings - Fork 38
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
Commissioning was failed at the step “Connecting device to GHSAFM-3p-ecosystem...” #180
Comments
From the log, we see that the first step of commissioning (to the local Android fabric) was successful:
GHSAFM then takes over to commission on its own fabric.
So the pairing failed with error code [50]. From https://github.com/project-chip/connectedhomeip/blob/master/docs/ERROR_CODES.md, we see that this is a timeout issue.
Not clear why it's not getting a reply back from the device without the device logs. |
Hi Pierre, Thanks for your reply, since nanoleaf's device cannot capture logs currently, I redo it with other device, here are the info and logs: GHSAFM-3p-ecosystem version: 1.4.2 device used to test: Google Play Services version: com.google.android.gms.optional_home [234523042] [23.45.23 (100400-0)] [Download:0000026b/dl-Home.optional_234523100400.apk] [download:/Home.optional/234523100400:Home.optional:234523100400] Phone logs: attachment Device logs: attachment |
I tried to commission a Nanoleaf light strip, it was successful on a Pixel mobile, but it was failed on other mobiles, the fail was at the step “Connecting device to GHSAFM-3p-ecosystem...”.
Here is the info:
GHSAFM-3p-ecosystem version: 1.4.2
device used to test:
Name: Nanoleaf Strip FB9-BE09
Model Number: NL68
Firmware Version: 3.5.41
Hardware Version: 4.1.8
Google Play Services version: com.google.android.gms.optional_home [234414042] [23.44.14 (100400-0)] [Download:0000025d/dl-Home.optional_234414100400.apk] [download:/Home.optional/234414100400:Home.optional:234414100400]
Phone logs: attachment
Device logs: not available
logs.txt
The text was updated successfully, but these errors were encountered: