-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: startupOrder not supported in Edge Device Model schema #3023
Comments
There is actually a bug when an edge model is created using API: the Json property name for properties is set with a lowercase letter, but when saving to Azure the first letter is capitalized. Then the list of modules is not recognized. |
kbeaugrand
added a commit
that referenced
this issue
Dec 5, 2024
* Add of layerId in device twin * #2998 Quartz migration for SendPlanningCommand * #2856 Disable built-in device model deletion * #3238 Update view when a device is unchecked * 3239 Allow to delete a planning from client * 3239 Allow to delete a planning * 2998 Schedule commands * #3239 Change checkboxes for layers displayed * Merge from main * 2516 add supportLoRaFeatures tag in template file * #3250 Import device list using the template given * #2985 Batch import creates ABP tags in Device Twin for OTAA-based device models * #3251 Import device - data overwritten * Unit tests * Update src/IoTHub.Portal.Infrastructure/Jobs/SendPlanningCommandJob.cs Co-authored-by: Kevin BEAUGRAND <[email protected]> * #2958 Remove 'Connection State' and 'Last status update' columns * #3023 startupOrder not supported in Edge Device Model schema --------- Co-authored-by: E068097 <[email protected]> Co-authored-by: judramos <[email protected]>
9 tasks
kbeaugrand
added a commit
that referenced
this issue
Dec 5, 2024
* Add of layerId in device twin * #2998 Quartz migration for SendPlanningCommand * #2856 Disable built-in device model deletion * #3238 Update view when a device is unchecked * 3239 Allow to delete a planning from client * 3239 Allow to delete a planning * 2998 Schedule commands * #3239 Change checkboxes for layers displayed * Merge from main * 2516 add supportLoRaFeatures tag in template file * #3250 Import device list using the template given * #2985 Batch import creates ABP tags in Device Twin for OTAA-based device models * #3251 Import device - data overwritten * Unit tests * Update src/IoTHub.Portal.Infrastructure/Jobs/SendPlanningCommandJob.cs Co-authored-by: Kevin BEAUGRAND <[email protected]> * #2958 Remove 'Connection State' and 'Last status update' columns * #3023 startupOrder not supported in Edge Device Model schema --------- Co-authored-by: E068097 <[email protected]> Co-authored-by: judramos <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
I should be able to specify the
startupOrder
parameter in the Edge Device Model schema in order for it to be applied in the Azure IoT Hub deploymentCurrent Behavior
The
startupOrder
parameter isn't supported in the portal's API endpoint body, it is ignored if you add it to the schema.Steps to Reproduce
startupOrder
parameter in the edgeModule parametersstartupOrder
parameters definedContext (Environment)
Portal version:
LoRaWAN Stack version:
Logs
Additional Information
The text was updated successfully, but these errors were encountered: