Why is the "TOO_EARLY" problem?

Tcy · February 22, 2023, 12:20am

bconway · February 22, 2023, 1:32am

chirpstack/chirpstack/blob/master/api/proto/gw/gw.proto#L77


      
          // Ignored (when a previous item was already emitted).
          IGNORED = 0;
          
          
// Packet has been programmed for downlink.
          OK = 1;
          
          
// Rejected because it was already too late to program this packet for downlink.
          TOO_LATE = 2;
          
          
// Rejected because downlink packet timestamp is too much in advance.
          TOO_EARLY = 3;
          
          
// Rejected because there was already a packet programmed in requested timeframe.
          COLLISION_PACKET = 4;
          
          
// Rejected because there was already a beacon planned in requested timeframe.
          COLLISION_BEACON = 5;
          
          
// Rejected because requested frequency is not supported by TX RF chain.
          TX_FREQ = 6;

You may have a (too large) disparity in timekeeping between your server and gateway.