-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web server not responding anymore in V3.6.0 #79
Comments
Dont be afraid, AFAIK you cannot brick your SmartEVSE, you can always flash a new version through the built in USB-C bus. If the MQTT server is connected, it means your wifi is connected, which should mean your webserver is connected. Are you sure you are surfing to http://ipaddress-of-your-smartevse? Some browsers try to redirect you to https, which will not work (not at 3.6.0, spoiler alert!) You can also try to go to http://ip/update for direct update Or try another browser? |
I tried the IP address, the SmartEVSE name, the DHCP name. Ping works fine, however when accessing port 80 the connection is dropped. When accessing another port (e.g. 81) the connection is never made. When I use 'curl -X GET http://ipaddress-of-smartevse/settings' it replies 'Recv failure: Connection reset by peer.' |
What always works is reflashing, instructions see bottom of page https://github.com/dingo35/SmartEVSE-3.5/blob/master/docs/configuration.md |
What I have discovered today is, I replaced my old SmartEVSE version with V3 controller. It came with 3.0.1 SW version. I connected it to WiFi and set fixed IP address - works great. |
If you set "wifi" from "Enabled" to "Setup" on the LCD screen, you should be able to connect to the SmartEVSE AP via 192.168.4.1 and set a static IP. If it for some reason that fails, you can always goto /erasesettings and repeat the wifi setup procedure. |
If you have these problems with 3.6.0, why dont you downgrade to 3.5.1 with USB-C cable? Link is posted in this thread.... |
Downgraded to 3.5.1 via USB-C cable, rebooted controller, the web page showup. |
Your downgrade obviously did not succeed... EDIT: Make sure you add the -t upload parameter when compiling; you should see messages like 10% written, 20% , etc. |
I tried to upload the firmware.bin file with ESP32 flash download tool v3.9.6 (downloaded from Espressif site) |
There are two partitions, the first one starts at 0x10000 |
Flashing those two partitions together fixed the webaccess problem All settings were gone and have to reconfigure the controller |
The settings were gone because you did /erasesettings, not because of reflashing those two partitions... |
Yes, I noticed that. |
This should solve the problem: |
I have tested more the 3.5.1 and 3.6.1 |
I've had the same issue, the 83adad1.zip is fixed the webserver issue |
Thanks for your reports guys, this should be solved in 3.6.1 . |
Mine "bricked" when updating from 3.7.0 to 3.7.2. First, check where the device has popped up.. from experience, it's quite easy to find the last connected device by just looking into the kernel log, and looking in the last couple of lines:
Then, install esptool, and flash the firmware:
It'll take some time to flash to both partitions, so don't stress :-) |
I've uploaded version 3.6.0 on a newly bought SmartEVSE. Before that it had 3.5.1 for a few days.
It worked for a few days without any problems.
After some issues with the Wifi the web server stopped working. MQTT still works.
I can also ping.
When accessing port 80 the port is found, but the connection is dropped immediately.
A tried resetting a few times, doesn't help.
A tried starting the Wifi Portal, this also doesn't work.
Fortunately, charging still works :-)
I'm stuck in the middle here, because when the web server doesn't work, I can't update, and get logs.
I'm afraid to do anything else, because it might brick my SmartEVSE.
I think this needs good investigation because it might also occur at other users.
And I like some help getting a working version on the SmartEVSE. Would uploading the bin file with the Espressif flash download tool work? Or should I try something else first.
The text was updated successfully, but these errors were encountered: