Class C Downlinks in Things Stack v3.24.0

Device join and send uplink without problems. But when I attempt a downlink, logs indicate that scheduling is attempted several times, and then fails with a TOO_EARLY or “schedule in Rx window {window} failed” message.

These are all Class C Devices. I am running a private network, but devices are on FSB 2 for now until our factory changes to another FSB.

What is the reason that downlinks are never delivered? My understanding with Class C is that they should be delivered as soon as possible, which should be immediately.

1 Like

This ended up having nothing to do with class C or things stack at all. A random router I was using seems to just be malfunctioning. No firewall in place, but messages to port 1700 not passing.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.