# Strange MQTT Client behavior **URL:** \ **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:** 5\ **Page:** 5
**Author:** ![Russell\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/russell_s/32/45779_2.png) [@Russell\_S](https://community.homey.app/u/Russell_S)\ **Post date:** [June 8, 2021, 8:41am UTC](https://community.homey.app/t/strange-mqtt-client-behavior/45105/81 "2021-06-08T08:41:39Z")
That sounds interesting. Do I use the MQTT Hub App to create a MQTT device ?. I’ve never really used it before . ---
**Author:** ![Zimo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/zimo/32/16621_2.png) [@Zimo](https://community.homey.app/u/Zimo)\ **Post date:** [June 8, 2021, 9:06am UTC](https://community.homey.app/t/strange-mqtt-client-behavior/45105/82 "2021-06-08T09:06:50Z")
yes - add new device and choose MQTT hub device. ---
**Author:** ![Russell\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/russell_s/32/45779_2.png) [@Russell\_S](https://community.homey.app/u/Russell_S)\ **Post date:** [June 8, 2021, 9:26am UTC](https://community.homey.app/t/strange-mqtt-client-behavior/45105/83 "2021-06-08T09:26:58Z")
Thanks. I just downloaded it. It looks like theres a bit to learn but I’d dare say it will sort out my problems for now. The disabling of flows issue is happening on a daily basis now and is majorly screwing up my house hold. Nearly tripped over last night as my lights wouldn’t turn on… 😩 Would you mind telling me quickly how can I add or create a Virtual/MQTT device based on the input of a 433Mhz motion sensor… ? Whenever it trIggers it sends a MQTT message containing the text “076F2C”. How do I translate that into making a virtual/MQTT type device ? Thanks again … ---
**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")
@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… ---
**Author:** ![Russell\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/russell_s/32/45779_2.png) [@Russell\_S](https://community.homey.app/u/Russell_S)\ **Post date:** [June 8, 2021, 11:03am UTC](https://community.homey.app/t/strange-mqtt-client-behavior/45105/85 "2021-06-08T11:03:54Z")
Thanks mate. Tonight I spent some more time making sure all my settings were correct as I didn’t know much about Tasmota, using MQTT or setting up Homey when I got my system originally going… With the original “disabling of flows” errors that I was experiencing I think that may of been due to the original code of the MQTT client as that now doesn’t occur anymore when I try to discover new Tasmota devices. After some thought I think I might have a theory as to why these new more recent errors are occurring . Tonight I went to check the settings of my SonOff RF bridge (Tasmota) configuration. I noticed that I had previously set logging to “all”. I did this (at the time) as I was having issues getting it going . I never changed those settings back to default and just kept using them. Tonight I put those logging settings back to normal default… After doing that change Ive noticed all my flows wont receive any inputs or triggers anymore… I went through some MQTT client logs and noticed it would occasionally reference “tele/rfbridge1” as the topic. I’ve always use “stat/rfbridge1” in my flows… Tonight I went and changed all my flows to listen to “tele/rfbridge1” instead . Now they work again … Do you think all the recent disable flow errors I was experiencing over the last few days was due to the log settings I had previously setup on my SonOff-RF bridge combined with using “stat/rfbridge1” when listening for wildcards in my flows ? It’s too early to tell but everything seems to be runnings fine since I made these new changes … [Previous page](https://community.homey.app/t/strange-mqtt-client-behavior/45105.md?page=4)