# \[APP\]\[Pro\] Tasmota MQTT **URL:** \ **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:** 21
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [June 7, 2023, 10:39am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/405 "2023-06-07T10:39:54Z")
> [@Martin072](#): > > Would be great if there would be an option to provide a custom topic that could be configured, i.e. “home/tasmota/” for me The app is really complex. I’m currently trying to change it so it supports it. But I’m not sure if it breaks something down the road. I’ll tag you once I get a working version. Edit: So the app works using the topic as an identifier. And it will be really hard to find a way to predict the right topic if the topic is unknown. E.g. These are the topics with prefixes ```auto home/tasmota/tele/steckdose02/STATE tele/steckdose02/STATE steckdose02/tele/STATE ``` And it will be really hard to make a algorithm to filter out everything “unnecessary”. Currently, it works with a three-part topic. And it can switch topic and prefix to look what is the a known topic (tele, stat) and take the other one as the device name | topic | prefix | messageTyp | | --- | --- | --- | | tele | steckdose02 | STATE | | stat | steckdose02 | STATE | | steckdose02 | tele | STATE → would be switched to tele, steckdose, STATE | And I can’t find a way without user input to filter e.g. /home/tasmota/… or everything else. Tl;dr: I can’t find a way to make it work in the current state of the app. ---
**Author:** ![Martin072](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin072/32/70637_2.png) [@Martin072](https://community.homey.app/u/Martin072)\ **Post date:** [June 7, 2023, 11:00am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/406 "2023-06-07T11:00:01Z")
Hmm. This part: (line 252) ```auto for (let topic in this.topics) { this.subscribeTopic(this.topics[topic] + "/#"); this.subscribeTopic("+/" + this.topics[topic] + "/#"); } ``` Subscribes to the topics, then line 176: ```auto this.topics = ["stat", "tele"]; ``` Seem to define the topic. Would it not be that easy to add it before the topics, i.e (for example). this.topics = [“home/tasmota/stat”, “home/tasmota/tele”]; I did try something different, but no joy, and not sure why… When I receive a tasmota MQTT message, I re-publish it without the “home/tasmota/” so it looks exactly as a default tasmota device, however, homey does not discover the devices… ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [June 7, 2023, 11:05am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/407 "2023-06-07T11:05:58Z")
That is not the problem of the app. It’s on the deeper end. Since the app generates everything dynamically what the device can do and can’t do, it’s really complex. And I would to change the app on the ground up how it works. And without knowing the subject that well I will not rewrite this app. There are around 6k devices using this app with the default topic/prefix combo. So it easiest way would be to change your topics to the default. > > ---
**Author:** ![Martin072](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin072/32/70637_2.png) [@Martin072](https://community.homey.app/u/Martin072)\ **Post date:** [June 7, 2023, 11:31am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/408 "2023-06-07T11:31:42Z")
Ok, not ideal situation, as I will need to reprogram all my custom scripts and that would take forever. But I will have a look what I can do myself I am new to homey pro, I guess one cannot alter the program on the Homey Pro device to play around with it? ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [June 7, 2023, 11:46am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/409 "2023-06-07T11:46:53Z")
> [@Martin072](#): > > I am new to homey pro, I guess one cannot alter the program on the Homey Pro device to play around with it? You can, spkesDE just shared with you GitHUB links, you can download then and install via CLI (search for CLI install). Still I would say, modifying your scripts might be easier, or ? 😉 ---
**Author:** ![Martin072](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin072/32/70637_2.png) [@Martin072](https://community.homey.app/u/Martin072)\ **Post date:** [June 7, 2023, 4:35pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/410 "2023-06-07T16:35:25Z")
I guess yes.Will see how much work is involved. Thanks for all the help so far ---
**Author:** ![Shiki](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@Shiki](https://community.homey.app/u/Shiki)\ **Post date:** [June 8, 2023, 3:24am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/411 "2023-06-08T03:24:05Z")
Thanks, I overlook on the information given. Yes, it will give the updated on each type of changed value. ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [June 16, 2023, 2:49pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/412 "2023-06-16T14:49:30Z")
Hi @spkesDE , I know you will be not happy if I ask, but I will try 🙂 As my Sonoff R2 POW died, I ordered replacement Sonoff Dual R3 v2 (R2 is EOL). Flashed Tasmota on it, seeing a lot of values but unfortunately not in Homey. Do you think it could be “easily” extended by additional “sensors” ? **Homey** - _eg. missing current, active power, apparent and reactive power (at least current of active power would be useful)_ _note : might be pain, as I see it’s reported per switch ;-(_ ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/0/104b67e6ef8b68cf6b6cd4219d6a144d60f4b78b.png) ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/1/417c97a2832c0d218a027a06fb86604c2175a9ad.png) **Tasmota web** ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/6/e648cc77f856ff2e646aa9f21bd4ae8c14aa1a2d.png) Worst case I would setup MQTT device or maybe DC device and configure it via mqtt but if I could avoid such potential point of failure, would be great. If anyhow useful, I sent diag - fe782aaa-0aef-499c-ad61-66a4af48d060 _MQTT Broker packet details_ `Packet published {"Time":"2023-06-16T15:59:38","Switch1":"ON","Switch2":"ON","ENERGY":{"TotalStartTime":"1970-01-01T00:00:00","Total":0.086,"Yesterday":0.000,"Today":0.086,"Period":[2,0],"Power":[19,0],"ApparentPower":[57,0],"ReactivePower":[54,0],"Factor":[0.33,0.00],"Voltage":244,"Current":[0.235,0.000],"BL09XX":{"Temperature":44.2}},"TempUnit":"C"}` Thank you. 🥺 🥺 🥺 ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [June 16, 2023, 5:32pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/413 "2023-06-16T17:32:23Z")
Once I find time, I can add these. Not sure how to manage dual socket ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [June 16, 2023, 5:49pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/414 "2023-06-16T17:49:12Z")
> [@spkesDE](#): > > Not sure how to manage dual socket Thank you, appreciated 🙂 Just clarification, dual socket is recognized (switch1, switch2), just not the sensor values on those dual sockets - Power":[19,0],“ApparentPower”:[57,0],“ReactivePower”:[54,0],“Factor”:[0.33,0.00] ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [June 18, 2023, 7:22pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/415 "2023-06-18T19:22:01Z")
In case someone will be looking for some solution, in case you have some Tasmota device which provides some sensor data which is not supported eg. by given implementation, seems Device Capabilities can provide easily workaround. Like in case of Dual R3, parsing JSON MQTT message is working quite well… _Not full example just to get idea how to parse JSON and path (I didn’t know myself)._ ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/a/aa7b7f01f0fe6efd8127392ffdf7e5c5c6007431.png) ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/3/734ce4cf19ac3ce85cb4cdc279757bdd35d6b6d4.png) ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/0/303d170c2fda1bc67ea52fa4cb5db9b93096fb94.png) And resulting device which works aside of Tasmota one : ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/c/cc635b9361d29601bda40ee4212ab3f7f881ae1a.png) ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/f/cf10f5c52a1edfbc3aad9d8ed4ed8ae7ecd778c8.png) Eg. Voltage and Temperature is taken directly from Tasmota implementation (means no need to include them into flows, parsing MQTT JSON etc.) : ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/9/a95108eeb20c53ab873664b2207c00ee501f0832.png) ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/9/69a72d87f572ea533f09632ce2ecabbf7d024b36.png) ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/3/33782f7e6752c5a462683fce3d13266aee68fb05.png) ---
**Author:** ![Adam\_P](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adam_p/32/71668_2.png) [@Adam\_P](https://community.homey.app/u/Adam_P)\ **Post date:** [June 22, 2023, 7:27am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/416 "2023-06-22T07:27:41Z")
Hello, please i have a 4ch relay and would like to named the channels, is it possible to do it? Or can i add this switch separately? Thank you ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [June 22, 2023, 7:55am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/417 "2023-06-22T07:55:05Z")
You can have workaround using Device capabilities app, like I described above, it’s similar concept ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [July 22, 2023, 5:23pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/419 "2023-07-22T17:23:23Z")
Hey @Adam_P, I’m not sure how I could implement this. I think this is not possible with the current way how this apps and the homey sdk works. > [@Sharkys](#): > > Do you think it could be “easily” extended by additional “sensors” ? I have this on my to-do list. I didn’t forget your feature request @Sharkys, as my favorite app breaker 😆 But I really didn’t find any time nor motivation for this, since this app still requires a ton of work to meet my standards. The Codebase is still a freaking mess… ---
**Author:** ![C\_Brade](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/c_brade/32/12394_2.png) [@C\_Brade](https://community.homey.app/u/C_Brade)\ **Post date:** [July 27, 2023, 8:14am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/424 "2023-07-27T08:14:29Z")
hi @spkesDE i have a problem while adding a tasmoto rgb led. I can add any device I want except this Athom GU10 lamp. when the config is like this: | GPIO # | Component | | --- | --- | | GPIO00 | None | | GPIO01 | None | | GPIO02 | None | | GPIO03 | None | | GPIO04 | PWM 1 | | GPIO05 | PWM 4 | | GPIO09 | None | | GPIO10 | None | | GPIO12 | PWM 2 | | GPIO13 | PWM 5 | | GPIO14 | PWM 3 | | GPIO15 | None | | GPIO16 | None | | GPIO17 | None | it is not possible to add the lamp. when I remove now one GPIO config and set it to none, doesn’t matter which one, it will be found. Do you have a solution for my problem? > **[Athom 4.5W 300lm RGBCCT Bulb (LB10-5W-TAS) Configuration for Tasmota](https://templates.blakadder.com/athom_LB10-5W-TAS.html)** > > Configure your smart RGB colorcolor temperature adjustable bulb to work with Tasmota open source firmware. it is this kind of LED. Thanks a lot on my homey pro 2019, when I added similar lamps a year ago, in the past everything was working fine with these kind of bulbs. i also tried older versions of tasmota (tested 10-13) but that didn’t effect the pairing process… ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [July 27, 2023, 5:55pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/425 "2023-07-27T17:55:42Z")
Could you restart the app, try to pair the bulb with and without the gpio config and then send a diagnostics report? ---
**Author:** ![PjO](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pjo/32/8517_2.png) [@PjO](https://community.homey.app/u/PjO)\ **Post date:** [August 12, 2023, 7:53pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/426 "2023-08-12T19:53:53Z")
Hi, Im switching over to the Tasmota MQTT app for all my sonoff devices which I flashed to TASMOTA. Everything was working quite nice and fast, however **I don’t know how to get the temperature reading** from a temp sensor which I connected to SONOFF TH (10/16) module. I can see it comming in, in the MQTT logs: ```auto 20230812-19:49:32 received '{"Time":"2023-08-12T20:49:32","DS18B20":{"Temperature":23.9},"TempUnit":"C"}' on 'tele/hottubpomp/SENSOR' ``` The device works as a switch, so can turn the hottubpomp on/off via Homey, but cannot do anything with the measured temperature, since its not available. What am I doing wrong? Thnx ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [August 13, 2023, 12:26pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/427 "2023-08-13T12:26:06Z")
I really don’t know why it won’t add the Sensor to the device. Could you install the latest test version, re-add the device, and send me a diagnostics report? > **[Tasmota MQTT](https://homey.app/en-us/app/com.paveld.tasmota/Tasmota-MQTT/)** > > Adding support for tasmota devices through MQTT ---
**Author:** ![PjO](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pjo/32/8517_2.png) [@PjO](https://community.homey.app/u/PjO)\ **Post date:** [August 14, 2023, 8:16pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/428 "2023-08-14T20:16:26Z")
Thanks that test version worked apparently! Now figuring out the temperature values in combination with the flows. Thanks again. ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [September 4, 2023, 3:38pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/429 "2023-09-04T15:38:37Z")
@spkesDE would you know please, why minimum refresh interval is set to 3 min max? I wonder why this restriction (I know it’s not set by you but previous author, just wondering). Thank you [Previous page](https://community.homey.app/t/app-pro-tasmota-mqtt/26164.md?page=20) [Next page](https://community.homey.app/t/app-pro-tasmota-mqtt/26164.md?page=22)