- Added
--headers
flag tottn-lw-cli applications webhooks set
allowing users to set HTTP headers to add to webhook requests. - Added
getByOrganizationId
andgetByUserId
methods to the JS SDK - Added a new documentation system
- Added a newline between list items returned from the CLI when using a custom
--output-format
template. - Added an
--api-key
flag tottn-lw-cli login
that allows users to configure the CLI with a more restricted (Application, Gateway, ...) API key instead of the usual "all rights" OAuth access token. - Added API for getting the rights of a single collaborator on (member of) an entity.
- Added Application Payload Formatters Page in the console
- Added Class C and Multicast guide
- Added CLI support for enabling/disabling JS, GS, NS and AS through configuration
- Added components overview in documentation
- Added Device Templates to create, convert and map templates and assign EUIs to create large amounts of devices
- Added Downlink Queue Operations guide
- Added end device level payload formatters to console
- Added event streaming views for end devices
- Added events to device registries in the Network Server, Application Server and Join Server.
- Added functionality to delete end devices in the console
- Added Gateway General Settings Page to the console
- Added Getting Started guide for command-line utility (CLI)
- Added initial overview page to console
- Added native support to the Basic Station LNS protocol in the Gateway Server.
- Added NS-JS and AS-JS Backend Interfaces 1.0 and 1.1 draft 3 support
- Added option to revoke user sessions and access tokens on password change.
- Added support for NS-JS and AS-JS Backend Interfaces
- Added support for URL templates inside the Webhook paths ! The currently supported fields are
appID
,appEUI
,joinEUI
,devID
,devEUI
anddevAddr
. They can be used using RFC 6570 - Added the
go-cloud
integration to the Application Server. Seettn-lw-cli applications pubsubs --help
for more details. - Added the
go-cloud
integration to the Application Server. This integration enables downlink and uplink messaging using the cloud pub-sub by setting up the--as.pubsub.publish-urls
and--as.pubsub.subscribe-urls
parameters. You can specify multiple publish endpoints or subscribe endpoints by repeating the parameter (i.e.--as.pubsub.publish-urls url1 --as.pubsub.publish-urls url2 --as.pubsub.subscribe-urls url3
). - Added the Gateway Data Page to the console
- Added view to update the antenna location information of gateways
- Added view to update the location information of end devices
- Added views to handle integrations (webhooks) to the console
- Added Working with Events guide
- Changed database index names for invitation and OAuth models. Existing databases are migrated automatically.
- Changed HTTP API for managing webhooks to avoid conflicts with downlink webhook paths
- Changed interpretation of frequency plan's maximum EIRP from a ceiling to a overriding value of any band (PHY) settings
- Changed the prefix of Prometheus metrics from
ttn_
tottn_lw_
- Deprecated
JsEndDeviceRegistry.Provision()
rpc. Please useEndDeviceTemplateConverter.Convert()
instead - Fixed Basic Station CUPS LNS credentials blob.
- Fixed a leak of entity information in List RPCs
- Fixed an issue that resulted in some event errors not being shown in the console
- Fixed an issue where incorrect error codes were returned from the console's OAuth flow.
- Fixed clearing component addresses on updating end devices through CLI
- Fixed CLI panic for invalid attributes.
- Fixed crash when running some
ttn-lw-cli organizations
commands without--user-id
flag. - Fixed dwell-time issues in AS923 and AU915 bands.
- Fixed occasional issues with downlink payload length
- Fixed the
x-total-count
header value for API Keys and collaborators - Fixed the error that is returned when deleting a collaborator fails.
- Removed the address label from Prometheus metric
grpc_server_conns_{opened,closed}_total
- Renamed the label
server_address
of Prometheus metricsgrpc_client_conns_{opened,closed}_total
toremote_address
- Resolved an issue where the stack complained about sending credentials on insecure connections.
- The Events endpoint no longer requires the
_ALL
right on requested entities. All events now have explicit visibility rules. - Updated node packages to fix known vulnerabilities
Docker images
docker pull thethingsnetwork/lorawan-stack:latest
docker pull thethingsnetwork/lorawan-stack:3
docker pull thethingsnetwork/lorawan-stack:3.1
docker pull thethingsnetwork/lorawan-stack:3.1.0