Unable to pair matter device since 16th dec update #61
Comments
|
Something what I want to note: When I look at this I have the feeling that the setup does a lookup for the device in the network, however my understanding is that this appears only after the device was on-boarded (and has received its credentials and certificates). |
|
I also confirmed that pairing with the latest Matter virtual device also does fail with the same issue. Home App: 2.62.1.15 (All this still worked a few days ago.) |
|
A few things to help diagnose this issue:
Full logs on device: I've seen something similar in the past. This was caused with mismatched signing certs between the device and the client app. See project-chip/connectedhomeip@faad9e1. |
|
I installed latest version of GHSAFM and re-created my Home and I found the following: 1. I can pair a new Matter device with the GHSAFM app, but previously this on-boarded it also on the Google Fabric (for Google Home). Now it seems that's not the case anymore. In any case, I then go to the device to "Share" it with the Google Home app, and while on-boarding on the Google Home app, the error posted above can be seen.Again when it fails during pairing after starting the sharing: Full device logs: https://gist.githubusercontent.com/lpfsue/a89c6c22e39780240a1c7756a3a91f5c/raw/f8cccad1b74c8849c61a0db62c7e50f309e0e082/logs_ghsafm_pair_share_virtual_device.log 2. When I just try to pair the device with the Google Home app, I see the same error at the same stage.Full device logs: https://gist.githubusercontent.com/lpfsue/a89c6c22e39780240a1c7756a3a91f5c/raw/f8cccad1b74c8849c61a0db62c7e50f309e0e082/logs_gh_pair_virtual_device.log App VersionsGHSAFM: v1.2.2 Additional Notes: I tried this with two separate setups (with different Google accounts and phones with the same result). This worked with the pre-v1.0 release, then until last week even with the latest v1.0 release but now it's broken. I also checked for the initial report, before I went back to the virtual device, I build the demo with the latest v1.0 commit https://github.com/project-chip/connectedhomeip/tree/v1.0-branch (f6d47664f174adb08df3b7694029c6cd897ebc8c) |
|
@pierredelisle
Attach log. |
|
Same for me! Getting exactly the same error (also in the adb logcat) when trying to on-board a HUE bridge! |
|
Opps, the same issue after Google Home updated. |
|
Are you checking with Google on this issue? |
|
All, sorry for the delay. I'll be looking into this today and report back. |
@lpfsue
Correct, this has changed. The device is first commissioned to the local Android fabric, and then control is passed back to GHSAFM to commission into its own fabric. Now regarding the error: To verify independently that device sharing works fine, I'd suggest testing multi-admin with GHSAFM-TC (target commissioner version of GHSAFM) instead of GHA. |
|
Following your advice, I created and tested only one developer console project in my test account. But pairing still fails. Below is the issue path, log and video. After Google Nest hub 2th generation new firmware release on 12/13, Nethub 2th firmware was updated. And I checked the release notes on 12/15 and configured the environment for the Matter 1.0 test. But it doesn't pair with the thread module. My thread module is a Light bulb sample model. Issue step 1-1 Thread module Power on (nordic nrf52840 <- Supports Matter 1.0 (use to sdk 2.2.0) The above issue is 100% reproducible. My Developer Console reproduce video Google Nest hub 2th fw version issue log Please advise on this matter. |
|
hi.. I tried removing all the projects from the developer console and recreating just one project and it still doesn't pair. Prior to the Matter 1.0 update, it paired without problems. Please provide an exact solution for this problem |
|
Looking at the video provided, it appears that you are using the Google Home Application to commission. But with respect to this project (GHSAFM), are you able to reproduce with the sample app? |
|
I'm also having the same issue as others. I am unable to pair in Google Home successfully. I only have one project within the home developer console. I have other projects in GCP, but I'm assuming that wouldn't be the issue. I tested GHSAFM and multi-master with GHSAFM-TC, and that flow worked successfully. I tried multi-master provisioning in GHSAFM and sharing with GHA, but that failed, similar to pairing directly in GHA. |
|
The issues reported here are not directly related to the sample app, so I suggest to do the follow-up in the Google Nest Community > Smart Home Developer Forum. For example, this issue appears to be the same as the one reported here: |
|
@cw-20021349 I was finally able to pair with Google Home. You may want to try again now. |
|
@jahubba |
|
I wasn't pairing with thread, just wifi. I am using an esp32s3 board with a lighting-app example. I had been getting the same error during pairing, but it started working today. My Google home pairing looks a bit different, too, it has a light bulb during matter pairing now. |
|
@jahubba |
|
yes, I am on a pixel phone, (6) and the developer option is on. I did not see an OS upgrade. I'm not sure if my apps upgraded, but below are my versions: GHA 2.62.80.2 |
|
I also use pixel 6 and have the same app version as you Google's Matter 1.0 update is so confusing. |
|
@cw-20021349 sorry to hear that you're still encountering issues! Are you still seeing the following in your phone's logcat output? If so, could you please share details of how you are managing certificates for your build? As mentioned by Pierre above, the developer forums would be the best place to discuss this issue further as the scope of this issue is not specific to the Sample App. The issue of commissioning failure due to accounts in multiple projects mentioned here should be resolved at this time. For anyone that was able to commission simply by changing to an account that uses only one project, changing back to the original account should now be working. |
|
@aBozowski |
I have a custom matter device based on v1.0 (using 0xfff1 as vendor and 0x8000 as product, also registered as device in the dev console). Previously I was able to pair the device but since the update yesterday/this week the pairing fails with the following message on logcat:
When I compare this to my custom controller it will just go straight to adding the fabrics certificates after receving the DAC, PAI.
But the commissioning using the Google Play Service will just stop with the error on the phone before reaching that point on the device. And timeout and abort the pairing at some point.
The text was updated successfully, but these errors were encountered: