# Strange MQTT Client behavior

**URL:** <https://community.homey.app/t/strange-mqtt-client-behavior/45105>\
**Category:** Apps\
**Tags:** flow, mqtt\
**Created:** [March 22, 2021, 7:03pm UTC](https://community.homey.app/t/strange-mqtt-client-behavior/45105 "2021-03-22T19:03:01Z")\
**Posts on this page:** 1\
**Showing post:** 84

<div class="post-metadata">

**Author:** ![HarriedeGroot](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/harriedegroot/32/56160_2.png) [@HarriedeGroot](https://community.homey.app/u/HarriedeGroot)\
**Post date:** [June 8, 2021, 10:39am UTC](https://community.homey.app/t/strange-mqtt-client-behavior/45105/84 "2021-06-08T10:39:53Z")

</div>

@Russell_S A general example can be found here:

> [@Tasmota flashed Window Sensor ON/OFF to true/false? MQTT](https://community.homey.app/t/tasmota-flashed-window-sensor-on-off-to-true-false-mqtt/47761/8):
>
> Just create an MQTT Device and add a ‘Turned On/Off’ capability pointing to the correct state & command topics of your tasmota device. Then you have two options to solve your problem: Either configure the input and output templates like this: input: value == ‘on’ output: value ? ‘on’ : ‘off’ Or leave the input & output templates empty. After creating the device, go to the advanced device config and select ‘on/off’ for the ‘on/off values’ setting (true/false in screenshot), thi…

---

_[View the full topic](https://community.homey.app/t/strange-mqtt-client-behavior/45105)._