RE: AWS IoT FOTA job gets queued but never starts

Oli — Mon, 19 May 2025 00:46:59 GMT

The issue was that I was passing a client_id in my main.c based on hardware id so the CONFIG_AWS_IOT_CLIENT_ID_STATIC configuration option was getting ignored. I scheduled the job for "academy_thing" but the client was connecting as "80380020C920".

RE: AWS IoT FOTA job gets queued but never starts

Oli — Sun, 18 May 2025 23:58:08 GMT

I enabled AWS FOTA debug logging and am seeing this:

00:00:34.211,944] <dbg> aws_fota: topic_type_get: Received topic: $aws/things/80380020C920/jobs/$next/get/accepted
[00:00:34.211,975] <dbg> aws_fota: on_publish_evt: Checking for an available job
[00:00:34.212,066] <dbg> aws_fota: parse_job_execution: Job doc: {"clientToken":"","timestamp":1747612515}
[00:00:34.212,371] <dbg> aws_fota: parse_job_execution: Got only one field
[00:00:34.212,402] <dbg> aws_fota: parse_job_execution: No queued jobs for this device

Not sure what it means. It looks like it is receiving an incorrect job document?

I added some logging and it seems that the job document is indeed

{"clientToken":"","timestamp":1747613442}

Which is weird because in the AWS IOT job document page it shows:

{
  "operation": "app_fw_update",
  "fwversion": "v1.0.1",
  "size": 402884,
  "location": {
    "protocol": "http",
    "host": "my-bucket.s3.us-east-2.amazonaws.com",
    "path": "/v1.0.1.bin"
  }
}