# \[APP\]\[Pro\] Tasmota MQTT

**URL:** <https://community.homey.app/t/app-pro-tasmota-mqtt/26164>\
**Category:** Apps\
**Tags:** homey-pro\
**Created:** [February 20, 2020, 6:14pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164 "2020-02-20T18:14:10Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![Magic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/magic/32/12395_2.png) [@Magic](https://community.homey.app/u/Magic)\
**Post date:** [April 16, 2020, 5:39am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/61 "2020-04-16T05:39:45Z")

</div>

super, thx, i find solution. Delete problematic device. In first time i add via SONOFF APP, after added correctly, i add in SONOFF app, and all its ok, now i can delete in SONOFF APP, when i do some changes on device, like name, or other, i must do same step again.

---

<div class="post-metadata">

**Author:** ![pavlo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pavlo/32/17311_2.png) [@pavlo](https://community.homey.app/u/pavlo)\
**Post date:** [April 18, 2020, 6:49am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/62 "2020-04-18T06:49:53Z")

</div>

@Magic, Thanks for letting me know. Glad it works now.

@PascalB I checked tasmota behavior . It looks like there is no way to trigger forced tele topic update except one. You can use SetOption59=1 it will force tasmota to update tele if switch is turned on or off. Please, try if SetOption59 helps for your case and let me know. If it fixes a problem I will add this command to adding device process in my app.

---

<div class="post-metadata">

**Author:** ![PascalB](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PascalB](https://community.homey.app/u/PascalB)\
**Post date:** [April 18, 2020, 1:11pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/63 "2020-04-18T13:11:15Z")

</div>

SetOption59 was already on. Switching to off and back again no difference…

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 18, 2020, 1:23pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/64 "2020-04-18T13:23:25Z")

</div>

> [@PascalB](#):
>
> Interestingly, the state update of the device in the Sonoff app is also instant on Homey when switched through your Tasmota app, where the HA is not…?

Which implementation on HA do you use? Tele messages are for telemetry, they are _meant_ to occur only once every minute or so. It sounds like HA isn’t subscribing to `stat/*` messages, which are meant to be sent when the status of a device has changed.

My app doesn’t sent any `tele` messages at all, AFAIK.

---

<div class="post-metadata">

**Author:** ![PascalB](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PascalB](https://community.homey.app/u/PascalB)\
**Post date:** [April 18, 2020, 6:05pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/65 "2020-04-18T18:05:50Z")

</div>

I have tried autodiscovery and manual, both with the same result. The thing is that it does work with your Sonoff app, just not with the Tasmota app. Which lead me to reason that there is something different on that side in stead of HA…

---

<div class="post-metadata">

**Author:** ![pavlo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pavlo/32/17311_2.png) [@pavlo](https://community.homey.app/u/pavlo)\
**Post date:** [April 19, 2020, 1:24pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/66 "2020-04-19T13:24:13Z")

</div>

@PascalB I checked Sonoff app behavior and there is indeed no other commands as @robertklep mentioned. And according to tasmota wiki there is no way to trigger tele message only SetOption59 can help. Only explanation is that Sonoff app sets default tele update interval to 300 seconds and its twice faster then default. Also I totally agree with @robertklep, HA shouldn’t use tele to detect device status it shoult use stat topic.Anyway I added SetOption59=1 to my app on device adding. You can try it but you will need to remove and add device.

New test version 0.4.7 can be found here: [Tasmota MQTT App for Homey | Homey](https://homey.app/en-gb/app/com.paveld.tasmota/Tasmota-MQTT/test/) what is changed:

- Improved onoff capability functionality
- Fixed power monitoring for some devices
- Enabled SetOption59 on device adding

---

<div class="post-metadata">

**Author:** ![PascalB](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PascalB](https://community.homey.app/u/PascalB)\
**Post date:** [April 19, 2020, 3:47pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/67 "2020-04-19T15:47:06Z")

</div>

So the new version doesn’t change what I’m experiencing. However, when digging around some more , I have noticed that when I use the switch1 to toggle the light (so one layer deeper than the icon in the device screen, after a long press), it does update instantly in HA!

So the question is: what is the difference when toggling through the icon on the device screen vs one layer deeper?

Hope I am explaining myself clear enough with this…

---

<div class="post-metadata">

**Author:** ![pavlo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pavlo/32/17311_2.png) [@pavlo](https://community.homey.app/u/pavlo)\
**Post date:** [April 19, 2020, 8:42pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/68 "2020-04-19T20:42:15Z")

</div>

Thanks. Actually now everything crystal clear. toggling from devices sending command Power0 (which is turning on or off all switches of device) and toggling from device list sending command Power# where # is switch number. I would say this is tasmota fw bug, Power0 should behave similar to Power#. I thought it is a good idea to send one command instead of sending command per switch. OK will change behavior to sending command per switch and produce new test version. It should be relatively easy fix so will try to find some time tomorrow.

---

<div class="post-metadata">

**Author:** ![pavlo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pavlo/32/17311_2.png) [@pavlo](https://community.homey.app/u/pavlo)\
**Post date:** [April 20, 2020, 5:28pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/69 "2020-04-20T17:28:26Z")

</div>

@PascalB  
New version published to beta [Tasmota MQTT App for Homey | Homey](https://homey.app/en-gb/app/com.paveld.tasmota/Tasmota-MQTT/test/)  
Please check if it fixes your issue and let me know.

---

<div class="post-metadata">

**Author:** ![PascalB](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PascalB](https://community.homey.app/u/PascalB)\
**Post date:** [April 20, 2020, 7:15pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/70 "2020-04-20T19:15:15Z")

</div>

Absolutely, nice work!

---

<div class="post-metadata">

**Author:** ![pavlo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pavlo/32/17311_2.png) [@pavlo](https://community.homey.app/u/pavlo)\
**Post date:** [April 27, 2020, 6:51am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/71 "2020-04-27T06:51:14Z")

</div>

Hi everybody. I found a little bit of free time and added dimmer support. If you already added a dimmable device in the previous version of the application you will need to remove it and add it again. Keep in mind that this is a test version so it can be a little bit unstable. You can take it here: [Tasmota MQTT App for Homey | Homey](https://homey.app/en-gb/app/com.paveld.tasmota/Tasmota-MQTT/test/)

---

<div class="post-metadata">

**Author:** ![Robin\_van\_Kekem](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_van_kekem/32/8187_2.png) [@Robin\_van\_Kekem](https://community.homey.app/u/Robin_van_Kekem)\
**Post date:** [April 29, 2020, 11:17am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/72 "2020-04-29T11:17:21Z")

</div>

Yes, I had the same issue. After I’ve updated the firmware of Tasmota to the latest the issue was solved.

---

<div class="post-metadata">

**Author:** ![Evert\_Hoefnagel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evert_hoefnagel/32/17735_2.png) [@Evert\_Hoefnagel](https://community.homey.app/u/Evert_Hoefnagel)\
**Post date:** [April 29, 2020, 3:53pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/73 "2020-04-29T15:53:41Z")

</div>

Very nice work now it’s perfect

---

<div class="post-metadata">

**Author:** ![Retetiba](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/retetiba/32/16426_2.png) [@Retetiba](https://community.homey.app/u/Retetiba)\
**Post date:** [May 7, 2020, 4:21pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/74 "2020-05-07T16:21:43Z")

</div>

Hi to all,

Hopefully some one can help me with the following. I have installed on Homey the mqtt broker and client. I have an AliExpress Tuya reflashed to Tasmota. With some testing I found some settings which are working in the Tasmota web interface.

When I install the unit in Homey via the Tasmota app, it finds the switch and allows switching. However it does not allow changing colors or brightness. To me I think this has to do with the settings in Tasmota. Does anyone know how to solve this?

I have the latest Homey software and mqtt client/broker installed. The switch has Tasmota 8.2

Thanks in advance.

Rene

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/8/c8738de6043d38d0e54fc0c0e249bde4e0e1dd0d.jpeg) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/2/32f7bbb0093756716d00e72812776da29d024d7c.jpeg)

---

<div class="post-metadata">

**Author:** ![pavlo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pavlo/32/17311_2.png) [@pavlo](https://community.homey.app/u/pavlo)\
**Post date:** [May 7, 2020, 6:01pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/75 "2020-05-07T18:01:01Z")

</div>

@Retetiba Sorry, color control not supported yet. Application supports now (of course if it supported by device) on/off, power monitoring and dimming. I have implemented but not released yet white temperature control and working now on color control. I hope I could finalize it in 2-3 weeks but it really depend if I would have free time so no promises. When beta version will be ready I will leave message in this topic.

---

<div class="post-metadata">

**Author:** ![Retetiba](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/retetiba/32/16426_2.png) [@Retetiba](https://community.homey.app/u/Retetiba)\
**Post date:** [May 8, 2020, 7:52am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/76 "2020-05-08T07:52:49Z")

</div>

@pavlo, Thank you for the feedback. I was not aware. If I can help in testing a beta version, I am available.

---

<div class="post-metadata">

**Author:** ![pavlo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pavlo/32/17311_2.png) [@pavlo](https://community.homey.app/u/pavlo)\
**Post date:** [May 10, 2020, 9:18am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/77 "2020-05-10T09:18:48Z")

</div>

Hi everybody, color light support here 🙂  
Version 0.6.0 under test now: [Tasmota MQTT 0.6.0 beta](https://homey.app/en-gb/app/com.paveld.tasmota/Tasmota-MQTT/test/)  
**If you already added your color light in the previous version, please, remove it and add again.**  
Keep in mind that there is a lot of different color lights that support color temperature and color with 2, 3, 4, and 5 channels control and I tested it only with Sonoff B1 bulb (5 channel) so it is possible that something is not working correctly. If you noticed some wrong behavior, please, write a bug report for me here.

---

<div class="post-metadata">

**Author:** ![PascalB](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PascalB](https://community.homey.app/u/PascalB)\
**Post date:** [May 19, 2020, 7:43pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/78 "2020-05-19T19:43:35Z")

</div>

Just added a Tasmotized Tuya power strip with 4 outlets and USB ports. Works great with Home Assistant, and also with your app. However, all 5 switches are in the same device, which is kind of a shame. I think we discussed this earlier and it had to do with the switching? Anyway, is it possible to add every switch from this strip as a separate device like in Home Assistant?

---

<div class="post-metadata">

**Author:** ![pavlo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pavlo/32/17311_2.png) [@pavlo](https://community.homey.app/u/pavlo)\
**Post date:** [May 20, 2020, 5:11am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/79 "2020-05-20T05:11:41Z")

</div>

Hi @PascalB,  
With the current version of the application, you can’t. But I also had this idea to add a power strip as separate switches. There is a couple of potential problems but it should be doable. Will try to implement this.

---

<div class="post-metadata">

**Author:** ![PascalB](https://avatars.discourse-cdn.com/v4/letter/p/dbc845/32.png) [@PascalB](https://community.homey.app/u/PascalB)\
**Post date:** [May 20, 2020, 8:36am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/80 "2020-05-20T08:36:47Z")

</div>

Awesome! 5 devices controllable for €25, doesn’t get much cheaper than that 😛

[Previous page](https://community.homey.app/t/app-pro-tasmota-mqtt/26164.md?page=3)

[Next page](https://community.homey.app/t/app-pro-tasmota-mqtt/26164.md?page=5)
