After reading this issue https://github.com/Lora-net/packet_forwarder/issues/16
I think than it would be great to have a global discussion about the responsibility of each layer, and if the duty cycle is not managed by the packet forwarder, implementing this counter on the lora-gateway-bridge.
@brocaar Is there any limit for downlink for the device?
I have a couple of devices, for one device I sent the downlink to enable the GPS, setting the position message limit and heartbeat message limit in the morning and I got the confirmation in form of uplink that my configurations have applied and after that every uplink I got as expected result.
Now I am trying the same procedure for other devices but I am not getting any confirmation for configuration from the devices after sending the downlink
So questions are
Is there any limit for the number of downlinks or the size of the downlink we can send to the device?
Because the configuration is getting applied OTA, is it specific to the time when we can apply the configuration on the device by sending the downlink?
Sorry for few basic questions but I am really struggling to understand this
Duty Cycles apply to both uplink and downlink, it is the time that the device is broadcasting (sending or receiving) GPS devices can come very close to Duty Cycle limits depending on the resolution (accuracy) that the device is configured to report as well as the reporting interval…
This will depend on your SF, payload size, etc. The easiest way to be sure is to ensure that you are using certified devices… otherwise, more on the subject here… LoRa — LoRa documentation although this can be mind numbing… so instead, just make sure you use reputable devices, and revert to the supplier for duty cycle validation calrifying SF as well as whichever country you are in and therefore which Duty Cycles apply