espressif / esp-rainmaker

ESP RainMaker Agent for firmware development
Apache License 2.0
431 stars 145 forks source link

Problem with WiFi setup (MEGH-4722) #270

Closed TKBeckum closed 1 year ago

TKBeckum commented 1 year ago

Answers checklist.

IDF / ESP32-Arduino version.

ESP- Arduino 2.0.9

Operating System used.

macOS

How did you build your project?

Arduino IDE

Development Kit.

ESP-WROOM-32

What is the expected behavior?

I try to use the rainmaker software on a device. I used the switch example. I expected in installs correctly

What is the actual behavior?

It is compiling and loading correctly, producing the QR-code. When using the QR-code to setup the device, the Rainmaker app is connecting, and I chose the correct network and pwd, but at the second item (confirming network) it reacts with: WiFi-status: authentication error.

Steps to reproduce.

  1. Step compiling the switch example
  2. Step uploading to device
  3. Step getting QR-code
  4. Step Using Rainmaker app (on IOS)
  5. Step App is connecting
  6. Step I choose the right Wifi network and pwd
  7. Step at the second item (confirming network) it reacts with: WiFi-status: authentication error. ...

Debug Logs.

No logs

More Information.

No

shahpiyushv commented 1 year ago

WiFi-status: authentication error is indeed received if there is Wi-Fi authentication failure. On your device serial terminal, do you see that the device eventually connected to the AP, or does it just indicate error? Does your access point have any additional settings which may disallow new devices to join directly? Can you try with a different access point, may be a simple hotspot?

TKBeckum commented 1 year ago

Thanks for your response. I am afraid something wrong with the device. Bought three of them together, but none of them works. Tried to establish connection to the WiFi with the simple ESP32 WiFi example (hard coding the WiFi credentials, but that also didn't work (see attachment; I disguised my SSID and BSSID in the output). What is your opinion?

On Thu, 15 Jun 2023 at 11:04, Piyush Shah @.***> wrote:

WiFi-status: authentication error is indeed received if there is Wi-Fi authentication failure. On your device serial terminal, do you see that the device eventually connected to the AP, or does it just indicate error? Does your access point have any additional settings which may disallow new devices to join directly? Can you try with a different access point, may be a simple hotspot?

— Reply to this email directly, view it on GitHub https://github.com/espressif/esp-rainmaker/issues/270#issuecomment-1592654548, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKQTGRU7XIKU56R4HGVUVPDXLLFZXANCNFSM6AAAAAAZGJAN44 . You are receiving this because you authored the thread.Message ID: @.***>

TKBeckum commented 1 year ago

An update: after erasing all flash with esptool, now rainmaker is working! Thanks for your attention.

On Thu, 15 Jun 2023 at 15:44, Theo van der Krogt @.***> wrote:

Thanks for your response. I am afraid something wrong with the device. Bought three of them together, but none of them works. Tried to establish connection to the WiFi with the simple ESP32 WiFi example (hard coding the WiFi credentials, but that also didn't work (see attachment; I disguised my SSID and BSSID in the output). What is your opinion?

On Thu, 15 Jun 2023 at 11:04, Piyush Shah @.***> wrote:

WiFi-status: authentication error is indeed received if there is Wi-Fi authentication failure. On your device serial terminal, do you see that the device eventually connected to the AP, or does it just indicate error? Does your access point have any additional settings which may disallow new devices to join directly? Can you try with a different access point, may be a simple hotspot?

— Reply to this email directly, view it on GitHub https://github.com/espressif/esp-rainmaker/issues/270#issuecomment-1592654548, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKQTGRU7XIKU56R4HGVUVPDXLLFZXANCNFSM6AAAAAAZGJAN44 . You are receiving this because you authored the thread.Message ID: @.***>