[RELEASE] Tasmota (Connect) for Sonoff, Tuya, SmartLife & other ESP8266 devices)

Tap & hold for 5 seconds on the “About SmartThings” box to enable “Developer mode”

FIrst - thank you for your replies and suggestions - it’s much appreciated!

I’m unable to enable developer mode following the directions given. No matter how long I press and hold “about SmartThings” nothing changes and no “developer mode” option appears.

I’ve rebooted the phone and tried multiple times. I do see the manually installed smartapp (named Tasmota (Connect)2) now appear in the “Add SmartApp” menu on my phone, but when I tap it the menu disappears and the smartapp does not show in my list. I can do this several times with not changes.

Super odd as I’ve added SmartApps before, again thanks for the patience and any advice or direction…

UPDATE: I was able to add the smartapp Tasmota (Connect) with an android tablet with no issues. No idea why I couldn’t do this with my IOS device.

I added the SmartApp then added the device. I have a Sonoff TH16 and in SmartThings when I added it I got two devices, one for the switch (open/close) and one for the temp sensor. The open/close does not activate the Sonoff device, and the temperature reading is not showing in the app. When I log directly into the flashed device via a webpage I can open/close and see the temperature.

Thoughts on why SmartThings doesn’t seem to connect to it?

Guys - I think this is my fault, I’m seeing there is more setup needed in the smartapp. Sorry for filling up this thread, I’ll do more reading and try to resolve this myself (RTFM).

Thanks again for your work on this!

UPDATE: Everything is working! I don’t know why the SmartThings app for IOS won’t work, but everything “just worked” in the android app (Version, including the option to enable Developer mode (though I didn’t need it). Also noticed that Android app shows Fahrenheit while IOS shows Celsius, but the number is Fahrenheit (so it’s not a conversion, it’s just the wrong letter!). I’m so glad I have Android devices I could use, I’ve included this here just in case someone else has these issues with IOS and this helps in some way.

This is probably a dumb question, sorry about that but what are the benefits of flashing Tasmota on an ESP8266 or ESP8285 Wifi device to be able to control it with Smartthings? It is my understanding that the main reason to “Tasmotize” a device is to have full local control vs cloud based solutions. However, isn’t the SmartApp for Tasmota (Connect) cloud based? Or am I missing something and the “tasmotized” devices can indeed work locally with smartthings by this solution?

Thank you very much for your replies, are very appreciated!

A question: in the Smarthtings App, when I pull up the Tasmota (Connect) smartapp, there is a setting called ‘Device Health Check’ that defaults to 5 minutes.

I can’t find any documentation for this setting in this thread or in the GitHub readme. The groovy file simply says “Check in on device health every so often” but doesn’t really say what this does.
Is it how often the smartapp polls devices? Any implication to setting it to 1 min rather than the default 5 min?

This allows all Tasmota devices to be under SmartThings app and the communication is between SmartThings Hub/Cloud and Tasmota local/LAN devices.

If real-time status is working fine for you, then is fine to keep it to the default 5 min.

It is the frequency of the hub pinging all the Tasmota devices for status.

If real-time status is working fine for you, then is fine to keep it to the default 5 min.

I’m actually trying to solve the following: I have a dual plug switch running Tasmota, and I have a smartthings automation such that when ST senses that switch 1 is in use (measured by power draw), it turns on switch 2. And the reverse: when switch 1’s power draw goes low, it turns off switch 2.

This was working fine for the past year, but sometime in the past few weeks, something changed such that there is an extremely noticeable delay (as in multiple minutes) in Smarthings noticing that switch 1’s power draw has increase and thus triggering the power on to switch 2. I doubled checked via the device’s tasmota web page that the power draw is indeed being reported correctly, but for some reason smartthings is not picking it up for many minutes.

I have no idea why something that was previously working fine has recently started lagging like this but I assume it’s due to the many smartthings backend changes that have been going on.

Thus, I’m trying to see if there’s anything I can tweak or tune to try to increase the response time of my automation and reduce the lag.

Check the Tasmota device console: You should find similar to these. If isn’t, then something is not right, and could be tricky to debug…

05:25:46.239 RUL: TELE-ENERGY#TOTAL performs "WebSend [] /?json={"StatusSNS":{"ENERGY":{"Total":"264.039"}}}"
05:25:46.800 RSL: stat/tasmota/RESULT = {"WebSend":"Done"}
05:25:46.816 RUL: TELE-ENERGY#VOLTAGE performs "WebSend [] /?json={"StatusSNS":{"ENERGY":{"Voltage":"246"}}}"
05:25:47.380 RSL: stat/tasmota/RESULT = {"WebSend":"Done"}
05:25:47.397 RUL: TELE-ENERGY#CURRENT performs "WebSend [] /?json={"StatusSNS":{"ENERGY":{"Current":"0.105"}}}"
05:25:47.963 RSL: stat/tasmota/RESULT = {"WebSend":"Done"}

Thanks for the reply @hongtat . So if my internet connection fails then I wouldn’t be able to control the Tasmota devices via Smartthings, right?


You wouldn’t be able to control Tasmota devices via ST, if internet connection fails.

this is only for wifi device?

i have Moes wall switch but is zigbee so not luck here, i am correct?

Yes. This is for wifi ESP8266 devices.

1 Like

Can you help us with zigbee version of switch

We will donate the developer with solutuin 30€ until now

Please if you have time check this thread