# RAK 5205 tracker

**URL:** <https://www.thethingsnetwork.org/forum/t/rak-5205-tracker/18052>\
**Category:** End Devices (Nodes)\
**Created:** [September 20, 2018, 2:11pm UTC](https://www.thethingsnetwork.org/forum/t/rak-5205-tracker/18052 "2018-09-20T14:11:22Z")\
**Posts on this page:** 1\
**Showing post:** 70

<div class="post-metadata">

**Author:** ![kastayou](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kastayou/32/35697_2.png) [@kastayou](https://www.thethingsnetwork.org/forum/u/kastayou)\
**Post date:** [January 4, 2019, 6:49pm UTC](https://www.thethingsnetwork.org/forum/t/rak-5205-tracker/18052/70 "2019-01-04T18:49:38Z")

</div>

Please note that they have released two different firmwares that output v2.0.0.0 on the console.  
One of the 2.0.0.0 version has a bug and can only send confirmed messages which will quickly violate the TTN fair use policy

> [@Fair Use Policy explained](https://www.thethingsnetwork.org/forum/t/limitations-data-rate-packet-size-30-seconds-uplink-and-10-messages-downlink-per-day-fair-access-policy/1300):
>
> For The Things Network’s public community network the [Fair Access Policy](https://www.thethingsnetwork.org/docs/lorawan/duty-cycle.html#maximum-duty-cycle) limits the data each end-device can send, by allowing: An average of 30 seconds uplink time on air, per 24 hours, per device. At most 10 downlink messages per 24 hours, including the ACKs for confirmed uplinks. A good goal is to keep the application payload under 12 bytes, and the interval between messages at least several minutes. An [online airtime calculator can give you some insight](https://avbentem.github.io/airtime-calculator). The following regulations apply a…

For the other 2.0.0.0 version, I am not sure if by default the node is sending unconfirmed messages or if you need to manually change the parameter

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/rak-5205-tracker/18052)._
