I would just like to ask for your opinion on OTA design of very closed system.
Our device will consist of ESP32 based gateway between Android app running on a dedicated tablet or smartphone and various process controllers that support different low level interfaces. Practically, Android tablet/smartphone app provides just a fancy UI for this device (similar to OBD dongle and Android/iOS app). ESP32 gateway has no access to internet and communicates to Android device via BLE using custom interface to provide data retrieved from process controllers. Unlike ESP32, Android device can access Internet most of the time, but not always.
The gateway software has to be OTA capable and all information indicates that BLE OTA is probably too slow for about 1.4 MB. So, for OTA updates, I think that the application running on Android device can get an update (probably both for app and for ESP32) from Internet (when available), later at some point ask ESP32 to enable its Wi-Fi and start acting as an AP and pass the update data to it via Wi-Fi. The question is - is it better (safer, faster, simpler, more reliable) to create an HTTP server/client type of communication between the two or plain TCP socket interface is sufficiently good and safe for this OTA data transfer?
Thanks a lot.
OTA from Android / iOT app
Re: OTA from Android / iOT app
Hi ndjurov
I have Exactly this question too
is it possible ?
I have Exactly this question too
is it possible ?
-
- Posts: 9749
- Joined: Thu Nov 26, 2015 4:08 am
Re: OTA from Android / iOT app
Should work fine. HTTP or raw TCP doesn't really matter that much; use whichever you prefer.
Re: OTA from Android / iOT app
Thanks a lot.
Who is online
Users browsing this forum: No registered users and 92 guests