[DEPRECATED] Tasmota 7.x/8.x firmware for Hubitat + Tuya, Sonoff and other drivers

peterkant · April 5, 2020, 1:08am

Great thanks!

markus · April 6, 2020, 1:59am

markus:

Why this driver?
There's a lot of confusion on which Tasmota driver to use with HE, for some reason there are those that have an issue with using a modified version of Tasmota. The only change in my Tasmota firmware is adding a way to push data to HE without using Polling (known to be a bad idea with HE and is NOT real-time) or Rules in Tasmota (doesn't run as fast as C++ code and is MUCH slower than this firmware). Even the version using Rules is using polling for certain things. There's also routes using MQTT+Node-RED (or MQTT+something else), this is an advanced solution that is meant for those that truly want maximum flexibility with the trade-off of more work and the need to understand more types of technologies.
My combination of firmware+driver doesn't use polling and is as optimized as can be.
With this said, if you're new to using Tasmota, use this driver . If you for some reason don't want to use a non-original release of Tasmota, understand the limitations of other solutions and live with those.
NO functionality is removed from Tasmota in this custom firmware, nor is this adding a measurable overhead. The code added basically takes the MQTT JSON data and sends it over http to HE. That is all.

Closed Beta driver
There is a new driver in Closed Beta, it remains there because documentation isn't ready, apart form that it is ready for production use. It is much more optimized and handles many more devices in a way which is much easier to install and use. Basically it is ONE parent driver and the child drivers and devices are auto-detected and auto-installed for most types of devices and configurations. If you want to try it and think you can do without much documentation, send me a PM.

Updated the first post to make it clear what is what, it can be confusing to know how to get Tasmota working and I hope this at least helps with choosing the driver. I understand there are those that don't want to use my custom firmware for some reason, if that is the case, then don't, as described above, there are alternatives. My hope is that anyone publishing alternatives explains the differences, trade-offs and reasoning why their way is the way to go and how it is accomplished. It shouldn't be needed to read the source code to understand the basic differences and trade-offs being made. I've explained the approach used by my firmware+driver before, but now it's in the first post and I hope it is now clear.

I don't mean to offend anyone, but please, when posting a driver for something that already has an actively maintained driver, make sure to explain clearly the how and why, it's hard enough for most to know what to choose.

bigrizz · April 6, 2020, 7:01am

Hi Markus. Did you ever get that 2-channel dimmer delivered? Did you make it work with your new driver by chance?

markus · April 6, 2020, 7:02am

I did get it, I've not had time to even connect it yet, life has been in the way. Sorry, it takes longer than I had expected.

bigrizz · April 6, 2020, 7:05am

No worries at all. I understand how that happens. I might connect mine up and see how it works in Tuya first. I was holding off until you had a chance to play with it. No hurry for me.

j2hdwd · April 8, 2020, 9:07pm

Hi @markus, how's it going? are you okay adding this one too? DD001-MINI(G)-IR-V08 LED Controller
(If it's not already there)

so just so I'm clear, the drivers for the devices are added to your new driver? (the parent child one)

markus · April 10, 2020, 12:49am

I'll add it, looking at the template there is no support for an IR Remote, even though the picture shows one. The IR Remote is not yet supported in the driver anyway, so no problem.
And yes, it's for the new driver, so future requests like this, please post in that thread.

markus · April 10, 2020, 12:50am

Do so, I'll look at this soon I hope, just been a crazy last few weeks.

aahanmohan · April 10, 2020, 9:45am

Hi Markus,
Thank you so much for sharing these! I have 2 wifi based smartlife/tuya contact sensors - would the distance sensor firmware work with them? I'm not too sure about which one I ought to use and I don't want to brick them. Thank you!

j2hdwd · April 10, 2020, 2:00pm

Much appreciated!!!!

markus · April 10, 2020, 4:31pm

Do you have a link to the device template from here? :

You probably will need my Closed Beta driver for these. The firmware to use is probably the standard Hubitat Tasmota build, but I'd need to know exactly what device it is to tell you for sure.

aahanmohan · April 10, 2020, 5:52pm

Hi Markus,
Thanks for responding so quickly! This is the one

Fingers crossed! I absolutely hate the latency over wifi and IFTTT. Really wish I'd just bought more Zigbee ones. They weren't even that much more expensive than this. I just figured I'd try these out because Tuya plugs etc hadn't been too bad. Little did I know.

markus · April 10, 2020, 6:02pm

Both good and bad news, yes, this can be done, but expect 4s delays, maybe less, but it will not be as fast as a Zigbee sensor. Reading the instructions it does look like tuya-convert could be a very hard thing to do, probably best to flash over serial. As far as drivers go, there would be no support for the battery status, but if you do flash it you can use my Closed Beta driver to have it show as a Contact Sensor without having to use a virtual device and RM. PM if you want access to the Closed Beta.

aahanmohan · April 10, 2020, 6:07pm

Hi Markus,
4s is about a fifth of what I'm current dealing with so this seems like a godsent as far as I'm concerned! PMing you now - thank you so much!

scottwolf · April 10, 2020, 8:46pm

Not seeing a way to PM you, potentially as I am a new user. I have a Tuya garage door opener I'd like to try out that has Tasmota flashed, and it sounds like your beta driver is more appropriate when attempting to support non-standard devices.

j2hdwd · April 10, 2020, 9:46pm

OK will post it on a diff thread. And yes, I won't be using the IR anyway. Cheers bud.

markus · April 11, 2020, 2:12am

Yes, since you're new you can't PM, I'll add you to the Closed Beta thread, the only thing missing for the version of the driver is good documentation, please read through the thread to get a good understanding on how it works.
Also, post a link to your device in the Closed Beta thread, most informative would be if you can find it here:

Ok, please post in the Closed Beta thread

DementedDragon · April 13, 2020, 11:02pm

Ditto that markus

yototogblo · April 16, 2020, 6:45pm

I have 2 KMC 4 Power Monitor Plugs. I flashed Tasmota Hubitat v8.1.0 (followed the guidelines so flashed the official tasmota first, then minimal and then the hubitat version). The plugs are connected to my WiFi and the hub recognized them successfully. However, I can no longer control the plugs even manually.

When I send a command via Hubitat, the LED blinks blue and the WebUI console displays "RSL: stat/tasmota/RESULT = {"Command":"Error"}". Trying to turn the power on manually does nothing.

Please any idea how I can get this working?

Thanks

yototogblo · April 16, 2020, 7:47pm

Ok, really weird; I did a "reset 5" and I can now control only the middle plug via Hubitat and the WebUI. However, the other 2 plugs can't be controlled.

Also, manual control still doesn't work and the switch is inverted both in the WebUI and in HE (says "on" when the middle relay is "off" and "off" when middle relay is "on"). Any ideas how to fix pls?

P.S.
Hitting configure did the trick! Working fine now. Thanks much for this driver!