[Release] Tasmota Sonoff Hubitat Driver & Device Support

It is totally dependent on what driver you are using. I would not recommend using a driver that is paired to another firmware unless you are 100% sure it will work. In general, only use the driver that was designed for your firmware unless the developer has said it's okay (i.e. if they wrote both drivers).

If the firmware is the 6.7.1 released by @ericm or my 7.x firmware, my drivers will most likely work for those models. I’ve only tested them recently with 7.x, but there are no changes affecting thise particular type of devices in the communication with Hubitat.

NOW it's safe. :slight_smile: I've just seen so many people grab a driver from one post and expect it to work with firmware from another.

I have received my plugs and written drivers for them. Had to first figure out which chips were used and to which pins they went. A multimeter and reading on the chips was all I needed. If you figure out the pins a driver is quick and easy. In fact, my currently released drivers with a device Template with the correct pins should be all that is needed. Though I’d be happy to generate a driver if you have the template.

Which plugs? Can you link to them?

If they take Tasmota, they are ESP8266. I mean, what else does Tasmota work with? If they don't how will you flash the firmware to them? I'm a little confused by what you're saying. You just can't write a driver and have that work with any wifi plug out there.

I live in China and got these off Taobao, can't find them outside of China. They are Tuya based, I've not seen any similar to them in the device list for Tasmota. This is why I had to trace down which pins the HLW8012 chip and the LEDs were connected to. I find the easiest way to do so is by getting the specs of the chip, figuring out which pin(s) are used to communicate with it and then trace those pins back to the pins on the ESP8266 MCU.

See above for the chip-part. When it comes to Tasmota based devices, writing drivers which can handle all devices Tasmota can handle, is not at all difficult.
For example, at the moment any Wifi plug used for Energy Monitoring running the 6.7.1 or 7.x Tasmota firmware with Hubitat support really only need to make sure the correct Template is applied as well as possibly some other settings in Tasmota. I can add this template to the driver and generate a driver which automatically applies that Template. In fact, the driver I have already released allows you to paste in your own Template in Preferences to override the one used by the driver.
When it comes to other capabilities, such as temperature and humidity reading and other sensor data, that is only a matter of adding parsers and attributes for the data sent by Tasmota. A debug log using my EM Plug driver showing both manual and automatic updates from such a device is really all that is needed, as long as the correct Template and settings are applied to the Tasmota-based device to begin with.
If you would talk about writing drivers for any Wifi plug out there running any firmware, yes, that would be complicated and take a lot of time.

1 Like

I'm sorry but I still don't understand why you have to look at what chip the plug is using. They are all using ESP8266 of your can't use TASMOTA. Correct?

Oh this is cool. After looking at your drivers I get it. If I already know the template names, will your connect app find sonoff devices and allow you to apply templates to generic devices without having to create a new driver in Hubitat?

The main chip (MCU) is the ESP8266, many devices have secondary chips for things such as Temperature reading, Energy Monitoring, or even to turn on and off the relays and receive button presses (such as many of the Tuya wall switches). These are the chips you must know to which pins they are connected. Tasmota handles the communication with these secondary chips. Same goes for any LEDs and buttons on the devices, those you also need to know where they are connected to.

1 Like

The auto-discovery feature of Tasmota Connect is broken, but you can use it and input the IP of the device, then you can apply templates to "any" device. At least as long as you don't have special features needed, such as energy monitor or temperature monitor. For those, you would need to start with a generic driver for them. Some devices require much more than just a Template, such as Tuya wall switches using the TuyaMCU. But you can start with the Generic driver and go from there, please leave a comment in my 7.x release thread about which devices work with which driver and Template so that others can get the benefit as well.
Do note that in the non-generic drivers, there are sometimes additional settings being set in Tasmota. The Command functions of the Tasmota firmware are used frequently to set things like LedPower, LedState and setOption81. See here.


I'm using firmware 6.7.1 with eric's drivers. They are basic and mini devices, so they are fully compatible with them. I haven't tried yet your drivers with tasmota 7.x, but I'll have to do it and see if there are no more huge logs. Apart from this, they are working like a charm. No issues except those logs, and I don't find a way to cut them.
Thank you for your reply. I'll try your drivers and let you know.

Please do, looking forward to it, if you can't get the driver to be almost completely silent, do tell me and I'll make some adjustments, it should be as silent as it can. If you see messages you don't think you need to see, talk with me in the other thread and we'll see how to best resolve this.

As I worte in my last reply, I'm using 6.7.1 firmware released by ericm, so there sohuld be no problem with it. Anyway, I'll try 7.x firmware released by markus and see if it get's solved. Thank you.

Ok, thank you. See you there.

1 Like

I am a bit new to this and was wondering if anyone had any recommendations for a Driver for a Garage Door relay with a Reed sensor.
AGSHOME Smart Wi-Fi Garage Door Opener Remote - Flashed OTA to Tasmota 8.1.0

Configured with the following template
{"NAME":"Garage Opener","GPIO":[0,107,0,108,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":54}

When I connect directly to the device, everything works as expected with the sensor confirming the off and on position off the door.
However when trying to load it into hubitat I am having trouble finding a driver that reads that status of the sensor instead of the off or on button I clicked.

Any ideas are appreciated


1 Like

Welcome to the Hubitat forum!
That is a TuyaMCU-based device, and it might need some special handling in the driver. To know what is needed, check the console for the message when the door is opened/closed.
As for getting the status to Hubitat, with the original Tasmota firmware it needs to either be done by polling or via an MQTT server and gateway. There's a modified version of Tasmota for Hubitat which can get instant status updates. For TuyaMCU you need 7.x or 8.x, 6.7.1 doesn't work. Downgrading from 8.1.0 can be tricky, but it CAN be done. There's a Hubitat version for 8.1.0, but this has not been tested much since it was released yesterday.
For more information, check this thread:

Thanks! I will do some poking around with the MCU drives and see what I find.

Thanks again


Hey David,

I have a AGSHome Garage door and curious how you flashed this device with Tasmota. Can you retrace your steps please?

I tried using tuya-convert but either I'm doing something wrong or maybe you used something else possibly.