ClemensGruber

Looks like hard coded without any option to avoid this: https://github.com/prampec/IotWebConf/blob/b89ac9f61b2022cc0c794a74751c5019b4679eef/src/IotWebConf.cpp#L367-L376

Would be interested in a general solution also, without forking the lib! A kind of parameter if wifi parameters are obligatory.

In the GitHub issues and library examples I found `forceApMode(),` that will be helpful for the described scenaro. So I can omit joinig a Wifi network that's not there because...

The working module with voltage below 3.9 V is a T-Call I ordered a time ago, it has a different silkscreen at the ESP32 module as you can see on...

Here are ongoing test with the **older T-Call SIM800C (left side on the pic in the last posting)**. I connected the discharged LiPo with ~3.9 V to this board and...

 I have spent a hour to test all 16 T-Call SIM800C boards I have laying around at my workbench. - all 16 working via SIM800 with USB-Power - all...

I had a detailed look at the two boards the working one is the on the **left** side vs. the not working! I found some not populated parts at the...

Any answer from @LilyGO about this issue?

@LilyGO we are still waiting for an answer.

You can find a project documentation under https://community.hiveeyes.org/t/openhive-esp32-ttgo-t-call-sim800c/4202 and corresponding code via https://github.com/ClemensGruber/open-hive_bee-monitoring/blob/master/open-hive_esp32_ttgo-t-call-sim800c.ino but with the current hardware from TTGO I could not recommand the TTGO T-Call!