Hi @all,
I'm new here, so greets from Germany
I have a problem with a Wemos D1 mini clone (ESP8266) - I can't connect to webrepl. I tried firmwares 1.9.3, 1.8.7, stables, nightlies... Flashing with esptool went without errors, enabling webrepl via the serial repl worked as expected... I connect my PC to the AP of the ESP (IP 192.168.4.1), ping it to be sure, open the webrepl.html, and click 'Connect'. But instead of asking for the password I configured during webrepl_setup, the button changes to 'Disconnect' for a fraction of a second, and then immediately back to 'Connect'. No error message, nothing. The page looks just like after a fresh reload...
Any help would be much appreciated, thanks in advance!
Best regards,
René
Wemos D1 mini: no connection to WEBREPL
Re: Wemos D1 mini: no connection to WEBREPL
Are you using the default address when you click Connect ?
As a temporary workaround, you could try deploying the image https://github.com/vgkits/vanguard/blob ... -0.1.0.img which was created on a NodeMCU-M by running the deployall.py routine from https://github.com/vgkits/vanguard/tree ... /utilities and then backed up from the device as a firmware image. You can see a demo of a Webrepl session from that image at https://vgkits.org/blog/2018/05/08/intr ... -tutorial/ and the WebREPL is configured in https://github.com/vgkits/vanguard/blob ... es/boot.py if you aim to specialise your own deployall.py behaviour. The deployall.py script will quite likely autodetect a D1 mini and install a proper configuration for you if you are on Linux or Mac and maybe even windows. See config.py in that same folder for parameters.
The vanguard-0.1.0.img itself is intended for a 1MB device but should run correctly if it is flashed using the correct esptool.py parameters for a D1 mini, though the filesystem will be smaller than your 4MB. This is one benefit of using deployall.py which would target the device directly and create the proper size filesystem.
As a temporary workaround, you could try deploying the image https://github.com/vgkits/vanguard/blob ... -0.1.0.img which was created on a NodeMCU-M by running the deployall.py routine from https://github.com/vgkits/vanguard/tree ... /utilities and then backed up from the device as a firmware image. You can see a demo of a Webrepl session from that image at https://vgkits.org/blog/2018/05/08/intr ... -tutorial/ and the WebREPL is configured in https://github.com/vgkits/vanguard/blob ... es/boot.py if you aim to specialise your own deployall.py behaviour. The deployall.py script will quite likely autodetect a D1 mini and install a proper configuration for you if you are on Linux or Mac and maybe even windows. See config.py in that same folder for parameters.
The vanguard-0.1.0.img itself is intended for a 1MB device but should run correctly if it is flashed using the correct esptool.py parameters for a D1 mini, though the filesystem will be smaller than your 4MB. This is one benefit of using deployall.py which would target the device directly and create the proper size filesystem.