Skip to content
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

Closed
RonaldSpijk opened this issue May 24, 2024 · 19 comments
Closed

Web server not responding anymore in V3.6.0 #79

RonaldSpijk opened this issue May 24, 2024 · 19 comments

Comments

@RonaldSpijk
Copy link

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.

@dingo35
Copy link
Owner

dingo35 commented May 24, 2024

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?

@RonaldSpijk
Copy link
Author

I tried the IP address, the SmartEVSE name, the DHCP name.
I tried various browsers, chrome F12, curl. All with the same result.

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.'
I also tried to post some settings to see if the commands get there, but nothing changes.

@dingo35
Copy link
Owner

dingo35 commented May 24, 2024

What always works is reflashing, instructions see bottom of page https://github.com/dingo35/SmartEVSE-3.5/blob/master/docs/configuration.md

@AndrejSNC
Copy link

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.
Then I updated it to 3.6.0 it connected back to the old dynamic IP address, which I don't like. I can start WiFi setup in menu, connect to access point but the configuration page does not open on my phone. How can I access this configuration, to set back static IP? Tried 192.168.4.1 and it did not connect.

@dingo35
Copy link
Owner

dingo35 commented May 25, 2024

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.

@deekoowee
Copy link

Similar problem here. Controlled worked until I upgrade it to 3.6.0
Controller answer for ping at 192.168.4.1, but do not answer to browser. Tried with Chrome and Curl
Also tried the /erasesettings, but no luck.
I tried to flash the firmware with ESP32 flash download tool v3.9.6 , but nothing changed
Connected serial cable and telnet shows;
pic
Any suggestions to fix the controller's firmware

@dingo35
Copy link
Owner

dingo35 commented May 29, 2024

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....

@deekoowee
Copy link

Downgraded to 3.5.1 via USB-C cable, rebooted controller, the web page showup.
Showed version 3.6.0 at left top corner of the screen
After few minutes, the webserver has lost, no communication with any browser.
Some mystery, which I don't catch up.

@dingo35
Copy link
Owner

dingo35 commented May 30, 2024

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.

@deekoowee
Copy link

I tried to upload the firmware.bin file with ESP32 flash download tool v3.9.6 (downloaded from Espressif site)
I used settings like this, only filename was changed.
pic
the bar at bottom on window runs ok.

@mstegen
Copy link

mstegen commented May 30, 2024

There are two partitions, the first one starts at 0x10000
The second one starts at 0x1c0000
Try flashing both partitions. That should do the trick.

@deekoowee
Copy link

Flashing those two partitions together fixed the webaccess problem

All settings were gone and have to reconfigure the controller

@dingo35
Copy link
Owner

dingo35 commented May 30, 2024

The settings were gone because you did /erasesettings, not because of reflashing those two partitions...

@deekoowee
Copy link

Yes, I noticed that.
It is not big deal to make new settings again

@dingo35
Copy link
Owner

dingo35 commented May 31, 2024

This should solve the problem:
83adad145a90903.zip

@deekoowee
Copy link

I have tested more the 3.5.1 and 3.6.1
Both give Communication errors. LCD screen have "ERROR NO SERIAL COM CHECK CFG OR WIRING" and pushbuttton light blinks fast red.
Wiring has not changed and config should be ok, because I downgrade to 1.8.0 and it doesn't give any errors.

@AlbertHakvoort
Copy link

This should solve the problem: 83adad145a90903.zip

I've had the same issue, the 83adad1.zip is fixed the webserver issue

@dingo35
Copy link
Owner

dingo35 commented Jun 5, 2024

Thanks for your reports guys, this should be solved in 3.6.1 .

@Wireheadbe
Copy link

Wireheadbe commented Nov 17, 2024

Mine "bricked" when updating from 3.7.0 to 3.7.2.
Here's how I flashed in a Debian-based distribution:

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:

sudo dmesg -T

Then, install esptool, and flash the firmware:

sudo apt install esptool
esptool --port /dev/ttyUSB0 write_flash 0x10000 firmware.bin
esptool --port /dev/ttyUSB0 write_flash 0x1c0000 firmware.bin

It'll take some time to flash to both partitions, so don't stress :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants