Releases: TheThingsNetwork/lorawan-stack
Releases · TheThingsNetwork/lorawan-stack
v3.10.10
Fixed
- Synchronization in Gateway Server scheduler that caused race conditions in scheduling downlink traffic.
- Handling of
DLChannelReq
if dependentNewChannelReq
was previously rejected.
Docker images
docker pull thethingsnetwork/lorawan-stack:3.10
docker pull thethingsnetwork/lorawan-stack:3.10.10
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10.10
v3.11.0
Important
- The v3.11 Identity Server requires a database schema migration (
ttn-lw-stack is-db migrate
) when upgrading from v3.10. - The v3.11 Network Server requires Redis 6 or higher.
- The v3.11 Network Server requires a data migration (
ttn-lw-stack ns-db migrate
) when upgrading from v3.10.
Added
- Reset functionality in Network Server, which resets session context and MAC state (see
ttn-lw-cli end-devices reset
command). For OTAA all data is wiped and device must rejoin, for ABP session keys, device address and downlink queue are preserved, while MAC state is reset. - Store and retrieve Gateway Claim Authentication Code from database.
- This requires a database schema migration (
ttn-lw-stack is-db migrate
) because of the added column. - This uses the same encryption key set using the
is.gateways.encryption-key-id
configuration option.
- This requires a database schema migration (
- Improved handling of connection issues in the Console, as well as automatic reconnects.
- Helpful details for synthetic meta events in the data view of the Console.
- Support field mask paths in Storage Integration API requests.
- CUPS redirection.
- This requires a database schema migration (
ttn-lw-stack is-db migrate
) because of the added columns.
- This requires a database schema migration (
- Configuration option (
is.user-registration.enabled
) to enable or disable user registrations. - Missing CLI commands for getting single API keys or collaborators for entities.
- New Account App for authentication, authorization and account related functionality.
- This introduces various UX improvements and new designs around e.g. user login, registration and the "forgot password" flow.
- Integrate Device Repository.
- Device Repository component to integrate Device Repository with The Things Stack. See the
dr
configuration section.- The Device Repository database is bundled automatically into Docker release images. See the
ttn-lw-stack dr-db init
command to manually fetch the latest changes.
- The Device Repository database is bundled automatically into Docker release images. See the
- Device repository service to the JavaScript SDK.
- Choosing array representation for end device session keys as well as gateway EUI.
Changed
- Network Server does not store
recent_uplinks
,recent_adr_uplinks
andrecent_downlinks
anymore. - Improved Network Server downlink task performance.
- Improved Network Server matching performance.
- Network Server matching mapping in the database.
- This requires a database migration (
ttn-lw-stack ns-db migrate
).
- This requires a database migration (
- Sending a non-empty implicitly specified field disallowed field will now cause RPCs to fail. E.g. if RPC supports paths
A
andA.B
, sending value withA.C
non-empty and field maskA
would result in an error. - Improved content of emails sent by the Identity Server.
- Stricter validation of the maximum length of string fields, binary fields, lists and maps.
- Frequency plans and webhook templates are now included in Docker images, and used by default, instead of fetching directly from GitHub.
- JavaScript entrypoints changed from
oauth.css
andoauth.js
toaccount.css
andaccount.css
. Note: For deployments using custom frontend bundles (e.g. via--is.oauth.ui.js-file
), the filenames have to be updated accordingly as well.
Removed
- Application Server linking. The Network Server now pushes data to the cluster Application Server instead.
- Applications which desire to handle payload decryption within their own domains should disable payload decryption at application or device level and decrypt the payload on their own end.
- While not backwards compatible, the decision to remove linking was heavily motivated by scalability concerns - the previous linking model scales poorly when taking high availability and load balancing concerns into account.
- The option to disable CUPS per gateway
gcs.basic-station.require-explicit-enable
.
Fixed
- Network Server DevStatusReq scheduling conditions in relation to frame counter value.
- Missing
authentication
,remote_ip
anduser_agent
fields in events when using event backends other thaninternal
. - Handling of
DLChannelReq
if dependentNewChannelReq
was previously rejected. - Login after user registration leading to dead-end when originally coming from the Console.
- Frame counter display of end devices on initial page load in the Console.
- AU915-928 data rate indexes in Regional Parameter specification versions below 1.0.2b.
Docker images
docker pull thethingsnetwork/lorawan-stack:3.11
docker pull thethingsnetwork/lorawan-stack:3.11.0
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.11
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.11.0
v3.11.0-rc2
Docker images
docker pull thethingsnetwork/lorawan-stack:3.11
docker pull thethingsnetwork/lorawan-stack:3.11.0-rc2
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.11
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.11.0-rc2
v3.11.0-rc1
v3.10.7
Fixed
- The inability to see individual end devices in the Console due to field mask errors.
Docker images
docker pull thethingsnetwork/lorawan-stack:3.10
docker pull thethingsnetwork/lorawan-stack:3.10.7
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10.7
v3.10.6
⚠️ Known Bugs ⚠️
The v3.10.6 release contains a bug in the Console that prevents device views from loading.
Added
- Configuration option
is.admin-rights.all
to grant admins all rights, including_KEYS
and_ALL
. - Configuration option
is.user-registration.contact-info-validation.token-ttl
to customize the validity of contact information validation tokens. ttn-lw-stack
CLI command for creating an API Key with full rights on a user.
Changed
- Packet Broker API version to
v3.2.0-tts
and routing API tov1.0.2-tts
. - Emails with temporary tokens now also show when these tokens expire. Custom email templates can use
{{ .TTL }}
and{{ .FormatTTL }}
to render the expiry durations.
Deprecated
- Packet Broker mutual TLS authentication: use OAuth 2.0 client credentials instead; set
pba.authentication-mode
tooauth2
and configurepba.oauth2
. - Packet Broker forwarder blacklist setting
pba.home-network.blacklist-forwarder
has become ineffective.
Docker images
docker pull thethingsnetwork/lorawan-stack:3.10
docker pull thethingsnetwork/lorawan-stack:3.10.6
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10.6
v3.10.5
Changelog
Added
- Support for sending end device uplinks using the CLI (see
ttn-lw-cli simulate application-uplink
command). - Clients can now perform custom ADR by modifying ADR parameters in
mac-state.desired-parameters
of the device.
Changed
- Form field layouts in the Console (field labels are now dispayed above the field).
- Small structural changes to the custom webhook form in the Console.
- Renamed experimental command
ttn-lw-cli simulate uplink
tottn-lw-cli simulate gateway-uplink
. - Renamed experimental command
ttn-lw-cli simulate join-request
tottn-lw-cli simulate gateway-join-request
.
Fixed
- Removed misleading warning message for missing package data when setting up the storage integration package association.
Detailed Release notes
Docker images
docker pull thethingsnetwork/lorawan-stack:3.10
docker pull thethingsnetwork/lorawan-stack:3.10.5
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10.5
v3.10.4
Added
- Configure application activation settings from the CLI (see
ttn-lw-cli application activation-settings
commands). - User API keys management to the Console.
Purge
RPC and cli command for entity purge (hard-delete) from the database.- More password validation rules in the user management form in the Console.
- Support for class B end devices in the Console.
- MAC settings configuration when creating and editing end devices in the Console.
- Support for the LR1110 LTV stream protocol.
Changed
- Branding (updated TTS Open Source logo, colors, etc).
Fixed
- Simulated uplinks visibility in webhook messages.
- Retransmission handling.
- RTT recording for LBS gateways. The maximum round trip delay for RTT calculation is configurable via
--gs.basic-station.max-valid-round-trip-delay
. - Memory leak in GS scheduler.
Docker images
docker pull thethingsnetwork/lorawan-stack:3.10
docker pull thethingsnetwork/lorawan-stack:3.10.4
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10.4
v3.10.3
Added
- Configure application activation settings from the CLI (see
ttn-lw-cli application activation-settings
commands).
Security
- Fixed an issue with authentication on the
/debug/pprof
,/healthz
and/metrics
endpoints.
Docker images
docker pull thethingsnetwork/lorawan-stack:3.10
docker pull thethingsnetwork/lorawan-stack:3.10.3
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10
docker pull ghcr.io/thethingsnetwork/lorawan-stack:3.10.3
v3.9.5 (backport)
Security
- Fixed an issue with authentication on the
/debug/pprof
,/healthz
and/metrics
endpoints.
Docker images
docker pull thethingsnetwork/lorawan-stack-dev:c742fb3176002e43d7427186de84f502abe4fdbf
docker pull thethingsnetwork/lorawan-stack:3.9
docker pull thethingsnetwork/lorawan-stack:3.9.5