# MQTT Bidirectional Components

**URL:** <https://forum.inductiveautomation.com/t/mqtt-bidirectional-components/44455>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [March 15, 2021, 3:59am UTC](https://forum.inductiveautomation.com/t/mqtt-bidirectional-components/44455 "2021-03-15T03:59:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![james.beeley](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.beeley/32/28019_2.png) [@james.beeley](https://forum.inductiveautomation.com/u/james.beeley)\
**Post date:** [March 15, 2021, 3:59am UTC](https://forum.inductiveautomation.com/t/mqtt-bidirectional-components/44455/1 "2021-03-15T03:59:02Z")

</div>

I’m reading values from a groov RIO device through the MQTT Engine tag provider. I want to have the ability to change LED states through a component on my screen.

When I bind to the MQTT Engine tag, the bidirectional property on my component is disabled. As a workaround, I duplicated the tags in my default tag provider, and used a tag event script on value changed.

 ![Untitled](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/6/76734d55924f00093113625827fd9611be045e53.png)

While this does change the value of the MQTT Engine tag in my tag browser, my LED doesn’t change.

Is there a workaround to make this possible? I ran into problems using MQTT Transmission, but am open to exploring that option if it’s a better approach.

---

<div class="post-metadata">

**Author:** ![james.beeley](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.beeley/32/28019_2.png) [@james.beeley](https://forum.inductiveautomation.com/u/james.beeley)\
**Post date:** [March 18, 2021, 12:05am UTC](https://forum.inductiveautomation.com/t/mqtt-bidirectional-components/44455/2 "2021-03-18T00:05:14Z")

</div>

Solved. My problem was with components breaking after restoring from a much older version of Ignition. MQTT works fine.