Hi,
Regarding EU868 regional duty-cycle regulations (ETSI EN300.220-2), which typically cap transmissions at 1% (36s/hour):
I would like to clarify how ChirpStack handles this internally:
Downlink Scheduling
Does ChirpStack enforce a mandatory T_off (silence period) between subsequent downlinks based on the T_off = ToA / 0.01 - To_A formula, or does it simply track the 36s/hour sliding window budget?
Uplink Validation
If an end-device sends uplinks faster than the T_off but remains within the 36s/hour legal limit, does ChirpStack discard these frames or mark them as invalid?
Network Behavior
Is the "1% rule" in ChirpStack managed as a strict per-message interval (T_off) or as a collective hourly budget? This is crucial for me to understand if I can send small bursts of data or if I must strictly space every uplink according to the individual T_off of the previous packet.