Scheduled - During this maintenance window we will update The Things Stack to v3.9.3. We do not expect noticeable downtime during this deployment.

Here is the changelog since the current version 3.9.1:

Added
- Add the-things-stack device template converter, enabled by default. Effectively, this allows importing end devices from the Console.
- Support for binary decoding downlink messages previously encoded with Javascript or CayenneLPP.
- Common CA certificates available in documentation.
- Service data fields to pub/subs and webhooks in the Console.

Changed
- Scheduling failure events are now emitted on unsuccessful scheduling attempts.
- Default Javascript function signatures to encodeDownlink(), decodeUplink() and decodeDownlink().
- Default Class B timeout is increased from 1 minute to 10 minutes as was originally intended.
- Update Go to 1.15
- Application, gateway, organization and end device title sections in the Console.
- Network Server downlink queues now have a capacity - by default maximum application downlink queue length is 10000 elements.
- Improve ADR algorithm loss rate computation.

Deprecated
- Previous Javascript function signatures Decoder() and Encoder(), although they remain functional until further notice.

Fixed
- CLI login issues when OAuth Server Address explicitly includes the :443 HTTPS port.
- Documentation link for LoRa Cloud Device & Application Services in the Lora Cloud integration view in the Console.
- Webhooks and Pub/Subs forms in the Console will now let users choose whether they want to overwrite an existing record when the ID already exists (as opposed to overwriting by default).
- Tenant Billing Server suspending unmanaged tenants.
- Reconnection issue to AWS IoT MQTT when the session expired (default after 15 minutes).
- Pub/Sub integrations not backing off on internal connection failures.
- Network Server ping slot-related field validation.
- Memory usage of Network Server application uplink queues.
- Incorrect uplink FCnt display in end device title section.
- Service Data messages being routed incorrectly.
Sep 16, 11:37 CEST