Setup working on V2 but no live data or JOIN on V3

ipn_las_farm_real · August 12, 2021, 2:16pm

I have a TTKGW (Kickstart Gateway) working fine on V2 with several end devices, but had troubles on V3 migration. I can migrate the GW, and it is connected to V3 (freqn plan = EU_863_870_TTN + SF9 for RX2 + standard options). I can migrate End device to V3 and get JOIN + data from a GW 6km away from mine, but cant’ get any JOIN from my GW; also no traffic/live data on my GW when connected to V3.
On a bench setup:
TTKGW connected to V2 → works fine with my device migrsted to V3 (Join success + periodic data)
TTKGW connected to V3 → no JOIN with same end device above, and no traffic at all no TTKGW - I can see the 5th led blinking when my end device tries to Join but no live traffic is visible.

what I’m I missing?

robmileshull · August 12, 2021, 3:45pm

I’m having the same problem. The Gateway log says that a lora message has been received from the device and that an MQTT message has been sent out to the server, but nothing appears on the server end.

The packet count for the gateway is always zero. I’m using the lmic-node (GitHub - lnlp/LMIC-node: LMIC-node | One example to rule them all. LMIC-node is an example LoRaWAN app) software in a Heltec Lora V2 which I know works on LoRa. I’ve tried APB and OTA authentication.

My gut feeling is that something in the keys or application setup is wrong, but I’ve no way to prove this. If anyone can help with these questions I’d be most grateful:

does the packet count on the gateway console show ota key requests?
does the server silently reject incoming lora messages from the gateway if they are invalid? Is there any way I can enable more logging via the gateway configuration?
are there any other application settings required to make a device work, over and above the ones used to configure the device (is there an app key or something needed there)
does TTN V3 actually work with Heltec ESP32 devices?
will the packet count on a gateway advance if there are no integrations assigned to the incoming data?

Any help would be greatly appreciated.

adamjennison · August 16, 2021, 8:27am

I’ve the same issue.
I’ve followed the instructions to the letter on The Things Kickstarter Gateway | The Things Stack for LoRaWAN (thethingsindustries.com)

Rob and Brian (elsewhere on these forums) have followed the same instructions but separately to see if it’s the way and individual is interpreting the instructions that’s causing it to fail - but no, all three have the same problem after upgrading TTKG’s from V2 to V3.

We’ve had long discussions among our local TTN/dev group and have spent weeks on this issue now and are still failing.

Via UART I can see the MON,MQTT etc flowing nicely.
I can see it accept packets and fwd them via MQTT but there’s nothing in the V3 gateway console, no joins, no uplinks - nothing.

We’ve around 14 of these TTKG gateways to upgrade and this is a serious concern, the Hull community has relied on these gateways after the local Council purchased them on behalf of the community to kickstart a TTN, not being able to move to V3 will effectively kill TTG in the area.

The community doesn’t have the funds to purchase another 14 gateways to replace them

Has anyone else come across this problem?

WIFI: IP Address: 0.0.0.0
SNTP: State change from 0 to 1
CB: INET: Gateway has WiFi
INET: State change to 2
INET: Connected to a network, waiting for DHCP lease, checking validity with ping
SNTP: State change from 1 to 2
WIFI: IP Address: 192...*
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
INET: State change to 3
INET: Ping probe
INET: Error sending probe on Eth
INET: Ping response from MRF24WN, set as default
INET: State change to 4
SNTP: State change from 2 to 3
SNTP: State change from 3 to 4
MON: SYS Stack size: 3965
MON: TCPIP Stack size: 3793
MON: APP Stack size: 8008
MON: LoRa Stack size: 3913
MON: heap usage: 179KB (188KB), free: 160KB
SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
INET: State change to 5

MAIN: Leaving state 2
MAIN: Entering state 3

CNFG: Load online user config state change to 4
HTTP: Close active socket 0
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1007 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CONF: Parsing response token: HTTP/1.1 200 OK
CONF: ROUTER URL: mqtts://eu1.cloud.thethings.network:8881

CNFG: Load online user config state change to 6
FREQ: APP_URL_Buffer: https://eu1.cloud.thethings.network/api/v2/frequency-plans/EU_863_870_TTN
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1609 bytes
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3793
MON: APP Stack size: 3292
MON: LoRa Stack size: 3913
MON: heap usage: 265KB (272KB), free: 73KB
HTTP: Connection Closed
HTTP: Close active socket 1

CNFG: Load online user config state change to 7

CNFG: Configuring LoRa module
LORA: Changing state from 2 to 3
LORA: Starting reconfiguration
LGMD:Answer, cmd: 0x31, size: 1
LGMD:Answer, cmd: 0x31, size: 1
LGMD:Command, cmd: 0x3A, size: 0
LGMD:Answer, cmd: 0x3A, size: 16
Version, hwrev: 1, major: 1, minor: 4, band: 1
Serial: 4C-47-38-34-33-31-36-30-30-33-36-35
LGMD:Command, cmd: 0x34, sie: 1
LGMD:Answer, cmd: 0x34, size: 1
LGMD:Command, cmd: 0x34, size: 6
LGMD:Answer, cmd: 0x34, size: 1
LGMD:Command, cmd: 0x35, sie: 1
LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x36, sie: 1
LGMD:Answer, cmd: 0x36, size: 1
LGMD:Command, cmd: 0x37, sie: 1

LGMD:Answer, cmd: 0x37, size: 1
LGMD:Command, cmd:0x40, size: 1
LGMD:Answer, cmd: 0x40, size: 1
LGMD:Command, cmd:0x31, size: 1
LGMD:Answer, cmd: 0x31, size: 1
LGMD:Command, cmd: 0x30, size: 0
LGMD:Timeout on cmd: 0x30
LORA: configLora OK
LORA: Configuration succeeded
LORA: Starting operation
LORA: Changing state from 3 to 4
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3793
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 189KB (272KB), free: 150KB
LGMD:Receiving unknown data
LORA: Changing state from 4 to 5

CNFG: Load online user config state change to 9

MAIN: Leaving state 3
MAIN: Entering state 4
FLASH: Loading FOTA Data
FIRM: Requesting key …
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 515 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
FIRM: Starting download
FIRM: available bytes: 79
FIRM: (Downloaded FOTA key) F7 ****************************************
FIRM: (Stored FOTA key) F7 ***************************************
FIRM: Firmware is already downloaded
MAIN: No new firmware available

MAIN: Leaving state 4
MAIN: Entering state 5
MQTT: GOT IP: 63.34.215.128
Connecting to: 63.34.215.128
MQTT: Connection Opened: Starting TLS Negotiation
MQTT: Wait for SSL Connect
MQTT: TLS ready: Connect MQTT
RQMQTT: Connected

MAIN: Gateway bridging

MQTT: Sending status packet
MQTT: Report reboot error: 0103
MQTT: Sending status succeeded: 0
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3793
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3793
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 1
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
LORA: Kick LoRa module with ACK after not acked it for 60s
LGMD:LORA: Accepted packet

MQTT: Sending UPLINK OK
MQTT: Sending status packet
MQTT: Sending status succeeded: 2
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB

LORA: Kick LoRa module with ACK after not acked it for 60s
MQTT: Sending status packet
MQTT: Sending status succeeded: 6
LGMD:Rejected packet (0x11) *<----- is this a problem? *

MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
LGMD:Rejected packet (0x11) <— This looks strange…

MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 7
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB

This is an example of a lora sensor sending data - this can be seen to be accepted via the V3 application but when looking at the json payload it was fwd via a V2 gateway
The V3 isn’t mentioned and nothing shows up in the V3 gateway live data feed.

MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB
LGMD:LORA: Accepted packet

MQTT: Sending UPLINK OK
MQTT: Sending status packet
MQTT: Sending status succeeded: 23
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3292
MON: LoRa Stack size: 3857
MON: heap usage: 283KB (284KB), free: 55KB

I also see this on UART:
LORA: Kick LoRa module with ACK after not acked it for 60s

I have removed and re-seated the lora module, just in case, but it’s still the same.

Any help with the above problem will be appreciated as others are having exactly the same issue with TTKG gateways and the move V3.

adamjennison · August 16, 2021, 1:41pm

Successful update

I’ve gone through all sorts of incremental changes to all parts of the console and local configs.

It finally connected and data started to flow when I removed the gateway_ID**@ttn** from the local gateway setup page.

so my (local) gateway settings:
Gateway ID is the same as that you used in the V3 console, it doesn’t need @ttn postfixing to the id.
Account server for me (EU) is https://eu1.cloud.thethings.network
And the gateway key is the api key with link rights

I reset the gateway and tried the old gatewayid@ttn to see if I can replicate the previous failure and it was exactly the same, connection seen in the V3 console but no data or info on the live data and a v3 application didn’t use the gateway.

Reset to use gatewayid only and everything works as it should… data is flowing in the v3 console and the v3 app is showing as using the v3 gateway

A good afternoon of effort…

Let me know if it works for you too?

ipn_las_farm_real · August 16, 2021, 2:03pm

Just tested and it works!!!

also I was convinced I already had tried it before, but seems not.

Thanks!!!

adamjennison · August 16, 2021, 2:58pm

There’s nothing better than seeing something work after loads of failure attempts…

I can imagine your shout from here when you saw data in the console… I did similar but unfortunately the only one listening was the dog, who raised an eyelid as to say “meh…”

Now onto the next set of problems