Google Home Commissioning Problem

HI,

I have compiled Nordic Light Example for nRF5340-DK   and flashed it.

I'm using a border router based on beagle bone and OpenThread 1.3

On nRF5340-DK I have set up an active dataset (the same as BR).

When I'm sending ping 2001:db8:1:ffff::808:808   from nRF5340-DK I'm getting a nice response confirming my connection with the internet. I'm able as well to ping mobile phone IP from  nRF5340-DK.

When I doing commissioning with Google Home app on phone after device discovery and scanning QR code I'm getting information that the device requires Thread Border Router (information in Polish language). It says that I should connect with Border Router and configure the device once again. 
The problem is that this device already is connected to Border Router and has internet access, as proved by ping 2001:db8:1:ffff::808:808 and phone IP . 

Below is log from my nRF5340-DK which I'm getting during this process.

uart:~$ I: BLE advertising is already enabled
I: 231303 [DL]BLE connection established (ConnId: 0x00)
I: 231308 [DL]Current number of connections: 1/1
I: 231313 [DL]CHIPoBLE advertising stopped
I: 231317 [DL]NFC Tag emulation stopped
D: 231996 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 232003 [BLE]local and remote recv window sizes = 5
I: 232008 [BLE]selected BTP version 4
I: 232011 [BLE]using BTP fragment sizes rx 128 / tx 128.
D: 232100 [DL]ConnId: 0x00, New CCCD value: 0x0002
D: 232105 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
D: 232112 [IN]BLE EndPoint 0x200127d0 Connection Complete
I: 232118 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 131)
D: 232240 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 232248 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 232256 [EM]Received message of type 0x20 with protocolId (0, 0) and MessageCounter:193343940 on exchange 51106r
D: 232266 [EM]Handling via exchange: 51106r, Delegate: 0x20006614
D: 232272 [SC]Received PBKDF param request
D: 232276 [SC]Peer assigned session ID 37342
D: 232279 [SC]Found MRP parameters in the message
D: 232284 [SC]Including MRP parameters in PBKDF param response
I: 232290 [IN]Prepared unauthenticated message 0x2002ece0 to 0x0000000000000000 (0) of type 0x21 and protocolId (0, 0) on exchange 51106r with MessageCounter:164129078.
I: 232306 [IN]Sending unauthenticated msg 0x2002ece0 with MessageCounter:164129078 to 0x0000000000000000 at monotonic time: 0000000000038B71 msec
D: 232319 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 232326 [SC]Sent PBKDF param response
D: 232380 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 232388 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 14)
D: 232450 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 232458 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 232466 [EM]Received message of type 0x22 with protocolId (0, 0) and MessageCounter:193343941 on exchange 51106r
D: 232476 [EM]Found matching exchange: 51106r, Delegate: 0x20006614
D: 232482 [SC]Received spake2p msg1
I: 234057 [IN]Prepared unauthenticated message 0x2002ec70 to 0x0000000000000000 (0) of type 0x23 and protocolId (0, 0) on exchange 51106r with MessageCounter:164129079.
I: 234072 [IN]Sending unauthenticated msg 0x2002ec70 with MessageCounter:164129079 to 0x0000000000000000 at monotonic time: 0000000000039258 msec
D: 234085 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 234093 [SC]Sent spake2p msg2
E: 234095 [DL]Long dispatch time: 1637 ms, for event type 16388
D: 234130 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 234138 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
D: 234200 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 234208 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 234216 [EM]Received message of type 0x24 with protocolId (0, 0) and MessageCounter:193343942 on exchange 51106r
D: 234226 [EM]Found matching exchange: 51106r, Delegate: 0x20006614
D: 234232 [SC]Received spake2p msg3
D: 234235 [SC]Sending status report. Protocol code 0, exchange 51106
I: 234242 [IN]Prepared unauthenticated message 0x2002ecf8 to 0x0000000000000000 (0) of type 0x40 and protocolId (0, 0) on exchange 51106r with MessageCounter:164129080.
I: 234257 [IN]Sending unauthenticated msg 0x2002ecf8 with MessageCounter:164129080 to 0x0000000000000000 at monotonic time: 0000000000039311 msec
D: 234270 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 35)
I: 234279 [SC]SecureSession[0x20004430]: Moving from state 'kEstablishing' --> 'kActive'
D: 234286 [IN]SecureSession[0x20004430]: Activated - Type:1 LSID:36426
D: 234293 [IN]New secure session activated for device <FFFFFFFB00000000, 0>, LSID:36426 PSID:37342!
I: 234302 [SVR]Commissioning completed session establishment step
I: 234308 [DIS]Updating services using commissioning mode 0
D: 234313 [DL]Using Thread extended MAC for hostname.
I: 234319 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
I: 234328 [DL]advertising srp service: F599816147F4BA1C._matterc._udp
D: 234334 [DIS]Scheduling extended discovery timeout in 900s
D: 234341 [DL]CHIPoBLE advertising set to off
I: 234380 [SVR]Device completed Rendezvous process
E: 234385 [DL]Long dispatch time: 176 ms, for event type 16388
D: 234391 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 234399 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 234409 [EM]Received message of type 0x2 with protocolId (0, 1) and MessageCounter:74440050 on exchange 51107r
D: 234420 [EM]Handling via exchange: 51107r, Delegate: 0x2001019c
D: 234426 [IM]Received Read request
D: 234431 [DMG]IM RH moving to [GeneratingReports]
D: 234436 [DMG]Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
D: 234445 [DMG]<RE:Run> Cluster 28, Attribute 2 is dirty
D: 234451 [DMG]Reading attribute: Cluster=0x0000_0028 Endpoint=0 AttributeId=0x0000_0002 (expanded=0)
D: 234461 [DMG]<RE> Sending report (payload has 37 bytes)...
I: 234467 [IN]Prepared secure message 0x2002ee90 to 0xFFFFFFFB00000000 (0) of type 0x5 and protocolId (0, 1) on exchange 51107r with MessageCounter:203257533.
I: 234483 [IN]Sending encrypted msg 0x2002ee90 with MessageCounter:203257533 to 0xFFFFFFFB00000000 (0) at monotonic time: 00000000000393F1 msec
D: 234496 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 72)
D: 234504 [DMG]<RE> OnReportConfirm: NumReports = 0
D: 234509 [DMG]<RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D: 234516 [DMG]IM RH moving to [AwaitingDestruction]
D: 234522 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
D: 234550 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 234558 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 234566 [EM]Received message of type 0x2 with protocolId (0, 1) and MessageCounter:74440051 on exchange 51108r
D: 234576 [EM]Handling via exchange: 51108r, Delegate: 0x2001019c
D: 234582 [IM]Received Read request
D: 234586 [DMG]IM RH moving to [GeneratingReports]
D: 234590 [DMG]Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
D: 234599 [DMG]<RE:Run> Cluster 28, Attribute 4 is dirty
D: 234604 [DMG]Reading attribute: Cluster=0x0000_0028 Endpoint=0 AttributeId=0x0000_0004 (expanded=0)
D: 234613 [DMG]<RE> Sending report (payload has 37 bytes)...
I: 234620 [IN]Prepared secure message 0x2002ee90 to 0xFFFFFFFB00000000 (0) of type 0x5 and protocolId (0, 1) on exchange 51108r with MessageCounter:203257534.
I: 234634 [IN]Sending encrypted msg 0x2002ee90 with MessageCounter:203257534 to 0xFFFFFFFB00000000 (0) at monotonic time: 000000000003948A msec
D: 234647 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 72)
D: 234654 [DMG]<RE> OnReportConfirm: NumReports = 0
D: 234659 [DMG]<RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D: 234666 [DMG]IM RH moving to [AwaitingDestruction]
D: 234671 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
D: 234725 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 234733 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 234741 [EM]Received message of type 0x2 with protocolId (0, 1) and MessageCounter:74440052 on exchange 51109r
D: 234751 [EM]Handling via exchange: 51109r, Delegate: 0x2001019c
D: 234757 [IM]Received Read request
D: 234761 [DMG]IM RH moving to [GeneratingReports]
D: 234765 [DMG]Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
D: 234774 [DMG]<RE:Run> Cluster 3e, Attribute 2 is dirty
D: 234779 [DMG]Reading attribute: Cluster=0x0000_003E Endpoint=0 AttributeId=0x0000_0002 (expanded=0)
D: 234788 [DMG]<RE> Sending report (payload has 36 bytes)...
I: 234795 [IN]Prepared secure message 0x2002ee90 to 0xFFFFFFFB00000000 (0) of type 0x5 and protocolId (0, 1) on exchange 51109r with MessageCounter:203257535.
I: 234809 [IN]Sending encrypted msg 0x2002ee90 with MessageCounter:203257535 to 0xFFFFFFFB00000000 (0) at monotonic time: 0000000000039539 msec
D: 234822 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 234829 [DMG]<RE> OnReportConfirm: NumReports = 0
D: 234834 [DMG]<RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D: 234841 [DMG]IM RH moving to [AwaitingDestruction]
D: 234846 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
D: 234900 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 234908 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 234916 [EM]Received message of type 0x2 with protocolId (0, 1) and MessageCounter:74440053 on exchange 51110r
D: 234926 [EM]Handling via exchange: 51110r, Delegate: 0x2001019c
D: 234932 [IM]Received Read request
D: 234936 [DMG]IM RH moving to [GeneratingReports]
D: 234940 [DMG]Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
D: 234949 [DMG]<RE:Run> Cluster 3e, Attribute 3 is dirty
D: 234954 [DMG]Reading attribute: Cluster=0x0000_003E Endpoint=0 AttributeId=0x0000_0003 (expanded=0)
D: 234963 [DMG]<RE> Sending report (payload has 36 bytes)...
I: 234970 [IN]Prepared secure message 0x2002ee90 to 0xFFFFFFFB00000000 (0) of type 0x5 and protocolId (0, 1) on exchange 51110r with MessageCounter:203257536.
I: 234984 [IN]Sending encrypted msg 0x2002ee90 with MessageCounter:203257536 to 0xFFFFFFFB00000000 (0) at monotonic time: 00000000000395E8 msec
D: 234997 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 235004 [DMG]<RE> OnReportConfirm: NumReports = 0
D: 235009 [DMG]<RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D: 235016 [DMG]IM RH moving to [AwaitingDestruction]
D: 235021 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
D: 235075 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 235083 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 235091 [EM]Received message of type 0x2 with protocolId (0, 1) and MessageCounter:74440054 on exchange 51111r
D: 235101 [EM]Handling via exchange: 51111r, Delegate: 0x2001019c
D: 235107 [IM]Received Read request
D: 235111 [DMG]IM RH moving to [GeneratingReports]
D: 235115 [DMG]Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
D: 235124 [DMG]<RE:Run> Cluster 3e, Attribute 1 is dirty
D: 235129 [DMG]Reading attribute: Cluster=0x0000_003E Endpoint=0 AttributeId=0x0000_0001 (expanded=0)
D: 235138 [DMG]<RE> Sending report (payload has 36 bytes)...
I: 235145 [IN]Prepared secure message 0x2002ee90 to 0xFFFFFFFB00000000 (0) of type 0x5 and protocolId (0, 1) on exchange 51111r with MessageCounter:203257537.
I: 235159 [IN]Sending encrypted msg 0x2002ee90 with MessageCounter:203257537 to 0xFFFFFFFB00000000 (0) at monotonic time: 0000000000039697 msec
D: 235172 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 235179 [DMG]<RE> OnReportConfirm: NumReports = 0
D: 235184 [DMG]<RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D: 235191 [DMG]IM RH moving to [AwaitingDestruction]
D: 235196 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
D: 235250 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 235258 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 235266 [EM]Received message of type 0x2 with protocolId (0, 1) and MessageCounter:74440055 on exchange 51112r
D: 235276 [EM]Handling via exchange: 51112r, Delegate: 0x2001019c
D: 235282 [IM]Received Read request
D: 235286 [DMG]IM RH moving to [GeneratingReports]
D: 235290 [DMG]Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
D: 235299 [DMG]<RE:Run> Cluster 1d, Attribute 1 is dirty
D: 235304 [DMG]Reading attribute: Cluster=0x0000_001D Endpoint=0 AttributeId=0x0000_0001 (expanded=0)
D: 235314 [DMG]<RE> Sending report (payload has 400 bytes)...
I: 235322 [IN]Prepared secure message 0x2002ee90 to 0xFFFFFFFB00000000 (0) of type 0x5 and protocolId (0, 1) on exchange 51112r with MessageCounter:203257538.
I: 235336 [IN]Sending encrypted msg 0x2002ee90 with MessageCounter:203257538 to 0xFFFFFFFB00000000 (0) at monotonic time: 0000000000039748 msec
D: 235349 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 235357 [DMG]<RE> OnReportConfirm: NumReports = 0
D: 235361 [DMG]<RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D: 235369 [DMG]IM RH moving to [AwaitingDestruction]
D: 235374 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
D: 235382 [DL]SRP update succeeded
D: 235425 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 235433 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 235495 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 235503 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 235565 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 235573 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 57)
D: 235636 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 235643 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 235705 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 235713 [EM]Received message of type 0x2 with protocolId (0, 1) and MessageCounter:74440056 on exchange 51113r
D: 235723 [EM]Handling via exchange: 51113r, Delegate: 0x2001019c
D: 235729 [IM]Received Read request
D: 235733 [DMG]IM RH moving to [GeneratingReports]
D: 235738 [DMG]Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
D: 235746 [DMG]<RE:Run> Cluster 31, Attribute fffc is dirty
D: 235752 [DMG]Reading attribute: Cluster=0x0000_0031 Endpoint=0 AttributeId=0x0000_FFFC (expanded=0)
D: 235761 [DMG]<RE> Sending report (payload has 37 bytes)...
I: 235767 [IN]Prepared secure message 0x2002ee90 to 0xFFFFFFFB00000000 (0) of type 0x5 and protocolId (0, 1) on exchange 51113r with MessageCounter:203257539.
I: 235781 [IN]Sending encrypted msg 0x2002ee90 with MessageCounter:203257539 to 0xFFFFFFFB00000000 (0) at monotonic time: 0000000000039905 msec
D: 235794 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 72)
D: 235802 [DMG]<RE> OnReportConfirm: NumReports = 0
D: 235807 [DMG]<RE> ReportsInFlight = 0 with readHandler 0, RE has no more messages
D: 235814 [DMG]IM RH moving to [AwaitingDestruction]
D: 235819 [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
D: 235845 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 238360 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 240868 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 240925 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
I: 241961 [DL]BLE GAP connection terminated (reason 0x13)
I: 241966 [DL]Current number of connections: 0/1
E: 255875 [BLE]ack recv timeout, closing ep 0x200127d0
D: 255880 [IN]Clearing BLE pending packets.
I: 255884 [BLE]Releasing end point's BLE connection back to application.
I: 255890 [DL]Closing BLE GATT connection (ConnId 00)

In the google developer console, I have the below configuration. I also have to check if email address used in the developer console is the same one I'm using on my phone's Google Home App. Any idea why I have a problem with adding nRF5340-DK  as a device in Google Home App?  This is my first attempt to commission Matter device so I will appreciate any help.  

  • Hi Michal,

    If you want to access a specific ecosystem like Apple Homekit, or Google Home. You need to use board routers like Homepod Mini or Google Nest Hub from specific vendors.

    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 on how to test Nordic examples with the Google Home ecosystem: https://developers.home.google.com/matter/vendors/nordic-semiconductor. Prerequisites are mentioned here Get started with Matter  |  Google Home.

    Best regards,

    Charlie

  • Hello Charlie,

    I have both Homepod Mini and Google Nest Hub in the network and I was trying to add Nordic Light Example for nRF5340-DK  as device in Google Home App.  Unfortunatelly effect is exactly the same like with use OpenThread1.3 border router. Homepod Mini and Google Nest Hub are authenticated with the same e-mail like for Phone with Google Home App.

    If I understand well google-matter-preview.patch allow to have possibility to add Matter device to Google fabric with use Google Home?

    Is it possible to have patch which I can use with SDK 2.1.2 installed through nRF Toolchain Manager?

    When we can expect  SDK which will allow for integrattion with Google and Apple fabric, so we can use Siri or Google Asistant to control Matter devices?

    Best Regards,

    Michal

  • Hi Michal,

    Matter SDK 1.0 is integrated into NCS since v2.1.1 and its support for Matter over Thread is no longer experimental, so it is better to start your development with NCS above v2.1.1.

    For Google Home, the developer preview update of Google Nest Hub 2nd which supports Mater 1.0 may still not reach your device. We have a customer who successfully tested NCSv2.1.0 with the alpha beta update channel, but it is not clear for NCS v2.1.1 or NCS v2.1.2, because even our device did not get updated yet. The out-of-data guidance using NCS1.7.1 should still work, we expect google will have an update for support on the Matter 1.0 device.

    For  Apple HomePod mini/Samsung SmartThings hub v3, we have confirmed they work well with NCS v2.1.1, if you have any problem you can open a dedicated ticket to discuss.

    You can refer to the comment here: https://devzone.nordicsemi.com/support-private/support/298036#permalink=805302

    Bes regards,

    Charlie

  • Thank you Charlie for clarification. I was digging into this subject the whole night to find out why commissioning to Google fabric is not working. I already applied the google patch dedicated for NCS1.7.1  to  NCS2.1.1  (as it was not possible to find a newer one).  I was following https://developers.home.google.com/matter/vendors/nordic-semiconductor guidance once doing that. It goes halfway through  with commissioning (at the end  Google Home App  says that  BR is needed - all devices are in the same network with newer firmware and I can easily have ping between themselves and the internet)
    Looks like I need to wait for Nordic or  Google official  SDK/Patch - but at least I know to not look for a reason why it's not working (it was not so obvious why it's not working when you take into consideration that NCS1.7.1 with patch has this possibility)

    Thanks to your help we can switch to Apple and I hope in meantime we hope you will be able to provide a solution for Google:)  Do you think on November Nordic Webinar I can get more feedback about it?

  • Hi!

    Michal P said:
    Do you think on November Nordic Webinar I can get more feedback about it?

    Unfortunately you will have to wait and see about whether or not this will be mentioned. However, I believe there will be a Q&A part, so you could always ask yourself.

    Regards,

    Elfving

Related