Attachments (0)
Nordic Case Info
  • Case ID: 298036
Options

Google Home App - Matter commissioning fails

Dan

Hi - I am trying to commission my NRF5340DK board with NRF Connect SDK v.2.1.1 using Google Home App over Matter using the Matter light bulb sample.

My OTBR is a Google Nest Hub 2 running Chrome OS

My smartphone is Motorola Pure G running Android 11; Google Home Assistant app (GHA) version: 2.60.1.19

The GHA app is able to connect and begin the matter commissioning process. See the log from the NRF5340DK below. But after a few moments, while waiting to connect, the GHA "Connecting to Device Screen" abruptly closes (crashes?) and brings me back to my GHA home settings screen with nothing added.

Welcome any suggestions or advice. I am excited and eager to get my Nordic device to be controllable with GHA.

Thanks! Dan.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
uart:~$ I: nRF5 802154 radio initialized
I: 4 Sectors of 4096 bytes
I: alloc wra: 1, e20
I: data wra: 1, 310
*** Booting Zephyr OS build v3.1.99-ncs1 ***
I: Init CHIP stack
I: 173 [DL]BLE address: D0:50:98:AB:07:E6
I: 199 [DL]OpenThread started: OK
I: 202 [DL]Setting OpenThread device type to ROUTER
I: 207 [SVR]Server initializing...
D: 210 [FP]Initializing FabricTable from persistent storage
I: 216 [TS]Last Known Good Time: 2022-11-04T17:19:10
I: 221 [DMG]AccessControl: initializing
I: 225 [DMG]Examples::AccessControlDelegate::Init
I: 229 [DMG]AccessControl: setting
I: 232 [DMG]DefaultAclStorage: initializing
I: 236 [DMG]DefaultAclStorage: 0 entries loaded
D: 240 [IN]UDP::Init bind&listen port=5540
E: 244 [IN]SO_REUSEPORT failed: 109
D: 248 [IN]UDP::Init bound to port=5540
D: 251 [IN]BLEBase::Init - setting/overriding transport
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Parents
  • 0

    Hi Dan,

    At this time point, Google doesn't publicly support Matter yet, so it is not possible to test it without accessing the special beta firmware called Google Early Access Program. Here is the instruction how to test Nordic examples with Google ecosystem: https://developers.home.google.com/matter/vendors/nordic-semiconductor. Do you have followed this document?

    Best regards,

    Charlie

  • 0 in reply to Charlie

    Hi Charlie - I did read through it, but it seemed like it was written a while ago since it initially installs NRF v1.7.1

    west init -m github.com/.../sdk-nrf --mr v1.7.1

    (and then later updates to the most recent version).

    The essence of it seems to be applying google's patch in step 9 to the matter/connectedhomeip repo, which I did. What wasn't clear to me, is what is the cleanest way to get NRF Connect to build with the google-patched version of matter/connectedhomeip vs the one that NRF includes in its own repo?

    Thanks, Dan.

Reply
  • 0 in reply to Charlie

    Hi Charlie - I did read through it, but it seemed like it was written a while ago since it initially installs NRF v1.7.1

    west init -m github.com/.../sdk-nrf --mr v1.7.1

    (and then later updates to the most recent version).

    The essence of it seems to be applying google's patch in step 9 to the matter/connectedhomeip repo, which I did. What wasn't clear to me, is what is the cleanest way to get NRF Connect to build with the google-patched version of matter/connectedhomeip vs the one that NRF includes in its own repo?

    Thanks, Dan.

Children
  • 0 in reply to Dan

    Hi Dan,

    Google's public guidance was released in July - it is pretty out-of-date. It still uses old test event branch of Matter upstream repo, which only works with very old NCS v1.7.1. If you don't have access to goolge nest's developer preview software and want to test your Nest Hub 2nd gen with current production software, follow the guide to patch your cloned connectedhomeip and build the examples such as examples/lighting-app/nrfconnect. The FW should work.

    The NCS 2.1.1 already supports Matter v1.0, IMHO there is no point to follow this guide. Supposedly this guide should be updated soon. There are also quite some alternatives that publicly support Matter - for example Apple HomePod mini/Samsung SmartThings hub v3. These devices works quite well with NCS v2.1.1.

    Best Regards,

    Larry

  • 0 in reply to Larry

    Larry - bless you! Just forced an update to iOS16.1.1 (despite having auto updates, my iPhone was still on a previous version) and was able to scan a QR code and successfully commission an NRF5340DK device using my Apple Home app and issue voice commands to turn it on and off. Thank you for taking the time to read and respond to my question - much appreciated!

  • 0 in reply to Dan

    Hi Dan,  have you been able to test this aswell with GHA?  After Goolgle announced support for Matter 1.0

    I'm able do perform full commissioning but  just after it I'm getting information that the device is offline and I cannot control it. My device is nRF5340 with SDK 2.1.2    OTBR Nest Hu2. All software upgraded to the latest announced by google soft releases.  Anybody was successful to commission and control devices with Google Home App?

  • 0 in reply to Michal P

    Michal - just seeing this now - I was working on another project and wasn't checking here -  sorry for the delay in responding to you.

    I recently updated to NRF Connect SDK 2.2.0 and seem to have lost the ability to commission the light_bulb sample over Matter using the Apple Home app, and still cannot commission it using the Google Home App.

    If you or anyone else has been able to successfully commission an NRF DK with either google home or apple homepod, I would welcome hearing about it. Or if the Nordic team can try and provide us with suggestions/best practices for doing so, that would also be welcome. Thanks!

    Here is the log output from the NRF5340 DK:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    uart:~$ I: nRF5 802154 radio initialized
    I: 4 Sectors of 4096 bytes
    I: alloc wra: 1, f80
    I: data wra: 1, 48
    *** Booting Zephyr OS build v3.2.99-ncs1 ***
    I: Init CHIP stack
    I: 183 [DL]BLE address: F9:0E:36:CD:F5:F4
    I: 210 [DL]OpenThread started: OK
    I: 213 [DL]Setting OpenThread device type to ROUTER
    I: 218 [SVR]Server initializing...
    D: 221 [FP]Initializing FabricTable from persistent storage
    I: 228 [TS]Last Known Good Time: 2023-02-27T14:46:47
    I: 234 [DMG]AccessControl: initializing
    I: 237 [DMG]Examples::AccessControlDelegate::Init
    I: 242 [DMG]AccessControl: setting
    I: 245 [DMG]DefaultAclStorage: initializing
    I: 249 [DMG]DefaultAclStorage: 0 entries loaded
    D: 253 [IN]UDP::Init bind&listen port=5540
    E: 257 [IN]SO_REUSEPORT failed: 109
    D: 260 [IN]UDP::Init bound to port=5540
    D: 264 [IN]BLEBase::Init - setting/overriding transport
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Dan

    Hi Dan

    I was able to comission with GHA and nRF Connect 2.2.0 (further detail here: https://issuetracker.google.com/issues/262773689), with a pristine build an a full flash erase before programming.

Terms of service