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.  

Parents
  • hi

    I'm experiencing the same issue after Google Nest 2th matter 1.0 update on 12/19.

    During commissioning, a BLE terminate event is sent to the thread.

    I: 50520 [DL]BLE GAP connection terminated (reason 0x13)

    D: 50526 [IN]Clearing BLE pending packets.

    Are there any successful cases of commissioning with the Google Nest 2th hub for users who use the Nordic thread module for this problem?

    After Google Nest hub 2th generation new firmware release on 12/13, Nethub 2th firmware was updated.
    (https://support.google.com/googlenest/answer/7365257?hl=en#zippy=%2Ccurrent-preview-program-firmware-version)

    And I checked the release notes on 12/15 and configured the environment for the Matter 1.0 test.
    (https://developers.home.google.com/matter/release-notes)

    But it doesn't pair with the thread module. My thread module is a Light bulb sample model.
    Prior to the Matter 1.0 update, it paired normally.

    Issue step

    1-1 Thread module Power on (nordic nrf52840 <- Supports Matter 1.0 (use to sdk 2.2.0)
    1-2 Enter Google Home (Nest hub 2th registered)
    1-3 add and manage
    1-4 Set up devcie
    1-5 New device
    1-6 found matter device
    1-7 Scan Matter QR code
    1-8 Connecting device to google home..
    1-9 pairing failed

    The above issue is 100% reproducible.

    My Developer Console
    https://drive.google.com/file/d/1njXeuUD9bBvl7k8SI6NhQSHJsPNH9H4z/view?usp=sharing

    reproduce video
    https://drive.google.com/file/d/1TRbETcwY6YJobEYTo2NUoVxXFOSL9_ca/view?usp=sharing

    Google Nest hub 2th fw version
    https://drive.google.com/file/d/1YNPXQSOzReG6HJFs2ZRZV0O943MyQVhk/view?usp=sharing

    issue log
    https://drive.google.com/file/d/1sX0YCvFKEOkW_n-Tl7-wImFNqq0gTxwF/view?usp=share_link

    D: 48502 [DMG]Command handler moving to [ Preparing]

    D: 48507 [DMG]Command handler moving to [AddingComm]

    D: 48512 [DMG]Command handler moving to [AddedComma]

    D: 48517 [DMG]Decreasing reference count for CommandHandler, remaining 0

    I: 48525 [EM]<<< [E:31821r M:46579253] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)

    I: 48536 [IN](S) Sending msg 46579253 on secure session with LSID: 22045

    D: 48542 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)

    D: 48550 [DMG]Command handler moving to [CommandSen]

    D: 48555 [DMG]Command handler moving to [AwaitingDe]

    E: 48559 [DL]Long dispatch time: 326 ms, for event type 16388

    D: 48630 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

    D: 48638 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)

    D: 48720 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

    D: 48728 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 127)

    D: 48810 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

    I: 50520 [DL]BLE GAP connection terminated (reason 0x13)

    D: 50526 [IN]Clearing BLE pending packets.

    I: 50530 [DL]Current number of connections: 0/1

    I: 165904 [FS]Fail-safe timer expired

    E: 165908 [SVR]Failsafe timer expired

    D: 165911 [IN]SecureSession[0x20003500]: MarkForEviction Type:1 LSID:22045

    I: 165918 [SC]SecureSession[0x20003500]: Moving from state 'kActive' --> 'kPendingEviction'

    D: 165926 [IN]SecureSession[0x20003500]: Released - Type:1 LSID:22045

    E: 165932 [SVR]Commissioning failed (attempt 1): 32

    D: 165938 [IN]SecureSession[0x20003500]: Allocated Type:1 LSID:22047

    D: 165944 [SC]Assigned local session key ID 22047

    D: 165949 [SC]Waiting for PBKDF param request

    D: 165953 [DL]CHIPoBLE advertising set to on

    I: 165957 [DIS]Updating services using commissioning mode 1

    D: 165962 [DL]Using Thread extended MAC for hostname.

    D: 165967 [DL]Using Thread extended MAC for hostname.

    I: 165972 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1

    E: 165981 [DIS]Failed to advertise commissionable node: 3

    E: 165986 [DIS]Failed to finalize service update: 1c

    E: 165991 [ZCL]OpCreds: Got FailSafeTimerExpired

    E: 165995 [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!

    I: 166002 [TS]Pending Last Known Good Time: 2022-12-20T13:22:06

    I: 166008 [TS]Previous Last Known Good Time: 2022-12-20T13:22:06

    I: 166014 [TS]Reverted Last Known Good Time to previous value

    D: 166020 [DMG]Endpoint 0, Cluster 0x0000_0030 update version to 53616286

    D: 166026 [ZCL]Failsafe timeout, tell platform driver to revert network credentials.

    E: 166034 [DL]Long dispatch time: 126 ms, for event type 32782

    I: 166039 [FS]Fail-safe cleanly disarmed

    I: 166045 [DL]CHIPoBLE advertising started

    I: 166050 [DL]NFC Tag emulation started

    I: 196050 [DL]CHIPoBLE advertising mode changed to slow

  • I encountered the same problem the week before christmas (not tested again since then, I'll try to do it next week). My local setup was the same as in my earlier post in this thread. same Versions on the Nest Hub and my nRF light_bulb (and the same with an ESP32). Except that the GHA got updated to v2.62.1.9.

    During the time my setup was working I made a test out of curiosity and found out, that with the Google setup "every Matter command" goes to the server in the first place and then comes back to the local setup (so with Google it is not a 100% local setup, which Matter advertises).

    My guess now is that the updates of the server and the app must "align" or match. But because the distribution is spread through time this is not guaranteed. If someone has a better clue, please tell me!

    See also my Google issue: https://issuetracker.google.com/issues/262773689

Reply
  • I encountered the same problem the week before christmas (not tested again since then, I'll try to do it next week). My local setup was the same as in my earlier post in this thread. same Versions on the Nest Hub and my nRF light_bulb (and the same with an ESP32). Except that the GHA got updated to v2.62.1.9.

    During the time my setup was working I made a test out of curiosity and found out, that with the Google setup "every Matter command" goes to the server in the first place and then comes back to the local setup (so with Google it is not a 100% local setup, which Matter advertises).

    My guess now is that the updates of the server and the app must "align" or match. But because the distribution is spread through time this is not guaranteed. If someone has a better clue, please tell me!

    See also my Google issue: https://issuetracker.google.com/issues/262773689

Children
  • HI,  close to Christmas I got a similar problem again. I got support from Google - they mention that for some reason they got some problems with Google Home App which cause the device to be seen offline and you cannot control it. 
    The solution in my case was Nest Hub gen.2  factory reset (with volume button), then removing cache  Google Home App on phone settings, then removing  Google Home App from the phone, and then fresh install from Google Play Store. I hope it will help if anyone will get similar problem Slight smile

Related