The Google Home Sample App for Matter (GHSA for Matter) uses the Home Mobile SDK to create an Android app that's similar to Google Home.

License: Apache License 2.0

Kotlin 99.24% Python 0.34% Shell 0.42%

sample-apps-for-matter-android's Introduction

Google Home Mobile SDK Sample Applications for Matter

The "Google Home Application (GHA)" is Google's flagship application for interacting with smart home devices that are part of the Google ecosystem.

Google also offers the Google Home Mobile SDK for developers interested in building their own Android applications to interact with smart home devices.

This repository features a suite of "Google Home Mobile SDK Sample Applications for Matter" that provide concrete examples of how to use the Google Home Mobile SDK.

These sample applications can be used as the starting point to build your smart home application for Matter devices. They can also be used as learning tools to better understand key Matter concepts, as well as tools to debug and troubleshoot interactions with Matter devices.

These sample applications have been developed to cater to the following use-case scenarios.

Third-Party Ecosystem (3p-ecosystem) If your organization supports its own ecosystem of smart devices, then the "3p-ecosystem" sample application is for you. It leverages the commissioning, device sharing, and discovery APIs offered in the Google Home Mobile SDK. Note that the sample application provides supports only for a demo fabric based on the Matter SDK. If you plan to make your application available in production, then you will have to deal with the complexity of managing in a secure fashion your own Matter fabric.

Note: This application used to be known as GHSAFM. It has been renamed GHSAFM-3p-ecosystem.

See 3p-ecosystem sample app.

Clone the repository

$ git clone https://github.com/google-home/sample-apps-for-matter-android.git

sample-apps-for-matter-android's People

Contributors

Stargazers

Watchers

sample-apps-for-matter-android's Issues

Google play services

Issue

What are the requirements for a device/emulator to run this app?
Does it need the latest beta version of google play services?
Or it’s because the hub has not been setup yet?

2022-09-18 03:52:28.035 21011-21011 HomeViewModel           com.google.homesampleapp.default     D  commissionDevice
2022-09-18 03:52:28.038 21011-21011 HomeFragment            com.google.homesampleapp.default     D  commissionDeviceStatus.observe: status [com.google.homesampleapp.TaskStatus$InProgress@3c21706]
2022-09-18 03:52:28.045 21011-21786 ConnectionStatusConfig  com.google.homesampleapp.default     W  Dynamic lookup for intent failed for action: com.google.android.gms.home.service.START
2022-09-18 03:52:28.050 21011-21786 GmsClient               com.google.homesampleapp.default     W  unable to connect to service: com.google.android.gms.home.service.START on com.google.android.gms
2022-09-18 03:06:13.662 16447-16447 HomeViewModel           com.google.homesampleapp.default     E  com.google.android.gms.common.api.ApiException: 17: API: CommissioningClient.API is not available on this device. Connection failed with: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}

Environment

Google Play Services: v 22.35.14 (190800-473845267)
Android: API 33, Android 13
Google Home and Google Play are installed.
Repository cloned with LFS initialized.

Cannot use sample app to install matter device running on ESP32

I've two Matter wifi devices running on ESP32 devkits (C3 and S3) and a Google Nest.

I can install and control both of them nicely using Google Home app.

But I cannot install them using the default sample app for matter, neither using the targetcommissioner variant.

Can you please let me know what to do ?
Where should I put a breakpoint to check whether the device is scanned by the app ?

No Discriminator extra when sharing the matter device.

Description: The 3rd app get no discriminator param in getIntent().getExtras() when sharing the matter device.

Reproduction steps
1, open this sample app (sample-app-for-matter-android), commission a matter device
2, open the device fragment, share it
3, choose 3rd app (3rd app has config ACTION_COMMISSION_DEVICE intent filter)
4, check getIntent().getExtras()

problem:
No Discriminator param

Expect：
Discriminator param is in getIntent().getExtras(), because 3rd app need it to scan ble of the Matter device and do commission.

[native] native crash

Reproduction steps

A test device(tv-app) was commissioned by GHSAFM
stay on the homepage for a while,then it may crash

Version(s)
latest

LOG
crash.txt

GHSAFM crashed with Fatal signal 6 (SIGABRT)

@pierredelisle The issue started when I switched from polling to device state change subscriptions.
I have noticed there is an issue with shutting subscriptions at the moment.

Utils.kt (line 291-293)

// We currently have issues with terminating subscriptions.
// Toggle this switch to test both behaviors.
const val UNSUBSCRIBE_ENABLED = false

Could this be related to the crash?🤔

The crash log(log_level = error) is shown below. I have also uploaded a larger log file showing all the debug logs leading to the **SIGABRT**

2023-02-28 16:19:23.106 22897-10318 DMG                     com.google.homesampleapp.default     E  Subscription Liveness timeout with SubscriptionID = 0x3de99ed0, Peer = 01:0000000000000003
---------------------------- PROCESS ENDED (22897) for package com.google.homesampleapp.default ----------------------------
2023-02-28 16:19:27.804 22897-10122 DL                      com.google.homesampleapp.default     E  Chip stack locking error at '../../src/transport/Session.h:187'. Code is unsafe/racy
2023-02-28 16:19:27.804 22897-10122 -                       com.google.homesampleapp.default     E  chipDie chipDie chipDie
2023-02-28 16:19:27.805 22897-10122 libc                    com.google.homesampleapp.default     A  Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 10122 (FinalizerDaemon), pid 22897 (mpleapp.default)
2023-02-28 16:19:27.844 10547-10547 DEBUG                   pid-10547                            A  pid: 22897, tid: 10122, name: FinalizerDaemon  >>> com.google.homesampleapp.default <<<
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #01 pc 0000000000830908  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chipAbort+12)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #02 pc 00000000016e4c68  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chipDie+56)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #03 pc 00000000016e4bf4  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chip::Platform::Internal::AssertChipStackLockedByCurrentThread(char const*, int)+100)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #04 pc 00000000016f8714  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chip::Transport::Session::RemoveHolder(chip::SessionHolder&)+40)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #05 pc 00000000016f80ac  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chip::SessionHolder::Release()+60)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #06 pc 00000000016f8048  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chip::SessionHolder::~SessionHolder()+40)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #07 pc 000000000084e064  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chip::app::ReadPrepareParams::~ReadPrepareParams()+36)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #08 pc 0000000001678d50  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chip::app::ReadClient::~ReadClient()+104)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #09 pc 000000000082c0e8  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (void chip::Platform::Delete<chip::app::ReadClient>(chip::app::ReadClient*)+44)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #10 pc 000000000082c08c  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chip::Controller::ReportCallback::~ReportCallback()+216)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #11 pc 000000000082c1bc  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (chip::Controller::ReportCallback::~ReportCallback()+32)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #12 pc 000000000082add0  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/base.apk (offset 0x100f000) (Java_chip_devicecontroller_ReportCallbackJni_deleteCallback+132)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #13 pc 0000000000049a34  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/oat/arm64/base.odex (art_jni_trampoline+132)
2023-02-28 16:19:27.920 10547-10547 DEBUG                   pid-10547                            A        #20 pc 0000000000400e0a  /data/app/~~IPRKzMBSc8cXgdyPJArmjQ==/com.google.homesampleapp.default-h93aTJRYcr2aBvZ-pKE1-A==/oat/arm64/base.vdex (chip.devicecontroller.ReportCallbackJni.finalize+22)

Steps to Reproduce

Commission color temperature light(ESP32 light example) to GHSAFM
Toggle between the HomeFragment and the DeviceFragmnet continuously

Complete Log

2023-02-28.GHSA.Crash.log

Fields in Basic Info cluster

In devices.proto you have vendorId and productId as strings, but they are Uints in Matter. Also, I find it more useful to display the name and vendor strings than the ids, so I changed it like this:

// VID / PID
uint32 vendorId = 2;
string vendorName =3;
uint32 productId = 4;
string productName = 5;

Over in ClusterHelpers readBasicClusterVendorIDAttribute() is not useful or used because the commissioning API returns the vendorId. So I deleted it and added readBasicClusterVendorNameAttribute() and readBasicClusterProductNameAttribute()

I have not checked this yet, but when you assign the device name in the Google Home dialog it should also write that name into the BasicInfo cluster using the NodeLabel Attribute, then the sample app can retrieve that string and use the same device name that the Home app is using.

NodeLabel Attribute
The NodeLabel attribute SHALL represent a user defined name for the Node. This attribute
SHOULD be set during initial commissioning and MAY be updated by further reconfigurations.

I also removed the endpoint parameter from these calls since it is only legal to have the Basic Info cluster on EP0.

the function of share device can not work

after share device, another commissioner can not to commission the shared device

another commissioner's full log
commission_error.txt

Unable to publish to Play Store - GmsCore module dependency minimum version declared in the AndroidManifest.xml file is invalid: -1

When trying to publish an app to the Play Store containing code based on this example it fails with the following message:

"message": "The GmsCore module dependency minimum version declared in the AndroidManifest.xml file is invalid: -1.",
"status": "PERMISSION_DENIED"

It appears to refer to this code:

https://github.com/google-home/sample-app-for-matter-android/blob/264c8404cac2b5d1e4195adb6cea4caf12c812bc/app/src/main/AndroidManifest.xml#L71-L79

Is the example incorrect or is using it restricted in some way? It appears to indicate to Play Services to download the Matter modules, which is useful to have in case the user doesn't have them installed (or doesn't want to re-install the Google Home app to trigger a download).

RootCA keypair

GSAFM create a new commissioner, and when it does that it has to create a new root key pair. Where is this key pair being stored?

Could the sample show a way to use Google Cloud to hold the root key pair remotely, and then provide intermediate CA pairs to the commissioner app?

Consider if the user deletes their app and then wants it back. The root key pair has been lost.

Commissioning with Matter virtual device Fail

Hi, I met problem after first time commissioning success with Matter virtual device using Sample app. I remove the device from Sample app, then I stop the Matter virtual device and run it again. After 1st time commissioning, it always fails. I try to rebuild the Matter virtual device or delete the items under chef/linux/out but no luck.

How could I make it commissionable again and anything notice required?

Below is the log.

matter@timyao-Predator-PH315-54:~/connectedhomeip/examples/chef$ ./linux/out/rootnode_dimmablelight_bCwGYSDpoe
DBG  [1675827624.207472][5539:5539] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
DBG  [1675827624.208037][5539:5539] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
ERR  [1675827624.208049][5539:5539] CHIP:DL: ChipLinuxStorage::Init: Attempt to re-initialize with KVS config file: /tmp/chip_kvs
DBG  [1675827624.208121][5539:5539] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
DBG  [1675827624.208149][5539:5539] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
DBG  [1675827624.208168][5539:5539] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
INF  [1675827624.208265][5539:5539] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-UsYcR1)
ERR  [1675827624.208390][5539:5539] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
INF  [1675827624.208399][5539:5539] CHIP:DL: NVS set: chip-counters/reboot-count = 9 (0x9)
INF  [1675827624.208566][5539:5539] CHIP:DL: Got Ethernet interface: enp44s0
INF  [1675827624.208652][5539:5539] CHIP:DL: Found the primary Ethernet interface:enp44s0
INF  [1675827624.208737][5539:5539] CHIP:DL: Got WiFi interface: wlp0s20f3
INF  [1675827624.208997][5539:5539] CHIP:DL: Found the primary WiFi interface:wlp0s20f3
ERR  [1675827624.209012][5539:5539] CHIP:SPT: *** WARNING: Using temporary passcode 20202021 due to no neither --passcode or --spake2p-v
ERR  [1675827624.209020][5539:5539] CHIP:SPT: *** WARNING: Using temporary test discriminator 3840 due to --discriminator not given on c
ERR  [1675827624.209027][5539:5539] CHIP:SPT: PASE PBKDF iterations set to 1000
INF  [1675827624.209034][5539:5539] CHIP:SPT: LinuxCommissionableDataProvider didn't get a PASE salt, generating one.
INF  [1675827624.209870][5539:5539] CHIP:DL: Device Configuration:
INF  [1675827624.209879][5539:5539] CHIP:DL:   Serial Number: TEST_SN
INF  [1675827624.209886][5539:5539] CHIP:DL:   Vendor Id: 65521 (0xFFF1)
INF  [1675827624.209893][5539:5539] CHIP:DL:   Product Id: 32768 (0x8000)
INF  [1675827624.209901][5539:5539] CHIP:DL:   Hardware Version: 0
INF  [1675827624.209905][5539:5539] CHIP:DL:   Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
INF  [1675827624.209911][5539:5539] CHIP:DL:   Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
INF  [1675827624.209918][5539:5539] CHIP:DL:   Manufacturing Date: (not set)
INF  [1675827624.209923][5539:5539] CHIP:DL:   Device Type: 65535 (0xFFFF)
INF  [1675827624.209928][5539:5539] CHIP:-: ==== Onboarding payload for Standard Commissioning Flow ====
INF  [1675827624.209950][5539:5539] CHIP:SVR: SetupQRCode: [MT:Y.K90AFN00KA0648G00]
INF  [1675827624.209957][5539:5539] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code:
INF  [1675827624.209963][5539:5539] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3AY.K90AFN00KA0648G00
INF  [1675827624.209972][5539:5539] CHIP:SVR: Manual pairing code: [34970112332]
INF  [1675827624.210017][5539:5539] CHIP:-: PW_RPC initialized.
INF  Starting pw_rpc server on port 33000
> INF  [1675827624.210050][5539:5539] CHIP:SVR: Server initializing...
DBG  [1675827624.210061][5539:5539] CHIP:FP: Initializing FabricTable from persistent storage
INF  [1675827624.210094][5539:5539] CHIP:TS: Last Known Good Time: 2023-02-08T03:23:31
INF  [1675827624.210209][5539:5539] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x7F8D2A00A0695E62, Fabric
INF  [1675827624.210285][5539:5539] CHIP:FP: Fabric index 0x2 was retrieved from storage. Compressed FabricId 0xE2983F7852F2DA80, Fabric
INF  [1675827624.210297][5539:5539] CHIP:DMG: AccessControl: initializing
INF  [1675827624.210301][5539:5539] CHIP:DMG: Examples::AccessControlDelegate::Init
INF  [1675827624.210310][5539:5539] CHIP:DMG: AccessControl: setting
INF  [1675827624.210314][5539:5539] CHIP:DMG: DefaultAclStorage: initializing
INF  [1675827624.210345][5539:5539] CHIP:DMG: AccessControl: validating f=1 p=a a=c s=1 t=0
INF  [1675827624.210349][5539:5539] CHIP:DMG:   validating subject 0xFFFFFFFD00010001
INF  [1675827624.210376][5539:5539] CHIP:DMG: AccessControl: validating f=2 p=a a=c s=1 t=0
INF  [1675827624.210380][5539:5539] CHIP:DMG:   validating subject 0x000000000001B669
INF  [1675827624.210389][5539:5539] CHIP:DMG: DefaultAclStorage: 2 entries loaded
DBG  [1675827624.210396][5539:5539] CHIP:IN: UDP::Init bind&listen port=5540
DBG  [1675827624.210414][5539:5539] CHIP:IN: UDP::Init bound to port=5540
DBG  [1675827624.210417][5539:5539] CHIP:IN: TransportMgr initialized
INF  [1675827624.210490][5539:5539] CHIP:DL: writing settings to file (/tmp/chip_kvs-rXHV90)
ERR  [1675827624.210587][5539:5539] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
INF  [1675827624.210618][5539:5539] CHIP:DL: writing settings to file (/tmp/chip_kvs-ccHLT2)
ERR  [1675827624.216298][5539:5539] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
INF  [1675827624.216513][5539:5539] CHIP:DL: writing settings to file (/tmp/chip_kvs-Yhk111)
ERR  [1675827624.216592][5539:5539] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
INF  [1675827624.216599][5539:5539] CHIP:ZCL: Using ZAP configuration...
DBG  [1675827624.216622][5539:5539] CHIP:DMG: Failed to read stored attribute (0, 0x0000_0028, 0x0000_0005: ../third_party/connectedhome
DBG  [1675827624.216637][5539:5539] CHIP:DMG: Failed to read stored attribute (0, 0x0000_0028, 0x0000_0010: ../third_party/connectedhome
DBG  [1675827624.216653][5539:5539] CHIP:DMG: Failed to read stored attribute (0, 0x0000_002C, 0x0000_0000: ../third_party/connectedhome
DBG  [1675827624.216666][5539:5539] CHIP:DMG: Failed to read stored attribute (0, 0x0000_002C, 0x0000_0001: ../third_party/connectedhome
INF  [1675827624.216686][5539:5539] CHIP:DMG: AccessControlCluster: initializing
DBG  [1675827624.216694][5539:5539] CHIP:DMG: Endpoint 0, Cluster 0x0000_0030 update version to 40bdf34b
DBG  [1675827624.216709][5539:5539] CHIP:ZCL: GeneralDiagnostics: OnDeviceReboot
DBG  [1675827624.216714][5539:5539] CHIP:DMG: Endpoint 0, Cluster 0x0000_0033 update version to c83b81a8
DBG  [1675827624.216730][5539:5539] CHIP:EVL: LogEvent event number: 0x0000000000080000 priority: 2, endpoint id:  0x0 cluster id: 0x000
INF  [1675827624.216739][5539:5539] CHIP:ZCL: Initiating Admin Commissioning cluster.
DBG  [1675827624.216744][5539:5539] CHIP:DMG: Endpoint 0, Cluster 0x0000_0004 update version to 800c3657
DBG  [1675827624.216747][5539:5539] CHIP:DMG: Endpoint 0, Cluster 0x0000_0004 update version to 800c3658
ERR  [1675827624.216752][5539:5539] CHIP:ZCL: Failed to read ActiveLocale with error: 0x86
DBG  [1675827624.216760][5539:5539] CHIP:DMG: Endpoint 1, Cluster 0x0000_0004 update version to eb3ca3c4
DBG  [1675827624.216765][5539:5539] CHIP:DMG: Endpoint 1, Cluster 0x0000_0004 update version to eb3ca3c5
DBG  [1675827624.216770][5539:5539] CHIP:DMG: Endpoint 1, Cluster 0x0000_0005 update version to 9b763012
INF  [1675827624.216779][5539:5539] CHIP:SVR: Fabric already commissioned. Disabling BLE advertisement
INF  [1675827624.216784][5539:5539] CHIP:DIS: Updating services using commissioning mode 0
INF  [1675827624.216959][5539:5539] CHIP:DIS: CHIP minimal mDNS started advertising.
DBG  [1675827624.217362][5539:5539] CHIP:DL: Using wifi MAC for hostname
INF  [1675827624.217368][5539:5539] CHIP:DIS: Advertise operational node 7F8D2A00A0695E62-DB65B20E832306FD
DBG  [1675827624.217672][5539:5539] CHIP:DIS: Responding with _matter._tcp.local
DBG  [1675827624.217677][5539:5539] CHIP:DIS: Responding with 7F8D2A00A0695E62-DB65B20E832306FD._matter._tcp.local
DBG  [1675827624.217683][5539:5539] CHIP:DIS: Responding with 7F8D2A00A0695E62-DB65B20E832306FD._matter._tcp.local
DBG  [1675827624.217686][5539:5539] CHIP:DIS: Responding with 089798EB67930000.local
DBG  [1675827624.217690][5539:5539] CHIP:DIS: Responding with 089798EB67930000.local
DBG  [1675827624.217694][5539:5539] CHIP:DIS: Responding with _I7F8D2A00A0695E62._sub._matter._tcp.local
INF  [1675827624.217697][5539:5539] CHIP:DIS: CHIP minimal mDNS configured as 'Operational device'; instance name: 7F8D2A00A0695E62-DB65
INF  [1675827624.218408][5539:5539] CHIP:DIS: mDNS service published: _matter._tcp
DBG  [1675827624.218485][5539:5539] CHIP:DL: Using wifi MAC for hostname
INF  [1675827624.218491][5539:5539] CHIP:DIS: Advertise operational node E2983F7852F2DA80-0000000000000001
DBG  [1675827624.219165][5539:5539] CHIP:DIS: Responding with _matter._tcp.local
DBG  [1675827624.219171][5539:5539] CHIP:DIS: Responding with E2983F7852F2DA80-0000000000000001._matter._tcp.local
DBG  [1675827624.219177][5539:5539] CHIP:DIS: Responding with E2983F7852F2DA80-0000000000000001._matter._tcp.local
DBG  [1675827624.219181][5539:5539] CHIP:DIS: Responding with 089798EB67930000.local
DBG  [1675827624.219184][5539:5539] CHIP:DIS: Responding with 089798EB67930000.local
DBG  [1675827624.219189][5539:5539] CHIP:DIS: Responding with _IE2983F7852F2DA80._sub._matter._tcp.local
INF  [1675827624.219192][5539:5539] CHIP:DIS: CHIP minimal mDNS configured as 'Operational device'; instance name: E2983F7852F2DA80-0000
INF  [1675827624.220208][5539:5539] CHIP:DIS: mDNS service published: _matter._tcp
INF  [1675827624.220225][5539:5539] CHIP:IN: CASE Server enabling CASE session setups
DBG  [1675827624.220237][5539:5539] CHIP:IN: SecureSession[0x55ac7a003300]: Allocated Type:2 LSID:58211
DBG  [1675827624.220244][5539:5539] CHIP:SC: Allocated SecureSession (0x55ac7a003300) - waiting for Sigma1 msg
INF  [1675827624.220248][5539:5539] CHIP:SVR: Joining Multicast groups
DBG  [1675827624.220293][5539:5539] CHIP:ZCL: Emitting StartUp event
DBG  [1675827624.220303][5539:5539] CHIP:EVL: LogEvent event number: 0x0000000000080001 priority: 2, endpoint id:  0x0 cluster id: 0x000
INF  [1675827624.220308][5539:5539] CHIP:SVR: Server Listening...
INF  [1675827624.220311][5539:5539] CHIP:DL: Device Configuration:
INF  [1675827624.220318][5539:5539] CHIP:DL:   Serial Number: TEST_SN
INF  [1675827624.220327][5539:5539] CHIP:DL:   Vendor Id: 65521 (0xFFF1)
INF  [1675827624.220334][5539:5539] CHIP:DL:   Product Id: 32768 (0x8000)
INF  [1675827624.220341][5539:5539] CHIP:DL:   Hardware Version: 0
INF  [1675827624.220345][5539:5539] CHIP:DL:   Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
INF  [1675827624.220348][5539:5539] CHIP:DL:   Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
INF  [1675827624.220353][5539:5539] CHIP:DL:   Manufacturing Date: (not set)
INF  [1675827624.220356][5539:5539] CHIP:DL:   Device Type: 65535 (0xFFFF)
INF  [1675827624.220362][5539:5539] CHIP:SVR: SetupQRCode: [MT:Y.K90AFN00KA0648G00]
INF  [1675827624.220365][5539:5539] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code:
INF  [1675827624.220368][5539:5539] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3AY.K90AFN00KA0648G00
INF  [1675827624.220373][5539:5539] CHIP:SVR: Manual pairing code: [34970112332]
DBG  [1675827624.723419][5539:5539] CHIP:DIS: SRV record already actively processed.
DBG  [1675827624.723642][5539:5539] CHIP:DIS: SRV record already actively processed.
DBG  [1675827624.723915][5539:5539] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827624.724053][5539:5539] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827624.724072][5539:5539] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.
DBG  [1675827624.724650][5539:5539] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827624.724735][5539:5539] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827624.724756][5539:5539] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.
DBG  [1675827624.724897][5539:5539] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827624.724969][5539:5539] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827624.724989][5539:5539] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.
DBG  [1675827628.610975][5539:5539] CHIP:DIS: SRV record already actively processed.
DBG  [1675827628.611157][5539:5539] CHIP:DIS: SRV record already actively processed.
DBG  [1675827628.611368][5539:5539] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827628.611477][5539:5539] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827628.611495][5539:5539] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.

matter@timyao-Predator-PH315-54:~/connectedhomeip/examples/chef$ ./linux/out/rootnode_dimmablelight_bCwGYSDpoe > log.txt
INF  [1675827652.931748][5545:5545] CHIP:SVR: Server initializing...
INF  Starting pw_rpc server on port 33000
DBG  [1675827652.931766][5545:5545] CHIP:FP: Initializing FabricTable from persistent storage
INF  [1675827652.931798][5545:5545] CHIP:TS: Last Known Good Time: 2023-02-08T03:23:31
INF  [1675827652.931920][5545:5545] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x7F8D2A00A0695E62, Fabric
INF  [1675827652.932019][5545:5545] CHIP:FP: Fabric index 0x2 was retrieved from storage. Compressed FabricId 0xE2983F7852F2DA80, Fabric
INF  [1675827652.932030][5545:5545] CHIP:DMG: AccessControl: initializing
INF  [1675827652.932041][5545:5545] CHIP:DMG: Examples::AccessControlDelegate::Init
INF  [1675827652.932047][5545:5545] CHIP:DMG: AccessControl: setting
INF  [1675827652.932050][5545:5545] CHIP:DMG: DefaultAclStorage: initializing
INF  [1675827652.932085][5545:5545] CHIP:DMG: AccessControl: validating f=1 p=a a=c s=1 t=0
INF  [1675827652.932089][5545:5545] CHIP:DMG:   validating subject 0xFFFFFFFD00010001
INF  [1675827652.932124][5545:5545] CHIP:DMG: AccessControl: validating f=2 p=a a=c s=1 t=0
INF  [1675827652.932132][5545:5545] CHIP:DMG:   validating subject 0x000000000001B669
INF  [1675827652.932142][5545:5545] CHIP:DMG: DefaultAclStorage: 2 entries loaded
DBG  [1675827652.932146][5545:5545] CHIP:IN: UDP::Init bind&listen port=5540
DBG  [1675827652.932169][5545:5545] CHIP:IN: UDP::Init bound to port=5540
DBG  [1675827652.932173][5545:5545] CHIP:IN: TransportMgr initialized
INF  [1675827652.932255][5545:5545] CHIP:DL: writing settings to file (/tmp/chip_kvs-Yh13Fs)
ERR  [1675827652.932345][5545:5545] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
INF  [1675827652.932375][5545:5545] CHIP:DL: writing settings to file (/tmp/chip_kvs-GS7lvw)
ERR  [1675827652.937619][5545:5545] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
INF  [1675827652.937843][5545:5545] CHIP:DL: writing settings to file (/tmp/chip_kvs-kB36Gu)
ERR  [1675827652.937944][5545:5545] CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
INF  [1675827652.937951][5545:5545] CHIP:ZCL: Using ZAP configuration...
DBG  [1675827652.937973][5545:5545] CHIP:DMG: Failed to read stored attribute (0, 0x0000_0028, 0x0000_0005: ../third_party/connectedhome
DBG  [1675827652.937984][5545:5545] CHIP:DMG: Failed to read stored attribute (0, 0x0000_0028, 0x0000_0010: ../third_party/connectedhome
DBG  [1675827652.937995][5545:5545] CHIP:DMG: Failed to read stored attribute (0, 0x0000_002C, 0x0000_0000: ../third_party/connectedhome
DBG  [1675827652.938003][5545:5545] CHIP:DMG: Failed to read stored attribute (0, 0x0000_002C, 0x0000_0001: ../third_party/connectedhome
INF  [1675827652.938035][5545:5545] CHIP:DMG: AccessControlCluster: initializing
DBG  [1675827652.938048][5545:5545] CHIP:DMG: Endpoint 0, Cluster 0x0000_0030 update version to 12a3098a
DBG  [1675827652.938058][5545:5545] CHIP:ZCL: GeneralDiagnostics: OnDeviceReboot
DBG  [1675827652.938061][5545:5545] CHIP:DMG: Endpoint 0, Cluster 0x0000_0033 update version to cb0f29a9
DBG  [1675827652.938073][5545:5545] CHIP:EVL: LogEvent event number: 0x0000000000090000 priority: 2, endpoint id:  0x0 cluster id: 0x000
INF  [1675827652.938079][5545:5545] CHIP:ZCL: Initiating Admin Commissioning cluster.
DBG  [1675827652.938083][5545:5545] CHIP:DMG: Endpoint 0, Cluster 0x0000_0004 update version to df1beeba
DBG  [1675827652.938086][5545:5545] CHIP:DMG: Endpoint 0, Cluster 0x0000_0004 update version to df1beebb
ERR  [1675827652.938090][5545:5545] CHIP:ZCL: Failed to read ActiveLocale with error: 0x86
DBG  [1675827652.938097][5545:5545] CHIP:DMG: Endpoint 1, Cluster 0x0000_0004 update version to 4b0e3c5e
DBG  [1675827652.938100][5545:5545] CHIP:DMG: Endpoint 1, Cluster 0x0000_0004 update version to 4b0e3c5f
DBG  [1675827652.938103][5545:5545] CHIP:DMG: Endpoint 1, Cluster 0x0000_0005 update version to 9e658433
INF  [1675827652.938108][5545:5545] CHIP:SVR: Fabric already commissioned. Disabling BLE advertisement
INF  [1675827652.938111][5545:5545] CHIP:DIS: Updating services using commissioning mode 0
INF  [1675827652.938314][5545:5545] CHIP:DIS: CHIP minimal mDNS started advertising.
DBG  [1675827652.938714][5545:5545] CHIP:DL: Using wifi MAC for hostname
INF  [1675827652.938720][5545:5545] CHIP:DIS: Advertise operational node 7F8D2A00A0695E62-DB65B20E832306FD
DBG  [1675827652.939020][5545:5545] CHIP:DIS: Responding with _matter._tcp.local
DBG  [1675827652.939025][5545:5545] CHIP:DIS: Responding with 7F8D2A00A0695E62-DB65B20E832306FD._matter._tcp.local
DBG  [1675827652.939031][5545:5545] CHIP:DIS: Responding with 7F8D2A00A0695E62-DB65B20E832306FD._matter._tcp.local
DBG  [1675827652.939035][5545:5545] CHIP:DIS: Responding with 089798EB67930000.local
DBG  [1675827652.939040][5545:5545] CHIP:DIS: Responding with 089798EB67930000.local
DBG  [1675827652.939046][5545:5545] CHIP:DIS: Responding with _I7F8D2A00A0695E62._sub._matter._tcp.local
INF  [1675827652.939050][5545:5545] CHIP:DIS: CHIP minimal mDNS configured as 'Operational device'; instance name: 7F8D2A00A0695E62-DB65
INF  [1675827652.939699][5545:5545] CHIP:DIS: mDNS service published: _matter._tcp
DBG  [1675827652.939774][5545:5545] CHIP:DL: Using wifi MAC for hostname
INF  [1675827652.939778][5545:5545] CHIP:DIS: Advertise operational node E2983F7852F2DA80-0000000000000001
DBG  [1675827652.940402][5545:5545] CHIP:DIS: Responding with _matter._tcp.local
DBG  [1675827652.940409][5545:5545] CHIP:DIS: Responding with E2983F7852F2DA80-0000000000000001._matter._tcp.local
DBG  [1675827652.940413][5545:5545] CHIP:DIS: Responding with E2983F7852F2DA80-0000000000000001._matter._tcp.local
DBG  [1675827652.940416][5545:5545] CHIP:DIS: Responding with 089798EB67930000.local
DBG  [1675827652.940418][5545:5545] CHIP:DIS: Responding with 089798EB67930000.local
DBG  [1675827652.940422][5545:5545] CHIP:DIS: Responding with _IE2983F7852F2DA80._sub._matter._tcp.local
INF  [1675827652.940424][5545:5545] CHIP:DIS: CHIP minimal mDNS configured as 'Operational device'; instance name: E2983F7852F2DA80-0000
INF  [1675827652.941363][5545:5545] CHIP:DIS: mDNS service published: _matter._tcp
INF  [1675827652.941372][5545:5545] CHIP:IN: CASE Server enabling CASE session setups
DBG  [1675827652.941384][5545:5545] CHIP:IN: SecureSession[0x55f67817f800]: Allocated Type:2 LSID:63347
DBG  [1675827652.941390][5545:5545] CHIP:SC: Allocated SecureSession (0x55f67817f800) - waiting for Sigma1 msg
INF  [1675827652.941395][5545:5545] CHIP:SVR: Joining Multicast groups
DBG  [1675827652.941434][5545:5545] CHIP:ZCL: Emitting StartUp event
DBG  [1675827652.941444][5545:5545] CHIP:EVL: LogEvent event number: 0x0000000000090001 priority: 2, endpoint id:  0x0 cluster id: 0x000
INF  [1675827652.941449][5545:5545] CHIP:SVR: Server Listening...
INF  [1675827652.941452][5545:5545] CHIP:DL: Device Configuration:
INF  [1675827652.941459][5545:5545] CHIP:DL:   Serial Number: TEST_SN
INF  [1675827652.941469][5545:5545] CHIP:DL:   Vendor Id: 65521 (0xFFF1)
INF  [1675827652.941476][5545:5545] CHIP:DL:   Product Id: 32768 (0x8000)
INF  [1675827652.941481][5545:5545] CHIP:DL:   Hardware Version: 0
INF  [1675827652.941483][5545:5545] CHIP:DL:   Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
INF  [1675827652.941486][5545:5545] CHIP:DL:   Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
INF  [1675827652.941491][5545:5545] CHIP:DL:   Manufacturing Date: (not set)
INF  [1675827652.941495][5545:5545] CHIP:DL:   Device Type: 65535 (0xFFFF)
INF  [1675827652.941502][5545:5545] CHIP:SVR: SetupQRCode: [MT:Y.K90AFN00KA0648G00]
INF  [1675827652.941508][5545:5545] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code:
INF  [1675827652.941511][5545:5545] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3AY.K90AFN00KA0648G00
INF  [1675827652.941516][5545:5545] CHIP:SVR: Manual pairing code: [34970112332]
DBG  [1675827682.884317][5545:5545] CHIP:DIS: SRV record already actively processed.
DBG  [1675827682.884500][5545:5545] CHIP:DIS: SRV record already actively processed.
DBG  [1675827682.884719][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827682.884848][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827682.884873][5545:5545] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.
DBG  [1675827683.804839][5545:5545] CHIP:DIS: SRV record already actively processed.
DBG  [1675827683.805008][5545:5545] CHIP:DIS: SRV record already actively processed.
DBG  [1675827683.805217][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827683.805321][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827683.805335][5545:5545] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.
DBG  [1675827685.035119][5545:5545] CHIP:DIS: SRV record already actively processed.
DBG  [1675827685.035283][5545:5545] CHIP:DIS: SRV record already actively processed.
DBG  [1675827685.035467][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827685.035604][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827685.035621][5545:5545] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.
DBG  [1675827685.036117][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827685.036192][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827685.036212][5545:5545] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.
DBG  [1675827685.036335][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827685.036406][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827685.036426][5545:5545] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures.
DBG  [1675827689.130476][5545:5545] CHIP:DIS: SRV record already actively processed.
DBG  [1675827689.130632][5545:5545] CHIP:DIS: SRV record already actively processed.
DBG  [1675827689.130805][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp44s0:  ../third_party/connectedhomeip/src/
DBG  [1675827689.130926][5545:5545] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../third_party/connectedhomeip/src/
DBG  [1675827689.130947][5545:5545] CHIP:DIS: mDNS broadcast had only partial success: 1 successes and 2 failures

Vendor ID for commissioner

I believe you are supposed to be able to pass a vendor ID into ChipDeviceController(). I don't see a way to set my vendor ID into the library so that it will make a fabric specific to that ID.

question about commission environment

Hi All
I have a question
I tried to set a commission with Pixel & Google Nest 2gen & SiliconLabs(BRD4161A)
but commissioning is failed.
I captured the failed log attaching the file
Can I get the advice for solving this problem??

HomeConnectionLog.txt

Commissioning with "Matter Virtual Device"

In Build a Matter virtual device Colab, it teaches us how to make a Matter virtual device. In step 6. Commission the device, it says a hub is required to commission your device on the Matter fabric.
In Build an Android App for Matter Colab, it teaches us how to make an Android App that works with a virtual device or an ESP32. In the welcome page, it says "You don't need a hub, for example a Google Nest Hub (2nd Generation), to commission and control devices with the sample app."

When I connect to the Matter virtual device using the Google Home app, the screenshot shows "You need a hub to control with Google." and "Can't find device." I test the commissioning using GHSAFM, and no luck "Can't find device." too.

Is a Google Nest hub Gen 2 required for commissioning the virtual device?

Matter virtual device environment: Windows 11 Subsystem for Linux, run Docker.
Android device: Sony Xperia 1; OS: Android 11; Google Play services version: 23.03.13 (150400-503260631); Google Home app shows Matter related text and detect the Matter device.

Using Plus button to add device throws an error

I've built the "default" flavor of this Sample app, and now I'd like to add a real Matter device (e.g. ESP32) using the + button on the bottom right of Home page.
But when I click on the button, nothing happens, and I see the following error logs:

2022-11-28 17:56:49.445 14569-14869/com.google.homesampleapp.default W/ConnectionStatusConfig: Dynamic lookup for intent failed for action: com.google.android.gms.home.service.START
2022-11-28 17:56:49.448 14569-14869/com.google.homesampleapp.default W/GmsClient: unable to connect to service: com.google.android.gms.home.service.START on com.google.android.gms
2022-11-28 17:56:49.463 14569-14569/com.google.homesampleapp.default E/GHSAFM-HomeViewModel: com.google.android.gms.common.api.ApiException: 17: API: CommissioningClient.API is not available on this device. Connection failed with: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
        at com.google.android.gms.common.internal.ApiExceptionUtil.fromStatus(com.google.android.gms:play-services-base@@18.1.0:3)
        at com.google.android.gms.common.api.internal.ApiExceptionMapper.getException(com.google.android.gms:play-services-base@@18.1.0:1)
        at com.google.android.gms.common.api.internal.zag.zad(com.google.android.gms:play-services-base@@18.1.0:1)
        at com.google.android.gms.common.api.internal.zabq.zaE(com.google.android.gms:play-services-base@@18.1.0:7)
        at com.google.android.gms.common.api.internal.zabq.zaD(com.google.android.gms:play-services-base@@18.1.0:2)
        at com.google.android.gms.common.api.internal.zabq.zar(com.google.android.gms:play-services-base@@18.1.0:24)
        at com.google.android.gms.common.api.internal.zabt.run(com.google.android.gms:play-services-base@@18.1.0:12)
        at android.os.Handler.handleCallback(Handler.java:942)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loopOnce(Looper.java:201)
        at android.os.Looper.loop(Looper.java:288)
        at android.os.HandlerThread.run(HandlerThread.java:67)

This error occurs both on my Pixel 4a on Android 13 and my Android 12 smartphone.

Can you please help ?

Uploading CHIP Maven artifacts

I am trying to figure how to do this, but I am not succeeding.

https://stackoverflow.com/questions/75400578/uploading-android-native-artifacts-to-maven

Matter has released 1.0.0.2 version

The Android library probably should be updated to this release.
https://github.com/project-chip/connectedhomeip/releases/tag/v1.0.0.2

Any API to provide custom root certificate authority (RootCA) ?

Is there any way to provide custom root CA for custom fabric ?

Commissioning API needs to return FabricId

The commissioning API does not return the FabricId (or I can't find it) for the newly commissioned device. This needs to saved with the device ID because later you have to have FabricId in order to be able to set the ACL. FabricId can vary by the device since it is a function of how many times the device has been commissioned.

I am trying to work around this by reading the ACL list back out of the device and searching it for my commissioning ACL entry which contains the FabricId.

build.gradle plugin classpath is specified twice

        classpath "com.google.dagger:hilt-android-gradle-plugin:2.38.1"
        classpath 'com.google.protobuf:protobuf-java:3.4.0'
        classpath 'com.google.dagger:hilt-android-gradle-plugin:2.41'

This triggers weird compile errors after a gradle upgrade.

Error when commissioning and communicating with the app (Failed to parse IP address)

I'm trying to perform the commissioning process through this sample app, but it stays at the "Connecting with Matter device" during some long time and ends with a message that says something like "We have problems communicating with GHSAFM" and in the sample app there wasn't any device.

Investigating, I found that the app crashes with the following stacktrace:

2022-09-27 00:22:10.656 28832-28832/com.google.homesampleapp.default E/CTL: Failed to parse IP address.
2022-09-27 00:22:10.684 28832-28832/com.google.homesampleapp.default E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.google.homesampleapp.default, PID: 28832
    chip.devicecontroller.ChipDeviceControllerException: ../../src/controller/java/CHIPDeviceController-JNI.cpp:328: CHIP Error 0x0000002F: Invalid argument
        at chip.devicecontroller.ChipDeviceController.establishPaseConnectionByAddress(Native Method)
        at chip.devicecontroller.ChipDeviceController.establishPaseConnection(ChipDeviceController.java:135)
        at com.google.homesampleapp.chip.ChipClient.awaitEstablishPaseConnection(ChipClient.kt:113)
        at com.google.homesampleapp.commissioning.AppCommissioningService$onCommissioningRequested$1.invokeSuspend(AppCommissioningService.kt:93)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loopOnce(Looper.java:226)
        at android.os.Looper.loop(Looper.java:313)
        at android.app.ActivityThread.main(ActivityThread.java:8751)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

As I saw that it had a problem with parsing the IP address, I debugged the app to obtain the values at com.google.homesampleapp.chip.ChipClient.awaitEstablishPaseConnection(ChipClient.kt:113):

deviceId = 15
ipAddress = "fe80::1252:1cff:fe62:b430%wlan0"
port = 5540
setupPinC0de = 71410408

Full Logcat

Although this problem, the device seems to be at the Google Home App, but I cannot toggle the light of the device (It pops a Toast notification saying that there was an error).

Unable to comission TE9 all clusters app

Issue

When I try to commission an ESP32C3 running the TE9 all-clusters app (as suggested here), commissioning fails with the error message

Connectivity problem We're having trouble communicating with Google

I have run through the verification steps https://developers.home.google.com/matter/verify-services and all are ok

Environment

Phone: Pixel 6
Android: 13
Google Play Services: 22.30.17
Settings -> Google -> Devices & sharing -> Matter devices & services is listed
Sample App: 1.0.1 release apk

Sample app can't commission Tapo P125M

I'm just getting started working with matter and matter devices. I was given a Tapo P125M (one of the only released Matter devices on the market) to see what sort of POC i could create. I found the sample app and figured if it could commission this device then i had a great starting point. The Tapo device has no problem being added to google home and pops up as a matter device found on my pixel 7 as soon as it enters pairing mode.

Environment:
GHSAFM Version: 1.3.0-default
Device FW: Tapo P125M latest FW as of 2/22/2023
Pixel 7 Android version 13 Build Number TQ1A.230205.002

Clean Slate: Yes
I reset the cache and app data before doing the commissioning
Device was factory reset also and not commissioned to any other matter controllers or devices (Nest Hub, Alexa, Homekit)

Device Logs
logs.txt

I looked into the logs, i 'm not 100% sure what i'm looking at but it looks like the error is in this location

02-22 10:26:59.195 11018 11200 D CTL : Successfully finished commissioning step 'SendAttestationRequest'
02-22 10:26:59.195 11018 11200 D CTL : AutoCommissioner setting attestationElements buffer size 278/278
02-22 10:26:59.195 11018 11200 D CTL : Commissioning stage next step: 'SendAttestationRequest' -> 'AttestationVerification'
02-22 10:26:59.195 11018 11200 D CTL : Performing next commissioning step 'AttestationVerification'
02-22 10:26:59.195 11018 11200 D CTL : Verifying attestation
02-22 10:26:59.225 11018 11200 E CTL : Failed in verifying 'Attestation Information' command received from the device: err 101. Look at AttestationVerificationResult enum to understand the errors
02-22 10:26:59.226 11018 11200 D GHSAFM-BaseCompletionListener: onCommissioningStatusUpdate nodeId [1] stage [AttestationVerification] errorCode [172]
02-22 10:26:59.226 11018 11200 D CTL : Error on commissioning step 'AttestationVerification': '../../src/controller/CHIPDeviceController.cpp:1031: CHIP Error 0x000000AC: Internal error'
02-22 10:26:59.226 11018 11200 E CTL : Failed to perform commissioning step 8
02-22 10:26:59.226 11018 11200 D CTL : Going from commissioning step 'AttestationVerification' with lastErr = '../../src/controller/CHIPDeviceController.cpp:1031: CHIP Error 0x000000AC: Internal error' -> 'Cleanup'
02-22 10:26:59.226 11018 11200 D CTL : Performing next commissioning step 'Cleanup' with completion status = '../../src/controller/CHIPDeviceController.cpp:1031: CHIP Error 0x000000AC: Internal error'
02-22 10:26:59.226 11018 11200 D CTL : Expiring failsafe on proxy 0xb4000074c23192c8
02-22 10:26:59.226 11018 11200 D DMG : ICR moving to [AddingComm]
02-22 10:26:59.226 11018 11200 D DMG : ICR moving to [AddedComma]
02-22 10:26:59.227 11018 11200 D EM : <<< [E:8354i M:255348771] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
02-22 10:26:59.227 11018 11200 D IN : (S) Sending msg 255348771 on secure session with LSID: 32953
02-22 10:26:59.227 11018 11200 D DMG : ICR moving to [CommandSen]
02-22 10:26:59.227 11018 11200 D DMG : ICR moving to [AwaitingDe]
02-22 10:26:59.227 11018 11200 D EM : <<< [E:8353i M:255348772 (Ack:5745903)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
02-22 10:26:59.228 11018 11200 D IN : (S) Sending msg 255348772 on secure session with LSID: 32953
02-22 10:26:59.228 11018 11200 D EM : Flushed pending ack for MessageCounter:5745903 on exchange 8353i
02-22 10:26:59.240 11018 11200 D EM : >>> [E:8354i M:5745904 (Ack:255348771)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
02-22 10:26:59.240 11018 11200 D EM : Found matching exchange: 8354i, Delegate: 0xb40000759c7a3418
02-22 10:26:59.240 11018 11200 D EM : Rxd Ack; Removing MessageCounter:255348771 from Retrans Table on exchange 8354i
02-22 10:26:59.240 11018 11200 D DMG : ICR moving to [ResponseRe]
02-22 10:26:59.240 11018 11200 D DMG : InvokeResponseMessage =
02-22 10:26:59.240 11018 11200 D DMG : {
02-22 10:26:59.240 11018 11200 D DMG : suppressResponse = false,
02-22 10:26:59.240 11018 11200 D DMG : InvokeResponseIBs =
02-22 10:26:59.240 11018 11200 D DMG : [
02-22 10:26:59.240 11018 11200 D DMG : InvokeResponseIB =
02-22 10:26:59.240 11018 11200 D DMG : {
02-22 10:26:59.240 11018 11200 D DMG : CommandDataIB =
02-22 10:26:59.240 11018 11200 D DMG : {
02-22 10:26:59.240 11018 11200 D DMG : CommandPathIB =
02-22 10:26:59.240 11018 11200 D DMG : {
02-22 10:26:59.240 11018 11200 D DMG : EndpointId = 0x0,
02-22 10:26:59.240 11018 11200 D DMG : ClusterId = 0x30,
02-22 10:26:59.240 11018 11200 D DMG : CommandId = 0x1,
02-22 10:26:59.240 11018 11200 D DMG : },
02-22 10:26:59.240 11018 11200 D DMG :
02-22 10:26:59.240 11018 11200 D DMG : CommandFields =
02-22 10:26:59.240 11018 11200 D DMG : {
02-22 10:26:59.240 11018 11200 D DMG : 0x0 = 0,
02-22 10:26:59.240 11018 11200 D DMG : 0x1 = "" (0 chars),
02-22 10:26:59.240 11018 11200 D DMG : },
02-22 10:26:59.240 11018 11200 D DMG : },
02-22 10:26:59.240 11018 11200 D DMG :
02-22 10:26:59.240 11018 11200 D DMG : },
02-22 10:26:59.240 11018 11200 D DMG :
02-22 10:26:59.240 11018 11200 D DMG : ],
02-22 10:26:59.240 11018 11200 D DMG :
02-22 10:26:59.240 11018 11200 D DMG : InteractionModelRevision = 1
02-22 10:26:59.240 11018 11200 D DMG : },
02-22 10:26:59.241 11018 11200 D DMG : Received Command Response Data, Endpoint=0 Cluster=0x0000_0030 Command=0x0000_0001
02-22 10:26:59.241 11018 11200 D CTL : Failsafe disarmed
02-22 10:26:59.241 11018 11200 D GHSAFM-BaseCompletionListener: onCommissioningStatusUpdate nodeId [1] stage [Cleanup] errorCode [0]
02-22 10:26:59.241 11018 11200 D CTL : Successfully finished commissioning step 'Cleanup'
02-22 10:26:59.241 11018 11200 D GHSAFM-BaseCompletionListener: BaseCompletionListener onCommissioningComplete(): nodeId [1] errorCode [172]
02-22 10:26:59.242 11018 11200 D IN : SecureSession[0xb40000767c7e4ec0]: MarkForEviction Type:1 LSID:32953
02-22 10:26:59.242 11018 11200 D SC : SecureSession[0xb40000767c7e4ec0]: Moving from state 'kActive' --> 'kPendingEviction'
02-22 10:26:59.242 11018 11200 E EM : Failed to send Solitary ack for MessageCounter:5745904 on exchange 8354i:2
02-22 10:26:59.242 11018 11200 D DMG : ICR moving to [AwaitingDe]
02-22 10:26:59.242 11018 11200 D IN : SecureSession[0xb40000767c7e4ec0]: Released - Type:1 LSID:32953
02-22 10:26:59.243 11018 11018 E GHSAFM-AppCommissioningService$onCommissioningRequested: onCommissioningRequested() failed
02-22 10:26:59.243 11018 11018 E GHSAFM-AppCommissioningService$onCommissioningRequested: java.lang.IllegalStateException: Commissioning failed with error code [172]
02-22 10:26:59.243 11018 11018 E GHSAFM-AppCommissioningService$onCommissioningRequested: at com.google.homesampleapp.chip.ChipClient$awaitCommissionDevice$2$1.onCommissioningComplete(ChipClient.kt:162)
02-22 10:26:59.243 11018 11018 E GHSAFM-AppCommissioningService$onCommissioningRequested: at chip.devicecontroller.ChipDeviceController.onCommissioningComplete(ChipDeviceController.java:285)
02-22 10:26:59.245 10172 10746 I CommissioningServiceBin: Received commissioning error 1000 from bound service. [CONTEXT service_id=336 ]
02-22 10:26:59.246 11018 11018 D GHSAFM-AppCommissioningService$onCommissioningRequested: Commissioning: commissioningServiceDelegate.sendCommissioningError() succeeded

Notes and Questions:
This device has no problem connecting through the Google Home App, using the add device flow and selecting a Matter device and scanning the QR code. It does give me the warning that i need a hub to communicate to this device. (I've ordered a Nest Hub 2).

My questions are do i need the Nest Hub to be able to commission this device? Should the sample app be able to commission this device?

Any Help or pointers would be appreciated. Still very new to matter.

Connectivity problem when commissioning

I can't perform commissioning process to connect an esp32 light example from the esp-matter repo although that with other tools, such as HomeAssistant or Chip-tool, I'm able to perform the process and interact with the device.
I can start the commissioning process, and watching the logs from the esp32, the phone and the esp32 seems to be communicating with each other, but at the end, at the phone I get "Connectivity problem. We're having trouble communicating with Google." message and there is no added device after all.

I already send a report through the feedback option from the three dots menu over the error explaining exactly the same.

GHSAFM app not working

I installed GHSAFM-1.2.2-default-debug.apk on my phone.
The information on my phone is as follows.

Samsung SM-G970N (Android 12)
After installing the app, when I click the "+" button to add a device, the following error occurs.

com.google.android.gms.common.api.ApiException: 17: API: CommissioningClient.API is not available on this device. Connection failed with: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
at com.google.android.gms.common.internal.ApiExceptionUtil.fromStatus(com.google.android.gms:play-services-base@@18.1.0:3)
at com.google.android.gms.common.api.internal.ApiExceptionMapper.getException(com.google.android.gms:play-services-base@@18.1.0:1)
at com.google.android.gms.common.api.internal.zag.zad(com.google.android.gms:play-services-base@@18.1.0:1)
at com.google.android.gms.common.api.internal.zabq.zaE(com.google.android.gms:play-services-base@@18.1.0:7)
at com.google.android.gms.common.api.internal.zabq.zaD(com.google.android.gms:play-services-base@@18.1.0:2)
at com.google.android.gms.common.api.internal.zabq.zar(com.google.android.gms:play-services-base@@18.1.0:24)
at com.google.android.gms.common.api.internal.zabt.run(com.google.android.gms:play-services-base@@18.1.0:12)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.os.HandlerThread.run(HandlerThread.java:67)

Implementing commissioning in custom app

I'm trying to implement the commissioning mecanism in a custom app written in Java.

Here is my version of commissionDevice() in Java:

public void commissionDevice() {

        CommissioningRequest commissionDeviceRequest = CommissioningRequest.builder()
                .setCommissioningService(new ComponentName(this, AppCommissioningService.class.getName()))
                .build();
        
        Matter.getCommissioningClient(this)
                .commissionDevice(commissionDeviceRequest)
                .addOnSuccessListener(new OnSuccessListener<IntentSender>() {
                    @Override
                    public void onSuccess(IntentSender intentSender) {
                        Log.i(getClass().getName(), "onSuccess() Success getting the IntentSender");
                        // Communication with fragment is via livedata
                        _commissionDeviceIntentSender.postValue(intentSender);
                    }
                })
                .addOnFailureListener(new OnFailureListener() {
                    @Override
                    public void onFailure(@NonNull Exception e) {
                        Log.e(getClass().getName(), "onFailure() Setting up the IntentSender failed : " + e.getMessage());
                    }
                });
    }

Calling this method properly triggers onSuccess() callback, but for some reason the call to _commissionDeviceIntentSender.postValue(intentSender); does nothing, and no error log to help.

Shouldn't this call open the "Scan Matter QR code" screen ?

Can you please help getting this working ?

Dynamic parts list on EP0

Section 9.13.6 of the CHIP spec describes how a controller is able to monitor devices being added or removed from a bridge.

When an update to the set of Bridged Devices (which are exposed according to the Section 9.13.11,
“Best practices for Bridge Manufacturers”) occurs, the Bridge SHALL
• on the Descriptor cluster of endpoint 0: update the PartsList attribute (add/remove entries from
this list)
• update the exposed endpoints and their descriptors according to the new set of Bridged Devices

Nodes that wish to be notified of added/removed devices SHOULD monitor changes of the PartsList
attribute in the Descriptor cluster on endpoint 0.

Does Google Home monitor EP0/PartsList on every device, or does it look for Bridges and only monitor EP0/PartsList on those devices?

If I have a non-bridge device, dynamically create an EP (which is not disallowed) and update EP0/PartsList will Google Home rescan the device and add/remove an icon for the new EP? Or do I need to create a bogus bridge cluster (aggregator)?

Adding Manufacturer specific clusters

In order to add manufacturer specific clusters I have to recompile: https://github.com/google-home/sample-app-for-matter-android/tree/main/app/third_party/connectedhomeip/libs

Can you publish a repository showing exactly how these libs were built? When I build from CHIP source my libs don't match yours.

Security Policy violation Binary Artifacts

This issue was automatically created by Allstar.

Security Policy Violation
Project is out of compliance with Binary Artifacts policy: binaries present in source code

Rule Description
Binary Artifacts are an increased security risk in your repository. Binary artifacts cannot be reviewed, allowing the introduction of possibly obsolete or maliciously subverted executables. For more information see the Security Scorecards Documentation for Binary Artifacts.

Remediation Steps
To remediate, remove the generated executable artifacts from the repository.

First 10 Artifacts Found

app/third_party/connectedhomeip/libs/AndroidPlatform.jar
app/third_party/connectedhomeip/libs/CHIPController.jar
app/third_party/connectedhomeip/libs/SetupPayloadParser.jar
app/third_party/connectedhomeip/libs/jniLibs/arm64-v8a/libCHIPController.so
app/third_party/connectedhomeip/libs/jniLibs/arm64-v8a/libSetupPayloadParser.so
app/third_party/connectedhomeip/libs/jniLibs/arm64-v8a/libc++_shared.so
app/third_party/connectedhomeip/libs/jniLibs/armeabi-v7a/libCHIPController.so
app/third_party/connectedhomeip/libs/jniLibs/armeabi-v7a/libSetupPayloadParser.so
app/third_party/connectedhomeip/libs/jniLibs/armeabi-v7a/libc++_shared.so
app/third_party/connectedhomeip/libs/jniLibs/x86/libCHIPController.so
Run a Scorecards scan to see full list.

Additional Information
This policy is drawn from Security Scorecards, which is a tool that scores a project's adherence to security best practices. You may wish to run a Scorecards scan directly on this repository for more details.

⚠️ There is an updated version of this policy result! Click here to see the latest update

Allstar has been installed on all Google managed GitHub orgs. Policies are gradually being rolled out and enforced by the GOSST and OSPO teams. Learn more at http://go/allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

Type safety between deviceId and devicePtr

It would be helpful to have type safety between deviceId and devicePtr since it is very easy to pass in the wrong one

How to create Groups and Bindings from ChipDeviceController

How do I translate these into API calls on the CHIP controller?

./chip-tool groupsettings add-group grp1 0x0001
./chip-tool groupsettings add-keysets 0x0042 0 0x000000000021dfe0 hex:d0d1d2d3d4d5d6d7d8d9dadbdcdddedf
./chip-tool groupsettings bind-keyset 0x0001 0x0042

Allowing uncertified devices

When I add an uncertified device to Apple Home during commissioning I get a popup asking me if I want to allow the uncertified device onto the Matter network. So how do you implement this popup on the Google side?

Standard icons for device types

It would be nice to have a defined standard set of icons for the Matter device types. That way everyone will use the same ones and not design their own or pick random ones (like I am doing right now).

Is there a sample app for Matter Thread ?

I'm looking for an app equivalent to GHSAFM allowing commissioningof Matter Thread devices (possibly via a border router such as Google Nest).

Any suggestion please ?

Crash when opening the sample app (BUG)

/AndroidRuntime: FATAL EXCEPTION: main
Process: com.google.homesampleapp.default, PID: 9256
java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app/~~jx_Fe-eqYxS-tONr3Cy6XQ==/com.google.homesampleapp.default-wKyd-x-gqtdpLGME0SbYeQ==/base.apk!/lib/arm64-v8a/libCHIPController.so" has bad ELF magic: 76657273
at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
at java.lang.Runtime.loadLibrary0(Runtime.java:998)
at java.lang.System.loadLibrary(System.java:1661)
at chip.devicecontroller.ChipDeviceController.(ChipDeviceController.java:747)
at chip.devicecontroller.ChipDeviceController.loadJni(ChipDeviceController.java:44)
at com.google.homesampleapp.chip.ChipClient$chipDeviceController$2.invoke(ChipClient.kt:52)
at com.google.homesampleapp.chip.ChipClient$chipDeviceController$2.invoke(ChipClient.kt:51)
at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
at com.google.homesampleapp.chip.ChipClient.getChipDeviceController(ChipClient.kt:51)
at com.google.homesampleapp.screens.home.HomeFragment.setDeviceAttestationDelegate(HomeFragment.kt:432)
at com.google.homesampleapp.screens.home.HomeFragment.onCreate(HomeFragment.kt:152)
at androidx.fragment.app.Fragment.performCreate(Fragment.java:3090)
at androidx.fragment.app.FragmentStateManager.create(FragmentStateManager.java:475)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:257)
at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1899)
at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1823)
at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1760)
at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:2985)
at androidx.fragment.app.FragmentManager.dispatchCreate(FragmentManager.java:2884)
at androidx.fragment.app.Fragment.onCreate(Fragment.java:1967)
at androidx.navigation.fragment.NavHostFragment.onCreate(NavHostFragment.kt:169)
at androidx.fragment.app.Fragment.performCreate(Fragment.java:3090)
at androidx.fragment.app.FragmentStateManager.create(FragmentStateManager.java:475)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:257)
at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1899)
at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1823)
at androidx.fragment.app.FragmentManager.execSingleAction(FragmentManager.java:1729)
at androidx.fragment.app.BackStackRecord.commitNowAllowingStateLoss(BackStackRecord.java:323)
at androidx.fragment.app.FragmentContainerView.(FragmentContainerView.kt:158)
at androidx.fragment.app.FragmentLayoutInflaterFactory.onCreateView(FragmentLayoutInflaterFactory.java:53)
at androidx.fragment.app.FragmentController.onCreateView(FragmentController.java:136)
at androidx.fragment.app.FragmentActivity.dispatchFragmentsOnCreateView(FragmentActivity.java:248)
at androidx.fragment.app.FragmentActivity.onCreateView(FragmentActivity.java:227)
at android.view.LayoutInflater.tryCreateView(LayoutInflater.java:1073)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:1001)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:965)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:1127)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:1088)
at android.view.LayoutInflater.inflate(LayoutInflater.java:686)
at android.view.LayoutInflater.inflate(LayoutInflater.java:538)
at android.view.LayoutInflater.inflate(LayoutInflater.java:485)
at androidx.appcompat.app.AppCompatDelegateImpl.setContentView(AppCompatDelegateImpl.java:710)
at androidx.appcompat.app.AppCompatActivity.setContentView(AppCompatActivity.java:195)
at androidx.databinding.DataBindingUtil.setContentView(DataBindingUtil.java:303)
at androidx.databinding.DataBindingUtil.setContentView(DataBindingUtil.java:284)
E/AndroidRuntime: at com.google.homesampleapp.MainActivity.onCreate(MainActivity.kt:41)
at android.app.Activity.performCreate(Activity.java:8054)
at android.app.Activity.performCreate(Activity.java:8034)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1341)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3688)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3864)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2253)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7870)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

Not a Matter-certified device

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-tool in a terminal and Apple Home seems to be working well too. I have attached the device logs showing the matter config and the commissioning error.

Version

Commit - 0eb3c6d2c126c020619d3fe40026c9fa52e1c80c

Device Error Log with GHSAFM as Commissioner

I (62538) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14 
I (62538) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (62548) chip[EM]: >>> [E:26846r M:247894512] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I (62568) esp_matter_command: Received command 0x0004 for enpoint 0x0000's cluster 0x0000003E
I (62568) chip[ZCL]: OpCreds: Received a CSRRequest command
I (62918) chip[ZCL]: OpCreds: AllocatePendingOperationalKey succeeded
I (63088) chip[ZCL]: OpCreds: CSRRequest successful.
I (63088) chip[EM]: <<< [E:26846r M:64238810] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I (63108) chip[IN]: (S) Sending msg 64238810 on secure session with LSID: 40484
I (63108) NimBLE: GATT procedure initiated: indicate; 
I (63118) NimBLE: att_handle=14

E (63118) chip[DL]: Long dispatch time: 567 ms, for event type 7
I (63168) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14 
I (63168) NimBLE: GATT procedure initiated: indicate; 
I (63178) NimBLE: att_handle=14

I (63258) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14 
I (63258) NimBLE: GATT procedure initiated: indicate; 
I (63268) NimBLE: att_handle=14

I (63348) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 14 
I (65198) chip[DL]: Write request/command received for CHIPoBLE TX CCCD characteristic (con 1 ) indicate = 0
I (65198) chip[DL]: CHIPoBLE unsubscribe received
I (65208) chip[DL]: BLE GAP connection terminated (con 1 reason 0x213)
I (65198) chip[BLE]: Releasing end point's BLE connection back to application.

Matter Device Config (ESP32)

I (76569) esp_matter_attribute: ********** Endpoint 0x0001's Cluster 0x0005's Attribute 0x0003 is 0 **********
I (76569) chip[EM]: <<< [E:22868r M:211225918 (Ack:72764337)] (S) Msg TX to 1:000000000001B669 [2653] --- Type 0001:09 (IM:InvokeCommandResponse)
I (76579) chip[IN]: (S) Sending msg 211225918 on secure session with LSID: 267
E (76599) chip[DL]: Long dispatch time: 127 ms, for event type 3
I (76609) chip[EM]: >>> [E:22868r M:72764338 (Ack:211225918)] (S) Msg RX from 1:000000000001B669 [2653] --- Type 0000:10 (SecureChannel:StandaloneAck)

> matter config
VendorId:        65521 (0xFFF1)
ProductId:       32768 (0x8000)
HardwareVersion: 0 (0x0)
PinCode:         20202021
Discriminator:   f00
Done

My Google Home Display keeps restarting

How can I get the logcat from it? Logcat should show me where the problem is. I'm probably sending it something it doesn't like.

Exception in onCommissioningRequested(): lateinit property chipClient has not been initialized

I'm trying to implement the commissioning mecanism in a custom app
After starting commissioning a device, the method AppCommissioningService's onCommissioningRequested() is properly called, but then the following exception is thrown:

lateinit property chipClient has not been initialized

Any idea why ?
How to initialize chipClient ?

For info, here is how chipClient is declared in the service:

@Inject
internal lateinit var chipClient: ChipClient

Something went wrong with google sample app (GHSAFM)

My device is silab evb for matter over wifi, but GHSAFM always get the following error.
Please help to check.

01-06 19:18:35.389  2259  2259 I MatterCommissioner: Sent CommissioningComplete. [CONTEXT service_id=336 ]
01-06 19:18:35.389  2259  5073 D EM      : Flushed pending ack for MessageCounter:252160983 on exchange 64964i
01-06 19:18:35.389  2259  2259 I MatterCommissioner: Commissioning completed successfully. [CONTEXT service_id=336 ]
01-06 19:18:35.389  2259  2259 I SetupDeviceViewModel: **Commissioning completed successfully**. [CONTEXT service_id=336 ]
01-06 19:18:35.389  2259  2259 I BleScanner: Disconnecting and closing Bluetooth GATT connection. [CONTEXT service_id=336 ]
01-06 19:18:35.397  2259  2259 I SetupDeviceChimeraActiv: Commissioning service provided; opening a commissioning window. [CONTEXT service_id=336 ]
01-06 19:18:36.183  2259  2259 I SetupDeviceViewModel: Opened commissioning window at fe80::8ada:1aff:fee4:bc14%38[5540] [CONTEXT service_id=336 ]
01-06 19:18:36.189  2259  2259 I CommissioningServiceBin: Sending commissioning request to bound service. [CONTEXT service_id=336 ]
01-06 19:19:26.673  2259  2259 W CommissioningServiceBin: Disconnected from service ComponentInfo{com.google.homesampleapp.default/com.google.homesampleapp.commissioning.AppCommissioningService} [CONTEXT service_id=336 ]
01-06 19:19:27.802  2259  2259 I CommissioningServiceBin: Connected to service ComponentInfo{com.google.homesampleapp.default/com.google.homesampleapp.commissioning.AppCommissioningService}. [CONTEXT service_id=336 ]
**01-06 19:20:36.193  2259  2259 W CommissioningServiceBin: Gave up waiting for commissioning response after 120000ms [CONTEXT service_id=336 ]
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: Showing error status. [CONTEXT service_id=336 ]
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: m.fjj: Timed out waiting for commissioner to respond (ComponentInfo{com.google.homesampleapp.default/com.google.homesampleapp.commissioning.AppCommissioningService}).**
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at m.fpa.a(:com.google.android.gms.optional_home@[email protected] (100400-0):12)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at m.bnj.b(:com.google.android.gms.optional_home@[email protected] (100400-0):2)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at m.bnj.f(:com.google.android.gms.optional_home@[email protected] (100400-0):4)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at m.bno.j(:com.google.android.gms.optional_home@[email protected] (100400-0):3)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at m.bng.run(:com.google.android.gms.optional_home@[email protected] (100400-0):0)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at android.os.Handler.handleCallback(Handler.java:883)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at android.os.Handler.dispatchMessage(Handler.java:100)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at android.os.Looper.loop(Looper.java:238)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at android.app.ActivityThread.main(ActivityThread.java:7823)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at java.lang.reflect.Method.invoke(Native Method)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:512)
01-06 19:20:36.195  2259  2259 E SetupDeviceChimeraActiv: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1017)

logcat4.txt

How can I check that the matter feature of the current phone is available?

I see this: https://developers.home.google.com/matter/verify-services

But when users use it, there is difficult to do these operations.

Is there any way to determine that GMS service in the user's mobile phone supports the Matter feature?

Update README to note differences between releases

Due to the difference in the Matter SDK SHA that Google's Developer Preview rolls up to, vs where the SDK is today, we have multiple minor version releases available (1.0, 1.1, 1.2). Each is intended for a different purpose, and we should clarify this in the README until our public developer support fully aligns with the Matter 1.0 spec.

Unable to pair matter device since 16th dec update

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:

12-16 14:28:09.704 24297 24297 I MatterCommissioner: Retrieved DAC chain. [CONTEXT service_id=336 ]
12-16 14:28:09.704 24297 24476 D EM      : Flushed pending ack for MessageCounter:85930631 on exchange 36107i
12-16 14:28:09.705 24297 24297 D DMG     : ICR moving to [AddingComm]
12-16 14:28:09.705 24297 24297 D DMG     : ICR moving to [AddedComma]
12-16 14:28:09.705 24297 24297 D EM      : <<< [E:36108i M:35017989] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
12-16 14:28:09.705 24297 24297 D IN      : (S) Sending msg 35017989 on secure session with LSID: 25824
12-16 14:28:09.705 24297 24297 D DMG     : ICR moving to [CommandSen]
12-16 14:28:09.710 24297 24476 D EM      : >>> [E:36108i M:85930632 (Ack:35017989)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
12-16 14:28:09.710 24297 24476 D EM      : Found matching exchange: 36108i, Delegate: 0x714d244108
12-16 14:28:09.710 24297 24476 D EM      : Rxd Ack; Removing MessageCounter:35017989 from Retrans Table on exchange 36108i
12-16 14:28:09.710 24297 24476 D DMG     : ICR moving to [ResponseRe]
12-16 14:28:09.710 24297 24476 D DMG     : Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0003
12-16 14:28:09.711 24297 24476 D DMG     : ICR moving to [AwaitingDe]
12-16 14:28:09.711 24297 24476 D EM      : <<< [E:36108i M:35017990 (Ack:85930632)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
12-16 14:28:09.711 24297 24476 D IN      : (S) Sending msg 35017990 on secure session with LSID: 25824
12-16 14:28:09.711 24297 24297 I MatterCommissioner: Retrieved PAI chain. [CONTEXT service_id=336 ]
12-16 14:28:09.712 24297 24476 D EM      : Flushed pending ack for MessageCounter:85930632 on exchange 36108i
12-16 14:28:09.712 24297 24297 D DMG     : ICR moving to [AddingComm]
12-16 14:28:09.712 24297 24297 D DMG     : ICR moving to [AddedComma]
12-16 14:28:09.712 24297 24297 D EM      : <<< [E:36109i M:35017991] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
12-16 14:28:09.712 24297 24297 D IN      : (S) Sending msg 35017991 on secure session with LSID: 25824
12-16 14:28:09.713 24297 24297 D DMG     : ICR moving to [CommandSen]
12-16 14:28:09.716 24297 24476 D EM      : >>> [E:36109i M:85930633 (Ack:35017991)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
12-16 14:28:09.716 24297 24476 D EM      : Found matching exchange: 36109i, Delegate: 0x712a71ef88
12-16 14:28:09.716 24297 24476 D EM      : Rxd Ack; Removing MessageCounter:35017991 from Retrans Table on exchange 36109i
12-16 14:28:09.717 24297 24476 D EM      : >>> [E:36109i M:85930634 (Ack:35017991)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
12-16 14:28:09.717 24297 24476 D EM      : Found matching exchange: 36109i, Delegate: 0x712a71ef88
12-16 14:28:09.717 24297 24476 D EM      : CHIP MessageCounter:35017991 not in RetransTable on exchange 36109i
12-16 14:28:09.717 24297 24476 D DMG     : ICR moving to [ResponseRe]
12-16 14:28:09.717 24297 24476 D DMG     : Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0001
12-16 14:28:09.718 24297 24476 D DMG     : ICR moving to [AwaitingDe]
12-16 14:28:09.719 24297 24476 D EM      : <<< [E:36109i M:35017992 (Ack:85930634)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
12-16 14:28:09.719 24297 24476 D IN      : (S) Sending msg 35017992 on secure session with LSID: 25824
12-16 14:28:09.719 24297 24476 D EM      : Flushed pending ack for MessageCounter:85930634 on exchange 36109i
12-16 14:28:09.720 24297 24297 I MatterCommissioner: Retrieved attestation response. [CONTEXT service_id=336 ]
12-16 14:28:09.721 24297 24297 I MatterCommissioner: Retrieved attestation challenge. [CONTEXT service_id=336 ]
12-16 14:28:09.721 24297 24297 D DMG     : ICR moving to [AddingComm]
12-16 14:28:09.722 24297 24297 D DMG     : ICR moving to [AddedComma]
12-16 14:28:09.722 24297 24297 D EM      : <<< [E:36110i M:35017993] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
12-16 14:28:09.722 24297 24297 D IN      : (S) Sending msg 35017993 on secure session with LSID: 25824
12-16 14:28:09.722 24297 24297 D DMG     : ICR moving to [CommandSen]
12-16 14:28:09.725 24297 24476 D EM      : >>> [E:36110i M:85930635 (Ack:35017993)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
12-16 14:28:09.725 24297 24476 D EM      : Found matching exchange: 36110i, Delegate: 0x71270d5e88
12-16 14:28:09.725 24297 24476 D EM      : Rxd Ack; Removing MessageCounter:35017993 from Retrans Table on exchange 36110i
12-16 14:28:09.726 24297 24476 D EM      : >>> [E:36110i M:85930636 (Ack:35017993)] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
12-16 14:28:09.726 24297 24476 D EM      : Found matching exchange: 36110i, Delegate: 0x71270d5e88
12-16 14:28:09.726 24297 24476 D EM      : CHIP MessageCounter:35017993 not in RetransTable on exchange 36110i
12-16 14:28:09.726 24297 24476 D DMG     : ICR moving to [ResponseRe]
12-16 14:28:09.727 24297 24476 D DMG     : Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0005
12-16 14:28:09.727 24297 24476 D DMG     : ICR moving to [AwaitingDe]
12-16 14:28:09.728 24297 24476 D EM      : <<< [E:36110i M:35017994 (Ack:85930636)] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
12-16 14:28:09.728 24297 24297 I MatterCommissioner: Retrieved CsrResponse. [CONTEXT service_id=336 ]
12-16 14:28:09.728 24297 24476 D IN      : (S) Sending msg 35017994 on secure session with LSID: 25824
12-16 14:28:09.728 24297 24476 D EM      : Flushed pending ack for MessageCounter:85930636 on exchange 36110i
12-16 14:28:10.319  5802  5802 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
12-16 14:28:10.478 24297 24297 I MatterCommissioner: Disarming failsafe. [CONTEXT service_id=336 ]
12-16 14:28:10.478 24297 24297 D CSM     : FindOrEstablishSession: PeerId = [1:CFD6035521232E34]
12-16 14:28:10.479 24297 24297 D CSM     : FindOrEstablishSession: No existing OperationalSessionSetup instance found
12-16 14:28:10.479 24297 24297 D CTL     : OperationalSessionSetup[1:CFD6035521232E34]: State change 1 --> 2
12-16 14:28:10.480 24297 24297 D DIS     : Resolving 2AAD57707A02D131:CFD6035521232E34 ...
12-16 14:28:10.482 24297 24354 I ServiceResolverAdapter: Resolving address for 2AAD57707A02D131-CFD6035521232E34._matter._tcp [CONTEXT service_id=336 ]
12-16 14:28:10.485 24297 24354 I MatterDnsSdServiceResol: Starting search for ResolveServiceRequest{instanceName='2AAD57707A02D131-CFD6035521232E34', serviceType='_matter._tcp'}, timing out in 5000 ms... [CONTEXT service_id=336 ]
12-16 14:28:10.602 24297 24354 I ManagedMdnsServiceBrows: Starting mDNS search for 2AAD57707A02D131-CFD6035521232E34 Options(passive=true, subtypes=[I2AAD57707A02D131], queryMode=ipv4/ipv6) [CONTEXT service_id=336 ]
12-16 14:28:10.720 24297 24476 D DIS     : Checking node lookup status after 240 ms
12-16 14:28:13.566  5802  5802 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.threadnetwork.service.START dat=chimera-action: cmp=com.google.android.gms/.chimera.GmsApiService }
12-16 14:28:14.097  5802  5802 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.home.service.START dat=chimera-action: cmp=com.google.android.gms/.chimera.GmsApiService }
12-16 14:28:15.169  5802  5802 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.chimera.container.moduleinstall.ModuleInstallService.START dat=chimera-action: cmp=com.google.android.gms/.chimera.GmsApiService }
12-16 14:28:15.487 24297 27423 I ManagedMdnsServiceBrows: Stopping mDNS search for 2AAD57707A02D131-CFD6035521232E34 [CONTEXT service_id=336 ]
12-16 14:28:15.490 24297 24354 I ServiceResolverAdapter: Timed out searching for 2AAD57707A02D131-CFD6035521232E34._matter._tcp [CONTEXT service_id=336 ]
12-16 14:28:15.491 24297 24354 I ServiceResolverAdapter: No cached mDNS response found for 2AAD57707A02D131-CFD6035521232E34._matter._tcp [CONTEXT service_id=336 ]
12-16 14:28:18.651   763  5197 D ConnectivityService: requestNetwork for uid/pid:10078/27312 NetworkRequest [ TRACK_DEFAULT id=315, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
12-16 14:28:18.653   763   979 I chatty  : uid=1000(system) WifiStateMachin expire 10 lines
12-16 14:28:18.653  1506  1506 D PhoneSwitcherNetworkRequstListener: got request NetworkRequest [ TRACK_DEFAULT id=315, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 60
12-16 14:28:25.525 24297 24476 D DIS     : Checking node lookup status after 15044 ms
12-16 14:28:25.525 24297 24476 E DIS     : OperationalSessionSetup[1:CFD6035521232E34]: operational discovery failed: third_party/connectedhomeip/next/src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:174: CHIP Error 0x00000032: Timeout
12-16 14:28:25.528 24297 24476 W ChipController: Failed to resolve pointer for device CFD6035521232E34 [CONTEXT service_id=336 ]
12-16 14:28:25.528 24297 24476 W ChipController: chip.devicecontroller.ChipDeviceControllerException: third_party/connectedhomeip/next/src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:174: CHIP Error 0x00000032: Timeout
12-16 14:28:25.533 24297 24297 I MatterCommissioner: Could not disarm failsafe (error=0x2A97F190) [CONTEXT service_id=336 ]
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: Commissioning failed with state Failure obtaining credentials. [CONTEXT service_id=336 ]
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: m.epp: Failed to retrieve commissionee credentials.
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.erj.e(:com.google.android.gms.optional_home@[email protected] (020400-0):6)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.erc.b(:com.google.android.gms.optional_home@[email protected] (020400-0):0)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.nkd.f(:com.google.android.gms.optional_home@[email protected] (020400-0):4)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.nrb.run(:com.google.android.gms.optional_home@[email protected] (020400-0):7)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at android.os.Handler.handleCallback(Handler.java:790)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at android.os.Handler.dispatchMessage(Handler.java:99)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at android.os.Looper.loop(Looper.java:164)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at android.app.ActivityThread.main(ActivityThread.java:6494)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at java.lang.reflect.Method.invoke(Native Method)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: Caused by: m.feb: RPC ProvisionCertificateForCommissionee returned code CANCELLED; Sherlog for ProvisionCertificateForCommissionee is needed to diagnose.
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.fef.b(:com.google.android.gms.optional_home@[email protected] (020400-0):28)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.nkd.f(:com.google.android.gms.optional_home@[email protected] (020400-0):4)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.nrb.run(:com.google.android.gms.optional_home@[email protected] (020400-0):8)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.dtt.c(:com.google.android.gms.optional_home@[email protected] (020400-0):6)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.dtt.run(:com.google.android.gms.optional_home@[email protected] (020400-0):7)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at abrk.run(:com.google.android.gms@[email protected] (040400-493411920):0)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at java.lang.Thread.run(Thread.java:764)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: Caused by: m.mqz: CANCELLED: The operation was cancelled.
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.dse.c(:com.google.android.gms.optional_home@[email protected] (020400-0):95)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.fdb.a(:com.google.android.gms.optional_home@[email protected] (020400-0):59)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	at m.fef.b(:com.google.android.gms.optional_home@[email protected] (020400-0):11)
12-16 14:28:25.535 24297 24297 E SetupDeviceViewModel: 	... 8 more
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: Showing error status. [CONTEXT service_id=336 ]
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: m.fnx: Failed to retrieve commissionee credentials.
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.fuy.a(:com.google.android.gms.optional_home@[email protected] (020400-0):12)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.nxr.a(:com.google.android.gms.optional_home@[email protected] (020400-0):0)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.nxq.a(:com.google.android.gms.optional_home@[email protected] (020400-0):7)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.ehi.b(:com.google.android.gms.optional_home@[email protected] (020400-0):86)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.nkd.f(:com.google.android.gms.optional_home@[email protected] (020400-0):4)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.nrb.run(:com.google.android.gms.optional_home@[email protected] (020400-0):7)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at android.os.Handler.handleCallback(Handler.java:790)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at android.os.Handler.dispatchMessage(Handler.java:99)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at android.os.Looper.loop(Looper.java:164)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at android.app.ActivityThread.main(ActivityThread.java:6494)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at java.lang.reflect.Method.invoke(Native Method)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: Caused by: m.epp: Failed to retrieve commissionee credentials.
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.erj.e(:com.google.android.gms.optional_home@[email protected] (020400-0):6)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.erc.b(:com.google.android.gms.optional_home@[email protected] (020400-0):0)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	... 9 more
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: Caused by: m.feb: RPC ProvisionCertificateForCommissionee returned code CANCELLED; Sherlog for ProvisionCertificateForCommissionee is needed to diagnose.
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.fef.b(:com.google.android.gms.optional_home@[email protected] (020400-0):28)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.nkd.f(:com.google.android.gms.optional_home@[email protected] (020400-0):4)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.nrb.run(:com.google.android.gms.optional_home@[email protected] (020400-0):8)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.dtt.c(:com.google.android.gms.optional_home@[email protected] (020400-0):6)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.dtt.run(:com.google.android.gms.optional_home@[email protected] (020400-0):7)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at abrk.run(:com.google.android.gms@[email protected] (040400-493411920):0)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at java.lang.Thread.run(Thread.java:764)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: Caused by: m.mqz: CANCELLED: The operation was cancelled.
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.dse.c(:com.google.android.gms.optional_home@[email protected] (020400-0):95)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.fdb.a(:com.google.android.gms.optional_home@[email protected] (020400-0):59)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	at m.fef.b(:com.google.android.gms.optional_home@[email protected] (020400-0):11)
12-16 14:28:25.538 24297 24297 E SetupDeviceChimeraActiv: 	... 8 more

When I compare this to my custom controller it will just go straight to adding the fabrics certificates after receving the DAC, PAI.

# receive this command from my custom controller before successfully confirm pairing
CHIP:ZCL: OpCreds: Received an AddTrustedRootCertificate command

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.

Unable to see Matter devices & services option on Pixel 4a (Android 13)

I've followed the procedure described here:
https://developers.home.google.com/matter/verify-services

Basically I upgraded Google Services to the latest version and re-installed Google Home App.

Despite that, I don't see the
Matter devices & services option in Settings > Google > Devices & sharing

Any idea what to do please ?

built apk(or aab) size problem

hi,
I am experimenting to apply the matter library to my app.
It's the same when I built it in my app, but also when I saw it in this sample app.
I have a problem with apk size.

After building, the apk' size is too large, because libCHIPController.so file size is too large.

When I build on m1 Mac, the libCHIPController.so file is only 115/114 (Bytes) in arm64-v8a/armeabi-v7a in Analyze APK
However, when built on an intell cpu PC, it occupies 54.1 / 52.8 (MB). The gap is huge ~..;

Basically, Build options are the same. In app build.gradle, only arm64-v8a/armeabi-v7a was turned on for ndk.abiFilter,
and the jniLibs settings were set as follows.
packagingOptions {
jniLibs {
useLegacyPackaging false
}
}

how can I apply this library into my app, in the smallest possible capacity.

How to connect to Thread Border Router using Google Home sample app?

Hello,

I am trying to connect below Android application to Thread based matter device.
Sample app for matter android source: https://github.com/google-home/sample-app-for-matter-android/releases/tag/v1.3.0
Sample app for matter android apk: https://github.com/google-home/sample-app-for-matter-android/releases/download/v1.3.0/GHSAFM-1.3.0-default-debug.apk

I am facing the issue when I trying to connect Thread based matter device. Google sample application throwing the error as per below,

"Your device requires a Thread border router"

I have gone through https://openthread.io/guides/border-router/external-commissioning/android#thread_group_android_app. But application not available on Google play store.

Please guide for How connect Thread border router using Android application.

Thank you,
Palakkumar Suhagia,
Einfochips | Senior Engineer

Why is sample polling instead of using a notification?

Wouldn't it be more responsive if the app subscribed to notifications from the devices instead of polling them?

Jetpack Compose version

I am finding it difficult to translate some of the commissioning features of this app over to Jetpack Compose. It would be very helpful to have a Compose version of it.

Lost ability to commission, issue with uncertified devices and attestation?

Is there any solution to sharing the chip libraries with Google Home and this app? Related to this, I'm in a state right now where my Android app and devices can't talk to each other anymore because somehow the libraries are mismatched.

What is this commit? It is not in the CHIP tree.
Sync matterhorn with Matter SDK at commit 0b9cae0209263edef812f4df45a4d2035c092688.

jonsmirl@ares:~/aosp/esp-matter/connectedhomeip/connectedhomeip$ git show 0b9cae0209263edef812f4df45a4d2035c092688.
fatal: ambiguous argument '0b9cae0209263edef812f4df45a4d2035c092688.': unknown revision or path not in the working tree.

My devices are using CHIP:
commit 561d23d0db215a99705ff0696e73853c8edf11b2 (HEAD, tag: v1.0.0, origin/v1.0)

Verify the test device on sample app

I installed GHSAFM-1.3.0default.
I try commissioning to nRF52840 DK bord.(Nordic) Device type is Lock.
Result is commissioning error on following.

E/SetupDeviceViewModel: Commissioning failed with state Attestation failure. [CONTEXT service_id=336 ]

What do modify on sample app code for success commissioning.
Google Home App is successful on DK bord.

I attached commissioning log.
commissioning.log

Thank you for your support.

Documentation for the CHIP jars

I can't find documentation for any of the CHIP API at developers.home.google.com, shouldn't it be listed here?
https://developers.home.google.com/reference/com/google/android/gms/home/matter/commissioning/package-summary

The API all appears to be there, but many of the necessary parameters are completely mysterious and undocumented.

Room for device

Is there any mechanism to keep the room label for a device synchronized between Google Home and GHSAFM?

This should have been an attribute on the Basic Information cluster but it is not there. As a work around it could be encoded into NodeLabel, but then Google/Apple/Amazon need to agree on how it is encoded.

google-home / sample-apps-for-matter-android Goto Github PK

sample-apps-for-matter-android's Introduction

Google Home Mobile SDK Sample Applications for Matter

Clone the repository

sample-apps-for-matter-android's People

Contributors

Stargazers

Watchers

Forkers

sample-apps-for-matter-android's Issues

Issue

Environment

Steps to Reproduce

Complete Log

Below is the log.

Issue

Environment

Version

Device Error Log with GHSAFM as Commissioner

Matter Device Config (ESP32)

Recommend Projects

Recommend Topics

Recommend Org