TTN network stack V3 central 2

I am using the build-in MQTT broker for class A up-link and down-link message test. The LoRaWan stack version is V3.0.0-RC2.

I can successfully get the up-link message from the node device. But for the down-link message, I think it doesn’t work.

From the host PC, I open two terminals. One receives message with mosquitto_sub, and the other send out the message with mosquitto_pub. I use the following command to send out the message:

mosquitto_pub -u app1 -P NNSXS.UCV7QADOLDV5YAEPRVE6HBX3AFK22CVBWYAMKBQ.KNM665HUYJK7D3ZLRXORDXUGRIYQGOSQ6WHZQSF24RQAGSDSUOKA -h localhost -t "v3/app1/devices/dev1/down/push" -m '{"downlinks": [{"f_port": 15,"frm_payload": "QkJCQg==", "confirm": true}]}'

I think that I should receive this message in terminal one because I subscribe the topic “#”. Also I should get the ack message also. But I can get nothing output. While the uplink message works well.

Does anyone know what’s the wrong with it?




Again, the question: Has someone here a TTN v3 server running and open for public?

  • is there a hosting provider willing to rent some TTN V3 pre installed servers for a short period ?
  • what is the minimum / preferred hardware (cpu/mem/ect) to setup a V3 server ?
1 Like

Why not asking ? They offer hostings in Amsterdam and Paris. Regional food, tastes better!

bumped to V3.01 :sunglasses:

bumped to V3.02 :sunglasses:

We would like to build a local community network, which is probably funded by the state.
The network is to be built on the basis of the V3 stack, but operated on its own hardware. The network should be open to anyone and enable peering with the TTN.
Will this be possible and will there be licensing costs or costs for peering?
What other conditions are necessary to implement such a project?
For this we have some questions:

 • How does peering work in the V3?
 • Is peering already installed?
 • Will the peering be charged?


Is there, or will there be, a docker image of ‘thethingsnetwork/lorawan-stack’ for arm?

I have followed getting started with V3 docs, using Raspberry PI but
docker-compose --verbose run --rm stack is-db init
fails with
standard_init_linux.go:207: exec user process caused “exec format error”
Verbose logging reveals cockroach and redis start fine and it is the lorawan-stack stack image that is not arm64.


compose.cli.verbose_proxy.proxy_callable: docker inspect_image <- (‘thethingsnetwork/lorawan-stack’)
urllib3.connectionpool._make_request: http://localhost:None “GET /v1.30/images/thethingsnetwork/lorawan-stack/json HTTP/1.1” 200 None
compose.cli.verbose_proxy.proxy_callable: docker inspect_image -> {u’Architecture’: u’amd64’,

Any advice would be appreciated.


At the moment we don’t have a Docker image for Arm. It’s mostly because our build pipeline doesn’t support manifests at the moment.

We do, however, release binaries for various Arm platforms, see the assets under, for example,

You can easily turn this into a background process with systemd, see here:

LoRaWAN Deployment Models

As we get close to the production release of the V3 stack, it is important to understand the different deployment options and pros and cons of each one. This flexibility to choose between different models is one of the key features of the V3 stack.

is class c usable yet?

No, not on the public network

any timetable on it?

1 Like

bumped to V3.0.4 :sunglasses:

1 Like


1 Like

Haha @BoRRoZ. Why the sad face?

it’s not sad… it’s swet from you all working hard on V3 :wink:


bumped to V3.1.1 :sunglasses: