# Change in MQTT input node?

**URL:** <https://discourse.nodered.org/t/change-in-mqtt-input-node/11978>\
**Category:** General\
**Created:** [8 June 2019 14:12 UTC](https://discourse.nodered.org/t/change-in-mqtt-input-node/11978 "2019-06-08T14:12:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wb666greene](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wb666greene/32/6534_2.png) [@wb666greene](https://discourse.nodered.org/u/wb666greene)\
**Post date:** [8 June 2019 14:12 UTC](https://discourse.nodered.org/t/change-in-mqtt-input-node/11978/1 "2019-06-08T14:12:27Z")

</div>

I recently installed my Ai system at a friends shop. Virgin Linux install. Everything was working fine except the node-red flow that does the Email notifications and dashboard controller to set the operating mode.

Turns out there is a "new" property on the MQTT input node to select string or buffer output. Half of the mqtt input nodes from my import--\>clipboard installation ended up with the wrong setting. My 19.5 node-red systems don't have this property. I believe his system ended up with 20.5

Its just something I need to be aware of going forward and, maybe a useful heads up to someone who might encounter this after an update or when like me, moving a flow to a new installation.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [8 June 2019 14:34 UTC](https://discourse.nodered.org/t/change-in-mqtt-input-node/11978/2 "2019-06-08T14:34:06Z")

</div>

Yep, I have seen that as well. If I remember, I think in my case, the "old" flows where "migrated" so that auto-detect became the actual setting. In most cases, this worked fine but I did have some problems in some few nodes where i had to select the proper type
