# Gateway is receiving the exact same packet for DevAddr "BEACE103" every 10 minutes

**URL:** <https://www.thethingsnetwork.org/forum/t/gateway-is-receiving-the-exact-same-packet-for-devaddr-beace103-every-10-minutes/12581>\
**Category:** Uncategorized\
**Created:** [February 13, 2018, 8:09am UTC](https://www.thethingsnetwork.org/forum/t/gateway-is-receiving-the-exact-same-packet-for-devaddr-beace103-every-10-minutes/12581 "2018-02-13T08:09:57Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [May 10, 2018, 12:54pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-is-receiving-the-exact-same-packet-for-devaddr-beace103-every-10-minutes/12581/19 "2018-05-10T12:54:03Z")

</div>

So at least the static, plain text payload is limited in size a bit by some reverse Base64 (rather than just using the DevAddr and an empty payload to reduce the airtime).

But weird that a LoRaWAN provider is deploying devices [that are not LoRaWAN compliant](https://www.thethingsnetwork.org/forum/t/can-i-register-an-abp-device-that-has-fixed-devaddr-nwkskey-and-appskey/3831/16)?

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/gateway-is-receiving-the-exact-same-packet-for-devaddr-beace103-every-10-minutes/12581)._
