Device does not receive NRF_CLOUD_EVT_FOTA_DONE or NRF_CLOUD_EVT_FOTA_ERROR

RE: Device does not receive NRF_CLOUD_EVT_FOTA_DONE or NRF_CLOUD_EVT_FOTA_ERROR

teba99 — Fri, 27 Mar 2026 12:51:39 GMT

Yes, thanks, We'll follow up when we have more info.

RE: Device does not receive NRF_CLOUD_EVT_FOTA_DONE or NRF_CLOUD_EVT_FOTA_ERROR

Pascal Hdz — Fri, 27 Mar 2026 09:27:56 GMT

Hello Terrence,

I'm closing this ticket due lack of activity. Please open a new ticket in case you need further assistance.

Regards,

Pascal.

RE: Device does not receive NRF_CLOUD_EVT_FOTA_DONE or NRF_CLOUD_EVT_FOTA_ERROR

Pascal Hdz — Fri, 24 Oct 2025 10:13:11 GMT

Hello Terrence,

You can read more about it on the internet: https://docs.aws.amazon.com/iot/latest/developerguide/mqtt.html#mqtt-persistent-sessions

I would guess that you could use this to avoid missing the cloud event when you have establish your connection again.

Pascal.

RE: Device does not receive NRF_CLOUD_EVT_FOTA_DONE or NRF_CLOUD_EVT_FOTA_ERROR

teba99 — Fri, 24 Oct 2025 08:30:10 GMT

Hi Pascal,

Thanks for the info. Our device is line-powered, so battery life is not an issue. Can you explain how a persistent MQTT session would help?

Thanks,
-- Terrence

RE: Device does not receive NRF_CLOUD_EVT_FOTA_DONE or NRF_CLOUD_EVT_FOTA_ERROR

Pascal Hdz — Fri, 24 Oct 2025 08:21:27 GMT

Hello Terrence,

It's expected that if there's no disconnection when the event is sent to the device, the device won't be able to capture it, and therefore you'll experience this behavior. The mitigation option for this depends entirely on how your application handles connection issues. Suggesting a timeout may be a valid option, but it could potentially impact your battery life, and that's perhaps unacceptable, just to give you an example. Another option is to enable the persistent session that MQTT offers (I assume this is the protocol you're using).

Pascal.