v3.0 to v3.1 migration guide? WiFi not working...

[brp80000]

Sorry, where can I see "commit ID be115ec3ab28f7bbea3f4c7e5be3dd6b17bb8912"?

[brp80000]

WiFi is still not working ... it's starting to get very nervous. I am very disappointed with ESP32 and the support here

[luisonoff]

If you are not finding here the support you expected, try creating a new issue on the IDF github repository, attaching everything you can and logs and code and how it is failing, etc. I am sure they will take a look at it, please be patient because it is chinese new year holiday, until February 15th aprox.

[brp80000]

Sorry for the issue introduced in IDFv3.1.2. We have found the root cause. And it will be fixed in release/v3.1 branch today. The commit ID will be be115ec3ab28f7bbea3f4c7e5be3dd6b17bb8912. Please update IDF after the bugfix is merged into release/v3.1 and check whether it solves your problem.

I am update IDF ... WiFi is still not working
where can I see "commit ID be115ec3ab28f7bbea3f4c7e5be3dd6b17bb8912"?

[brp80000]

https://github.com/espressif/esp32-wifi-lib
0c5f3d45865423caa1f3069ecff905420641220b
I am download .zip and rewrite C:\msys32\home\myname\esp\esp-idf-v3.1.2\components\esp32\lib directory.
It`s solve my problem. Happy chinese new year to all
Thanks for supporting me(((

[meowsqueak]

Now I've got my thread back...

Unfortunately updating to the head of master for esp32-wifi-lib as suggested by brp80000 hasn't sorted out my problems with v3.1.2. In particular, approximately once in 5 or 10 resets I will see the WiFi connect, but the log will fill with the following message every second:

Code: Select all

W (8315) wifi: Haven't to connect to a suitable AP now!

A soft reset or reset via pin doesn't clear this condition. The only way I've been able to get past this is by power-cycling the ESP32. Then it will work for the next 5-10 resets until this situation happens again.

I worked with v3.0 for many months and never saw this happen. This is definitely new behaviour for me in v3.1.

[meowsqueak]

Just bumping this because WiFi behaviour has definitely regressed in 3.1 (compared to 3.0) and I think it's a major issue as it requires a hard power cycle to recover, which is impractical for many deployed IoT projects.

[ESP_Sprite]

Have you opened a bug on Github for this? If not, you may want to, it usually is tracked a bit easier there than a random forum post.

[permal]

FWIW, I've seen no issues whatsoever with Wifi. I'm always working against the tip of master so I've seen all the versions on my device and I do many, many, soft-resets while developing against my Wrover module.

Are you all sure that it is not something external affecting your wifi-connection?

[meowsqueak]

Have you opened a bug on Github for this? If not, you may want to, it usually is tracked a bit easier there than a random forum post.

I haven't, but I'll gather more info and put a report together. I'll test with master too.