These docs are for v2.0. Click to read the latest docs for v3.3.

Discussions

Ask a Question
Back to All

Best Practices for Managing Downlink Queues on Class A Devices?

Hi everyone,

I’ve been working on a project using a few Class A LoRaWAN devices (based on STM32 + RN2483) connected through The Things Stack, and I’m running into some confusion around downlink queue management.

Specifically, I’d like to understand what the best practices are for handling queued downlinks when devices check in infrequently (e.g., every 30 minutes). Sometimes I notice messages get lost or overwritten if I try to push multiple downlinks before the device’s next uplink.

Here are a few questions I hope someone can help clarify:

Is there a known limit to how many downlink messages can be queued per device?

What’s the behavior if multiple downlinks are scheduled but the device only uplinks once?

Are there strategies for prioritizing critical vs. non-critical downlink data in this kind of setup?

Any advice, documentation links, or examples from your own deployments would be super helpful!

Thanks in advance,
—Lucas_Builds

geometry dash lite