RAK2245 Rpi TTN logging

I have an rpi running the RAK2245 lora gateway hat pushing data to the TTN network.

However all the logs are empty. Is there any way I can log the gateway data of the devices that are communicating with the device so I can then push them to say one of my InfluxDB so I can see what traffic has been going through the device?

I don’t seem to be able to get any logging happening out of the server to the /var/logs. Also mosquitto_sub -h localhost -p 1883 -t “gateway/+/devices/+” doesn’t show any output of when devices are communicating (I may be looking in all the wrong places here too!).

I also thought about trying the http api, but it just seems to be for local application data for if I was using the gateway as a stand alone loraserver not connected to an external back end - how to setup the jwt token which seems like a good idea, but I’m not exactly 100% sure how to implement it correctly. It may not be what I need here though at all.

Then your question is off-topic here. This is the LoRaServer forum, if you are using TTN you are not using LoRaServer, even if RAK shipped a copy of it on your box/SD card.

Also mosquitto_sub -h localhost -p 1883 -t “gateway/+/devices/+” doesn’t show any output

That’s specific to LoRaServer (and the machine running the MQTT broker) and inapplicable to TTN.

I also thought about trying the http api,

Again specific to LoRaServer and inapplicable to TTN

I know this is the loraserver forum, the forum provided by the people who actually wrote the software which runs on my device, where else would I go to for software related help related questions for the loraserver.io?

It would seem that unless you plan on deploying a private lora then loraserver.io is about as useless as an ashtray on a motorbike. If they don’t want to get asked TTN related questions then remove the TTN packet forwarder functionality out of the provided server software.

I see a lot of this, if its not us its them - we don’t do that blah blah around lora/lora tech… all you’re all doing is killing off the desire to use the tech. A bit like how stackoverflow has been taken over by haters the last few years. This reply has just pushed me to think again about developing our own P-IoT you kids can kick, cry and scream from your own sandbox haha.

You’re really not being fair to anyone here.

If they don’t want to get asked TTN related questions then remove the TTN packet forwarder functionality out of the provided server software.

LoRaServer does not have any such functionality.

If you have a complaint, you should direct it at RAK, which combined several different pieces of software from different sources on the box they sold you.

LoRaServer and TTN are two entirely distinct worlds, granted there are people who move between them and a bit of friendliness, but if you are using one you are not using the other, and that goes both ways.

RAK sold you a product that supports three main possibilities:

  • connection to TTN
  • connection to some other external network server, possibly a cloud instance of LoRaServer
  • connection to an onbaord copy of LoRaServer

Since you are using TTN, the fact that the box also has a copy of LoRaServer on it is entirely irrelevant. LoRaServer specific parts of your box (like the gateway bridge and its MQTT feeds) will not help you at all when using the gateway with TTN.

Your issue is off topic here, you need to pursue it with RAK or failing that the TTN forum.

Thanks, got all that from your original post - hence my reply.

I would of thought data logging would be fairly simple to implement on a packet forwarder for devices that are capable of doing so, even to a local syslog server for devices unable to carry the log sizes. Anyway onwards and upwards I wont waste anymore time on it.

The problem is that your question actually isn’t actually related to loraserver.io. There may be some loraserver.io software running on your device but the way you’re using it has nothing to do with loraserver.io if you forward traffic to TTN.

That’s a pretty funny comparison but you can actually run a public network with loraserver.io. Several are running full fledged public networks based on loraserver.io actually. It’s extremely useful :partying_face:

I think you have a misconception which I’ll point out later. loraserver.io doesn’t provide a TTN packet forwarder. lora-gateway-bridge is incompatible with TTN so you can’t actually use it to send traffic to TTN. You’re doing something different all together @ccall48

I totally agree with this statement but I see it more on the TTN side of things as of late. Initially the TTN forum was open for all Lora and Lorawan discussions but it’s currently being used as a sort of issue tracker for TTN only things where moderators close posts that community members actually would answer if they weren’t closed prematurely and considered off topic. They have a reason for this naturally but it does drive people away.

The problem that you’re having is that you’re looking for something that will never be there. Using TTN means that you’re using all of TTN’s infrastructure and not using anything locally besides the Semtech packet forwarder. So you running mosquitto_sub against localhost won’t return anything because you’re using TTN’s server and their mqtt broker. You’re not using loraserver at all. Thus your question is solely a TTN related question :slightly_smiling_face:

You need the TTN app credentials and mqtt broker for your region and you’ll get what you need. The link below should get you what you want.

Many builds of common packet forwarders do in fact log to syslog - but if yours does not, you’ll have to take that up with RAK, or replace their software install with someone else’s - there are many ways to run a LoRaWAN gateway on a pi, even using RAK’s concentrator card.

The packet forwarder is not part of loraserver

Thanks mate,

I couldn’t agree more that the TTN side has been bad of late for closing posts relating to useful helpful information. Most people are just trying to learn and there is a few on there that have superiority complexes. I’m glad that now I’ve asked the question I know it is impossible I generally go with the no such thing as stupid questions only stupid people philosophy… In this case I guess my question did seem stupid to some.

You need the TTN app credentials and mqtt broker for your region and you’ll get what you need. The link below should get you what you want.

I believed this could very well be the case, but was just trying to be sure an clarify that. As I was hoping to get the data from the device itself rather then after a round trip through TTN mqqt broker.

I already collect a lot of node data using python and node-red to store the TTN mqtt data as well as other IoT device data into a influxdb for analysis and my own mapping etc…

We may look into setting up our own private lora network, I’ll have a talk with few we have in the local community and see what the consensus is as it maybe more beneficial to us long term using our own infrastructure rather then relying on a third party like TTN/TTI.


That’s simply not how LoRaWAN works.

Only the server (in your case the TTN server) knows how to make any sense of things, gateways only see encrypted traffic which they lack the keys to decode.

Please cease posting your issues here as they are entirely off-topic

Guys, please keep the conversation friendly, without emotions or irritations :slight_smile: Although I agree that we can not support any TTN related questions, one question which is not answered is:

“…the forum provided by the people who actually wrote the software which runs on my device”

@ccall48 Are you referring to the Gateway OS downloaded from www.loraserver.io? In that case I could see this question relevant (as you can configured the packaged Semtech UDP packet-forwarder to any Network Server, in which case the target is not relevant), but if this is the image provided by RAK / if you are using the TTN packet-forwarder, then you should discuss this in the TTN forum or with RAK.

Anyway, lets keep the discussion on a friendly tone! :slight_smile:

Hey mate,

I’m currently using the rak downloadable image for the last 4~5 months which has the loraserver.io if you load the web ui. This is what gave me the assumption that it was using it for the gateway packet forwarder when in actual fact it appears this is bypassed if you use the gateway cli and set it up to use TTN. Leaving access to the web ui open had me assuming wrongly on how they have implemented this.

So if I/we were to implement our own lora or lora/mesh or private network we would actually use the loraserver.io to register our gateways and node applications etc and then I would actually be using the loraserver part…

I can understand people losing their cool as some questions to experienced people seem mundane and boring to them, but you have to remember not everyone may have the same level of experience or understanding as you have.

1 Like

I understand where the confusion is coming from, but it is indeed correct that when you configure the RAK provided image for using with TTN, you are not using any of the LoRa Server components of the image (although they might still be running in the background).