# Dht11 cannot read temp and humidity on Lora shield gps

**URL:** <https://www.thethingsnetwork.org/forum/t/dht11-cannot-read-temp-and-humidity-on-lora-shield-gps/32383>\
**Category:** Uncategorized\
**Created:** [December 4, 2019, 6:25pm UTC](https://www.thethingsnetwork.org/forum/t/dht11-cannot-read-temp-and-humidity-on-lora-shield-gps/32383 "2019-12-04T18:25:43Z")\
**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:** [August 16, 2020, 8:43am UTC](https://www.thethingsnetwork.org/forum/t/dht11-cannot-read-temp-and-humidity-on-lora-shield-gps/32383/10 "2020-08-16T08:43:52Z")

</div>

> [@swebstergeo](#):
>
> I’m not quite sure how to unset OP\_TXRXPEND

You shouldn’t. Unless you’re referring to:

> [@cslorabox](#):
>
> that flag can often get stuck on in LMiC for various reasons

Just to be clear: bugs aside, it’s set when another transmission is already scheduled, so you should not run into that condition unless you’re transmitting too much. So: just adhere to the regulations and [other limitations](https://www.thethingsnetwork.org/forum/t/limitations-data-rate-packet-size-30-seconds-uplink-and-10-messages-downlink-per-day-fair-access-policy-guidelines/1300) and you should not run into that branch of the code at all.

(Aside: note that the `LMIC_setTxData2` is commented out in your sample code. So, that code is not sending anything. Also, [it’s very unlikely](https://www.thethingsnetwork.org/forum/t/dragino-with-ultrasonic-sensor-and-ttn/38423/3) you want the `-1` in `sizeof(mydata)-1`.)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/dht11-cannot-read-temp-and-humidity-on-lora-shield-gps/32383)._