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

"Failed to associate device." in Sending Wi-Fi Credentials in ESP Rainmaker App. (MEGH-5828) #322

Closed
3 tasks done
santoshurlam opened this issue Jul 25, 2024 · 14 comments
Closed
3 tasks done

Comments

@santoshurlam
Copy link

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

Wi-Fi Connectivity Issue with RainMaker App

When I'm running a example code of RMaker Switch, it was providing QR code and after scanning QR code through the ESP Rainmaker app after providing Wi-Fi credentials it is showing error in step 1 Sending Wi-Fi credentials: "Failed to associate device.".

  1. I have tried with BLE and Softap provisioning but not worked.
  2. I have tried with different Wi-Fi networks and also even by changing its security levels from WPA/WPA2 to open but not worked.
  3. I have tried asking chatgpt4.0 to modify the existing example code to get rid of those errors that I'm getting in Serial Monitor .
  4. I have changed all the settings which are suggested in the internet but not worked .
  5. I have degraded my ide, board versions as suggested in internet but didn't worked.
  6. Even I have changed the Wi-Fi settings in my mobile through developer options but, didn't worked.
    esp rmaker error

The errors I got in serial monitor were ;
Screenshot 2024-07-25 171154

I'm using ESP32-WROOM 32D with Arduino ide version 2.3.2 and esp32 board manager version 3.0.2 .
Anyone give me some suggestions on to get over with this issue.
These are the tools settings I'm using and some I altered the settings also but didn't worked.
Screenshot 2024-07-25 181344

@github-actions github-actions bot changed the title "Failed to associate device." in Sending Wi-Fi Credentials in ESP Rainmaker App. "Failed to associate device." in Sending Wi-Fi Credentials in ESP Rainmaker App. (MEGH-5828) Jul 25, 2024
@shahpiyushv
Copy link
Collaborator

Can you try by setting Partition Scheme as RainMaker, as mentioned in this README ?

@santoshurlam
Copy link
Author

Can you try by setting Partition Scheme as RainMaker, as mentioned in this README ?

Yeah I've tried that also but didn't worked , it gave bootloop in serial monitor.

@shahpiyushv
Copy link
Collaborator

@santoshurlam , serial monitor logs with the correct partition table?

@santoshurlam
Copy link
Author

@santoshurlam , serial monitor logs with the correct partition table?

I have used partition scheme : "RainMaker" but gave bootloop in serial monitor and then I've tried using "Huge APP" partition scheme atleast gave QR code but got the "Failed to associate device " issue in rainmaker app, as I've already mentioned above.

@shahpiyushv
Copy link
Collaborator

@santoshurlam , yes you have mentioned in the comment above that "it gave bootloop in serial monitor ", but it is not clear what you mean here. Is your device rebooting continuously? It can happen in one of the 2 cases:

  1. The bootloader did not find a valid firmware
  2. The firmware loaded but crashed due to some reason.

Without any logs for this scenario, we cannot say what the issue is. If the firmware itself was faulty, even in the first case, you wouldn't see any logs. Change in partition table does not change the firmware.

@santoshurlam
Copy link
Author

@santoshurlam , yes you have mentioned in the comment above that "it gave bootloop in serial monitor ", but it is not clear what you mean here. Is your device rebooting continuously? It can happen in one of the 2 cases:

  1. The bootloader did not find a valid firmware
  2. The firmware loaded but crashed due to some reason.

Without any logs for this scenario, we cannot say what the issue is. If the firmware itself was faulty, even in the first case, you wouldn't see any logs. Change in partition table does not change the firmware.

sorry for not properly specifiying the issue.
But now I've used partition scheme : "Rainmaker" and after compiling and uploading , I've got these in serial monitor ;
Screenshot 2024-07-25 222306
Correct me if I'm wrong anywhere bcoz I'm kinda new to this.
And also the tools settings which I've used this time ;
Screenshot 2024-07-25 222827

@shahpiyushv
Copy link
Collaborator

Seems the firmware is not flashed correctly on your device. After you change the partition table, please try enabling the "Erase All Flash Before Sketch Upload" option in the settings shown above and then recompile and re-flash.

@santoshurlam
Copy link
Author

Seems the firmware is not flashed correctly on your device. After you change the partition table, please try enabling the "Erase All Flash Before Sketch Upload" option in the settings shown above and then recompile and re-flash.

Sadly , I've tried now but same thing happened again like above.

@shahpiyushv
Copy link
Collaborator

"As above" could mean 2 different things. The original issue or the one after correcting the partition table. For the latter, you haven't shared any logs so can't say if bootloader itself hasn't loaded or if firmware hasn't loaded or if firmware has loaded but crashing continuously.

@AntonKozlenko1969
Copy link

The same problem. How can I fix this to move on?
platform 3.0.4
QR - ok
Error

Led flashing on button
BLE normal

@shahpiyushv
Copy link
Collaborator

@AntonKozlenko1969 In the original issue, the flash partition scheme was wrong, throwing nvs errors. When that was fixed, it was mentioned that the device keeps rebooting (but no logs were shared).

In your case, I see that you have shown that partition table is correct and QR code is printed. So not sure what you mean by "Same problem". Can you elaborate and share screenshots of phone app showing error and the corresponding serial terminal log ? Most of your log before the QR code is also hidden, so the info is incomplete.

@AntonKozlenko1969
Copy link

AntonKozlenko1969 commented Aug 5, 2024 via email

@AntonKozlenko1969
Copy link

AntonKozlenko1969 commented Aug 21, 2024 via email

@shahpiyushv
Copy link
Collaborator

Closing this as the issue was eventually resolved.

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

3 participants