TheThingsNetwork/lorawan-stack v3.7.2

on GitHub

Added

• CLI can now dump JSON encoded grpc_payload field for unary requests (see --dump-requests flag).
• Template ID column in the webhook table in the Console.
• Select all field mask paths in CLI get, list and search commands (see --all option).
• Create webhooks via webhook templates in the Console.
• ns.up.data.receive and ns.up.join.receive events, which are triggered when respective uplink is received and matched to a device by Network Server.
• ns.up.data.forward and ns.up.join.accept.forward events, which are triggered when respective message is forwarded from Network Server to Application Server.
• ns.up.join.cluster.attempt and ns.up.join.interop.attempt events, which are triggered when the join-request is sent to respective Join Server by the Network Server.
• ns.up.join.cluster.success and ns.up.join.interop.success events, which are triggered when Network Server's join-request is accepted by respective Join Server.
• ns.up.join.cluster.fail and ns.up.join.interop.fail events, which are triggered when Network Server's join-request to respective Join Server fails.
• ns.up.data.process and ns.up.join.accept.process events, which are triggered when respective message is successfully processed by Network Server.
• ns.down.data.schedule.attempt and ns.down.join.schedule.attempt events, which are triggered when Network Server attempts to schedule a respective downlink on Gateway Server.
• ns.down.data.schedule.success and ns.down.join.schedule.success events, which are triggered when Network Server successfully schedules a respective downlink on Gateway Server.
• ns.down.data.schedule.fail and ns.down.join.schedule.fail events, 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-port and --oauth-server-address options).

Changed

• 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_link event to ns.application.link.begin.
• Renamed ns.application.end_link event to ns.application.link.end.
• ns.up.data.drop and ns.up.join.drop events 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-Control header for static files.
• Sort events by time in the Console.

Removed

• ns.up.merge_metadata event.
• ns.up.receive_duplicate event.
• ns.up.receive event.

Fixed

• 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.

Changelog

Docker images

• docker pull thethingsnetwork/lorawan-stack:3.7.2