Skip to content

When activating an ABP device, fNwkSIntKey and sNwkSIntKey are both required and nullable #20

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

Open
philippe-tensio opened this issue May 23, 2025 · 0 comments

Comments

@philippe-tensio
Copy link

Description

Using the POST -> /api/devices/DEVEUI/activate, when sending a request that doesn't have a fNwkSIntKey and sNwkSIntKey, we still receive a HTTP 200, however the device will not activate. Even more confusing, is that both keys are displayed as 00000[...] in the Chirpstack UI, giving the impression that both keys are set properly.

If a fNwkSIntKey and sNwkSIntKey are provided, a HTTP 200 response is received and device becomes activated.

Would it be possible to for the request to return a HTTP 400, if we are missing fNwkSIntKey and sNwkSIntKey?

Repro steps

Using Chirpstack-Docker with Chirpstack 4.12 and Chirpstack-Rest-Api 4.12 and using an ABP Device, activate the device using the API (the issue will not occur if done using the UI).

Related issues

This forum post from 2023 helped show me the problem.

@philippe-tensio philippe-tensio changed the title When activating a device, fNwkSIntKey and sNwkSIntKey are both required and nullable When activating an ABP device, fNwkSIntKey and sNwkSIntKey are both required and nullable May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant