# TTN V2 to V3 migration

**URL:** <https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445>\
**Category:** Migrating Gateways to V3\
**Created:** [January 29, 2021, 9:44am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445 "2021-01-29T09:44:20Z")\
**Posts on this page:** 15\
**Page:** 3

<div class="post-metadata">

**Author:** ![Jeff-UK](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeff-uk/32/35697_2.png) [@Jeff-UK](https://www.thethingsnetwork.org/forum/u/Jeff-UK)\
**Post date:** [May 27, 2021, 10:15am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/46 "2021-05-27T10:15:47Z")

</div>

**IMPORTANT UPDATE!**

Recently @laurens has advised:

Since the v3.13 update of last week, we can exchange traffic between TTN V2 and The Things Stack Community Edition, _both ways_. **Meaning that you can start migrating your gateways as it won’t impact the coverage of the public network.**

Unless someone shouts and says something is broken or discovers an integration related issue it looks like we have green light to migrate our GW’s 🙂 🎆 🍾

_It may be prudent to start with one or two each or by co-ordination within communities to test as you go._

We would recommend that migration is undertaken _WITHOUT DELETING GW FROM V2_ - for now! Just in case you need to roll back whilst resolving any discovered issues.

Also if your GW is a TTIG - _HOLD ON V2 FOR NOW!_ We await formal announcement of CUPS support under TTS(CE) aka TTN V3. We will shout it on the Forum once TTIG migration is a supported option - testing is currenty underway and we will keep you updated under seperate threads/announcements.

Note: One of the roadblocks for myself and others in taking this step has been the lack of Cayenne/myDevices integration OoTB under Webhooks (formerly http integrations) in V3, with this change of guidance it shoud be the case that any V2 Cayenne integrations should continue to work with data fed through V3 GW’s until V2 shutdown (?) reducing risk…_anyone interested in Cayenne should start to lobby myDevice hard for an off the shelf V3 integration_ (TTI have done their bit - it is up to myDevices to step up now).

> **[Home - myDevices](https://mydevices.com/)**
>
> myDevices, an IoT Solutions company, empowers partners and resellers to deploy finished IoT plug-and-play solutions under their own brand.

[https://iotinabox.zendesk.com/hc/en-us/requests/new](https://iotinabox.zendesk.com/hc/en-us/requests/new)

Regular request posts here:? 😉

> **[myDevices Cayenne Community](https://community.mydevices.com/)**
>
> Community forum for Cayenne users

---

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [May 27, 2021, 11:02am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/47 "2021-05-27T11:02:43Z")

</div>

Wot’s this then?

![Screenshot 2021-05-27 at 12.02.13](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/9/a/9aec015ef77b5af866fa0fed70ecd60d7b4ce379.png)

---

<div class="post-metadata">

**Author:** ![Jeff-UK](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeff-uk/32/35697_2.png) [@Jeff-UK](https://www.thethingsnetwork.org/forum/u/Jeff-UK)\
**Post date:** [May 27, 2021, 12:34pm UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/48 "2021-05-27T12:34:06Z")

</div>

A nice surprise? Christmas come early!? Will have to experiment… 😉

---

<div class="post-metadata">

**Author:** ![Jeff-UK](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeff-uk/32/35697_2.png) [@Jeff-UK](https://www.thethingsnetwork.org/forum/u/Jeff-UK)\
**Post date:** [May 27, 2021, 1:20pm UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/49 "2021-05-27T13:20:29Z")

</div>

Did a quick check in between other tasks and yep its there 👏 - so quickly added integration to an existing V3 registered Laird RS186 t&h sensor that was used for early V3 tests and is running fine.

However, where I see payload decoded just fine in V3 console:

![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/8/1/81daae1f51bfafaad5d8a679f79417feb405b347.png)

There is a problem with Cayenne display that I will need to investigate further when I have a few mins (think I have seen this reported previously with an easy fix but damned if I can find quickly now I need it!)

![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/d/d/dd52b100e8db78e8fec3a9444c7162a5733004ce.png)

Office/Workbench a bit of a sweatshop but not that bad! 🤣😓 😅

Guess I have no excuses for GW migration now - just have to find time! (And figure out how to get around Covid travel bans…e.g. guess Hamburg GW off limits for now! ☹ )

---

<div class="post-metadata">

**Author:** ![dream\_tech](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/dream_tech/32/35697_2.png) [@dream\_tech](https://www.thethingsnetwork.org/forum/u/dream_tech)\
**Post date:** [May 27, 2021, 2:00pm UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/50 "2021-05-27T14:00:29Z")

</div>

Do we still have access to V2?

---

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [May 27, 2021, 2:42pm UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/51 "2021-05-27T14:42:23Z")

</div>

What have you tried in the way of accessing the v2 console???

Have you been told we can’t??

---

<div class="post-metadata">

**Author:** ![mid-walesha](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/mid-walesha/32/48324_2.png) [@mid-walesha](https://www.thethingsnetwork.org/forum/u/mid-walesha)\
**Post date:** [June 4, 2021, 7:27pm UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/52 "2021-06-04T19:27:17Z")

</div>

Anyone migrating their Things Outdoor Gateway - ensure the RTC is setup with NTP after installing the Basics Station firmware. SSH access required.

Time and Date with ours was out (causing issues with the certificates). School boy error!

---

<div class="post-metadata">

**Author:** ![ajayaj](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/ajayaj/32/38260_2.png) [@ajayaj](https://www.thethingsnetwork.org/forum/u/ajayaj)\
**Post date:** [June 8, 2021, 1:58pm UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/53 "2021-06-08T13:58:47Z")

</div>

I have migrated v2 gateway to v3 with gateway id, however status is ‘Disconnected’ in V3. The status in V2 is Connected. In V3 live data i coluld see the message:  
“The stream connection was lost due to a network error”

Please guide me on this to

---

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [June 8, 2021, 3:10pm UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/54 "2021-06-08T15:10:55Z")

</div>

> [@ajayaj](#):
>
> “The stream connection was lost due to a network error”

That’s just a console error saying that it lost connection to show the incoming stream of messages.

I’m not sure how well defined it is for gateway status if the v2 is processing the messages …

Do you have any v3 devices?

---

<div class="post-metadata">

**Author:** ![ajayaj](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/ajayaj/32/38260_2.png) [@ajayaj](https://www.thethingsnetwork.org/forum/u/ajayaj)\
**Post date:** [June 9, 2021, 5:36am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/55 "2021-06-09T05:36:45Z")

</div>

I have not activated any devices in V3 as of now. But planning to move all devices currently in V2 to V3. For this purpose as first step I moved the v2 gateway and encountered the error as mentioned. Are you saying by adding a new device to V3 stack may resolve the problem ?please let me know.

---

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [June 9, 2021, 7:57am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/56 "2021-06-09T07:57:11Z")

</div>

1. You are over thinking a simple disconnect between the server and your web browser.

2. Migrate devices first, then gateways.

3. You’ll have to migrate everything at some point, so just try it.

---

<div class="post-metadata">

**Author:** ![Maj](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/maj/32/47732_2.png) [@Maj](https://www.thethingsnetwork.org/forum/u/Maj)\
**Post date:** [June 23, 2021, 1:55am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/57 "2021-06-23T01:55:58Z")

</div>

> [@Jeff-UK](#):
>
> Since the v3.13 update of last week, we can exchange traffic between TTN V2 and The Things Stack Community Edition, _both ways_.

Has anyone observed this working in the AU cluster? ie. gateways configured on the V3 community au1 cluster forwarding to apps on the V2 AU/meshed cluster. Doesn’t seem to work for us.

---

<div class="post-metadata">

**Author:** ![AndyG](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/andyg/32/35697_2.png) [@AndyG](https://www.thethingsnetwork.org/forum/u/AndyG)\
**Post date:** [June 23, 2021, 2:48am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/58 "2021-06-23T02:48:54Z")

</div>

Hi, I have 2 gateways, one on V2 and the the other in V3, and a couple of devices in each.  
In the V2 console I see both gateways in the application metadata.  
In the V3 console I only see the V3 gateway in the application traffic metadata.  
I can take a look in node-red this evening to see if I get both from V3 via MQTT.

---

<div class="post-metadata">

**Author:** ![Maj](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/maj/32/47732_2.png) [@Maj](https://www.thethingsnetwork.org/forum/u/Maj)\
**Post date:** [June 23, 2021, 3:24am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/59 "2021-06-23T03:24:36Z")

</div>

OK I think we’ve worked it out.

For gateways using V3 band plan “Asia 920-923 MHz (used by TTN Australia)”, there is no corresponding band-plan in V2 and packets do not seem to be forwarded. For gateways using the “Asia 920-923 MHz” band plan, this maps to a V2 band plan and works OK. AU915 gateways will probably be fine.

We’ll work around it!

---

<div class="post-metadata">

**Author:** ![AndyG](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/andyg/32/35697_2.png) [@AndyG](https://www.thethingsnetwork.org/forum/u/AndyG)\
**Post date:** [June 23, 2021, 3:38am UTC](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445/60 "2021-06-23T03:38:22Z")

</div>

Mine are both AU915.

[Previous page](https://www.thethingsnetwork.org/forum/t/ttn-v2-to-v3-migration/43445.md?page=2)
