This morning, after upgrading my Laird gateway firmware, the device get connected. I don’t think it is related to the firmware directly (I see no reason as the protocol is the same). But I had to redeclare the gateway in the TTN backend, even in v2. The gateway id changed from laird-disk91-1 to eui-c0ee40… It is possible the ttn servers have also changed (now it is router.eu.thethings.network)
The laird FW version now is Laird Linux gatwick-laird-93.8.5.21 it was 93.7.x previously.
That said ; it means V3 devices could not be able to join V2 infrastructure currently running correctly.
I may have 2 other gateways with same configuration as the one migrated. I’ll make some join try on them to see if we can reproduce. (A bit more complicated to me as these gateways are not at home but deployed)
interesting - my first V3 gateway was/is a RAK833 on a Pi3 - it was very variable until I compiled the packet forwarder from the latest version and since then it’s been spot on.
Maybe there is something that V2 could tolerate that’s not acceptable in V3. Another thing to investigate!
Yes, that’s it. We don’t have forwarding to Packet Broker with the long discontinued TTN packet forwarder using the gRPC protocol. We’ll add that to the instructions, thanks, issue found!
Ok, cool ! thank you for sharing, I’ll upgrade my gateway soon … (… I have a lot to upgrade and all different !! )
Another question to make sure:
Does ttnv3 accepts Semtech Legacy protocol or just Basic Station ?
Perhaps spend 5 minutes on the documentation site?
The answer is V3 does support the Semtech UDP protocol as well as BasicStation and ttn-gateway-connector protocol. (The last protocol being used by the Kickstarter gateway and by gateways running mp-forwarder.)
Where did you get the information that mp-forwarder is supported in the documentation ? I was not able to find it and this question is basically the reason of that topic.
Haven’t looked for it in the documentation. Happen to have a special interest in mp-forwarder (being the author does that ) and because of that I already tested with a private instance of the stack before V3 was released. Have one of my gateways running it on the public V3 now. (The advantage of having 5 gateways on site, you can migrate one without sacrificing applications still on V2)
If you migrate to public V3 you’ll need to specify port 1881 for any connection using server type TTN. Do not add ‘@TTN’ to the serv_gw_id, just use the name. And you will have to create an API key as listed here.
By the way, I’ve found that page earlier: that’s clear for the SEMTECH UDP legacy packet forwarder. But I did not find anything about mp-forwader, so here was my question
The Things Kickstarter Gateway, is a gateway, not a protocol, apparently even if supported it is not working with Laird, so what can I conclude ?
And By-The-Way, sorry to ask lots of question and looking for precise response, But I’m trying to write a blog post as precise as possible and with less bug as possible on this complex topic, while migrating my gateways and trying to understand what is related to my personal setup vs a general case.
That’s not an easy job. So thank you for your help, and basically I hope this will help to reduce the number of question here at the end.
That the Laird gateway used a protocol (gRPC as mentioned by Johan) which is not supported? They have removed it from their recent images because support for the software was terminated by TTN some years ago. Keep in mind Laird did not use mp-forwarder, they used the TTN software written in Go. (Which uses 10 times the CPU required for mp-forwarder)
) and because of that I already tested with a private instance of the stack before V3 was released. Have one of my gateways running it on the public V3 now. (The advantage of having 5 gateways on site, you can migrate one without sacrificing applications still on V2)