SPIFSS.bin is no longer needed, the filesystem is embeded in the firmware.
I would recommend esptools to flash with the following command (substitute your com port and speed if necessary):
esptool.py -b 1500000 -p COM3 write_flash 0x000000 firmware.bin
The correct files are here:
There are BIN files ready to go in the releases section.
The others from my personal repo are very old, they were the foundation for the 1.x and 2.x official releases.
That's good news and thanks for the reply Chris.
Can you describe how you did it, and what file(s) you used. When I used firmware.bin in the web interface System section, all communications stopped and I haven't been able to monitor consumption since. I was going to reflash all files using the instructions at: https://openevse.dozuki.com/Guide/OpenEVSE+WiFi+%28Beta%29/14
What is the difference between the files at
The WiFi can be upgraded from the web interface. Upgrading from 2.5.0 to 2.5.2 should work fine. I did it in chrome just the other day.
Is this why my OpenEVSE stopped transmitting data after my attempt to upgrade to 2.5.2 from 2.5.0? I used the web interface System/WiFi Firmware/Choose File (firmware.bin)/Update.
The Wifi stopped transmitting and cannot be accessed in AP mode.
Was the bin file the wrong one to use?
Correct. Version 2 requires both firmware and a file system. The web interface will only load the firmware.
Yes, version 2.x of the WiFi firmware has many security enhancements.
Web interface Login with Username and Password
Ability to change default Username and Password
Encrypted (https) EmonCMS server with TLS Fingerprint verification
Encrypted (https) Ohm Connect server with TLS Fingerprint verification
MQTT with authentication
The firmware is available here:
You will need a USB serial adapter for the initial load. I recommend using ESPtools to upload the firmware with the following command.
esptool.py -b 1500000 -p COM3 write_flash 0x000000 firmware.bin 0x300000 spiffs.bin