-
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
Device did not pass attestation (error(s)=[1, 5, 11]) #156
Comments
Hey Jon, sorry to hear about the aggravation on this issue. Asking someone on our eng team to have a look. |
This appears to be another variation of the same problem. |
Back to attestation failing this morning.
|
Now the same device passed attestation. There is no pattern to these failures. |
Jon, do you have a project created for your test device? Also, could you try to reproduce with this tool: https://developers.home.google.com/matter/tools/virtual-device?hl=en This way I'd be able to test with the same environment on my side and help investigate. |
I have a project with all of the test IDs added. What does this error mean? attestation (error(s)=[1, 5, 11]) The error comes and goes on a device which has not been changed. Does this attestation chain onto a server at the CSA? Is that server going up and down? Another idea, is Google running multiple instances of the attestation checker? Maybe all of those instances are getting updated synchronously? one may be working ok, and another is not, and I randomly connect to them. |
Attestation errors are the following:
I've filed an issue so that enum names be shown on the logs instead of the enum int codes. |
Where does this nonce come from? I am not making it in my code. |
I don't really know how to debug this. The GPS library commissions my device twice. First time sets in the wifi credentials, the second time is my request. I would guess it is verifying attestation on both of the commissions, so why does the first one pass and the second one fail? Also, why is it intermittent? I can have a device fail for a few hours and then start working. I don't have the certificates wrong, because if they were wrong it would never work. Also, I can't generate these certificates anyway because I don't have access to the CHIP certificate authority, all I can do is use the ones provided in the SDK. |
I really don't know what is going on with this. I had a device fail 20 times. Went to a meeting, came back to debug and it works. |
Much later I figured out that this problem was due to testing on a Samsung device. After I switched to a Pixel device it went away and I forgot about it. I have not gone back and checked if GHSAFM now works on Samsung. Note --- this is probably because Samsung was working on Smarthings Matter support and they interfered with Google Home Matter support. Likely need to add continuous regression testing on Samsung devices. |
I am really getting tired of seeing this error. Please fix this to give more information so that I can tell why it is failing. This error is coming from GMS code and I can't see what it is doing. This error is interfering with my ability to develop devices.
I flashed three identical devices with the same image. One commissions, two fail with this error. And hour later one of them will commission and the other one still fails. Try again the next day and all thee may fail. It is just random if they succeed or not.
I am using the test certificates.
I have complained multiple times on the issue tracker and they just keep closing it.
https://issuetracker.google.com/issues/293901764
It is happening on both my Pixel phone and Samsung tablet. Both fully up to date.
Note that commissioning from Google Home works. It only fails using GHSAFM or my code which is derived from GHSAFM.
The text was updated successfully, but these errors were encountered: