Start a new topic

firmware upgrade


Just received my openevse 5.5 board

However, upon checking some of the options it seems some are missing

My version is 7.1.3, but the latest is 8.2.0.

I bit dissapointed that I did not received a module with the last release

Looking at the upgrade instructions, and they don't seem to have been updated

On one of the last steps, it mention yo need  3 files; flash.bat, open_evse.hex and eeprom_24.bin

However, on the repository for the last release ( 8.2.0)  there are a couple of hex files ( I assume I should use openevse.hex), there is no  bin o flash.bat files

What am I missing?

should just run the command to flash the hex file as per the Readme file:

`$ avrdude -p atmega328p -B6 -c usbasp -P usb -e -U flash:w:firmware.hex`

Any help appreciated

I don't know!

How can I check?

I've just installed a new VSCode + Platformio environment on a fresh Win10 machine, downloaded the the latest V4.1.3 project from github and tried to compile it, without success so far. It fails immediately.

Please take a look on the picture attached. You will also see how to check the espressif32 version that you are using.

By the way, the binary you made yesterday has been compiled from a V4.1.2dev version source code. Can you double check which version of code are you using?
Thank you!

(41.2 KB)

It seems I may have two exprssif libraies installed, see snapshot

I don't know how to check the version, this is all I could get

Not the version of platformio but the OpenEVSE WiFi source.

Can you please compile me the exact version of V4.1.3?

Here is the direct link to that version:

You can download the Source code (zip) below in the Assets, unpack, set the nodemcu-32s as default and compile.

Thank you in advance!

So, after a lot of struggle I figured out what was caused the compile error. I hope it will help others to get rid of this issue.

It turns out that the platformio is not able to find the "framework-arduinoespressif32" at version "2.10004.191002" required by "espressif32" version "1.11.1". It should be downloaded manually, I found it at sourceforge:

The content of the compressed file must be copied into folder:


This way the project will compile and binaries will be created.


With version 4.1.3 on first boot the webpage now says "Loading, please wait... (/)". It does the same using precompiled binaries from the git project page.

György, do you still need the compile of version 4.1.3?

I have been away, so I was not able to look at this

If you still need it, I will compile and send you the link


Hi Javier,

I was able to compile the code at the end so I have the latest firmware and it works with my Nodemcu-32S board.

Now I'm hunting components to build the hardware. Most of components I have already, but the current transformers (CR8420-1000-G and CR8450-1000) I'm not able to find anywhere.

Thank you for your help!

glad you managed to program the board

can't you buy the current transformers from USA?

I know is not ideal, but at least you know they work!


hello friends

do you have a video or tutorial on how to make esp-32 work?

how to flash and program

thank you,

I posted a reasonably comprehensive overview on updating the controller, and the ESP32, here:

I also added some instructions on the same thread - in my opinion far easier that Al Savage's (not to discredit his excellent work!

As per my notes, I used a wroom-32 board

Good luck!

There are several firmware update paths, but the choices you have are more limited if your ESP32 module does not have the USB interface.

With the software NodeMCU-PyFlasher and NodeMCU-PyFlasher the openevse_huzzah32.bin is installed

flash and done?

If you have an ESP32 with a USB connection, then you can use NodeMCU etc.  But not everyone has that slightly more expensive style of ESP32 module, which is why some people say, "this is so easy, it doesn't even require instructions" and others have had to jump through many hoops and outdated instructions that do not apply to our hardware.

That is why this thread contains at least two different ways to update firmware.

To further confuse: there are two different modules in every OpenEVSE:

The Controller

The ESP32/Wi-Fi

Each have their own separate firmware to be updated.  Updating the ESP32 can be relatively straightforward; updating the Controller' firmware is not.  And, if you update the ESP32 without updating the Controller's firmware as well, some of the firmware mis-matches will trigger other issues, depending on the age of the unit you're working with.  And, the hardware interfaces of the two modules are different, requiring separate tools and toolchains:

Controller: USB AVRISP hardware, and avrdude software

ESP32:  USB to TTL hardware, and esptool software

(or, with the USB-equipped version of the ESP32: NodeMCU (etc.))

I've hit all of these problems over the years with my 2017-era OpenEVSE (now upgraded from ESP2866->ESP32).  Regardless of how old your hardware or firmware is, the recipe I posted should handle all of these issues for all versions and revisions.

1 person likes this
Login or Signup to post a comment