Tasmota Firmware on Sonoff using Brett Sheleski integration

No I thought I would keep it a secret :blush:

Yes of cause. But I need to write it up first because its a little bit of black magic at this stage so I need to get it clear in my head how it works and then I will provide instructions. I will let you know

Hey…i’ve seen people do that. You help them out for days and then they figure it out themselves and poof…gone.

yep so have I. its very annoying, I personally think the Tasmota Firmware is vastly Superior to anything else out there. so Im committed to getting it working properly and then letting everyone know how to utilise it. otherwise whats the point of putting all the effort in.

I have managed to get the Tasmota firmware on the Sonoff Bridge. Also integrated the Bridge in Smartthings and now I have indeed 16 devices in my list. I used a Kaku (Klik Aan Klik Uit) YCT-102 remote to ‘learn’ all Kaku power plugs. But all devices have 'button" as suffix, and not ‘switch’ as mentioned by Brett. The devices also act as a button which I can ‘Push’. So I have a seperate ‘push’ button for light on and a ‘push’ button for light off. That’s not what I want. I’d rather have a switch on/off.
I also can’t see these devices in the ‘Automation’ list. What did I wrong and what can I do about it?

By the way Brett: many Thanks for this!

Hi all. As promised here are my findings regarding the Brett Sheleski Sonoff handler using the Tasmota firmware. I have been discussing this with Brett over the last few days. Basically here is what you have to do.
Follow the implementation instructions as described here https://github.com/BrettSheleski/SmartThingsPublic/tree/master/devicetypes/BrettSheleski/tasmota.src
But something which is not clear is that you only need to add one Device that being for the Tasmota Device Handler, you don’t need to add a device for the Tasmota-Power Device Handler because once the handler starts working it will spawn the children buttons.
But here is where it gets a bit screwy. When I first installed it, the Tasmota Device turned up in my Smartthings app with all null values. I pressed refresh 6 or 7 times, but there was no change. It didn’t even show up in the log window which was unusual. After chatting to Brett, he suggested that I only use the IP address in the properties without any header or trailing slashes (http://) I also used the username admin and password that I configured in the configure other option of the Tasmota Firmware.
Once you have values appearing in the app the next thing you have to do it go back into the “My Device Handlers” and then I select the Tasmota handler to enter into the code window. I then select the Simulator option in the top right-hand corner of the IDE. Set my Home location, Selected the device as virtual and hit install. This will cause the Tasmota handler to spawn its children (it should not be this way but it is. Brett is looking into it).
But I am pretty unimpressed at the performance. It’s very slow and Brett told me that if the device has a state change triggered by something else other than Smarthings then Smarthings won’t know about it. He is working on a Node-Red implementation with an app to solve this. But this got me thinking, perhaps we are going about this in an overly complicated manner.
The Tasmotta Firmware is very highly geared towards MQTT so why fight that. I have Node-Red running in my environment and I can pretty esily install an MQTT broker to integrate Node-Red to the Tasmota. Then what I am going to attempt to do it is get SmartThings to talk to Node-Red via Webservices to triger an MQTT event. This solution should also work with Home Assitant as well given that a lot of HA users also use Node red because the Automation is pretty clunky in HA. If it works I will share with the world. If it dosnt I will disappear into obscurity.
I will let you know how it goes.

I thought you said that the Tasmotta firmware was far superior? @erocm1231 firmware is a lot better than this, especially for the sonoff basic. If you trigger with GPIO14, it show the update in ST. Works a lot better IMHO. Here it is if you want to try it:

1 Like

Thanks Ryan, appreciate your opinion. The trouble is with this firmware if you have a freshly minted Sonoff that has the latest factory firmware the @erocm1231 firmware wont work. At least I haven’t had any success getting it to load. After loading the SSID that is supposed to show up doesn’t so you cant finish the job. I have never had any difficulty at all with Tasmota, it just works straight away and the device performs as it should. The Tasmotta firmware is also a far more complete framework and caters for pretty much every scenario not just Smartthings, so if you want to do some really special things like for example use a Sonoff as a proximity sensor you can. So I don’t think that the gap here is Tasmotta, its more likely that the Handler is still buggy.

Yeah…but we are using SmartThings…that’s why we’re on the SmartThings forum. This isn’t the Sonoff forum. LOL The Tasmota firmware sounds like it works great with MQTT but unfortunately that’s not supported natively in ST yet. So, I’ll stick with what I got for now.

Brand new sonoff devices will flash fine, you just need to use the ESP download tool, ensure it is set to 8mbit and dout as the flash interface.

@Ryan780 I’ve already modified Sonoff Basic with wired magnetic sensor connected to GPIO14 + GND and resistor 4,7k between 3,3v and DATA
I would like to be able to use it as momentary switch with door open/close status, something similar like Mimolite

Is it possible to achieve it with ESP firmware and following this instruction: [RELEASE] Sonoff, Sonoff TH, S20, Dual, 4CH, POW, & Touch Device Handler & SmartApp ($5 & $10 Smart Switches)

Where I can configure GPIO14 to give me back status Open/Close ?

Device Handler for Mimolite is here: https://github.com/fortrezz/smartthings
Documentation: http://www.homecontrols.com/homecontrols/products/pdfs/FZ-FortrezZ/FZMIMO2US-Guide-with-SmartThings.pdf

sonoff%20DH

or even to controll two garage doors

In the case of the Open close sensor, to control a garage door, you wouldn’t want the contact sensor to control the door opening. If reports if the door is open. Also, I don’t think the Sonoff will work for your use. The Sonoff is a 120v AC device and your garage door control circuit is 12v DC.

The build is similar to this instructable


or

I’m using my GPIO14 with wired magnetic sensor connected.
With Tasmota firmware I was able to successfully use it with Home Assistance, where I was able to see Open/Close status.
This modification is very popular in many platform OpenHAB, Domoticz, Supla.
The problem here is only with the Device Handler. Will be great if someone can help with modification of current code, and use something similar to “Mimolite” which is basically working on similar statuses.
I would like to have this in configured in SmartThings :slight_smile:

Sorry, i have no idea.

One quick workaround I’ve found is to first flash with Tasmota, then use its web interface to update the firmware to Eric Maycock (@erom1231) version located here https://github.com/erocm123/SmartThingsPublic/tree/master/devicetypes/erocm123/sonoff-ifan02-wifi-controller.src

Here’s the command I use to flash with the default tasmota sonoff.bin firware
$ esptool.py --port /dev/tty.SLAB_USBtoUART --baud 115200 write_flash 0x0
/Users/asub/Downloads/sonoff.bin
esptool.py v2.5.1
Serial port /dev/tty.SLAB_USBtoUART
Connecting…
Detecting chip type… ESP8266
Chip is ESP8285
Features: WiFi, Embedded Flash
MAC: dc:4f:22:db:a3:97
Uploading stub…
Running stub…
Stub running…
Configuring flash size…
Auto-detected Flash size: 1MB
Compressed 534032 bytes to 365310…
Wrote 534032 bytes (365310 compressed) at 0x00000000 in 32.2 seconds (effective 132.6 kbit/s)…
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Like others have said, when you flash with @erom1231 firmware it doesn’t provide the wifi access point to join. If I flash with tasmota first then use tasmota to update firmware and then use @erom1231 firmware, when it reboots I see the ap finally. No need to push and buttons, just wait a few minutes after the first tasmota flash to see the Sonoff gateway. Also be sure to powercycle after flashing

Also using the cp2102, and a new touchbar mac I didn’t require external usb power. The usb c and the ftdi provided plenty.

1 Like

Hello Sir could you send me tutorial for do that, i want my sonoff bridge can integrating with smarthing app, thank you

I sugest going a different road. Use matter and home assistant integration to Smarthings

Thank you Sir for your Advice

Is this no longer working or outdated . I have 15 tasmota sonoffs setup( all models) in smarthings for over a year ago all working great. I tried to setup a new sonoff touch 3way last week and it does not spawn any dependents in the app . Only the parent device shows up.

Well, do you have a driver that supports the creation of Children? I don’t believe this will support that as this driver is for a basic.

I found it he update his device handler 28 days ago for tasmota 7.0 but used the same name so when i looked at updates in repo it didnt find it. Up dated manualy and all is good.

1 Like