blynkkk / blynk_Issues

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

AP IP: 0.0.0.0

whogarden opened this issue · comments

With esp 2.0.0-rc1 and Blynk v1.0.1
An esp32 device flashed with Edgent_ESP32
gives : an AP with IP = 0.0.0.0
[114] Using default config.
[213]
___ __ __
/ _ )/ /_ _____ / /__
/ _ / / // / _ / '/
/
//_, /////_
/
__/ v1.0.1 on ESP32

[215] --------------------------
[218] Product: ESP32free
[220] Hardware: 1.0.0
[222] Firmware: 0.1.2 (build Jul 22 2021 15:03:08)
[227] Device: ESP32 @ 240MHz
[230] MAC: 30:AE:A4:02:3B:C4
[233] Flash: 4096K
[235] ESP sdk: v4.4-dev-2030-gd93887f9f-dirty
[239] Chip rev: 0
[241] Free mem: 226583
[243] --------------------------
[246] INIT => WAIT_CONFIG
[2850] AP SSID: Blynk ESP32free-CC7F2
[2850] AP IP: 0.0.0.0
[2851] AP URL: blynk.setup

commented

Check your router to have DHCP enabled please. Otherwise run Manual Connect during the device provision procedure.

Thank you for this reply.
DHCP is enabled.
And manual connect don't work because the AP IP is 0.0.0.0

It was working with esp32 version 1.0.5.
then I upgraded to new versions but :
It's not working with version 2.0.0.alpha1 (this version can not generate binaries)
It's not working with version 2.0.0.rc1 (this version can generate binaries).
I am now back to esp32 version 1.0.5
(with esp8266 3.0.1 AP IP is 192.168.4.1)
it's like this :
[527] Using default config.
[527]
___ __ __
/ _ )/ /_ _____ / /__
/ _ / / // / _ / '/
/
//_, /////_
/
__/ v1.0.1 on ESP8266

[534] --------------------------
[537] Product: Roller Shutter
[540] Hardware: 1.0.0
[542] Firmware: 0.1.0 (build Aug 6 2021 09:11:09)
[546] Device: ESP8266 @ 80MHz
[549] MAC: C4:5B:BE:4D:C5:C3
[552] Flash: 4096K
[554] ESP core: 3.0.2
[556] ESP SDK: 2.2.2-dev(38a443e)
[559] Boot Ver: 7
[561] Boot Mode:1
[563] FW info: 467040/491520, MD5:ebf15baad14a29d9cf86c8f8cbbb1094
[776] Free mem: 32552
[776] --------------------------
[776] INIT => WAIT_CONFIG
[1387] AP SSID: Blynk Roller Shutter-3E7F6
[1387] AP IP: 192.168.4.1
[1388] AP URL: blynk.setup

Can it be an esp32 issue?

commented

Yes, this could be due to unstable ESP32 core versions.
We recommend to use stable versions (1.0.6 is the latest one).

@Mark-Pan @vshymanskyy add to doc troubleshooting section?

Added to the docs

@whogarden please close the issue if it's fixed by using the stable ESP Core.

@vshymanskyy let's close by default, and reopen if not fixed. Link to doc also would be helpful in case anyone will google this issue and not doc.

https://docs.blynk.io/en/getting-started/activating-devices/blynk-edgent-wifi-provisioning#esp-32-esp-8266-specific-issues