Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to commission controller with rainmaker app (MEGH-5935) #329

Closed
3 tasks done
Shivi-6 opened this issue Aug 29, 2024 · 1 comment
Closed
3 tasks done

Not able to commission controller with rainmaker app (MEGH-5935) #329

Shivi-6 opened this issue Aug 29, 2024 · 1 comment

Comments

@Shivi-6
Copy link

Shivi-6 commented Aug 29, 2024

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

Hardware : ESP32-WROVER 16mb flash
Rainmaker sdk version : latest (main branch)
Rainmaker App version : latest as well as downgraded to 3.34

Steps :
cd $RMAKER_PATH/examples/matter/matter_controller
idf.py -p /dev/ttyUSB0 erase-flash
idf.py build
esptool.py -p /dev/ttyUSB0 write_flash 0x3e000 ....../partition.bin
cd $RMAKER_PATH/cli
rainmaker.py claim --matter /dev/ttyUSB0 --mac XXXXXXXXXX
cd $RMAKER_PATH/examples/matter/matter_controller
idf.py -p /dev/ttyUSB0 flash monitor

On app :
Connect to Wifi.
Open ESP Rainmaker app.
Add device
Scan the generated QR.
Wait for connection.

Issue:
After scanning QR code, the process gets stuck at generating matter credentials and then a pop-up comes to try again or exit setup with the following log :

I (36734) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: 86C1087DDB1024A5-8579D1AFDDBC996F.
I (36744) chip[DIS]: mDNS service published: _matter._tcp
D (36754) chip[DMG]: Endpoint 0, Cluster 0x0000_003E update version to d6ecb441
D (36754) chip[DMG]: Endpoint 0, Cluster 0x0000_003E update version to d6ecb442
D (36764) chip[DMG]: Command handler moving to [NewRespons]
D (36764) chip[DMG]: Command handler moving to [ Preparing]
D (36774) chip[DMG]: Command handler moving to [AddingComm]
D (36784) chip[DMG]: Command handler moving to [AddedComma]
I (36794) chip[ZCL]: OpCreds: successfully created fabric index 0x1 via AddNOC
D (36794) chip[DMG]: Decreasing reference count for CommandHandler, remaining 0
I (36804) chip[EM]: <<< [E:23566r S:47352 M:94146287 (Ack:49208700)] (S) Msg TX to 1:FFFFFFFB00000000 [24A5] [UDP:[FE80::909B:56FF:FE40:68DC%st1]:44889] --- Type 0001:09 (IM:InvokeCommandResponse)
D (36824) chip[DMG]: Command response sender moving to [AllInvokeR]
D (36824) chip[DMG]: Command handler moving to [AwaitingDe]
E (36824) chip[DL]: Long dispatch time: 839 ms, for event type 3
I (36844) chip[EM]: >>> [E:23565r S:47352 M:49208701 (Ack:94146283)] (S) Msg RX from 1:FFFFFFFB00000000 [24A5] --- Type 0000:10 (SecureChannel:StandaloneAck)
D (36854) chip[IN]: Received a duplicate message with MessageCounter:49208700 on exchange 23566r
I (36854) chip[EM]: >>> [E:23566r S:47352 M:49208700] (S) Msg RX from 1:FFFFFFFB00000000 [24A5] --- Type 0001:08 (IM:InvokeCommandRequest)
D (36874) chip[EM]: Found matching exchange: 23566r, Delegate: 0x0
D (36884) chip[EM]: Forcing tx of solitary ack for duplicate MessageCounter:49208700 on exchange 23566r
I (36894) chip[EM]: <<< [E:23566r S:47352 M:94146288 (Ack:49208700)] (S) Msg TX to 1:FFFFFFFB00000000 [24A5] [UDP:[FE80::909B:56FF:FE40:68DC%st1]:44889] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (36914) chip[EM]: >>> [E:23566r S:47352 M:49208702 (Ack:94146287)] (S) Msg RX from 1:FFFFFFFB00000000 [24A5] --- Type 0000:10 (SecureChannel:StandaloneAck)
D (36934) chip[EM]: Found matching exchange: 23566r, Delegate: 0x0
D (36934) chip[EM]: Rxd Ack; Removing MessageCounter:94146287 from Retrans Table on exchange 23566r
[0nD (127024) esp_netif_lwip: esp_netif_ip_lost_timer esp_netif:0x3ffd1bd4
D (127024) esp_netif_lwip: if0x3ffd1bd4 ip lost tmr: no need raise ip lost event
I (149874) chip[FS]: Fail-safe timer expired
E (149874) chip[SVR]: Failsafe timer expired
D (149874) chip[IN]: SecureSession[0x3ffb6db0]: MarkForEviction Type:1 LSID:47352
I (149894) chip[SC]: SecureSession[0x3ffb6db0, LSID:47352]: State change 'kActive' --> 'kPendingEviction'
D (149904) chip[IN]: SecureSession[0x3ffb6db0]: Released - Type:1 LSID:47352
E (149904) chip[SVR]: Commissioning failed (attempt 1): 32

Find the full log in attachment.
Debug log is enabled and default wifi ssid and password have been set in menuconfig.
ErrorLog.txt

@github-actions github-actions bot changed the title Not able to commission controller with rainmaker app Not able to commission controller with rainmaker app (MEGH-5935) Aug 29, 2024
@Shivi-6
Copy link
Author

Shivi-6 commented Sep 3, 2024

The issue is due to network issue. Hence closing the issue

@Shivi-6 Shivi-6 closed this as completed Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant