Using NetworkClient/TinyGsmClient with ESP_SSLClient for hybrid network. Main Loop get stuck after 30-40 mins.

[saadmustafa12]

Hello!

I have been using this library for long time, recently I made a hybrid system to work on GSM and WiFi at the same time by shifting to the one which is more stable. I am using ESP_SSLClient to switch between Network Client vs GSM Client. It is working fine, But after recent update to 2.1.8. Main loop gets stuck during update after 30-40 mins and nevers returns back while the second core keeps running fine. My heap goes down to 180k before getting stuck, I do have PSRAM enabled on ESP32 S3 (16 R2). I can't figure out what's wrong bcz main loop entirely gets stuck.

Also my hybrid network management works on 2nd Core different then main core. So main loop is never disturbed (moreover Library is Init and Deinit from main loop as well)

Any help will be appreciated.....

Thanks...

[mobizt]

When you update the library, it is necessary to check the examples and documentation for the changes and what is required to change in your code.

https://github.com/mobizt/FirebaseClient?tab=readme-ov-file#changes-since-v210
https://github.com/mobizt/FirebaseClient/tree/main/examples

[mobizt]

For ESP32, the PPP library is recommended for GSM modem.
https://github.com/mobizt/FirebaseClient/blob/main/examples/RealtimeDatabase/StreamPPP/StreamPPP.ino

Anyway, the SSL client is on your side, and you should debug it.

[saadmustafa12]

Actually I am getting GPS data over modem as well that's why I can't use PPP.

Do u have any recommended steps to debug? I tried adding some debug prints but bcz main loop get stuck I can't get anything to print.

I am using everything as in latest examples of TinyGSM in your library.

[saadmustafa12]

Also I just wanted to confirm that it is reliable to use NetworkClient with ESP_SSLClient. Instead of using SSL_CLIENT directly.....

[mobizt]

As I mentioned the SSL Client is on your side, and it is used for data transferring.

You have to debug the SSL client and memory usage. For ESP_SSLClient, please see https://github.com/mobizt/ESP_SSLClient.

[mobizt]

This macro enables the internal ESP_SSLClient which is the latest version as in https://github.com/mobizt/ESP_SSLClient.

FirebaseClient/examples/RealtimeDatabase/StreamGSM/StreamGSM.ino

Line 15 in 1b0d3b5

#define ENABLE_ESP_SSLCLIENT

For ESP_SSLClient debugging.

 /** Call setDebugLevel(level) to set the debug
  * esp_ssl_debug_none = 0
  * esp_ssl_debug_error = 1
  * esp_ssl_debug_warn = 2
  * esp_ssl_debug_info = 3
  * esp_ssl_debug_dump = 4
  */
  ssl_client.setDebugLevel(1);

What is the last FirebaseClient library version before update?

I focus on the SSL Client because library can't control the network and client and just use its Client class interfaces e.g. ::connect(), ::connected(), ::read() and ::write().

The timeout was applied when operating with SSL Client and data was transferred as small chunks and it will never get stuck at the library code.

[saadmustafa12]

Hello!

I have another question of same category of switching between GSM and WiFi simultaneuosly without reboot.
I solved my previous issue by using:

1. SSL_Client -> For WiFi operations
2. ESP_SSLClient -> For GSM Operations
3. Keeping AsyncClients same for both and changing SSL clients during swithing

It is working properly now without crash/stuck....

Now I have another problem during network change when I restart Realtime Database streaming i get this error

01:42:23.688 -> Firebase Client v2.2.1
01:42:23.688 -> Initializing app...
01:42:23.688 -> Debug task: 🔐 authTask, msg: Connecting to server...
01:42:23.688 -> Event task: 🔐 authTask, msg: authenticating, code: 7
01:42:23.688 -> Debug task: 🔐 authTask, msg: Connecting to server...
01:42:23.688 -> Event task: 🔐 authTask, msg: auth request sent, code: 8
01:42:23.688 -> Error task: task_8268, msg: operation was cancelled, code: -118
01:42:23.688 -> Firebase streaming cancelled (expected during network switch)

I am properly using :

Database.resetApp();
deinitializeApp(app);

before swithching network and library is reinitialized from scratch after network switching. But i think so the stream task does not end properly which is why i get this error? Can please point out what to do exactly ??

[mobizt]

Stream is a persistent task and always reconnect/resume by design. You should use AsyncClient:stopAsync("stream task uid") to stop stream task by its uid or use AsyncClient:stopAsync(true) to stop all tasks.

The task will be stop after some time that no data is currently processed.

[mobizt]

The debugging message from stream task like that is ok as it is maintained to run infinitely.

[saadmustafa12]

I tried adding:

streamClient.stopAsync(true);
Serial.printf("Stream client tasks after reset: %d\n", streamClient.taskCount());

Serial ouput after reset...

18:35:03.531 -> Stream client tasks after reset: 1

It seems like task is not cleared properly after stopAsync is called. I tried checking taskCount() after sometime as well with no luck

[mobizt]

The FirebaseApp is the auth and async task handler .

To stop the tasks, you should not reset and de-init the FirebaseApp before the tasks are cleared.

Don't do this.

streamClient.stopAsync(true);
aClient.stopAsync(true);
Database.resetApp();
deinitializeApp(app);

Should do this.

streamClient.stopAsync(true);
aClient.stopAsync(true);

// After some time
...
...

if (streamClient.taskCount() == 0 && aClient.taskCount() == 0)
{
      Database.resetApp();
      deinitializeApp(app);
}