# Cannot subscribe with MQTT QoS 1

**URL:** <https://forums.losant.com/t/cannot-subscribe-with-mqtt-qos-1/612>\
**Category:** Help\
**Created:** [September 3, 2017, 4:03am UTC](https://forums.losant.com/t/cannot-subscribe-with-mqtt-qos-1/612 "2017-09-03T04:03:39Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Jose\_Cruz](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jose_cruz/32/1580_2.png) [@Jose\_Cruz](https://forums.losant.com/u/Jose_Cruz)\
**Post date:** [August 18, 2021, 9:00pm UTC](https://forums.losant.com/t/cannot-subscribe-with-mqtt-qos-1/612/21 "2021-08-18T21:00:20Z")

</div>

> [@Brandon\_Cannaday](#):
>
> One caveat to keep in mind is that the MQTT rate limit (2/sec/topic) sill applies. So if that wildcard topic is receiving data for tons of devices, you could quickly exceed that limit.

Thanks for this piece of info, that basically ‘_seals the deal_’ on how we are going to proceed next 🙂 One last question, would you know or can guide me to where I can find out what is Losan’t current MQTT **keep alive** time set at? Thanks, 🔴

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [August 18, 2021, 9:17pm UTC](https://forums.losant.com/t/cannot-subscribe-with-mqtt-qos-1/612/22 "2021-08-18T21:17:40Z")

</div>

Keep alive intervals are not defined by Losant (or any MQTT broker). They are provided by your MQTT client in the [Connect Packet](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc385349238).

The client tells the broker what the keep alive interval should be. The client is then responsible for ensuring that the interval is never exceeded. If there’s no actual data to send, the client will send a [PINGREQ](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718081) packet to keep the connection alive.

The broker will disconnect the client if the client does not send any packets within the keep alive interval it specified in its own connect packet.

The default keep alive period for most MQTT clients is 60 seconds, which is generally a good value to use.

---

<div class="post-metadata">

**Author:** ![Jose\_Cruz](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jose_cruz/32/1580_2.png) [@Jose\_Cruz](https://forums.losant.com/u/Jose_Cruz)\
**Post date:** [August 18, 2021, 9:35pm UTC](https://forums.losant.com/t/cannot-subscribe-with-mqtt-qos-1/612/23 "2021-08-18T21:35:18Z")

</div>

Ok, let me readdress the question : what is Losant’s MQTT **client** keep alive period? Is it default, 60 sec? 🔴

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [August 18, 2021, 9:50pm UTC](https://forums.losant.com/t/cannot-subscribe-with-mqtt-qos-1/612/24 "2021-08-18T21:50:45Z")

</div>

Gotcha. Losant clients are wrappers around popular open-source MQTT clients. They all default to 60 seconds.

For example, our Node.js client uses [MQTT.js](https://github.com/mqttjs/MQTT.js) under the hood.

---

<div class="post-metadata">

**Author:** ![Jose\_Cruz](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jose_cruz/32/1580_2.png) [@Jose\_Cruz](https://forums.losant.com/u/Jose_Cruz)\
**Post date:** [August 18, 2021, 10:01pm UTC](https://forums.losant.com/t/cannot-subscribe-with-mqtt-qos-1/612/25 "2021-08-18T22:01:50Z")

</div>

Perfect, thanks many 🔴

[Previous page](https://forums.losant.com/t/cannot-subscribe-with-mqtt-qos-1/612.md?page=1)