OTA programming of ESP32 using cellular connection with the SIM800

[Markovicz]

Dear ESP32-fellows,

There are quite some tutorials for OTA programming of ESP32 with WIFI connection but I haven't seen one for cellular connection using popular modules like the SIM800.
A very good course is this one on Udemy:
https://www.udemy.com/course/advanced-esp32
Are there already ways to connect the ESP32 over cellular to OTA cloud services like Mongoose?

In particular, I have in mind using the board from lilygo:

https://github.com/Xinyuan-LilyGO/LilyGo-T-Call-SIM800

Best and thank you!

[PeterR]

Of course, its just software

The new ESP-NETIF interface makes it 'easy'er. You could create a new IF adaptor to your SIM800.
The SIM800 AT commands are not that complicated & there were lots of Ardunio examples when I last looked a couple of years ago. I started porting one but in the end wrote from scratch, what I found did not have proper error handling but was otherwise functional.

Once you have a new IF adaptor layer then it should be simple to swap over the latest ESP OTA Wifi example as the actual interface should have been requested using a character string.

[Markovicz]

Dear Peter,
A fast way of prototyping sth. would probably be using the TinyGSM library:
https://github.com/vshymanskyy/TinyGSM

I'm not sure if I can port the WiFi examples myself to cellular connection. It will take me a lot of time probably.

Eventually it is possible to create a webserver just like for the commmon WiFi OTA examples using cellular connection. The only remaining part would then to have mDNS for cellular IP.

Don't be hard on me, I'm just at the beginning of digging into OTA ...

[PeterR]

Don't be hard on me, I'm just at the beginning of digging into OTA

Why should I treat you differently to anyone else?

Yea; there is a bit of work. The main effort would be creating the NETIF adapter.
What are you using mDNS for?

I use mDNS adverts for Ethernet & it justs works using the STA recipe so I guess the component sends to all adapters.
The discovery protocol tells you which adaptor the service was discovered on, so that just works as well.