This topic created to focuss discussions around practicalities and issues arising from pending TTN V2 to TTN V3 migration, and associated V2 Sunset 2H’21 *Note TTN V2 Gateways currently forward to TTN V3 with no issues (*though you may see some GW metadata is stripped/annonymized, potentially affec…

[image] johan: [image] bluejedi: Has option ‘Make owner public’ been removed? Is owner now private or public? There’s really no such thing as an owner. This was already the case with V2, but that was a bit hacky. There are collaborators only, and those can be users or organizations. …

[image] johan: Well that’s great for Helium but that’s completely irrelevant. Can understand your reaction and perspective Johan, but it absolutely IS relevant - if we start hemoeraging users or GW providers in the meantime :wink: (Hi Jeroen BTW!) myDevices may be dragging their feet but th…

[image] Jeff-UK: [image] johan: The third thing we may want to add here is the owner Absolutely should have some mechanism for declaring that - as legally and for insurance may need to be able to contact the ‘responsible’ owner…what if the device is defective and starts causing interferen…

Effectively that is what we have now - the user contacted by message through TTN Forum or Console message :slight_smile: Most names on the system are fake or a user handle vs full name (bluejedi, Jeff-UK?!)

[image] Jeff-UK: Effectively that is what we have now - the user contacted by message through TTN Forum or Console message Sort of but not exactly. For V2 when owner was public for a gateway this meant that the TTN account name was public. When the account name is published the owner’s accou…

Per @pe1mew a visual representation of what has been described above and elsewhere: [image] TTN V2 to V3 migration Migrating Gateways to V3 Here is a visualization of the consequences of migrating gateways from V2 to V3: [image] [image] (to enlarge the images: right-cli…

Per @pe1mew a visual representation of what has been described above and elsewhere: [image] TTN V2 to V3 migration Here is a visualisation of the consequences of migrating gateways form V2 to V3: [image] [image] (right-click to enlarge the images)

[image] Jeff-UK: myDevices may be dragging their feet but they need to appreciate they risk loosing a lot too - profile and position as a (the?) leading external integration with TTI/TTN I nudged them again and I heard that my team already did so as well. There’s apparently something in the p…

[image] johan: I nudged them again and I heard that my team already did so as well :ok_hand: Is there anything the (a few!) users need to do to lobby or cajole them that might help your case or is that just noise and hinderance if you think progressing in a timely manner

how can i issue a “force rejoin” from the community backend to a remote device ?

TTN V2 to The Things Stack V3 Transition

TTN V2 to V3 Upgrade

Jeff-UK (Jeff Uk) January 29, 2021, 10:10am 64

Per @pe1mew a visual representation of what has been described above and elsewhere: