You do need access to an account server. You can use TTN’s account server on https://account.thethingsnetwork.org. We’re still doing quite some development on this, but as soon as the API is stable, we’ll define a specification for this account server so that you can implement your own.
This could be caused by a number of things. For example if you have a single-channel gateway closeby (#140), if you’re not in Europe (#119 and #120) or some other unknown issue. Talk to me on Slack tomorrow (CEST) and I can try to help you.
That’s not possible yet, but it’s on our todo list.
Only use confirmed uplink if you really need it. It eats downlink capacity.
That’s not possible yet, but it’s on our todo list.
This could be caused by a number of things. For example if you have a single-channel gateway closeby (#140), if you’re not in Europe (#119 and #120) or some other unknown issue. Talk to me on Slack tomorrow (CEST) and I can try to help you.
Thanks, @htdvisser. I’m in the UK and fairly sure there are not any other gateways nearby. I’m out of the office today, but will be back with the gateway tomorrow afternoon around 14:00 UTC.
Regarding confirmed uplink, I have a survey app from Multitech that uses this to measure downlink RSSI, which is then stored along with the GPS coordinates and timestamp. However, it just occurred to me that I should probably have been using the experimental branches from the Lora-net GitHub repos in order for the gateway to support ACKs.
Thanks @htdvisser , I understand it.So in that case if my private network cannot reach the internet, I cannot use the new backend from TTN till its API is stable right? I have noticed that the broker crashes if it cannot reach that server, so I commented it but still it was crashing.
In a private offline network (see wiki), you can implement your own authentication mechanism. It is still token-based, but you can issue your own tokens and disable authentication on MQTT, for example.
Yep… And the US frequencies in South America (except Brazil) and Canada. And there are a lot more exceptions, so we’ll probably build a list where you can find the correct frequency for each country.
Ah, that was the last missing puzzle piece in my application - that the DevEUI in the mqtt topic is the DevAddr (like 02E00202) with 8 pre-pended zeros. Actually discovered it by subscribing with wildcards ( +/devices/+/up ) in nodejs, and then printing out the topic when a message came in! Working great now…
We’re using tokens to authenticate and authorize users and applications. The tokens are issued by the account server. You can issue your own tokens if you implement your own account server too. We did not publish specifications for that yet because it is still in development. Tokens are signed with a private key and can be validated with a public key. This public key is required in the Broker to check if the token from the client (e.g. ttnctl) is valid.
It looks like you try to get the wrong key; the Broker tries to get the public key for validating the token from https://account.thethingsnetwork.org/key. The Broker tries this on start-up. If it fails, because there’s no internet, then the cached key is used. So make sure that your start the Broker at least once with an internet connection.
I use the standard command and I’m getting the following error message. I’ve managed to get the re-configured etc.
Setup up new account and password
Setup and Application
Associate the application
./ttnctl devices register personalized 02D1DD03
INFO Generating random NwkSKey and AppSKey…
FATAL Could not register device error=rpc error: code = 2 desc = Invalid operation: rpc error: code = 2 desc = Invalid operation: Unauthorized
Did you use the ttnctl applications use <AppEUI> command to activate your newly created application? See the AppEUI in the overview you get with ttnctl applications.
in the wiki could we add, it might make it a bit more clear for idiots like mw who need spoon feeding every command.
Application Management
Now create a new application with ttnctl applications create. In this example we will create an application named Hello World App. The
❯ ttnctl applications create ‘Hello World App’
INFO Application created successfully
If you work in a group, you can authorize your colleagues to manage the application with the ttnctl applications authorize command:
*Now type this to provide all the running details for you’re application. *
*> ttnctl applications * EUI Name Owner Access Keys Valid xxxxxxxxxxx xxx test1 test1@txxxx.xyz xxxxxxxxxxxxxxxxxxxxxxxxxxxxx= true
❯ ttnctl applications authorize 0807060504030201 john@doe.org
INFO User authorised successfully
I guess that once it id comletely develop you would provide some guide in order to know how to interface with a private account server too right?
Then that means too that for now if I want to use the TTN backed for a private network, I have to register my nodes into the TTN devices server otherwise I won’t see any traffic from my nodes since if they are not register, the broker wouldn’t allow them have access to the network, am I right?
I did it once, and now I don get the starting error in the broker, , thanks @johan
, thanks