MatchX no TX

[arjanvanb (Arjan)]

@jmarcelino

It’s even worse when using TTN’s own protocol (more latency than UDO)

Hmmm, I read that would in fact support scheduling on the gateway, but maybe not (yet):

@htdvisser

If your gateway is running Lora-net/packet_forwarder (v3 or later) or the new TheThingsNetwork/packet_forwarder this will happen automatically (soon)

Also, I made up my own reasoning for this:

@arjanvanb

I imagine there may be several reasons why TTN is sending instructions to gateways as late as possible:

• It allows TTN to choose another gateway as late as possible, or change the RX window to allow more urgent responses for other nodes to be sent.
• It allows TTN to drop responses and downlinks for nodes that have exceeded the (future) fair access policy, in favor of responding to nodes that have used less air time.
• …