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
Correct. Version 2 requires both firmware and a file system. The web interface will only load the firmware.
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?
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.
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 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.
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
Im having problems to access the web interface of OpenEVSE after setting up the Wi-Fi parameters.
Im following these steps:
- At first time, using a computer im connecting in the default SSID from OpenVSE (OpenEVSE_XXXXXXX)
- I can access the web interface through the IP address 192.168.4.1
- The web interface shows me the SSID from my access point, and then i put the password from my network
- Them the OpenEVSE connects into my infrastructure, and I can see in OpenEVSE display the IP address that it obtained from my DHCP server
- I can see the OpenEVSE connected to my access point as a client, I can ping the IP address from OpenEVSE, but when I try to access the web interface from OpenEVSE it does not respond.
Is this normal? Or should I access the OpenEVSE web interface normally using the IP address that it obtained?
Thank you guys!
Do you plan to use MQTT over TLS with client authentication (using RSA private key or signed JWT), for example to use public MQTT brokers like AWS IoT or Google Clout IoT Core ?
Peter, yes we plan to implement MQTT over TLS with client certs.
See Github issue: