# TypedInput for mqtt-in and out nodes

**URL:** <https://discourse.nodered.org/t/typedinput-for-mqtt-in-and-out-nodes/35751>\
**Category:** Feature Requests\
**Created:** [11 November 2020 15:13 UTC](https://discourse.nodered.org/t/typedinput-for-mqtt-in-and-out-nodes/35751 "2020-11-11T15:13:51Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![w4tsn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/w4tsn/32/11054_2.png) [@w4tsn](https://discourse.nodered.org/u/w4tsn)\
**Post date:** [12 November 2020 10:37 UTC](https://discourse.nodered.org/t/typedinput-for-mqtt-in-and-out-nodes/35751/5 "2020-11-12T10:37:23Z")

</div>

Is that something that could be changed? That the mqtt-node can create a connection to the broker not only on deploy but at runtime? This is crucial to get this node programmable and I think a programmable mqtt-in / out node is quite important for any automated setup.

Maybe toss that directly into the re-design of the node vor MQTTv5 discussed in [Node-RED Mqtt 5 support](https://discourse.nodered.org/t/node-red-mqtt-5-support/17847) ?

---

_[View the full topic](https://discourse.nodered.org/t/typedinput-for-mqtt-in-and-out-nodes/35751)._