# OTAA shows "Activation DevNonce not valid: already used"

**URL:** <https://www.thethingsnetwork.org/forum/t/otaa-shows-activation-devnonce-not-valid-already-used/5079>\
**Category:** v2 Backend\
**Created:** [January 25, 2017, 2:45am UTC](https://www.thethingsnetwork.org/forum/t/otaa-shows-activation-devnonce-not-valid-already-used/5079 "2017-01-25T02:45:13Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [February 7, 2018, 8:58pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-shows-activation-devnonce-not-valid-already-used/5079/20 "2018-02-07T20:58:11Z")

</div>

Or use ABP while developing other details of your device, and only when (almost) done go back to OTAA?

(For testing, if you [disable the ABP frame counter check](https://www.thethingsnetwork.org/forum/t/abp-node-stopped-working-fixed-by-creating-new-abp-why/3200/7), you could even use the same ABP details in multiple devices, I’d say.)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/otaa-shows-activation-devnonce-not-valid-already-used/5079)._