# MQTT Machines don't support string types?

**URL:** <https://community.tulip.co/t/mqtt-machines-dont-support-string-types/10107>\
**Category:** Support, Troubleshooting, & Help\
**Created:** [December 20, 2023, 4:58pm UTC](https://community.tulip.co/t/mqtt-machines-dont-support-string-types/10107 "2023-12-20T16:58:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard-SNN](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/richard-snn/32/1166_2.png) [@Richard-SNN](https://community.tulip.co/u/Richard-SNN)\
**Post date:** [December 20, 2023, 4:58pm UTC](https://community.tulip.co/t/mqtt-machines-dont-support-string-types/10107/1 "2023-12-20T16:58:16Z")

</div>

I’ve started playing around with MQTT for machines and I’ve had some luck. But when I went back and looked I noticed that integer attributes update fine but string ones never do.

I can browse and attach the attribute fine but they stay permanently stuck at “No data available” if if I force a new MQTT message to publish.

Is this expected?

EDIT: This is LTS 11.

---

<div class="post-metadata">

**Author:** ![Pete\_Hartnett](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete_hartnett/32/3678_2.png) [@Pete\_Hartnett](https://community.tulip.co/u/Pete_Hartnett)\
**Post date:** [December 21, 2023, 5:22pm UTC](https://community.tulip.co/t/mqtt-machines-dont-support-string-types/10107/2 "2023-12-21T17:22:19Z")

</div>

Hmmm. Certainly not expected. Just verified I am getting string updates on my machine in LTS11. Do you mind shooting an email to [support@tulip.co](mailto:support@tulip.co) so they can dig into your specific mapping?

Pete

---

<div class="post-metadata">

**Author:** ![Richard-SNN](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/richard-snn/32/1166_2.png) [@Richard-SNN](https://community.tulip.co/u/Richard-SNN)\
**Post date:** [January 2, 2024, 4:25pm UTC](https://community.tulip.co/t/mqtt-machines-dont-support-string-types/10107/3 "2024-01-02T16:25:54Z")

</div>

I was going to see if I could reproduce the issue on our dev instance (running biweekly release) first, but it looks like the connector host has not been updated (doesn’t allow secure MQTT connections).

IT should fix that sometime tomorrow.

---

<div class="post-metadata">

**Author:** ![Richard-SNN](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/richard-snn/32/1166_2.png) [@Richard-SNN](https://community.tulip.co/u/Richard-SNN)\
**Post date:** [January 11, 2024, 7:30pm UTC](https://community.tulip.co/t/mqtt-machines-dont-support-string-types/10107/4 "2024-01-11T19:30:49Z")

</div>

Just in case anyone else reads this, the problem should be fixed in the LTS 11.1 connector host.