Extracting Data from TTN to my Server

(Lora Wansmaru) #22

Continuation from the above question:

I am using the following URL to schedule downlink messages:
I have entered my-app-id/my-process-id and secret key, but in response I always get 502 Bad Gateway/ nginx/1.11.10

(Celia Garrido-Hidalgo) #23


I had never tried to implement the HTTP integration, but I tried yesterday to see how it works. As far as I know, you’re right, the Process ID is user-defined and the Authorization is optional. However, I’m not sure about the field URL.

I tried what you were trying to do, and I also got the “502 Bad Gateway” error. Then, I tried to use the URL of a Channel I created some months ago in ThingSpeak (https://thingspeak.com/), and it sends data from TTN to Thingspeak via HTTP (however, you were interested in downlink). Finally I tried to introduce the IP address of a server I created (http://xxx.xxx.xxx.xxx:8080/) in the URL field and it works, I receive a JSON from TTN and I suppose that sending downlink data to end-devices would not be a problem.

I’m also starting with TTN and so on, I hope these options can help you. Anyway, I’m sure some other people know the answer :wink:


(Celia Garrido-Hidalgo) #24

Hi again, this tool may be useful for inspecting your HTTP requests:



(Lora Wansmaru) #25

Thanks @celiagarridoh, just received the json data at my server using the step you had provided. The json data included the downlink url which is working perfectly to send downlink data. Great help ! :slight_smile:

(Lora Wansmaru) #26

Hi, anything about Gateway’s Device EUI??

(Celia Garrido-Hidalgo) #27


Try this: Ic880a concentrator with Raspberry pi Gateway


(Lora Wansmaru) #28



Can we change the operational frequency of RN2903 Lora Module?
As of now its being operated on 868 Mhz and in India this band is not licence free. TTN says it works on 865-867 Mhz but my module frequency does not change?
Any help

(Celia Garrido-Hidalgo) #29

I’ve never used this module, but as far as I know it operates in the 915 MHz frequency band, doesn’t it?


I’m sorry that I can’t help you.


(Lora Wansmaru) #30

Hi Celiagarridoh ,

Any idea if TTN supports 2 different Ports for uplink and downlink?
Currently it allows 1700 port on the Gateway to uplink and downlink. Can we change downlink port other than 1700?

(ahaw021) #31

What is the benefit of separating these function to different ports?


(ahaw021) #32

I don’t believe you can.Review: RN2903 AU firmware


(Lora Wansmaru) #33

Hi celiagarridoh ,

Is there any issue with Data Packets logs on the TTN console, my gateway and devices are working fine but no data on the console since 3-4 days,

Kindly advice,

(Saiprakash) #34

I am able to receving the uplink messages in Node.js(on console). Now i want to send those received uplink messages to my server(local host:xxxx) please tell me the procedure how to do this.

your help is most valuable to me.
please give me reply
Thank you

(Celia Garrido-Hidalgo) #35


I am so sorry that it’s been such a long time since you asked me, but I was finishing my exams at university. I’ve been a time disconnected, my apologies.

In response to @LoraWANSMARU, I cannot confirm that, I would also like to know the answer.

In response to @saiprakash, I think I used the “socket-io” client on Node.js:

io.connect('http://localhost:xxxx', { reconnect: true, query: "var=abc" })
socket.emit('abc', ...)

I send the data using the emit function, you can take a look while I update my nodes and, in case you need further information, don’t hesitate to ask.

My apologies one more time for being away such a long time, now I came back to stay :wink:

Best Regards,


The data stream is like that : Lora Node -> LoraGateway -> TTN ->myAPIserver.
We still cannot analysis the specific data on TTN, we only can read the data on our server, is that right ?
What is the advantage of this ?
Instead we can use thingspeak server directly and the LoraGateway sends the package from lora Nodes to thingspeak directly, so that we can read specific data with thingspeak api interface. This is so convenient and we only need one server.


If you only want your nodes to be able to connect to your LoRa Gateway and you only want your nodes to be able to connect, you indeed don’t need the TTN backend.
With TTN, your node could also connect to my Gateway (and all the others out there) and other nodes can use your Gateway to connect.
It is the difference between a private network and a public one.

(Arjan) #38

Also, the (TTN) LoRaWAN network servers provide downlinks, OTAA, ADR and later on class B and C. It’s not an easy task to do all that yourself.


Yes, this is right. I remember if I use thingspeak API interface, I do not have these functions to setup, Thanks


Your mean my lora node is connected to your (or others) gateway. Yes, that seems to be more public.


Yes, the idea is that if you would want to use the node while it is not within reach of your Gateway, but it can reach mine (or anyone others) Gateway, it can still send its data. And you (and only you) would still be able to retrieve it.
It might not be an issue for you if your nodes don’t move, are always in the same place, but the idea is to build a distributed network eventually covering the whole planet (or at least large parts of it), with not just one person / party / company being responsible for the gateways. So if you need coverage somewhere, you simply can decide to put a gateway there (without having to ask TTN to put it there) and while doing that not only helping yourself but anyone else in that area.