Not a Matter-certified device #93
Comments
|
Please provide complete logs from the phone. See https://github.com/google-home/sample-app-for-matter-android/wiki/How-to-investigate-issues-with-the-sample-app-(GHSAFM) |
|
@pierredelisle I can't access the device logs at this moment. I have included all the info I can provide at this moment below. Please let me know if there is anything else you need. GHSAFM version
Test Device
Google Play Services version
% adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep -E '(policy|optional)_home'
com.google.android.gms.optional_home [230617065] [23.06.17 (100400-0)] [Download:000001b8/dl-Home.optional_230617100400.apk] [download:/Home.optional/230617100400:Home.optional:230617100400]
% Phone logs
|
|
Facing same issue. It was working fine but from tomorrow, sample app is showing "Not a Matter--certified device" error. |
|
It looks like the device is failing attestation. I still can't figure out why. |
|
I am also facing the same issue (Unable to commission the device, shows error - "Not a certified matter device") with the GHSAFM test app this week. But with Chip tool it works fine without any issues Earlier, I was able to commission the device with Google Home Sample App for Matter (GHSAFM) without any issues with the color temperature light example with ESP32 C3 hardware. Here is the device log file |
|
Error : "Device did not pass attestation" Android side Logs :
|
|
@edWin-m I've also experienced some mDNS issues yesterday that eventually bubbled up as Device Attestation failures. I will be releasing version 1.4.0 shortly, which ignores device attestation failures. However, please note that if you build from main, that fix is already there (see commit 0eb3c6d). There should be no device attestation failures, but intermittent mDNS issues will still arise until a platform fix is done. |
|
@pierredelisle noted. I have already noticed the changes introduced in commit 0eb3c6d. Is there a way we can be notified when the team has found a fix for the mDNS issue? |
|
Hi @pierredelisle , |
|
I was also experiencing the same issue constantly yesterday and past Friday. Today, commissioning is working again even before commit 0eb3c6d. |
|
Hi @tetedoie , thanks for updating. it is working now. |
|
@khushbushah2302 Same here. @pierredelisle Does this mean the issue has been fixed? |
|
Well, the root cause of the "device certification failure" has been fixed. So I'll close this issue. However, there is a known issue with mDNS (as I mentioned above) that may happen (it's not deterministic), and the error message that bubbles up may vary. Team is working on a fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This device can't be set up or controlled with Google.
I was using this device recently (less than 24 hours ago) without this issue in GHSAFM. I can still commission it using the
chip-toolin a terminal and Apple Home seems to be working well too. I have attached the device logs showing thematter configand the commissioning error.Version
Commit -
0eb3c6d2c126c020619d3fe40026c9fa52e1c80cDevice Error Log with GHSAFM as Commissioner
Matter Device Config (ESP32)
The text was updated successfully, but these errors were encountered: