The following APIs can be used to create fota schedule files or files can be created directly into the \/var\/run\/.fota directory.<\/p>\n
\n------WebKitFormBoundaryfX3HU1aeZkuK5C0A
\nContent-Disposition: form-data; name=\"fotafile\"; filename=\"mbed-os.bin\"
\nContent-Type: application\/octet-stream<\/p>\n------WebKitFormBoundaryfX3HU1aeZkuK5C0A--
\n<\/code>\n<\/li>\n<\/ol>\n<\/li>\n
- \nCreates a schedule file using “schedule_file_name” field in \/var\/run\/.fota with the above JSON<\/p>\n
The operation scheduled time and time until setup starts is encoded in the file name.
\nfota__<\/p>\n
A fota daemon is running in mPower that will kick off the scheduled operation from this file at the encoded time info in the filename.<\/p>\n
https:\/\/<SERVER-IP>\/api\/lora\/fota
\n
\n{
\n\"scheduledTimeSinceUnixEpoch\": 1749562414,
\n\"keep_log\": false,
\n\"ssleep_time\": 1000,
\n\"sleep_time\": 1500,
\n\"schedule_filename\": \"fota_1749562414_0\",
\n\"setupTimeFromScheduledTime\": 0,
\n\"launchTimeFromSetupTime\": 60,
\n\"browserTimeBias\": 0,
\n\"transmission_type\": \"FOTA\",
\n\"multicastDeveui\": \"00-80-00-f5-d8-ec-69-a3\",
\n\"endDeviceDeveuis\": [\"00-80-00-00-00-aa-bb-01\"],
\n\"schedule_source\": \"Conduit\",
\n\"fotaFile\": \"mbed-os.bin\",
\n\"fotaDescriptor\": 0,
\n\"parity_fragments_per_session\": 100,
\n\"psleep_time\": 3000
\n}
\n<\/code>\n<\/li>\n- See progress of operations with these API calls, this API pulls data from files in \/var\/run\/.fota, progress and results are created by the fota daemon.\n
https:\/\/<SERVER-IP>\/api?fields=lora\/fotaprogress,lora\/fotaschedule,lora\/fotaresults
\n
\n{
\n\"code\" : 200,
\n\"result\" :
\n{
\n\"lora_fotaprogress\" : [],
\n\"lora_fotaresults\" : [],
\n\"lora_fotaschedule\" :
\n[
\n{
\n\"browserTimeBias\" : -5,
\n\"endDeviceDeveuis\" : [],
\n\"fotaDescriptor\" : 0,
\n\"fotaFile\" : \"mbed-os.bin\",
\n\"keep_log\" : false,
\n\"launchTimeFromSetupTime\" : 60,
\n\"multicastDeveui\" : \"00-80-00-f5-d8-ec-69-a3\",
\n\"parity_fragments_per_session\" : 100,
\n\"psleep_time\" : 3000,
\n\"schedule_filename\" : \"fota_36753562_1749562419_0\",
\n\"schedule_source\" : \"Conduit\",
\n\"scheduledTimeSinceUnixEpoch\" : 1749562419,
\n\"setupTimeFromScheduledTime\" : 0,
\n\"sleep_time\" : 1500,
\n\"ssleep_time\" : 1000,
\n\"transmission_type\" : \"FOTA\"
\n}
\n]
\n},
\n\"status\" : \"success\"
\n}
\n<\/code><\/li>\n- \nCreating a cancel file will stop the fota process and clean up the temporary session and device of the multicast EUI.
\nThe log and progress files will be removed.
\n
\n$ cd \/var\/run\/.fota
\n$ sudo touch cancel_36753562<\/p>\nadmin@mtcdt-444555:\/var\/run\/.fota$ ps aux | grep fota
\nroot 7265 0.9 1.6 16968 4220 ? Sl 08:06 0:00 \/usr\/bin\/lora-fota -d \/var\/run\/.fota -log \/var\/log\/log_fota_36753562_1750165566_0.log -resultfile \/var\/run\/.fota\/results_fota_36753562_1750165566_0.json -progfile \/var\/log\/progress_fota_36753562_1750165566_0.json -vv -rminput -j \/var\/run\/.fota\/fota_36753562_1750165566_0
\n<\/code>
\nThe server will NOT send downlinks to the end-devices to cancel the multicast and fragmentation session though.\n<\/li>\n<\/ol>\n
<\/p>\n
<\/p>\n