# Throttle mqtt traffic at flow startup

**URL:** https://discourse.nodered.org/t/throttle-mqtt-traffic-at-flow-startup/94660
**Category:** General
**Tags:** mqtt
**Created:** [15 January 2025 23:52 UTC](https://discourse.nodered.org/t/throttle-mqtt-traffic-at-flow-startup/94660 "2025-01-15T23:52:22Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [20 January 2025 14:31 UTC](https://discourse.nodered.org/t/throttle-mqtt-traffic-at-flow-startup/94660/12 "2025-01-20T14:31:29Z")

</div>

The snapshot of your mqtt-in nodes in that Adafruit forum shows 27 nodes, all subscribing to kd0ycl/f/something.

You can certainly replace all of these with a single subscription to kd0ycl/f/+ or kd0ycl/f/#, reducing your subscribe message volume by 95%.  
This is surely the way to go, no need for the more complex dynamic subscription (which anyway you have found the problem with)

If you want to avoid the massive switch node on your flow tab you could have the mqtt-in and switch on it's own tab, using link nodes to pass messages to the tab[s] where you process them.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/b/3b5d5957f0eb1967688fada6b82c061d505488be.png)

---

_[View the full topic](https://discourse.nodered.org/t/throttle-mqtt-traffic-at-flow-startup/94660)._