Matter Light Bulb fail commissioning in HA or Google Home

[vorrias]

Hi,
I am preparing my project for “MAKE IT MATTER” contest and I am running out of time.
So please help me if you can

Problems:
1 - I can not see the nRF7002-DK to be part of the Thread network
2 - I can not commission on the Matter Server the nRF7002-DK  running the Matter:Light bulb Application

In OTBR web  JOIN I can not see any connected  device. I suppose I must see the nRF7002-DK running Matter:Light bulb  
How can I achieve that?

What I have done:

1 - Build  Matter:Light bulb Application  following the example:
docs.nordicsemi.com/.../README.html

Board is working, buttons and LED s are working as in example.
LED is blinking slow waiting to commission.

2 - Configure OpenThread Radio Co-processor (RCP) on nRF52840 Dongle
Plug it into Raspberry Pi (running the OTBR)

3 - OTBR installed. Web page can be seen. OTBR  is LEADER
Looks that the nRF52840 dongle recognized as seen from WEB interface

Then I started the commissioning procedure using smartphone in two different Matter servers
I have the same results commissioning with NFC or QR code
The commissioning is going well until a point that reports unable to connect

Tests running on:

A) Home Assistant Mater Server.
HA is running in my local network. OTBR + nRF82540 dongle is connected on that network as well
This server is working OK . I have already commissioned a commercial plug using the QR without any problems

B) Google Home app in my smartphone

Results:

IN HOME ASSISTANT
- (LED blinking slow)
- Connect with the device  (LED blinking fast)
- Create Matter credentials (LED blinking fast)
- Check network connectivity (LED solid)
- inability to connect to the device. Make sure your phone is connected to Wi-Fi

IN GOOGLE HOME APP
- (LED blinking slow)
- Connect with the device  (LED blinking fast)
- Create Matter credentials (LED blinking fast)
- Uncertified device. It is not possible to configure this device with Google

What am I doing wrong?

Thank you

Vasilis

Some screenshots from OTBR web

[vorrias]

OK Maria,
Still not able to commission.
That is what I did:
1 - wifi_credentials/Kconfig in original state.
2 - add lines into prj.conf file:

CONFIG_WIFI_CREDENTIALS_STATIC=y

CONFIG_WIFI_CREDENTIALS_STATIC_SSID="LAB2"

CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD="password"

LAB2 is a closer hot spot with stronger signal
Smartphone also connected to LAB2
3 - Rebuild the nrf7002dk_nrf5340_cpuapp board
4 - In ACTIONS:
Build
Flash

I am sending bot commissioning GH and HA
The procedure goes well registering the device. Only final sate when connecting to Network fails.
On that stage LED is solid ON. Then after failure drops into commissioning mode
In Google Home message final message is :

"Something went wrong
Make sure you are connected to your network and try again"

In Home Assistant
"Can't connect to your device
Check your device instructions"


I don't know if it matters but in PROBLEMS tab I see a message No such file or directory".....
see image. Is this a problem?

Is that so difficult tro do? Looks a detailed is missing
Is anybody in Nodric did that?
Please advise me. I am stacked
Regards
Vasilis

Fullscreen 0435.log file commissionning in google home.txt Download

I: 30542 [DL]CHIPoBLE advertising mode changed to slow
I: 30550 [DL]CHIPoBLE advertising started
I: 41379 [DL]BLE connection established (ConnId: 0x00)
I: 41384 [DL]Current number of connections: 1/1
I: 41389 [DL]CHIPoBLE advertising stopped
I: 41392 [DL]NFC Tag emulation stopped
D: 42325 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 42332 [BLE]local and remote recv window sizes = 5
I: 42336 [BLE]selected BTP version 4
I: 42340 [BLE]using BTP fragment sizes rx 128 / tx 128.
D: 42347 [DL]ConnId: 0x00, New CCCD value: 0x0002
D: 42352 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
D: 42359 [IN]BLE EndPoint 0x2000ae00 Connection Complete
I: 42364 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 131)
D: 42491 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 42626 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 42634 [EM]>>> [E:58343r S:0 M:130127054] (U) Msg RX from 0:A830FE246DEFFF81 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I: 42647 [EM]<<< [E:58343r S:0 M:53953585] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I: 42658 [IN](U) Sending msg 53953585 to IP address 'BLE'
D: 42664 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 42761 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 42768 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 14)
D: 42851 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 42859 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 42866 [EM]>>> [E:58343r S:0 M:130127055] (U) Msg RX from 0:A830FE246DEFFF81 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
I: 44235 [EM]<<< [E:58343r S:0 M:53953586] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I: 44246 [IN](U) Sending msg 53953586 to IP address 'BLE'
D: 44251 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
E: 44259 [DL]Long dispatch time: 1400 ms, for event type 16388
D: 44379 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 44387 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
D: 44469 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 44478 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 44485 [EM]>>> [E:58343r S:0 M:130127056] (U) Msg RX from 0:A830FE246DEFFF81 [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
I: 44497 [EM]<<< [E:58343r S:0 M:53953587] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
I: 44508 [IN](U) Sending msg 53953587 to IP address 'BLE'
D: 44513 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 35)
I: 44522 [SC]SecureSession[0x200041e0]: Moving from state 'kEstablishing' --> 'kActive'
D: 44530 [IN]SecureSession[0x200041e0]: Activated - Type:1 LSID:62092
D: 44536 [IN]New secure session activated for device <FFFFFFFB00000000, 0>, LSID:62092 PSID:60093!
I: 44544 [SVR]Commissioning completed session establishment step
I: 44550 [DIS]Updating services using commissioning mode 0
I: 44556 [DIS]CHIP minimal mDNS started advertising.
D: 44561 [DL]CHIPoBLE advertising set to off
I: 44565 [SVR]Device completed Rendezvous process
D: 44604 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 44613 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 44621 [EM]>>> [E:58344r S:62092 M:260939178] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D: 44631 [IM]Received Read request
I: 44636 [EM]<<< [E:58344r S:62092 M:173049266] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I: 44647 [IN](S) Sending msg 173049266 on secure session with LSID: 62092
D: 44653 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 97)
D: 44740 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 47260 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 49767 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 49914 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 52480 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 54987 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 55089 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 57610 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 60117 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 60175 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 62740 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 65247 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 65350 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 67870 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 70377 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 70435 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 73000 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 75507 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 75610 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
I: 76600 [DL]BLE GAP connection terminated (reason 0x13)
D: 76605 [IN]Clearing BLE pending packets.
I: 76609 [DL]Current number of connections: 0/1
I: 104565 [FS]Fail-safe timer expired
E: 104569 [SVR]Failsafe timer expired
D: 104572 [IN]SecureSession[0x200041e0]: MarkForEviction Type:1 LSID:62092
I: 104579 [SC]SecureSession[0x200041e0]: Moving from state 'kActive' --> 'kPendingEviction'
D: 104587 [IN]SecureSession[0x200041e0]: Released - Type:1 LSID:62092
E: 104593 [SVR]Commissioning failed (attempt 1): 32
D: 104598 [IN]SecureSession[0x200041e0]: Allocated Type:1 LSID:62094
D: 104604 [DL]CHIPoBLE advertising set to on
I: 104608 [DIS]Updating services using commissioning mode 1
I: 104613 [DIS]CHIP minimal mDNS started advertising.
D: 104618 [DL]Using wifi MAC for hostname
I: 104622 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
D: 104631 [DIS]Responding with _matterc._udp.local
D: 104636 [DIS]Responding with 10401FF08571A2FC._matterc._udp.local
D: 104642 [DIS]Responding with F4CE36001DFE.local
D: 104646 [DIS]Responding with F4CE36001DFE.local
D: 104651 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 104656 [DIS]Responding with _S15._sub._matterc._udp.local
D: 104662 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 104667 [DIS]Responding with _CM._sub._matterc._udp.local
D: 104673 [DIS]Responding with 10401FF08571A2FC._matterc._udp.local
I: 104679 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 10401FF08571A2FC.
I: 104689 [DIS]mDNS service published: _matterc._udp
E: 104693 [ZCL]OpCreds: Got FailSafeTimerExpired
E: 104697 [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
I: 104704 [TS]Pending Last Known Good Time: 2024-01-18T14:54:43
I: 104710 [TS]Previous Last Known Good Time: 2024-01-18T14:54:43
I: 104716 [TS]Reverted Last Known Good Time to previous value
E: 104721 [DL]Long dispatch time: 152 ms, for event type 32782
I: 104727 [FS]Fail-safe cleanly disarmed
I: 104733 [DL]CHIPoBLE advertising started
I: 104737 [DL]NFC Tag emulation started

Fullscreen 5226.log file commissionning in ha.txt Download

I: 224970 [DL]BLE connection established (ConnId: 0x00)
I: 224975 [DL]Current number of connections: 1/1
I: 224980 [DL]CHIPoBLE advertising stopped
I: 224983 [DL]NFC Tag emulation stopped
D: 225926 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 225933 [BLE]local and remote recv window sizes = 5
I: 225938 [BLE]selected BTP version 4
I: 225941 [BLE]using BTP fragment sizes rx 128 / tx 128.
D: 225948 [DL]ConnId: 0x00, New CCCD value: 0x0002
D: 225953 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
D: 225960 [IN]BLE EndPoint 0x2000ae00 Connection Complete
I: 225966 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 131)
D: 226092 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 226227 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 226235 [EM]>>> [E:58346r S:0 M:130127058] (U) Msg RX from 0:653972D48721474E [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I: 226248 [EM]<<< [E:58346r S:0 M:53953588] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I: 226260 [IN](U) Sending msg 53953588 to IP address 'BLE'
D: 226265 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 226362 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 226370 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 14)
D: 226452 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 226460 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 226468 [EM]>>> [E:58346r S:0 M:130127059] (U) Msg RX from 0:653972D48721474E [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
I: 227833 [EM]<<< [E:58346r S:0 M:53953589] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I: 227844 [IN](U) Sending msg 53953589 to IP address 'BLE'
D: 227849 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
E: 227857 [DL]Long dispatch time: 1397 ms, for event type 16388
D: 241571 [DL]ConnId: 0x00, New CCCD value: 0x0000
D: 241575 [IN]Clearing BLE pending packets.
I: 241579 [BLE]Releasing end point's BLE connection back to application.
I: 241585 [DL]Closing BLE GATT connection (ConnId 00)
D: 241706 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x0e)
E: 241713 [BLE]no endpoint for BLE sent data ack
I: 241718 [DL]BLE GAP connection terminated (reason 0x16)
I: 241723 [DL]Current number of connections: 0/1
I: 241730 [DL]CHIPoBLE advertising started
I: 241734 [DL]NFC Tag emulation started
I: 271735 [DL]CHIPoBLE advertising mode changed to slow
I: 271743 [DL]CHIPoBLE advertising started
E: 272833 [SC]PASESession timed out while waiting for a response from the peer. Expected message type was 36
D: 272843 [IN]SecureSession[0x200041e0]: Released - Type:1 LSID:62094
E: 272849 [SVR]Commissioning failed (attempt 2): 32
D: 272854 [IN]SecureSession[0x200041e0]: Allocated Type:1 LSID:62095
I: 272860 [DIS]Updating services using commissioning mode 1
I: 272865 [DIS]CHIP minimal mDNS started advertising.
D: 272871 [DL]Using wifi MAC for hostname
I: 272874 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
D: 272884 [DIS]Responding with _matterc._udp.local
D: 272888 [DIS]Responding with 10401FF08571A2FC._matterc._udp.local
D: 272894 [DIS]Responding with F4CE36001DFE.local
D: 272899 [DIS]Responding with F4CE36001DFE.local
D: 272903 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 272909 [DIS]Responding with _S15._sub._matterc._udp.local
D: 272914 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 272920 [DIS]Responding with _CM._sub._matterc._udp.local
D: 272925 [DIS]Responding with 10401FF08571A2FC._matterc._udp.local
I: 272931 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 10401FF08571A2FC.
I: 272941 [DIS]mDNS service published: _matterc._udp

[Maria Gilje]

Hi Vasilis,

vorrias said:

I am sending bot commissioning GH and HA
The procedure goes well registering the device. Only final sate when connecting to Network fails.
On that stage LED is solid ON.

Which LED is solid ON? This is OK if it is LED2, based on the User Interface overview.

Here are a couple of things you can test if you don't have already:

• Make sure that the light bulb device is factory reset before starting the commissioning process.
• Erase and flash the device to make sure that there are nothing outdated on the device causing issues.
• Follow the Testing and Commissioning instructions for the light bulb sample.
• Connect the DK to a terminal to see its logging output.

Best regards,

Maria

[vorrias]

Hi Maria,

LED2 reports OK no problem.

Following your comments:

- Yes I am sure that the light bulb device is factory reset before starting the commissioning process.

- Yes it is fresh flash and there are nothing outdated 

- The testing and Commissioning is done using only one device the nRF7002-DK

- The terminal output is posted in previews post and it is the file 0435.log file commissionning in google home.txt

I do not have available now (soon may be) the nRF5340-DK to control the nRF7002-DL LED2 using nRF5340 switch.

I am trying to commission the nRF7002-DK to Google Home using this example

Connect with Google Nest Mini Hub:

https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/matter-testing-nrf-connect-sdk-platform-with-apple-google-and-samsung-ecosystems-218911247

I did everything as in example and in the end I have the message "can't reach device'.

If you see what the output is on the txt file posted before (0435.log file commissionning in google home.txt) you find that all stages are passed except the final.
Screen reports "preparing the device" after scanning the QR and connecting to Google Homer app. The app recognizes the nRF7002-DK and starts negotiating with it. This communication can be seen on the log file 0435.log file commissionning in google home.txt
That is true because after pooping the message  LED2 changes behavior (different flashing rate)

It proves that nRF7002-DK was discovered by Google Home app.

I am also sending the screenshots

   

Looks something is missed out.

Please advise if possible.

Regards

Vasilis

[Susheel Nuguru]

Sorry for the delayed response Vasilis, Maria is away and will be back to office on Monday. She will write to you then. Thanks for your patience so far.

[vorrias]

Thank you Susheel. No problem. I may have additional info on Monday from support given in contest's forum