search

thebigpotatoe / Super-Simple-RGB-WiFi-Lamp

A project based on the ESP8266 and WS2812b
MIT License
66 stars 28 forks source link

No web interface #26

Open Nicornru opened 4 years ago

Nicornru commented 4 years ago

Hi! I have an issue with control web-interface. I cannot see anything when I open the ESP's IP in any web-browser. I tried IE, Opera, Chrome. All adblockers are turned off. I tried to add a simpliest test page into the code, and couldn't see that too. And also - update page loads and works OK

Could you think of how to fix that?

Phantisy commented 4 years ago

If you open the browsers console (F12) are you seeing the pages code loading?

thebigpotatoe commented 4 years ago

I think i figured it. What version of the ESP8266 core are you using?

Seems like there are breaking changes with the latest version for the way the web server is loaded.

Please change the ESP8266 core version in your Arduino IDE boards manager back to 2.5.2. We will have to find a fix for this issue soon.

Nicornru commented 4 years ago

If you open the browsers console (F12) are you seeing the pages code loading?

If codepage is set, there's nothing. If not - I get ERR_INVALID_CHUNKED_ENCODING

Please change the ESP8266 core version in your Arduino IDE boards manager back to 2.5.2.

That worked! Thank you!

thebigpotatoe commented 4 years ago

Awesome. I'll keep this issue open till we have a fix

LarsMichelsen commented 4 years ago

Isn't this fixed with your commit? c482d6c8fde73ecf64ed931ddfef8570edebd168

I also had this issue, then changed the Web_Server.ino to:

restServer.send_P(200, "text/html", websiteSource);

As far as I remember that did make it work.

For the moment I reverted ESP8266 back to 2.5.2 for some other reason.

LarsMichelsen commented 4 years ago

Off topic: They also changed the upload form code. The compile_and_upload.py will also need a change.

thebigpotatoe commented 4 years ago

c48d6c was a stab at fixing it, but I ran into other issues in other parts of the code after fixing this. So there are clearly other code breaking changes from the 2.6.0 update that I need to dig into as you also mention.