WARNING: Flashing your device with a 3rd party firmware MAY cause your device to not boot again. To fix this you MAY have to flash through TTL. Don't be in a rush!
Auto-detection of device features and an all new optimized App! Also a whole lot more.
This driver has been in closed beta since February and has been stable since then. The device support is even greater than before and even so, it is now much easier to know what to install.
Which Devices Work?
Most devices that can run Tasmota work. Some may still need some special care, but most work as long as the template is correct. Read the docs for further information.
Read the documentation, if there are issues, post in THIS thread.
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.
A big THANK YOU to all the Beta testers and an even bigger thank you to those that wrote the documentation: @garyjmilne, @sebastien and @jchurch (also a big thank you to those that have promised to add more to the docs when time allows, there is still plenty to do!)