Controller commissioning cannot be completed with Rainmaker App (MEGH-5843)

[Shivi-6]

Answers checklist.

• I have read the Rainmaker documentation and the issue is not addressed there.
• I have updated my IDF branch (release/vX.Y) to the latest version and checked that the issue is present there. This is not applicable if you are using Rainmaker with Arduino.
• I have searched the Rainmaker forum and issue tracker for a similar issue and not found a similar issue.

General issue report

IDF branch : release/v5.3
Rainmaker branch : latest

After flashing the matter controller example on esp32-wrover kit (16mb flash), on commissioning, the app generates matter credentials, connects to the network but while connecting to the rainmaker app, it stops and "something went wrong" pop-up appears.
The error appears to be some transmit error from the logs :

I (174731) chip[EM]: >>> [E:4718r S:48611 M:70730357] (S) Msg RX from 2:DD673B6E2D2F91D5 [2387] --- Type 0001:02 (IM:ReadRequest)
I (174741) chip[EM]: <<< [E:4718r S:48611 M:8822237 (Ack:70730357)] (S) Msg TX to 2:DD673B6E2D2F91D5 [2387] [UDP:192.168.1.107:46943] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (174761) chip[EM]: <<< [E:4718r S:48611 M:8822238 (Ack:70730357)] (S) Msg TX to 2:DD673B6E2D2F91D5 [2387] [UDP:192.168.1.107:46943] --- Type 0001:05 (IM:ReportData)
I (174781) chip[EM]: >>> [E:4717r S:48611 M:70730358 (Ack:8822236)] (S) Msg RX from 2:DD673B6E2D2F91D5 [2387] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (174841) chip[EM]: >>> [E:4718r S:48611 M:70730359 (Ack:8822238)] (S) Msg RX from 2:DD673B6E2D2F91D5 [2387] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (174851) chip[EM]: >>> [E:4719r S:48611 M:70730360] (S) Msg RX from 2:DD673B6E2D2F91D5 [2387] --- Type 0001:02 (IM:ReadRequest)
I (174861) chip[EM]: <<< [E:4719r S:48611 M:8822239 (Ack:70730360)] (S) Msg TX to 2:DD673B6E2D2F91D5 [2387] [UDP:192.168.1.107:46943] --- Type 0001:05 (IM:ReportData)
I (175041) chip[EM]: >>> [E:4719r S:48611 M:70730361 (Ack:8822239)] (S) Msg RX from 2:DD673B6E2D2F91D5 [2387] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (175051) chip[EM]: >>> [E:4720r S:48611 M:70730362] (S) Msg RX from 2:DD673B6E2D2F91D5 [2387] --- Type 0001:02 (IM:ReadRequest)
I (175061) chip[EM]: <<< [E:4720r S:48611 M:8822240 (Ack:70730362)] (S) Msg TX to 2:DD673B6E2D2F91D5 [2387] [UDP:192.168.1.107:46943] --- Type 0001:05 (IM:ReportData)
I (175411) chip[EM]: Retransmitting MessageCounter:8822240 on exchange 4720r Send Cnt 1
I (175791) chip[EM]: Retransmitting MessageCounter:8822240 on exchange 4720r Send Cnt 2
I (176351) chip[EM]: Retransmitting MessageCounter:8822240 on exchange 4720r Send Cnt 3
I (177341) chip[EM]: Retransmitting MessageCounter:8822240 on exchange 4720r Send Cnt 4
**E (178961) chip[EM]: Failed to Send CHIP MessageCounter:8822240 on exchange 4720r sendCount: 4 max retries: 4
I (178961) chip[SC]: SecureSession[0x3ffc68e8, LSID:48611]: State change 'kActive' --> 'kDefunct'**
I (231111) wifi:[ADDBA]RX DELBA, reason:39, delete tid:0, initiator:1(originator)

Performing the same steps using another kit with esp32-s3 (8mb flash), it connects successfully and shows up as a controller in the rainmaker app.

What is the reason that the same process works with esp32-s3 and not with esp32?

[Shivi-6]

The issue is resolved on increasing the Timeout value. I am now able to connect the controller with Rainmaker and control end devices from app as well as console.