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

[j2hdwd]

Hi @markus, I'm interested in getting lumary LED strip which is listed in "supported" list.

Tasmota Device Templates Repository

just to confirm that it means I can tuya-convert it? do I use the same bin files as I have used on my power plugs?

then after that, as long as I install and choose the correct drivers, it should just work?

thanks

[markus]

@j2hdwd

I'm interested in getting lumary LED strip which is listed in "supported" list.

Yes, that one should work with the closed beta driver. I'll add it to the configuration list during the weekend.

[j2hdwd]

Awesome! thanks Markus. Oh, and hope you're keeping safe!

[markus]

@j2hdwd

Awesome! thanks Markus

You're welcome! It has been added. All good, Shanghai is well organized, I can't speak for the rest of China, but here it's very good considering the circumstances.

[peterkant]

Hi Markus, this is such a great addition to the HE platform!! Congrats!

I had a bunch of sonoff minis already flashed and working perfectly, having the ability to use wifi inexpensive switches within HE is just fantastic. I also bought a few of these:

Tasmota Device Templates Repository

They are both a plug and an RGB light. I could flash them to 8.1 without any problems. Within Hubitat, the "Tasmota generic wifi switch/plug" driver woks fine in order to control the plug itself, but I can't find a way to control de RGB Led in the device.

I guess I should have a parent driver for the plug/switch and a child to control the light, but I can't figure it out. This is how it looks if I access the device directly:

And the config I used after flashing:

Any ideas on how to solve this?

Thanks!

[markus]

@peterkant

Any ideas on how to solve this?

The unreleased Closed Beta driver solves this issue. It would be able to handle this device. If you want access, please PM me. The only thing missing with the Closed Beta driver is good documentation.

I'm glad you like my driver and that it comes to good use! Always happy to hear that!

[peterkant]

Great thanks!

[markus]

@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]

@markus

EDIT: Found one on Taobao and ordered it, but they won't ship for another week or so due to the Chinese New Year. At least... But when they do ship it will normally only take 2-3 days.

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

[markus]

@bigrizz

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

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]

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]

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]

@j2hdwd

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

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]

@bigrizz

I might connect mine up and see how it works in Tuya first.

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

[aahanmohan]

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]

Much appreciated!!!!

[markus]

@aahanmohan

would the distance sensor firmware work with them?

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

Tasmota Supported Devices Repository

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]

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]

@aahanmohan

Thanks for responding so quickly! This is the one

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]

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!