Bug: Batch import creates ABP tags in Device Twin for OTAA-based device models #2985
Comments
|
Removing those 3 parameters from the csv template does not fix the issue. |
|
If AppKey and AppEUI are filled, ABP properties (NwkSKey, AppSKey and DevAddr) are not setted in the device twin in azure. |
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]>
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
When importing a list of devices from the provided CSV template file, the portal should check the type of device authentication before creating it, and only set values for the proper authentication method (OTAA or ABP)
Current Behavior
The portal creates OTAA devices with all properties set (with values or empty strings depending on what's provided), which causes the devices to fail loading in the LoRa Network Server due to the presence of ABP variables in the Device Twin (e.g.
AppSKey).Steps to Reproduce
Context (Environment)
Portal version: 4.13.2
LoRaWAN Stack version: 2.2.2
Logs
Additional Information
The text was updated successfully, but these errors were encountered: