# How to set dwelltime to 0 at AS923 in lopy4?

**URL:** <https://www.thethingsnetwork.org/forum/t/how-to-set-dwelltime-to-0-at-as923-in-lopy4/50098>\
**Category:** Pycom\
**Created:** [July 26, 2021, 11:23pm UTC](https://www.thethingsnetwork.org/forum/t/how-to-set-dwelltime-to-0-at-as923-in-lopy4/50098 "2021-07-26T23:23:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![arya\_wakwaw](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arya_wakwaw/32/35697_2.png) [@arya\_wakwaw](https://www.thethingsnetwork.org/forum/u/arya_wakwaw)\
**Post date:** [July 26, 2021, 11:23pm UTC](https://www.thethingsnetwork.org/forum/t/how-to-set-dwelltime-to-0-at-as923-in-lopy4/50098/1 "2021-07-26T23:23:24Z")

</div>

hello, I have a problem when sending \>11 bytes payload at SF10 (AS923) my lopy is getting OSerror and in TTN displays "_not provided_ ". after I read it [https://lora-alliance.org/wp-content/uploads/2020/11/lorawan\_regional\_parameters\_v1.0.3reva\_0.pdf](https://lora-alliance.org/wp-content/uploads/2020/11/lorawan_regional_parameters_v1.0.3reva_0.pdf) , my problem occur due to dwelltime value is 1.  
How to set the dwelltime to 0? Because I think AS923 can so that.  
I’ve test using another node (ursalink sensor node) and it can send up to 33byte payload at SF10. so the dwelltime is 0.

I’m use  
End node : Lopy4 (lorawan version 1.0.2)  
Gateway : kerlink i station  
Lorawan server : router.as.1.thethings.network (TTNv2 cloud)

---

<div class="post-metadata">

**Author:** ![Jeff-UK](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeff-uk/32/35697_2.png) [@Jeff-UK](https://www.thethingsnetwork.org/forum/u/Jeff-UK)\
**Post date:** [July 27, 2021, 8:49am UTC](https://www.thethingsnetwork.org/forum/t/how-to-set-dwelltime-to-0-at-as923-in-lopy4/50098/2 "2021-07-27T08:49:15Z")

</div>

Cant be sure as dont have these devices and dont use/have access to those bands but suspect not so much a value as a state i.e. 1 = Dwell time limts enforced, 0 = Dwell time limits not enforced. Suggest review the code to see where enforcement is actioned to see if you can change state. Also be careful as dwell time enforcement (as in US under US915, where the limit is 400mS) is a regulatory limit by territory vs a technical/functional limit by device (again unsure but may be actual Dwell time limit changes by territory - same as or more of less than the US 400mS as above). As AS923 can be used in many territories it may be that turning on and off on the Ursalink (Milesight) device is permited as Dwell time may not be enforced in some territories where it can function… where in the world are you? Is dwell time limit a regulatory requirement in your area? Have your checked with authorative source?!

---

<div class="post-metadata">

**Author:** ![arya\_wakwaw](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arya_wakwaw/32/35697_2.png) [@arya\_wakwaw](https://www.thethingsnetwork.org/forum/u/arya_wakwaw)\
**Post date:** [October 19, 2021, 3:16am UTC](https://www.thethingsnetwork.org/forum/t/how-to-set-dwelltime-to-0-at-as923-in-lopy4/50098/3 "2021-10-19T03:16:58Z")

</div>

Hi jeff, yes I think my ursalink sensor node is have outdate firmware. I’ve read in updated documentation ([https://lora-alliance.org/wp-content/uploads/2020/11/RP\_2-1.0.2.pdf](https://lora-alliance.org/wp-content/uploads/2020/11/RP_2-1.0.2.pdf))  
 ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/2/4/2447efa1de5e0cc07481029626dba7a887b2d4eb.png)  
AS923-2 dwell time is limited