Let's Control It

You can add custom Commands using the serialcommands.txt way.

thanks

where do I find a list of available serial commands?

thanks Thomas

Not 100% complete list but here is the official commands:

https://espeasy.readthedocs.io/en/lates ... mmand.html

If you're missing something, give me a ping here.

thanks a lot

another question.

how can I set ip to dhcp via serial?

Thanks T

Set all DNS, gateway and IP to "0.0.0.0"

Thx

... hello again from Germany,

after a OS-crash last week I have installed the OS from scratch. Today now I download the Installer but have some Problems with it:

1. Fonts
I install the two fonts to the Windows folder more then twice but nothing helps. The Flasher show the right Font (I believe) but always open the both windows again telling me they can't find the Fonts.

2. GUI resolution
Have anybody try the Flasher on UHD? That is not realy funny if you need a Microscope to handle the Flasher (see Picture)

EDIT: ... and I can't open any firmware- File. Explorer opens but I can't chose one ...

Click save or CTRL+S and a settings file will appear in the settings folder. Open that file and change the pixels per inch value to something smaller (and save the file) and then start the flasher again.

... ty ... that works well. I have now set it to 96px and now it's ok.

The remaining problem is that the script folders pop up over and over again, no matter how often you install the fonts. That should be taken out of it completely. Simply put the reference to the fonts to be installed in a ReadMe and it is good

Yeah, I really need to update the Flasher.... Sorry for inconvenience.

... next problem ...

The Flasher don't find the active COM-port.

I use a flash- adapter ( see picture ) that use a CP10x from Silicon Labs. I also have some USB2SER and USB2I²C and USB21W that also use the same Chip.

The Flasher is known as COM6 but the Flashtool only see COM3 and COM4 as inactive (right). Now I have set the Flasher to COM1 but the same... They don't see them. Only if I overwrite the known COM3 or COM4 the tool see it... Is there an other way to flash ESPeasy to the ESP without using the Flashertool?


BTW:
For me it's not possible to flash with that Flasher... Nice idea, but what good is it if it just does not work?

Ok, easy now. I will try to get time to fix issue with not finding ports. It feels a lot better if I get some love...

... I believe in that... If you do it right then I spend you many hugz

BTW:
Is there a way after flashing to send the data inside "Post flash action" by hand via a terminal (putty or same like this)? I remember that this haven't work often and I never can connect to my wifi...

Or is there a way to connect the ESP via RXTX to a terminal-program to configure it over this way?

If you save a file with the name serialcommands.txt you can add commands in that one and only do a programming.

... ty, but witch vommands I have to send tu set the data for WIFI (i.e. UUID, Password a.s.o.)?

Meanwhile I have connect a terminal to the UART while botting, telling me that the WIFI- Settings are wrong:


INIT : Booting version: mega-20190630 (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3 PUYA support)
70 : INIT : Free RAM:29352
71 : INIT : Cold Boot - Restart Reason: External System
73 : FS : Mounting...
98 : FS : Mount successful, used 75802 bytes of 957314
451 : CRC : program checksum ...OK
462 : CRC : SecuritySettings CRC ...OK
464 : CRC : binary has changed since last save of Settings
572 : INIT : Free RAM:26504
574 : INIT : I2C
574 : INIT : SPI not enabled
589 : INFO : Plugins: 47 [Normal] (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3 PUYA support)
591 : WIFI : No valid wifi settings
592 : WIFI : Could not connect to AP!
593 : WIFI : Set WiFi to AP
1514 : WIFI : AP Mode ssid will be ESP_Easy_0 with address 192.168.4.1
2780 : AP Mode: Client connected: C0:C9:76:0D:1C:27 Connected devices: 1
2785 : Webserver: start
2849 : WD : Uptime 0 ConnectFailures 0 FreeMem 17800 WiFiStatus 0

It's all here: https://espeasy.readthedocs.io/en/lates ... mmand.html

... ty a lot ... Haven't noticed that it exist ...

1st hugz earned

Hi

I am trying to use the esp_easy_flasher.exe tool but I can't get the application to select a bin file

I click on the "open folder" button, an explorer windows open where I select a file but there is no OK button to accept the file so there is no way for me to enter the bin file in the application

help please

Don't forget to call the "save" command, or else the settings you just changed will not end up in the config file.

I click on the "open folder" button, an explorer windows open where I select a file but there is no OK button to accept the file so there is no way for me to enter the bin file in the application

That function is to explore folders only, so there is no Ok button to press. To select a upload file you must use the firmware (.bin) drop down box. If no files are seen in the drop down then that means you have an empty (or missing) /bin folder for the firmware files.

- Thomas

nice tool.
i use it a lot since it is really fast to flash standard esp builds

especially the post stuff like SSID and wpa2 key are nice
i have wpa2 with special characters and they do not get accepted by the esp setup page but i can send it easilly to the esp with the flasher tool

thanks

GravityRZ wrote: ↑31 Jan 2020, 08:56 nice tool.
i use it a lot since it is really fast to flash standard esp builds

especially the post stuff like SSID and wpa2 key are nice
i have wpa2 with special characters and they do not get accepted by the esp setup page but i can send it easilly to the esp with the flasher tool

thanks

Thanks for the feedback. Once I got the GUI job done I'll redo the flasher.

@grovkillen, I'm using ESP Easy Flasher version 0.04.007. As reported by GravityRZ, I also confirm that the WiFi Password field does not tolerate my credentials that have a $ (dollar sign) symbol. The command window shows the full password, but what gets stored in flash is terminated at the $ sign. For example, 1234$5678 would be saved as 1234. Just FYI.

- Thomas

ThomasB wrote: ↑03 Mar 2020, 01:04 @grovkillen, I'm using ESP Easy Flasher version 0.04.007. As reported by GravityRZ, I also confirm that the WiFi Password field does not tolerate my credentials that have a $ (dollar sign) symbol. The command window shows the full password, but what gets stored in flash is terminated at the $ sign. For example, 1234$5678 would be saved as 1234. Just FYI.

- Thomas

Thanks for the info.

I don't know if it's a recent WIndows update but the Flasher no longer finds the connected ESP. For Windows and Putty the respective COM port is addressable. I noticed in the log that the registry scan results are being saved and deleted. Can I disable the delete step and look at the scan results?

I suspect that there's a new way that Windows store the COM port in the registry.

Possibly. We can wait if there are more reports. My current workaround was to change the COM port in the device manager to one where non-active devices were seen/remembered.

Windows complained that the port number was in use but that was definitely not the case.

Is it a node that was working before on this Windows computer?
Can you also try in a different USB port?
I do have 1 board (my ESP12F flasher) that cannot be used by the flasher, but PlatformIO does see the board.

I flashed dozens of the same module before (Wemos D1 mini). The behavior is the same on all ports.

It could still be my PC so I‘ll do some more tests.

Just to be sure. I sometimes have issues with USB myself here on Windows too.
Sometimes power cycling (using powered USB hubs here) and re-inserting the USB cable will help as the hub may crash sometimes.
Only had that on USB2 hubs by the way, never on my Anker USB3 hub.

And sometimes I have to power cycle my USB-C block which is charger/external monitor/ethernet/USB-hub/audio for my laptop.

And if that doesn't help, power cycle all (including computer).

Not sure what happens then, as some USB devices still seem to work, like mouse (and monitor/ethernet/audio in my case) but my nodes cannot be programmed or accessed at all until a full power cycle.

Just rebooted and tried it on a different USB port. It works now and there. I have the impression that devices are recognized if they show up on the same port they were on in the past but not if they are connected to a different one.

Hello Development Team,

Here a question from a long-time fan.
Your work is highly appriciated.

After flashing, several settings on the ESP must be set manually.
Is it possible to put preferred settings in a (txt) file which can be imported into the ESP after flashing or as a post action?

Example:
predefinedSettings.txt
<UseNTP>true</UseNTP>
<UseDST>true</UseDST>

Or is this already implementend in the tool but did I not found it yet?<G>

Thanks for your time and understanding.
Best regards
ArjenW

Or is this already implementend in the tool but did I not found it yet?<G>

There is a checkbox for automatically running serial commands during post flash. You can place ESPEasy commands in the file: /settings/SerialCommand.txt

The available commands are listed here:
https://espeasy.readthedocs.io/en/lates ... mmand.html

It does not support setting NTP, but enabling DST is possible.
Example: - Thomas

Hello Thomas,

Thanks for your reply.
Are all the [internal] commands available or is there a limitation(list?)

Best regards
Arjen

Hello,

I am a new user on this forum, but I have been using ESPs for a while now, to create IoT devices for my home automation.

I have an issue with ESP Easy Flasher... actually, I never could get it working.
My PC runs updated Win10, the COM port is found, the ESP is found, and I can flash it using FlashESP8266.exe... but never with ESP.Easy.Flasher.exe.

Here is what I get (I gave the admin rights to ESP.Esay.Flasher, and jumped my Wemos D3 to Gnd) :


And the error log : If I try in the same conditions with the simpler tool "FlashESP8266.exe", it will work.

Seeing the number of users for whom it works, I assume I do something wrong. Maybe someone here may help me to figure it out.
If you want me to provide more logs, don't hesitate to ask.

Is this the only device connected to your PC on a serial port? IOW, is COM5 the same port you are flashing using the FlashESP8266.exe tool?

What model/type of board are you trying to flash?

It is a known issue that some USB to UART converters do not work with this flasher.
It looks like these USB devices are registered differently in Windows.
Not sure if it is a matter of "clones" or maybe a different revision triggering some other driver to get installed.

Ath wrote: ↑30 Jan 2021, 13:52 Is this the only device connected to your PC on a serial port? IOW, is COM5 the same port you are flashing using the FlashESP8266.exe tool?

What model/type of board are you trying to flash?

Yes, same port when it works... I just run another app.
It is a Wemos D1 mini Pro... but I had the issue with other boards based on ESP8266, including NodeMCU v3.

TD-er wrote: ↑30 Jan 2021, 14:58 It is a known issue that some USB to UART converters do not work with this flasher.
It looks like these USB devices are registered differently in Windows.
Not sure if it is a matter of "clones" or maybe a different revision triggering some other driver to get installed.

In other words, "it is probably normal" ?

It is not a blocking point, as I manage to flash with the other app, but this one seems very well made, and I would have liked to use it.

"Normal" or "not yet fixed"...

Hi,

First of all, congratulations for your hard work! I really appreciate ESPEasy an I use it every time I need a kind of automation. My last hardware is a cat feeder (PIR for detection, Servo for door opening, battery measurement and email notification).

Despite I use Esp Easy Flasher for two years without any problem, Post flash action is not working. I tried many ways to use it, without success. Do you know if there is a good tuto for using this option? It may be my fault
FYI, when I click on Prohgram only, the following error message is displayed, saying that the com port is already in use. When I click on Open serial monitor, nothing happen except the following message. Hope you can help me

I answer to myself
I tried another USB/Serial converter (FTDI and CH340). No difference. Borh converters flash ESP successufully but can't either post flash or open serial monitor.

When in Arduino IDE, serial monitor works fine (either boards).

Any idea?

Thanks in advance.

Can you test this experimental setup?
https://td-er.nl/ESPEasy/

Hi,

Many thanks

Unfortunatealy, it still doesn't work. I get the same error message:

Open serial monitor, COM port is not available
for flashing as long as this connection is open.

Just for your information, serial monitor works fine (same PC and Dev board) in Anduino IDE and Putty or Mobaxterm.

Hope you will find an answer.

The serial monitor in the flasher tool will not work if it doesn't recognize the serial port.
So that's not going to change, regardless the firmware you flash to the ESP.

The reason I gave that link was to make it easier to flash it as the web flasher does seem to recognize a lot more serial ports.
For interacting with the ESP through serial, for example to set wifi credentials, you may use some tools like Putty.

I tried another USB/Serial converter (FTDI and CH340). No difference. Borh converters flash ESP successufully but can't either post flash or open serial monitor.

It appears that the flash tool is not closing the serial port after flashing. That sounds like a USB serial driver compatibility issue. I'm using Win10 with FTDI driver version 2.12.24.0 dated 09-28-2016 and it works correctly with the flash tool. If you can find that driver then try it out.

A clumsy workaround might be achieved by flashing the device, then unplug the USB cable. This should close the serial port. Then plug it back in and restart the tool. Perhaps now the post flash and/or serial monitor will work. Admittedly not a pretty solution.

- Thomas

Hi,

I am trying to flash a wemos mini d1 with ESP_Easy_v2.0-20180321_normal_ESP8266_4096.bin and ESP_Easy_v2.0-20180321_test_ESP8266_4096 using the ESP.EASY.FLASHER gui from Grovkillen (0.04.007). It flashes fine as it shows up on my wifi as ESP_EASY_0. However, the wifi credentials (post flash action) is not working.

My workflow: I have checked "Post flash action", "Pause after flash (manual reboot", and "Force - Dout" (I am not sure what this is for though). I insert Unit name, wifi ssid, wifi password, COM port automatically selected, and I use the dropdown menu to select the bin file. I start the flash, when the pop up shows up for reset/reboot I unplug the usb, wait a couple seconds then plug it back in and click on the pop up. When I check the log, the post flash action section is empty. Could someone please help? I have been at this for days now.

Log:

######2021-08-26######
#######0.04.007#######
######FLASH INFO######
BIN file: ESP_Easy_v2.0-20180321_normal_ESP8266_4096.bin
COM port: (COM7) FTDI USB Serial Port (Port_#0001.Hub_#0002)
Baud rate: 115200
! FORCED DOUT ENABLED !
######POST FLASH######
Unit name: test_dimmer
Unit number:
Admin password:
WiFi SSID 1: xxxxxxxxxxxxxx
WiFi password 1: xxxxxxxxxxxxx
WiFi SSID 2:
WiFi password 2:
IP: 192.168.1.99
######FLASH LOG######
[esptool.exe -vv -bm dout -cd nodemcu -cb 115200 -cp COM7 -ca 0x00000 -cf "C:\Users\----\espeasy flasher (8-26-2021)\bin\ESP_Easy_v2.0-20180321_normal_ESP8266_4096.bin"]
[8/26/2021 8:54:42 PM] esptool v0.4.12 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>
[8/26/2021 8:54:42 PM] setting flash mode from qio to dout
[8/26/2021 8:54:42 PM] setting board to nodemcu
[8/26/2021 8:54:42 PM] setting baudrate from 115200 to 115200
[8/26/2021 8:54:42 PM] setting port from to COM7
[8/26/2021 8:54:42 PM] setting address from 0x00000000 to 0x00000000
[8/26/2021 8:54:42 PM] espcomm_upload_file
[8/26/2021 8:54:42 PM] espcomm_upload_mem
[8/26/2021 8:54:42 PM] setting serial port timeouts to 1000 ms
[8/26/2021 8:54:42 PM] opening bootloader
[8/26/2021 8:54:42 PM] resetting board
[8/26/2021 8:54:42 PM] trying to connect
[8/26/2021 8:54:42 PM] flush start
[8/26/2021 8:54:42 PM] setting serial port timeouts to 1 ms
[8/26/2021 8:54:42 PM] setting serial port timeouts to 1000 ms
[8/26/2021 8:54:42 PM] flush complete
[8/26/2021 8:54:42 PM] espcomm_send_command: sending command header
[8/26/2021 8:54:42 PM] espcomm_send_command: sending command payload
[8/26/2021 8:54:42 PM] read 0, requested 1
[8/26/2021 8:54:42 PM] trying to connect
[8/26/2021 8:54:42 PM] flush start
[8/26/2021 8:54:42 PM] setting serial port timeouts to 1 ms
[8/26/2021 8:54:42 PM] setting serial port timeouts to 1000 ms
[8/26/2021 8:54:42 PM] flush complete
[8/26/2021 8:54:42 PM] espcomm_send_command: sending command header
[8/26/2021 8:54:42 PM] espcomm_send_command: sending command payload
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] Uploading 608912 bytes from C:\Users\Mohammad\Documents\AMICE Design LLC\espeasy flasher (8-26-2021)\bin\ESP_Easy_v2.0-20180321_normal_ESP8266_4096.bin to flash at 0x00000000
[8/26/2021 8:54:42 PM] erasing flash
[8/26/2021 8:54:42 PM] size: 094a90 address: 000000
[8/26/2021 8:54:42 PM] first_sector_index: 0
[8/26/2021 8:54:42 PM] total_sector_count: 149
[8/26/2021 8:54:42 PM] head_sector_count: 16
[8/26/2021 8:54:42 PM] adjusted_sector_count: 133
[8/26/2021 8:54:42 PM] erase_size: 085000
[8/26/2021 8:54:42 PM] espcomm_send_command: sending command header
[8/26/2021 8:54:42 PM] espcomm_send_command: sending command payload
[8/26/2021 8:54:42 PM] setting serial port timeouts to 15000 ms
[8/26/2021 8:54:42 PM] setting serial port timeouts to 1000 ms
[8/26/2021 8:54:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:54:42 PM] writing flash
[8/26/2021 8:54:50 PM] ................................................................................ [ 13% ]
[8/26/2021 8:54:58 PM] ................................................................................ [ 26% ]
[8/26/2021 8:55:06 PM] ................................................................................ [ 40% ]
[8/26/2021 8:55:14 PM] ................................................................................ [ 53% ]
[8/26/2021 8:55:22 PM] ................................................................................ [ 67% ]
[8/26/2021 8:55:31 PM] ................................................................................ [ 80% ]
[8/26/2021 8:55:39 PM] ................................................................................ [ 94% ]
[8/26/2021 8:55:42 PM] ................................... [ 100% ]
[8/26/2021 8:55:42 PM] starting app without reboot
[8/26/2021 8:55:42 PM] espcomm_send_command: sending command header
[8/26/2021 8:55:42 PM] espcomm_send_command: sending command payload
[8/26/2021 8:55:42 PM] espcomm_send_command: receiving 2 bytes of data
[8/26/2021 8:55:42 PM] closing bootloader
[8/26/2021 8:55:42 PM] flush start
[8/26/2021 8:55:42 PM] setting serial port timeouts to 1 ms
[8/26/2021 8:55:42 PM] setting serial port timeouts to 1000 ms
[8/26/2021 8:55:42 PM] flush complete
[2021-08-26 20:55:42] DONE!
[2021-08-26 20:55:42] Waiting for user input (reset the unit).
[2021-08-26 20:55:54] Proceeding...
######POST FLASH######
############################
[2021-08-26 20:55:55] JOB COMPLETED, over and out!

I think that the ESP is still preparing the file system and rebooting after you flash it.
Based on the timings, I think the flasher tries to send the commands too soon.
One way to test this theory is to flash it again, as you won't touch the file system part when flashing the bin file (except when flashing a blank image)
If it then succeeds, then I guess the flasher may need to have a slightly longer delay to send the commands.