Thanks to the expertise of many community members and the effort of our core development team (@KtorZ, @htdvisser, @Thomas and myself), I’m proud to announce the staging environment of TTN back-end 1.0.
- Support for over-the-air-activation (OTAA) with custom security key per device
- Support for activation-by-personalization (ABP) with custom security key pair per device
- Support for confirmed uplink messages
- Support for unconfirmed downlink messages for Class A devices
- Deduplication of uplink messages
- Command line interface for managing users, applications, devices and testing connectivity
- Duty cycle calculations and best gateway selection for downlink
- MQTT authentication and authorization
- Support for EU 863-870 MHz frequency plan
- Designed for public community networking, private connected networking and private offline networking
- Make sure that your gateways are configured to use the new environment, see the announcement and Connect a Gateway.
- Follow the quick start guide with ttnctl, the command line interface.
- Get your data, see Connect an Application
- You can test uplink and downlink with ttnctl to test connectivity (see also quick start guide)
- Migrate from Croft
This is a staging environment which is much like a public beta that we update continuously. Do not use this environment for production. It is advisable, however, to migrate from Croft to the staging environment.
See GitHub for the list of issues. Issues that worth mentioning here:
- Support for EU 433 MHz, US 902-928 MHz, China 470-510 and 779-787 MHz and Australia 915-928 MHz (issue #119 and #120)
- Support for single channel gateways (issue #140)
- Fix technical debt (#90 and #109)
If you find any issues, please raise an issue on GitHub. That allows for easy communication with the core team, assignment of labels and milestones, reference issues and commits, and follow progress.
- Web dashboard as alternative to ttnctl (in progress)
- E-mail validation, password reset, two-factor authentication
- Delete applications
- Development mode for personalized (ABP) devices (issue #118)
- Design and implement service discovery (issue #70 and #71)
(When you’re reading this in the banner on top of the forum: you can read the responses here.)