Using FirebaseClient together with ESP8266HTTPClient

[nhiennn]

I use both FirebaseClient and ESP8266HTTPClient at the same time the checkUpdateAvailable() function does not work as expected.

Here is the summary of the code:

...

void checkUpdateAvailable() {
    WiFiClientSecure clientOTA;
    // clientOTA.setInsecure();
    String updateUrl = String(UPDATE_URL) + String(CURRENT_VERSION);
    HTTPClient httpOTA;
    
    if (httpOTA.begin(clientOTA, OTA_URL)) {
        int httpCode = httpOTA.GET();
        if (httpCode > 0) {
            if (httpCode == HTTP_CODE_OK) {
                String payload = httpOTA.getString();
                Serial.println(payload);
                Serial.println("Update available");
            }
        } else {
            Serial.printf("[HTTP] GET... failed, error: %s\n", httpOTA.errorToString(httpCode).c_str());
        }
        httpOTA.end();
    }
}

void setup()
{
    // ssl_client.setInsecure();
    initializeApp(client, app, getAuth(dbSecret));
    app.getApp<RealtimeDatabase>(Database);
    Database.url(FIREBASE_REALTIME_URL);
    Database.get(client, "/my-path", result, true);
}

void loop()
{
    Database.loop();
    
    if (condition_each_10_minutes) {
        checkUpdateAvailable();
    }
}

After that, I change this line of code

    Database.get(client, "/my-path", result, true); 

to this

    Database.get(client, "/my-path", result, false); 

Then function checkUpdateAvailable() work as is, but can not listening events from firebase realtime database on update.

Does anyone have any advice for me?

[mobizt]

In ESP8266, you don't have enough memory to open two network connections at the same time.

The memory used in WiFiClientSecure for your OTA library is large (> 16k by default).

If you use another WiFiClientSecure used for Firebase, you have to set its buffer size smaller like this.

FirebaseClient/examples/RealtimeDatabase/Async/Callback/Stream/Stream.ino

Line 99 in 937c388

ssl_client1.setBufferSizes(4096, 1024);

Or you have to stop Firebase before doing OTA and resume it after.

[mobizt]

Nothing is in the AsyncClient queue after it cleared which you have to wait a bit to let the async handler to work because of async operation design concept.

The auth handler is still running as it is the library core function as long as you place the <App>.loop() in the main loop.
https://github.com/mobizt/FirebaseClient?tab=readme-ov-file#async-client

[mobizt]

The problem is your OTA library uses too large memory while operating. You have to manage the use of WiFiClientSecure class.

[mobizt]

ssl_client.setBufferSizes(0, 0); does nothing because the minimum value to be set is 512 and you don't have to do this because it is dynamic allocation only when connecting to the server.

[mobizt]

You don't have enough memory to do many things in such 30-40k available free memory device.

The 7-10k memory should be reserved for systems. The > 16k (rx, ref) + 1k (tx, ref) was used by WiFiClientSecure used for your OTA library.

Move to ESP32 or Raspberry Pi Pico W is the option.

[nhiennn]

Ok, thank you for your support.
To reduce costs, I decided to use a flag to determine if there is an update and avoid handling the queue stream until the device restarts next time. 😂😂😂

if(otaStatus == 0) {
    Database.get(client, "/my-path", result, true); 
}