All notable changes to this project are documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Skipping payload crypto on application-level via application link's
skip_payload_cryptofield. - Authentication method, ID and Remote IP in events metadata.
- Service data messages published by integrations. Can be consumed using the bundled MQTT server, Webhooks or Pub/Sub integrations.
- Application package application-wide associations support.
- LoRaCloud DAS application package server URL overrides support.
- Option to reset end device payload formatters in the Console.
- Event stream start and stop events are not published anymore.
- JSON uplink message doc edited for clarity.
- End device
skip_payload_cryptofield: it gets replaced byskip_payload_crypto_override.
- Endless authentication refresh loop in the Console in some rare situations.
- Logout operation not working properly in the Console in some rare situations.
- Handling API key deletion event for applications, gateways, organizations and users.
- Organization API key deletion in the Console.
- CLI now only sends relevant end device fields to Identity Server on create.
3.8.4 - 2020-06-12
- Metrics for log messages, counted per level and namespace.
- Allow suppressing logs on HTTP requests for user-defined paths (see
--http.log-ignore-pathsoption). - Redux state and actions reporting to Sentry
- Serving frontend sourcemaps in production
- Frequency plan documentation.
- LoRa Basics Station documentation.
- Suppress a few unexpected EOF errors, in order to reduce noise in the logs for health checks.
- Packet Broker Agent cluster ID is used as subscription group.
- LinkADR handling in 72-channel bands.
- Data uplink metrics reported by Application Server.
3.8.3 - 2020-06-05
- Favicon to documentation pages.
- Draft template for documentation.
- Late scheduling algorithm; Gateway Server now takes the 90th percentile of at least the last 5 round-trip times of the last 30 minutes into account to determine whether there's enough time to send the downlink to the gateway. This was the highest round-trip time received while the gateway was connected.
- Downlink scheduling to gateways which had one observed round-trip time that was higher than the available time to schedule. In some occassions, this broke downlink at some point while the gateway was connected.
3.8.2 - 2020-06-03
- Console logout is now propagated to the OAuth provider.
- This requires a database migration (
ttn-lw-stack is-db migrate) because of the added columns. - To set the
logout-redirect-urisfor existing clients, the CLI client can be used, e.g.:ttn-lw-cli clients update console --logout-redirect-uris "https://localhost:8885/console" --redirect-uris "http://localhost:1885/console".
- This requires a database migration (
- Packet Broker Agent to act as Forwarder and Home Network. See
pbaconfiguration section. - JavaScript style guide to our
DEVELOPMENT.mddocumentation. - Schedule end device downlinks in the Console.
- Support for repeated
RekeyInd. (happens when e.g.RekeyConfis lost) - Validate the
DevAddrwhen switching session as a result of receivingRekeyInd. - Error details for failed events in the Console.
UnknownandOther clusterconnection statuses to the gateways table in the Console.- LoRaWAN 2.4 GHz band
ISM2400. - Unset end device fields using the CLI (see
--unsetoption) - Join EUI and Dev EUI columns to the end device table in the Console.
- CLI creates user configuration directory if it does not exist when generating configuration file.
- Upgrading guide in docs.
- Glossary.
- Event details in the Console traffic view.
- Gateway Server events for uplink messages now contain end device identifiers.
- Setting custom gateway attributes in the Console.
- Pub/Sub documentation.
- Return informative well-known errors for standard network and context errors.
- Error notification in list views in the Console.
- Latest "last seen" info and uplink frame counts for end devices in the Console.
- Latest "last seen" info for applications in the Console.
- Conformed JavaScript to new code style guide.
- Removed login page of the Console (now redirects straight to the OAuth login).
- Network Server now records
LinkADRReqrejections and will not retry rejected values. - Improved
NewChannelReq,DLChannelReqandLinkADRReqefficiency. - For frames carrying only MAC commands, Network Server now attempts to fit them in FOpts omitting FPort, if possible, and sends them in FRMPayload with FPort 0 as usual otherwise.
- Submit buttons are now always enabled in the Console, regardless of the form's validation state.
- Disabled ADR for
ISM2400band. - Network Server will attempt RX1 for devices with
Rx1Delayof 1 second, if possible. - Network Server will not attempt to schedule MAC-only frames in ping slots or RXC windows.
- Network Server will only attempt to schedule in a ping slot or RXC window after RX2 has passed.
- Network Server will schedule all time-bound network-initiated downlinks at most RX1 delay ahead of time.
- Network Server now uses its own internal clock in
DeviceTimeAns. - Troubleshooting section of
DEVELOPMENT.md - Change console field labels from
MAC versionandPHY versiontoLoRaWAN versionandRegional Parameters versionand add descriptions
- Handling of device unsetting the ADR bit in uplink, after ADR has been started.
- Invalid
oauth-server-addressin CLI config generated byusecommand when config file is already present. - Network Server now properly handles FPort 0 data uplinks carrying FOpts.
- Data rate 4 in version
1.0.2-aof AU915. - Incorrect
TxOffsetvalues used by Network Server in some bands. - OAuth authorization page crashing.
- Byte input in scheduling downlink view.
- OAuth client token exchange and refresh issues when using TLS with a RootCA.
- Join Server and Application Server device registries now return an error when deleting keys on
SEToperations. The operation was never supported and caused an error onGETinstead. - Clearing end device events list in the Console.
- Some views not being accessible in the OAuth app (e.g. update password).
LinkADRReqscheduling.- Unsetting NwkKey in Join Server.
- CSRF token validation issues preventing login and logout in some circumstances.
- Typo in Application Server configuration documentation (webhook downlink).
- Unset fields via CLI on Join Server, i.e.
--unset root-keys.nwk-key. - Reconnecting UDP gateways that were disconnected by a new gateway connection.
- ADR in US915-like bands.
3.7.2 - 2020-04-22
- CLI can now dump JSON encoded
grpc_payloadfield for unary requests (see--dump-requestsflag). - Template ID column in the webhook table in the Console.
- Select all field mask paths in CLI get, list and search commands (see
--alloption). - Create webhooks via webhook templates in the Console.
ns.up.data.receiveandns.up.join.receiveevents, which are triggered when respective uplink is received and matched to a device by Network Server.ns.up.data.forwardandns.up.join.accept.forwardevents, which are triggered when respective message is forwarded from Network Server to Application Server.ns.up.join.cluster.attemptandns.up.join.interop.attemptevents, which are triggered when the join-request is sent to respective Join Server by the Network Server.ns.up.join.cluster.successandns.up.join.interop.successevents, which are triggered when Network Server's join-request is accepted by respective Join Server.ns.up.join.cluster.failandns.up.join.interop.failevents, which are triggered when Network Server's join-request to respective Join Server fails.ns.up.data.processandns.up.join.accept.processevents, which are triggered when respective message is successfully processed by Network Server.ns.down.data.schedule.attemptandns.down.join.schedule.attemptevents, which are triggered when Network Server attempts to schedule a respective downlink on Gateway Server.ns.down.data.schedule.successandns.down.join.schedule.successevents, which are triggered when Network Server successfully schedules a respective downlink on Gateway Server.ns.down.data.schedule.failandns.down.join.schedule.failevents, which are triggered when Network Server fails to schedule a respective downlink on Gateway Server.- Specify gRPC port and OAuth server address when generating a CLI config file with
ttn-lw-cli use(see--grpc-portand--oauth-server-addressoptions). - Guide to connect MikroTik Routerboard
- Styling improvements to webhook and pubsub table in Console.
- Gateway location is updated even if no antenna locations had been previously set.
- Renamed
ns.application.begin_linkevent tons.application.link.begin. - Renamed
ns.application.end_linkevent tons.application.link.end. ns.up.data.dropandns.up.join.dropevents are now triggered when respective uplink duplicate is dropped by Network Server.- Network Server now drops FPort 0 data uplinks with non-empty FOpts.
- Frontend asset hashes are loaded dynamically from a manifest file instead of being built into the stack binary.
- Removed
Cache-Controlheader for static files. - Sort events by
timein the Console. - Restructure doc folder
ns.up.merge_metadataevent.ns.up.receive_duplicateevent.ns.up.receiveevent.
- End device claim display bug when claim dates not set.
- DeviceModeInd handling for LoRaWAN 1.1 devices.
- Do not perform unnecessary gateway location updates.
- Error display on failed end device import in the Console.
- Update password view not being accessible
- FOpts encryption and decryption for LoRaWAN 1.1 devices.
- Application Server returns an error when trying to delete a device that does not exist.
- Network Server returns an error when trying to delete a device that does not exist.
- Retrieve LNS Trust without LNS Credentials attribute.
- Too strict webhook base URL validation in the Console.
- Webhook and PubSub total count in the Console.
- DevEUI is set when creating ABP devices via CLI.
- CLI now shows all supported enum values for LoraWAN fields.
- Application Server does not crash when retrieving a webhook template that does not exist if no template repository has been configured.
- Application Server does not crash when listing webhook templates if no template repository has been configured.
- Error display on failed end device fetching in the Console.
- Various inconsistencies with Regional Parameters specifications.
3.7.0 - 2020-04-02
- Update gateway antenna location from incoming status message (see
update_location_from_statusgateway field and--gs.update-gateway-location-debounce-timeoption).- This requires a database migration (
ttn-lw-stack is-db migrate) because of the added columns.
- This requires a database migration (
- Access Tokens are now linked to User Sessions.
- This requires a database migration (
ttn-lw-stack is-db migrate) because of the added columns.
- This requires a database migration (
- Edit application attributes in Application General Settings in the Console
- New
useCLI command to automatically generate CLI configuration files. - View/edit
update_location_from_statusgateway property using the Console.
- Default DevStatus periodicity is increased, which means that, by default, DevStatusReq will be scheduled less often.
- Default class B and C timeouts are increased, which means that, by default, if the Network Server expects an uplink from the device after a downlink, it will wait longer before rescheduling the downlink.
- In case downlink frame carries MAC requests, Network Server will not force the downlink to be sent confirmed in class B and C.
- Fix organization collaborator view not being accessible in the Console.
- Error display on Data pages in the Console.
- Fix too restrictive MQTT client validation in PubSub form in the Console.
- Fix faulty display of device event stream data for end devices with the same ID in different applications.
- Trailing slashes handling in webhook paths.
- End device location display bug when deleting the location entry in the Console.
- GS could panic when gateway connection stats were updated while updating the registry.
- Local CLI and stack config files now properly override global config.
- Error display on failed end device deletion in the Console.
3.6.3 - 2020-03-30
- Limited throughput in upstream handlers in Gateway Server when one gateway's upstream handler is busy.
3.6.2 - 2020-03-19
- Entity events subscription release in the Console (Firefox).
- RekeyInd handling for LoRaWAN 1.1 devices.
- Network server deduplication Redis configuration.
- Change the date format in the Console to be unambiguous (
17 Mar, 2020). - Handling of uplink frame counters exceeding 65535.
- Gateway events subscription release in the Console.
- Panic when receiving a UDP
PUSH_DATAframe from a gateway without payload.
- Admin users that are suspended can no longer create, view or delete other users.
3.6.1 - 2020-03-13
- New
listandrequest-validationsubcommands for the CLI'scontact-infocommands. - Device Claim Authentication Code page in the Console.
- Gateway Server rate limiting support for the UDP frontend, see (
--gs.udp.rate-limitingoptions). - Uplink deduplication via Redis in Network Server.
- Network and Application Servers now maintain application downlink queue per-session.
- Gateway Server skips setting up an upstream if the DevAddr prefixes to forward are empty.
- Gateway connection stats are now cached in Redis (see
--cache.serviceand--gs.update-connections-stats-debounce-timeoptions).
- Telemetry and events for gateway statuses.
- Handling of downlink frame counters exceeding 65535.
- Creating 1.0.4 ABP end devices via the Console.
- ADR uplink handling.
- Uplink retransmission handling.
- Synchronizing Basic Station concentrator time after reconnect or initial connect after long inactivity.
- Changing username and password to be not required in pubsub integration.
3.6.0 - 2020-02-27
- Class B support.
- WebSocket Ping-Pong support for Basic Station frontend in the Gateway Server.
- LoRaWAN 1.0.4 support.
- Do not use
personal-filesplugin for Snap package. - Network Server will never attempt RX1 for devices with
Rx1Delayof 1 second. - Improved efficiency of ADR MAC commands.
- Gateway Configuration Server will use the default WebSocket TLS port if none is set.
- End device events subscription release in the Console.
- Blocking UDP packet handling while the gateway was still connecting. Traffic is now dropped while the connection is in progress, so that traffic from already connected gateways keep flowing.
- Join-request transmission parameters.
- ADR in 72-channel regions.
- Payload length limits used by Network Server being too low.
- CLI ignores default config files that cannot be read.
- Device creation rollback potentially deleting existing device with same ID.
- Returned values not representing the effective state of the devices in Network Server when deprecated field paths are used.
- Downlink queue operations in Network Server for LoRaWAN 1.1 devices.
3.5.3 - 2020-02-14
- Display of error payloads in console event log.
- Zero coordinate handling in location form in the Console.
- Updating
supports_class_cfield in the Device General Settings Page in the Console. - Updating MQTT pubsub configuration in the Console
- Handling multiple consequent updates of MQTT pubsub/webhook integrations in the Console.
- Displaying total device count in application overview section when using device search in the Console
- FQDN used for Backend Interfaces interoperability requests.
- Exposing device sensitive fields to unrelated stack components in the Console.
- CLI trying to read input while none available.
- Reconnections of gateways whose previous connection was not cleaned up properly. New connections from the same gateway now actively disconnects existing connections.
ttn-lw-stackandttn-lw-clifile permission errors when installed using snap.- You may need to run
sudo snap connect ttn-lw-stack:personal-files
- You may need to run
- Changing username and password to be not required in pubsub integration
3.5.2 - 2020-02-06
- Channel mask encoding in LinkADR MAC command.
- Frequency plan validation in Network Server on device update.
- Authentication of Basic Station gateways.
3.5.1 - 2020-01-29
- Responsive side navigation (inside entity views) to the Console.
- Overall responsiveness of the Console.
- Support for configuring Redis connection pool sizes with
redis.pool-sizeoptions.
- Crashes on Gateway Server start when traffic flow started while The Things Stack was still starting.
- Not detecting session change in Application Server when interop Join Server did not provide a
SessionKeyID.
3.5.0 - 2020-01-24
- Support for releasing gateway EUI after deletion.
- Support in the Application Server for the
X-Downlink-Apikey,X-Downlink-PushandX-Downlink-Replacewebhook headers. They allow webhook integrations to determine which endpoints to use for downlink queue operations. as.webhooks.downlinks.public-addressandas.webhooks.downlinks.public-tls-addressconfiguration options to the Application Server.- Support for adjusting the time that the Gateway Server schedules class C messages in advance per gateway.
- This requires a database migration (
ttn-lw-stack is-db migrate) because of the added columns.
- This requires a database migration (
end-devices use-external-join-serverCLI subcommand, which disassociates and deletes the device from Join Server.mac_settings.beacon_frequencyend device field, which defines the default frequency of class B beacon in Hz.mac_settings.desired_beacon_frequencyend device field, which defines the desired frequency of class B beacon in Hz that will be configured via MAC commands.mac_settings.desired_ping_slot_data_rate_indexend device field, which defines the desired data rate index of the class B ping slot that will be configured via MAC commands.mac_settings.desired_ping_slot_frequencyend device field, which defines the desired frequency of the class B ping slot that will be configured via MAC commands.- Mobile navigation menu to the Console.
- View and edit all Gateway settings from the Console.
skip_payload_cryptoend device field, which makes the Application Server skip decryption of uplink payloads and encryption of downlink payloads.app_s_keyandlast_a_f_cnt_downuplink message fields, which are set if theskip_payload_cryptoend device field is true.- Support multiple frequency plans for a Gateway.
- Entity search by ID in the Console.
resets_join_noncesnow applies to pre-1.1 devices as well as 1.1+ devices.- Empty (
0x0000000000000000) JoinEUIs are now allowed.
- Respect stack components on different hosts when connected to event sources in the Console.
- Pagination of search results.
- Handling OTAA devices registered on an external Join Server in the Console.
- RxMetadata Location field from Gateway Server.
- Channel mask encoding in LinkADR MAC command.
- Device location and payload formatter form submits in the Console.
- Events processing in the JS SDK.
- Application Server frontends getting stuck after their associated link is closed.
3.4.2 - 2020-01-08
- Forwarding of backend warnings to the Console.
- Auth Info service to the JavaScript SDK.
- Subscribable events to the JavaScript SDK.
- Include
gateway_IDfield in Semtech UDP configuration response from Gateway Configuration Server. - Sorting feature to entity tables in the Console.
- Increase time that class C messages are scheduled in advance from 300 to 500 ms to support higher latency gateway backhauls.
- Fix selection of pseudo wildcard rights being possible (leading to crash) in the Console even when such right cannot be granted.
- Fix loading spinner being stuck infinitely in gateway / application / organization overview when some rights aren't granted to the collaborator.
- Fix deadlock of application add form in the Console when the submit results in an error.
- Fix ttn-lw-cli sometimes refusing to update Gateway EUI.
3.4.1 - 2019-12-30
- Support for ordering in
ListRPCs. - Detect existing Basic Station time epoch when the gateway was already running long before it (re)connected to the Gateway Server.
- Reduce the downlink path expiry window to 15 seconds, i.e. typically missing three
PULL_DATAframes. - Reduce the connection expiry window to 1 minute.
- Reduce default UDP address block time from 5 minutes to 1 minute. This allows for faster reconnecting if the gateway changes IP address. The downlink path and connection now expire before the UDP source address is released.
- Fix class A downlink scheduling when an uplink message has been received between the triggering uplink message.
3.4.0 - 2019-12-24
- Downlink queue operation topics in the PubSub integrations can now be configured using the Console.
ListRPC in the user registry and related messages.- User management for admins in the Console.
users listcommand in the CLI.- Support for getting Kerlink CPF configurations from Gateway Configuration Server.
- Support for Microchip ATECC608A-TNGLORA-C manifest files in device template conversion.
- Fix the PubSub integration edit page in the Console.
- Fix updating and setting of webhook headers in the Console.
- Fix DevNonce checks for LoRaWAN 1.0.3.
3.3.2 - 2019-12-04
- Support for selecting gateways when queueing downlinks via CLI (see
class-b-c.gatewaysoption). - Options
is.oauth.ui.branding-base-urlandconsole.ui.branding-base-urlthat can be used to customize the branding (logos) of the web UI. - Email templates can now also be loaded from blob buckets.
- Support for pagination in search APIs.
- Search is now also available to non-admin users.
- Support for searching end devices within an application.
- Notification during login informing users of unapproved user accounts.
- Support maximum EIRP value from frequency plans sub-bands.
- Support duty-cycle value from frequency plans sub-bands.
- Allow enqueuing class B/C downlinks regardless of active device class.
- Fix crashing of organization collaborator edit page.
- Avoid validating existing queue on application downlink pushes.
- Correct
AU_915_928maximum EIRP value to 30 dBm in 915.0 – 928.0 MHz (was 16.15 dBm). - Correct
US_902_928maximum EIRP value to 23.15 dBm in 902.3 – 914.9 MHz (was 32.15 dBm) and 28.15 dBm in 923.3 – 927.5 MHz (was 32.15 dBm). This aligns with US915 Hybrid Mode. - Correct
AS_923maximum EIRP value to 16 dBm in 923.0 – 923.5 MHz (was 16.15 dBm).
- Keep session keys separate by
JoinEUIto avoid conditions where session keys are retrieved only byDevEUIand the session key identifier. This breaks retrieving session keys of devices that have been activated on a deployment running a previous version. Since the Application Server instances are currently in-cluster, there is no need for an Application Server to retrieve theAppSKeyfrom the Join Server, making this breaking change ineffective.
3.3.1 - 2019-11-26
- Add support for Redis Sentinel (see
redis.failover.enable,redis.failover.master-name,redis.failover.addressesoptions).
- Fix
AppKeydecryption in Join Server.
3.3.0 - 2019-11-25
- Add support for encrypting device keys at rest (see
as.device-kek-label,js.device-kek-labelandns.device-kek-labeloptions). - The Network Server now provides the timestamp at which it received join-accept or data uplink messages.
- Add more details to logs that contain errors.
- Support for end device pictures in the Identity Server.
- This requires a database migration (
ttn-lw-stack is-db migrate) because of the added columns.
- This requires a database migration (
- Support for end device pictures in the CLI.
- Fix an issue causing unexpected behavior surrounding login, logout and token management in the Console.
- Fix an issue causing the application link page of the Console to load infinitely.
3.2.6 - 2019-11-18
- Fix active application link count being limited to 10 per CPU.
- The Application Server now fills the timestamp at which it has received uplinks from the Network Server.
3.2.5 - 2019-11-15
- Support for creating applications and gateway with an organization as the initial owner in the Console.
- Hide views and features in the Console that the user and stack configuration does not meet the necessary requirements for.
- Full range of Join EUI prefixes in the Console.
- Support specifying the source of interoperability server client CA configuration (see
interop.sender-client-ca.sourceand related fields).
- Reading and writing of session keys in Application and Network server registries now require device key read and write rights respectively.
- Implement redesign of entity overview title sections to improve visual consistency.
--interop.sender-client-casin favor of--interop.sender-client-casub-fields in the stack.
- Fix gateway API key forms being broken in the Console.
- Fix MAC command handling in retransmissions.
- Fix multicast device creation issues.
- Fix device key unwrapping.
- Fix setting gateway locations in the Console.
3.2.4 - 2019-11-04
- Support LoRa Alliance TR005 Draft 3 QR code format.
- Connection indicators in Console's gateway list.
- TLS support for application link in the Console.
- Embedded documentation served at
/assets/doc.
- Fix device creation rollback potentially deleting existing device with same ID.
- Fix missing transport credentials when using external NS linking.
3.2.3 - 2019-10-24
- Emails when the state of a user or OAuth client changes.
- Option to generate claim authentication codes for devices automatically.
- User invitations can now be sent and redeemed.
- Support for creating organization API keys in the Console.
- Support for deleting organization API keys in the Console.
- Support for editing organization API keys in the Console.
- Support for listing organization API keys in the Console.
- Support for managing organization API keys and rights in the JS SDK.
- Support for removing organization collaborators in the Console.
- Support for editing organization collaborators in the Console.
- Support for listing organization collaborators in the Console.
- Support for managing organization collaborators and rights in the JS SDK.
- MQTT integrations page in the Console.
- Rename "bulk device creation" to "import devices".
- Move device import button to the end device tables (and adapt routing accordingly).
- Improve downlink performance.
- Fix issues with device bulk creation in Join Server.
- Fix device import not setting component hosts automatically.
- Fix NewChannelReq scheduling condition.
- Fix publishing events for generated MAC commands.
- Fix saving changes to device general settings in the Console.
3.2.2 - 2019-10-14
- Initial API and CLI support for LoRaWAN application packages and application package associations.
- New documentation design.
- Support for ACME v2.
- Deprecate the
tls.acme.enablesetting. To use ACME, settls.sourcetoacme.
- Fix giving priority to ACME settings to remain backward compatible with configuration for
v3.2.0and older.
3.2.1 - 2019-10-11
support-linkURI config to the Console to show a "Get Support" button.- Option to explicitly enable TLS for linking of an Application Server on an external Network Server.
- Service to list QR code formats and generate QR codes in PNG format.
- Status message forwarding functions to upstream host/s.
- Support for authorizing device claiming on application level through CLI. See
ttn-lw-cli application claim authorize --helpfor more information. - Support for claiming end devices through CLI. See
ttn-lw-cli end-device claim --helpfor more information. - Support for converting Microchip ATECC608A-TNGLORA manifest files to device templates.
- Support for Crypto Servers that do not expose device root keys.
- Support for generating QR codes for claiming. See
ttn-lw-cli end-device generate-qr --helpfor more information. - Support for storage of frequency plans, device repository and interoperability configurations in AWS S3 buckets or GCP blobs.
- Enable the V2 MQTT gateway listener by default on ports 1881/8881.
- Improve handling of API-Key and Collaborator rights in the console.
- Fix bug with logout sometimes not working in the console.
- Fix not respecting
RootCAandInsecureSkipVerifyTLS settings when ACME was configured for requesting TLS certificates. - Fix reading configuration from current, home and XDG directories.
3.2.0 - 2019-09-30
- A map to the overview pages of end devices and gateways.
- API to retrieve MQTT configurations for applications and gateways.
- Application Server PubSub integrations events.
mac_settings.desired_max_duty_cycle,mac_settings.desired_adr_ack_delay_exponentandmac_settings.desired_adr_ack_limit_exponentdevice flags.- PubSub integrations to the console.
- PubSub service to JavaScript SDK.
- Support for updating
mac_state.desired_parameters. --tls.insecure-skip-verifyto skip certificate chain verification (insecure; for development only).
- Change the way API key rights are handled in the
UpdateAPIKeyrpc for Applications, Gateways, Users and Organizations. Users can revoke or add rights to api keys as long as they have these rights. - Change the way collaborator rights are handled in the
SetCollaboratorrpc for Applications, Gateways, Clients and Organizations. Collaborators can revoke or add rights to other collaborators as long as they have these rights. - Extend device form in the Console to allow creating OTAA devices without root keys.
- Improve confirmed downlink operation.
- Improve gateway connection status indicators in Console.
- Upgrade Gateway Configuration Server to a first-class cluster role.
- Fix downlink length computation in the Network Server.
- Fix implementation of CUPS update-info endpoint.
- Fix missing CLI in
deb,rpmand Snapcraft packages.
3.1.2 - 2019-09-05
http.redirect-to-hostconfig to redirect all HTTP(S) requests to the same host.http.redirect-to-tlsconfig to redirect HTTP requests to HTTPS.- Organization Create page in the Console.
- Organization Data page to the console.
- Organization General Settings page to the console.
- Organization List page.
- Organization Overview page to the console.
- Organizations service to the JS SDK.
createmethod in the Organization service in the JS SDK.deleteByIdmethod to the Organization service in the JS SDK.getAllmethod to the Organizations service.getAllmethod to the Organization service in the JS SDK.getByIdmethod to the Organization service in the JS SDK.openStreammethod to the Organization service in the JS SDK.updateByIdmethod to the Organization service in the JS SDK.
- Improve compatibility with various Class C devices.
- Fix root-relative OAuth flows for the console.
3.1.1 - 2019-08-30
--tls.acme.default-hostflag to set a default (fallback) host for connecting clients that do not use TLS-SNI.- AS-ID to validate the Application Server with through the Common Name of the X.509 Distinguished Name of the TLS client certificate. If unspecified, the Join Server uses the host name from the address.
- Defaults to
ttn-lw-cli clients createandttn-lw-cli users create. - KEK labels for Network Server and Application Server to use to wrap session keys by the Join Server. If unspecified, the Join Server uses a KEK label from the address, if present in the key vault.
- MQTT PubSub support in the Application Server. See
ttn-lw-cli app pubsub set --helpfor more details. - Support for external email templates in the Identity Server.
- Support for Join-Server interoperability via Backend Interfaces specification protocol.
- The
generateDevAddressmethod in theNsservice. - The
Jsservice to the JS SDK. - The
listJoinEUIPrefixesmethod in theJsservice. - The
Nsservice to the JS SDK. - The new The Things Stack branding.
- Web interface for changing password.
- Web interface for requesting temporary password.
- Allow admins to create temporary passwords for users.
- CLI-only brew tap formula is now available as
TheThingsNetwork/lorawan-stack/ttn-lw-cli. - Improve error handling in OAuth flow.
- Improve getting started guide for a deployment of The Things Stack.
- Optimize the way the Identity Server determines memberships and rights.
--nats-server-urlin favor of--nats.server-urlin the PubSub CLI support.
ids.dev_addrfrom allowed field masks for/ttn.lorawan.v3.NsEndDeviceRegistry/Set.- Auth from CLI's
forgot-passwordcommand and made it optional onupdate-passwordcommand. - Breadcrumbs from Overview, Application and Gateway top-level views.
- Fix
grantsandrightsflags ofttn-lw-cli clients create. - Fix a bug that resulted in events streams crashing in the console.
- Fix a bug where uplinks from some Basic Station gateways resulted in the connection to break.
- Fix a security issue where non-admin users could edit admin-only fields of OAuth clients.
- Fix an issue resulting in errors being unnecessarily logged in the console.
- Fix an issue with the
configcommand rendering some flags and environment variables incorrectly. - Fix API endpoints that allowed HTTP methods that are not part of our API specification.
- Fix console handling of configured mount paths other than
/console. - Fix handling of
ns.dev-addr-prefixes. - Fix incorrect error message in
ttn-lw-cli users oauthcommands. - Fix propagation of warning headers in API responses.
- Fix relative time display in the Console.
- Fix relative time display in the Console for IE11, Edge and Safari.
- Fix unable to change LoRaWAN MAC and PHY version.
- Resolve flickering display issue in the overview pages of entities in the console.
3.1.0 - 2019-07-26
--headersflag tottn-lw-cli applications webhooks setallowing users to set HTTP headers to add to webhook requests.getByOrganizationIdandgetByUserIdmethods to the JS SDK.- A new documentation system.
- A newline between list items returned from the CLI when using a custom
--output-formattemplate. - An
--api-keyflag tottn-lw-cli loginthat allows users to configure the CLI with a more restricted (Application, Gateway, ...) API key instead of the usual "all rights" OAuth access token. - API for getting the rights of a single collaborator on (member of) an entity.
- Application Payload Formatters Page in the console.
- Class C and Multicast guide.
- CLI support for enabling/disabling JS, GS, NS and AS through configuration.
- Components overview in documentation.
- Device Templates to create, convert and map templates and assign EUIs to create large amounts of devices.
- Downlink Queue Operations guide.
- End device level payload formatters to console.
- Event streaming views for end devices.
- Events to device registries in the Network Server, Application Server and Join Server.
- Functionality to delete end devices in the console.
- Gateway General Settings Page to the console.
- Getting Started guide for command-line utility (CLI).
- Initial overview page to console.
- Native support to the Basic Station LNS protocol in the Gateway Server.
- NS-JS and AS-JS Backend Interfaces 1.0 and 1.1 draft 3 support.
- Option to revoke user sessions and access tokens on password change.
- Support for NS-JS and AS-JS Backend Interfaces.
- Support for URL templates inside the Webhook paths ! The currently supported fields are
appID,appEUI,joinEUI,devID,devEUIanddevAddr. They can be used using RFC 6570. - The
go-cloudintegration to the Application Server. Seettn-lw-cli applications pubsubs --helpfor more details. - The
go-cloudintegration to the Application Server. This integration enables downlink and uplink messaging using the cloud pub-sub by setting up the--as.pubsub.publish-urlsand--as.pubsub.subscribe-urlsparameters. 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). - The Gateway Data Page to the console.
- View to update the antenna location information of gateways.
- View to update the location information of end devices.
- Views to handle integrations (webhooks) to the console.
- Working with Events guide.
- Change database index names for invitation and OAuth models. Existing databases are migrated automatically.
- Change HTTP API for managing webhooks to avoid conflicts with downlink webhook paths.
- Change interpretation of frequency plan's maximum EIRP from a ceiling to a overriding value of any band (PHY) settings.
- Change the prefix of Prometheus metrics from
ttn_tottn_lw_. - Rename the label
server_addressof Prometheus metricsgrpc_client_conns_{opened,closed}_totaltoremote_address - Resolve an issue where the stack complained about sending credentials on insecure connections.
- The Events endpoint no longer requires the
_ALLright on requested entities. All events now have explicit visibility rules.
JsEndDeviceRegistry.Provision()rpc. Please useEndDeviceTemplateConverter.Convert()instead.
- Remove the address label from Prometheus metric
grpc_server_conns_{opened,closed}_total.
- Fix Basic Station CUPS LNS credentials blob.
- Fix a leak of entity information in List RPCs.
- Fix an issue that resulted in some event errors not being shown in the console.
- Fix an issue where incorrect error codes were returned from the console's OAuth flow.
- Fix clearing component addresses on updating end devices through CLI.
- Fix CLI panic for invalid attributes.
- Fix crash when running some
ttn-lw-cli organizationscommands without--user-idflag. - Fix dwell-time issues in AS923 and AU915 bands.
- Fix occasional issues with downlink payload length.
- Fix the
x-total-countheader value for API Keys and collaborators. - Fix the error that is returned when deleting a collaborator fails.
- Update node packages to fix known vulnerabilities.
3.0.4 - 2019-07-10
- Fix rights caching across multiple request contexts.
3.0.3 - 2019-05-10
- Support for getting automatic Let's Encrypt certificates. Add the new config flags
--tls.acme.enable,--tls.acme.dir=/path/to/storage,--tls.acme.hosts=example.com,--tls.acme.email=you@example.comflags (or their env/config equivalent) to make it work. The/path/to/storagedir needs to bechowned to886:886. See alsodocker-compose.yml. GetApplicationAPIKey,GetGatewayAPIKey,GetOrganizationAPIKey,GetUserAPIKeyRPCs and related messages.- "General Settings" view for end devices.
--credentials-idflag to CLI that allows users to be logged in with mulitple credentials and switch between them.- A check to the Identity Server that prevents users from deleting applications that still contain end devices.
- Application Collaborators management to the console.
- Checking maximum round-trip time for late-detection in downlink scheduling.
- Configuration service to JS SDK.
- Device list page to applications in console.
- Events to the application management pages.
- Round-trip times to Gateway Server connection statistics.
- Support for the value
cloudfor the--events.backendflag. When this flag is set, the--events.cloud.publish-urland--events.cloud.subscribe-urlare used to set up a cloud pub-sub for events. - Support for uplink retransmissions.
- Using median round-trip time value for absolute time scheduling if the gateway does not have GPS time.
- Change encoding of keys to hex in device key generation (JS SDK).
- Change interpretation of absolute time in downlink messages from time of transmission to time of arrival.
- Improve ADR algorithm performance.
- Improve ADR performance.
- Make late scheduling default for gateways connected over UDP to avoid overwriting queued downlink.
- Make sure that non-user definable fields of downlink messages get discarded across all Application Server frontends.
- Prevent rpc calls to JS when the device has
supports_joinset tofalse(JS SDK). - Update the development tooling. If you are a developer, make sure to check the changes in CONTRIBUTING.md and DEVELOPMENT.md.
- Fix
AppAsnot registered for HTTP interfacing while it is documented in the API. - Fix absolute time scheduling with UDP connected gateways
- Fix authentication of MQTT and gRPC connected gateways
- Fix connecting MQTT V2 gateways
- Fix faulty composition of default values with provided values during device creation (JS SDK)
- Fix preserving user defined priority for application downlink
- Fix UDP downlink format for older forwarders
- Fix usage of
URLclass in browsers (JS SDK)
3.0.2 - 2019-04-12
- Upgrade Go to 1.12
- Fix streaming events over HTTP with Gzip enabled.
- Fix resetting downlink channels for US, AU and CN end devices.
- Fix rendering of enums in JSON.
- Fix the permissions of our Snap package.
3.0.1 - 2019-04-10
dev_addrto device fetched from the Network Server.received_attoApplicationUpmessages.ttn-lw-cli users oauthcommands.- Event payload to
as.up.forward,as.up.drop,as.down.receive,as.down.forwardandas.down.dropevents. - Event payload to
gs.status.receive,gs.up.receiveandgs.down.sendevents. - OAuth management in the Identity Server.
- Document places in the CLI where users can use arguments instead of flags.
- In JSON, LoRaWAN AES keys are now formatted as Hex instead of Base64.
- Make device's
dev_addrupdate when the session'sdev_addris updated.
- Remove end device identifiers from
DownlinkMessagesent from the Network Server to the Gateway Server.
- Fix
dev_addrnot being present in upstream messages.