# Unable to switch activation mode in V3

**URL:** <https://www.thethingsnetwork.org/forum/t/unable-to-switch-activation-mode-in-v3/43624>\
**Category:** V3 Devices\
**Created:** [February 1, 2021, 10:56pm UTC](https://www.thethingsnetwork.org/forum/t/unable-to-switch-activation-mode-in-v3/43624 "2021-02-01T22:56:45Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![bluejedi](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/bluejedi/32/44639_2.png) [@bluejedi](https://www.thethingsnetwork.org/forum/u/bluejedi)\
**Post date:** [February 2, 2021, 12:29am UTC](https://www.thethingsnetwork.org/forum/t/unable-to-switch-activation-mode-in-v3/43624/5 "2021-02-02T00:29:04Z")

</div>

> [@jezd](#):
>
> - Once saves then restart device to gain new v3 Device Address which is key to routing to V3
> - Once you see join in V3 console and all looks good remove device from V2

This will only work when having (also) a V3 gateway and the device picks up up the join request from the V3 gateway first (instead of from a V2 gateway) as described [here](https://www.thethingsnetwork.org/forum/t/connecting-new-ttig-to-the-things-network-v3-problem/43363/13) (also check replies).  
If it picks up the join accept from a V2 gatewway first then it will start a session with V2 and traffic will be routed to the V2 environment and not V3.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/unable-to-switch-activation-mode-in-v3/43624)._
