Reactivate the device using API

ChirpStack Application Server
1

Hello

I was going through the chirpstack V3 API documents and found one interesting API.

[/api/devices/{device_activation.dev_eui}/activate]

image
image1194×177 11.6 KB

I also notice even after devices get deactivated due to redis TTL expire and devices become deactivated but we still have all activation parameters in DB in the device_activation table.

So now I will come to the question:

Suppose my device session TTL expires and the device shows deactivated in chirpstack. Can I still reactivate the device(OTAA) using this API, as we all have parameters in the device_activation table?

Thanks

2

I am not sure I understood correctly. To my understanding this is the same as “disable” on web interface of device > configuration > “device is disabled”

If device disabled or enabled there is no communication between chirpstack and the device. Chirpstack just ignores the device.

I don’t see a problem to re-activate the device. I don’t get what TTL has to do with chirpstack. Because of broken integration, chirpstack disables the device?

3

Thank you for your response.

Generally, when TTL expires, the redis device becomes deactivated and in device->activation it will have the “This device has not yet been activated.” message.

But what I observed is that session parameters still persisted in the DB in the device_activation table.

So, can we reactivate those devices using API?

Thanks

4

Yes you can. However, make sure to set the correct frame-counters.

5

Thank you for the response
I think frame counter also stores in same table?

Should i be using the same value?

Thanks