# TTIG does not support downlinks when not frequently receiving uplinks? **URL:** \ **Category:** TTIG - The Things Indoor Gateway\ **Created:** [November 22, 2019, 11:04pm UTC](https://www.thethingsnetwork.org/forum/t/ttig-does-not-support-downlinks-when-not-frequently-receiving-uplinks/32052 "2019-11-22T23:04:02Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [November 23, 2019, 9:11am UTC](https://www.thethingsnetwork.org/forum/t/ttig-does-not-support-downlinks-when-not-frequently-receiving-uplinks/32052/3 "2019-11-23T09:11:15Z")
Indeed, it’s quite likely that downlinks might arrive too late (or might not even be delegated to the TTIG by the backend?) when a TTIG is not receiving a lot of traffic: > [@New gateway: The Things Indoor Gateway](https://www.thethingsnetwork.org/forum/t/new-gateway-the-things-indoor-gateway/22049/678): > > In response to the "flashing green LED " question: > > Yes that’s normal behavior. > > If there’s no traffic on your gateway for about 60s, the WebSocket(WS) connection to the network is dropped intentionally and the gateway will re-connect. During reconnection, the LED will flash green. > > The reason for this to not have gateways actively connected to the network and taking up resources when there’s no traffic (since WS requires a persistent connection). …to which @tchenier already responded: > [@New gateway: The Things Indoor Gateway](https://www.thethingsnetwork.org/forum/t/new-gateway-the-things-indoor-gateway/22049/683): > > wouldn’t the Downlink listen window on the device be missed because of the large time delay between Uplink transmit and when the TTN servers received it? Therefore, unless another active gateway is in the area, you’d never be able to get a Downlink packet to the device. This includes confirmed uplinks and ADR (after 1 or 2 seconds), and less likely the very first OTAA Join Accept (after 5 or 6 seconds). Given its indoor use, it’s quite likely that it’s not receiving many packets from other users? A summary of some problems discussed hidden in other topics: - Some report it is not buffering the uplink: - …but others see it being sent, but much later, showing “retry” for uplinks that are actually only sent once: - Also, it seems it might cause uplinks to go missing if it’s already reconnecting: - Like also mentioned by @Vaelid above, this seems to affect ADR: I don’t know if there’s any GitHub project where this might be/have been reported on? (I don’t see it on, e.g., [The Things Network · GitHub](https://github.com/TheThingsNetwork), [The Things Products · GitHub](https://github.com/TheThingsProducts), [The Things Industries · GitHub](https://github.com/TheThingsIndustries), or maybe it is part of [GitHub - lorabasics/basicstation: LoRa Basics™ Station - The LoRaWAN Gateway Software](https://github.com/lorabasics/basicstation) ?) --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/ttig-does-not-support-downlinks-when-not-frequently-receiving-uplinks/32052)._