Temporary (intentional) unavailability of transport layer: Recommended way of handling situation in Firebase Client?

[romwam]

I use Firebase Client on a board with combined cellular connection (TinyGSM) and GNSS (on the modem chip).
For acquiring GNSS position i have to stop cellular communication until GNSS position is acquired and reenable cellular again afterwards.

This occurs also when Firebase Client is already up and working (Realtime DB + Storage in 2 async clients).

What is the recommended way of handling this situation w.r.t. Firebase Client. Should it be stopped? Is there a way to pause and resume Firebase operations while (knowingly) not network is available?

thanks for your feedback,

Roman

[mobizt]

You cannot pause the task unless stop to remove tasks.

You can use AsyncClientClass::stopAsync.
https://github.com/mobizt/FirebaseClient?tab=readme-ov-file#async-client
https://github.com/mobizt/FirebaseClient/blob/main/FAQ.md#q23-how-can-i-restart-the-realtime-database-stream

To check the number of tasks that stored in the async client's queue.
AsyncClientClass::taskCount()

After SSE Stream task has stopped, you can restart it by calling get again.