- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hi Etienne. CreateOTAUpdate doesn't yet support the destinationPackageVersions parameter that's in CreateJob. And therefore you can't yet use CreateOTAUpdate
to deploy package versions.
You could indeed consider to call StartSignerJob
, CreateStream
and CreateJob
individually to compose a job with an OTA-compatible job document. Similar to what I described here: https://repost.aws/questions/QUp0y4sHlfRe-uMooegUs7vA/how-to-configure-retries-on-ota-jobs-on-the-iot-core#AN5T7M-nUdQoqsIk06E-TXOA.
I suspect though that the benefits probably don't justify the work. A smaller and easier win might be to call CreatePackageVersion every time you upload a new firmware version to S3. And modify your device firmware to report the currently running firmware version in the new $package
reserved named shadow. Then you would benefit from the package version metrics in the console. That way software packages would at least help you visualize the versions deployed in your fleet.
Hi Greg.
Thank you so much for your help. Updating the $package shadow directly from devices is a great solution. I have all the information I needed.
Relevanter Inhalt
- Wie veröffentliche ich MQTT-Nachrichten von meinem Gerät auf AWS IoT Core, wenn ich Python verwende?AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr