# AS923 dwell time limitation for Australia

**URL:** <https://www.thethingsnetwork.org/forum/t/as923-dwell-time-limitation-for-australia/36601>\
**Category:** Frequency Plan\
**Created:** [April 30, 2020, 10:21am UTC](https://www.thethingsnetwork.org/forum/t/as923-dwell-time-limitation-for-australia/36601 "2020-04-30T10:21:34Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [June 19, 2020, 8:31am UTC](https://www.thethingsnetwork.org/forum/t/as923-dwell-time-limitation-for-australia/36601/10 "2020-06-19T08:31:51Z")

</div>

> [@arjanvanb](#):
>
> a maximum duty cycle […] is a regulation of one’s country, not something TTN has introduced

…but apparently the maximum duty cycles may have been limited even more by the LoRaWAN specifications:

> [@AS923 Duty Cycle](https://www.thethingsnetwork.org/forum/t/as923-duty-cycle/37924/2):
>
> It’s important to keep in mind that the duty cycle limitations described in the tables of the specifications are LoRaWAN-imposed limitations, and not legal limitations. If you build commercial devices and want them to be LoRaWAN certified, they need to comply with the specification. Development devices don’t have to be fully compliant with the specification. Any device (whether LoRaWAN or not, gateway or node, commercial or development) needs to be compliant with the legal limitations that apply in your country.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/as923-dwell-time-limitation-for-australia/36601)._