Migrating from TTNv2 to TTNv3

Andreas · November 11, 2021, 9:35am

Hi there,

as probably most of you know already, TTN is migrating from V2 to V3, which is a disruptive change. More information can be found at:

With kind regards,
Andreas.

Andreas · November 11, 2021, 9:35am

Sunsetting V2

TTN:

In the coming weeks we will schedule brownouts of the V2 community network. The goal of these brownouts is to create temporary interruptions in applications that still rely on V2. We hope that these interruptions will then trigger alerts to the relevant people, who may not be aware that some of their applications still rely on V2.

During these brownouts, the following will happen:

Access to the MQTT APIs will be disabled. Alternative access to the MQTT APIs will be available on ports 11883 (TCP) and 18883 (TLS).

Access to the Storage Integration will be disabled. Alternative access to the Storage Integration will be available on port 10443 (HTTPS).

External integrations will be paused, uplink traffic be queued and delivered after the brownout.

– The Things Network Status - The Things Network V2 is Permanently Shutting Down

Andreas · November 11, 2021, 9:43am

Activities by Hiveeyes people

@Thias submitted an update to the CayenneLPP payload decoder the other day already, see adapt decoder function to The Things Stack V3 by thiasB · Pull Request #23 · ElectronicCats/CayenneLPP · GitHub.
@tonke is working on adjusting Terkin for CPython / Raspberry Pi / Dragino accordingly, see Terkin-Variante für CPython / Raspberry Pi / Dragino LoRa/GPS HAT - #12 by Andreas.

Andreas · November 11, 2021, 10:14am

I just received this letter from TTN. They are getting serious now.

TTN:

Dear The Things Network community member,

Based on the data from your The Things Network account, you still have 2 active devices on The Things Network V2, namely on foobar (2).

The Things Network V2 will be shut down on December 1st, 2021. All devices still active on V2 will stop working on December 1st.

In the next weeks, we will create brownouts for the V2 community network. These brownouts are temporary interruptions in applications, to remind relevant people that some of their applications still rely on V2. More information will be released on our status page.

Why migrate to The Things Stack?

The Things Stack Community Edition is the next-generation LoRaWAN® Network Server with countless new features. It is also more strict with regard to non-compliance of LoRaWAN devices. By migrating to The Things Stack, you make sure that your devices are LoRaWAN compliant.

I am unable to physically reconfigure end devices. What should I do?

If you are unable to reconfigure end devices due to Covid-19 restrictions in your location, please contact us at community@thethingsnetwork.org

What about gateways connected to V2?

We also urge to migrate your gateways, but this is a separate process. If it is not possible to reconfigure gateways due to Covid-19 restrictions, they will keep working and providing coverage for The Things Stack Community Edition through Packet Broker. However, features like traffic view will be unavailable on gateways that have not been migrated to The Things Stack.

If you have any questions about migration, please visit our forum for more information.

We are here to help you make the transition smooth. A lot of content is available in our documentation, YouTube channel and website.

Already migrated your devices? Then we’re good - this email is not intended for you.

Best regards,
The Things Network

clemens · November 12, 2021, 9:14am

So there is a bolt-hole! ;-) Let’s see how many excuses TTN will get based on

Andreas · December 1, 2021, 6:32pm

Maybe this is helpful to anyone?

github.com/pycom/pycom-micropython-sigfox

LoPy4: sending LoRa datagram to TTN V3 Stack after restore LoRa nvsram failure

opened 03:16PM - 30 Nov 21 UTC

teusH

Use of LoPy4, firmware 1.20.2.rc10 (jan 2021) Issue with sending LoRa datagram …to TTN V3 Stack after restore LoRa nvsram. Migrating LoPy4 from V2 to V3 The Things Network Stack went ok after power off LoPy4, reset LoRa nvsram, power on. First join went OK. Rejoin after power cycle went ok. If no LoRa nvsram dump/restore is used sending to TTN V3 Stack works OK. The issue: those LoPy4's which use a restore of LoRa nvsram (so no rejoin) for sending the next datagram the LoRaWan package is not received by TTN. So the deepsleep/reuse of LoRa state seems not to work with V3. With TTN V2/deepsleep there was no LoRa state restore problem. V3 is using a strickter LoRa implementation. E.g DevID use. Is this a firmware issue or a use of LoRa state software issue?