TTN Console shows uplink traffic in gateway, but no data in application


(Everhamme) #1

I’ve had two issues so far with OTAA and getting data to show up in my application. There’s a few threads on here, but I don’t see many good documentations steps to try to figure out why data isn’t showing up on TTN… anyone interested in 1) helping me out with my particular issue and 2) contributing to a troubleshooting guide to make this process go smoother? it seems most of the troubleshooting threads on here are unresolved and the issue just magically fixes itself (with no change on the users end)

My am trying to get my STM32 board to send data to TTN.

Here’s my example sketch https://github.com/kriswiner/CMWX1ZZABZ/tree/master/Cicada (need to set subband to 2 to configure for ttn)… it uses CayenneLPP fyi…

Here’s what I did

  1. create a new app in ttn
  2. add a new device to this new app
  3. copy otaa keys to sketch (appEui, appKey, devEui), compile and run sketch
  4. Watch ttn gateway log console and ttn app/device console for traffic
  5. See device traffic on gateway for the join
  6. see device traffic on app/device for join
  7. see device traffic on gateway to send payload data (no errors on gateway console)
  8. see NO device traffic on app/device console for payload data (Frames up is not increasing above 0). I’ve tried disabling Counter Checks and no difference.

I’ve also tried deleting and creating a new application as well.

Any help is appreciated!

If OTAA is the preferred route to use on here then why is it to hard to troubleshoot?


Not receiving data in application anymore, but I still see it in gateway tab
#2

I don’t see any dragino question in here.
I don’t see any code you wrote or use for your stm32 board


(Everhamme) #3

ok wrong category… I was posting about dragino earlier and it opened up a draft message… my fault…

what code do you need? data is going to TTN Gateway, but not to application, seems like a TTN issue? all of the code is posted in GitHub… here’s the demo sketch I used (I did set subband=2) https://github.com/kriswiner/CMWX1ZZABZ/blob/master/Cicada/Cicada.v07/Cicada.v07.ino


(Everhamme) #4

Here’s the screenshot from the Gateway showing the node registering with OTAA I believe
Gateway11

Here’s the log data from the application console (with no payload message showing up
Application_device1


(Arjan) #5

So, there’s no OTAA problem.

What payload format did you set for the application? If you have the Cayenne integration enabled, then you might need to select “Cayenne LPP” for the payload format as well.

What’s the exact full packet you see at the gateway? MAC commands such as a DeviceTimeReq might cause display issues; see Cannot see data in device dashboard, while OTAA works and uplinks show in gateway’s traffic.


(Everhamme) #6

Here’s my payload snapshot

40582B012600010001FA6792FD360F6A882A3703030D6F38A34F9006CBC750AE58EDA5C8734A32
Application_device1c


(Arjan) #7

Unfortunately, an online decoder shows that this looks just just fine. (It’s just a LoRaWAN header for an unconfirmed uplink, the actual application payload, and the MIC. No MAC commands that could be troublesome.)

TTN should really not care about the application payload. You could copy the secret NwkSKey (and AppSKey) session keys from the device in TTN Console into that online decoder, to verify that the MIC is okay. (But bugs in your LoRaWAN stack aside, the MIC really should be valid, as the successful OTAA proves the keys are okay.) And check that there are no errors in the Trace part when clicking the uplink in the gateway’s Traffic page TTN Console. (Unfortunately, an invalid MIC is silently ignored.)

Did you already configure the Cayenne integration? Maybe remove that for a quick test?

Is the DevEUI really unique (not some easy to read value you created yourself)?

Is the application also registered to a handler in the us-west region, like your gateway is?

And any chance you can use an MQTT client (or ttnctl subscribe) to see if it the data is available even when it’s not shown in TTN Console?


Not receiving data in application anymore, but I still see it in gateway tab
(Youssefbaiji) #8

Same exact thing happened to me my application use to work fine ,now i get connection with my mdot but nothing appears on the TTN application page. any help


(Arjan) #9

Then the same suggestions to debug the problem apply. So, what’s your response to the suggestions in my previous post?


(Youssefbaiji) #10

What i did ,i troubleshooted today i thought maybe my mdot is not working ,so i updated the firmware i created a new application ,used teraterm to send AT+Send still nothing ,then i used my new xdot first time and the same problem happened , i suspected maybe the packet forwarder ,but the strange thing is when i used the mdotbox i could see payloads. so tomorrow ill try to change the handler because i live in USA but this handler use to work fine ill just change it and see thank you


(Arjan) #11

So, which handler and router are you using now?


(Youssefbaiji) #12

my gateway is multitech conduit configured as to forward packets to ttn and i use to use ttn-eu handler my application worked fine for 3 months now ,today after i returned from break ,i powered up i got nothing


#13

Hi Youssef,

Is this you ? :sunglasses:

yb

source


(Youssefbaiji) #14

yes it is thank you . i didnt see it ,was it out this week


(Youssefbaiji) #15

i changed the handler today from eu to west US and it worked .Thank you nothing was wrong. i dont know why it stopped working because it use to be working fine


(Everhamme) #16

I changed my handler as well from eu to west US … also re added the device. working now…

Thanks for all your help!


(Arjan) #17

For future visitors, @youssefbaiji and @everhamme:

Are your handler (for the application) and the router (for the gateway) in the same region now? So, is the gateway using ttn-router-us-west or ttn-router-eu, now that you’ve changed the application to use ttn-handler-us-west?


#23