@markus It doesn’t show a state change
Do you have the correct firmware, do you see the correct state on the Tasmota device webserver (not HE)? Did you press Configure in the Parent device?
Yes, yes, and yes
Logs, screenshots, the more information the better.
The only difference is that in the aapp, the non working devices say timeout while the working device says availible.
I have this same dimmer and I am so lost. I am new to Hubitat. Where do I enter these commands? In the HE web console or on the dimmer's web console? Or somewhere else? I don't even know if I really have the right firmware.
I used this guide to install Tasmota from a Antix Linux (debian based) laptop and it worked perfect. Flashing any Smart bulb, plug or switch with Tuya-Convert
I have Tasmota 8.1.0.2 installed at the end of this process. The dimmer switch is up on the WiFi.
I then used this guide to install the software/driver on the HE and everything seems fine:
I used the manual install process to add the dimmer switch by entering the IP. It found the parent device, but no child devices.
I found this thread that lists a number of strings to make it work but I don't know where to put these:
I can RTFM if someone points me in the right direction here.
And also, do I need a different Tasmota firmware to work with this driver/software? I see references to T4HE 8.x.x in the thread here. so maybe my 8.1.0.2 is not good.
This is all new to me btw. The HE, Tasmota, drivers, etc.
Help!
If the IPs are correct the issue is probably on your LAN. It can also be temporary that it reports like this. Is it still this way?
Install the Minimal build of 8.1.0.2 (on the Tasmota web page, go to "http://ip-of-your-tasmota-device") and then from that one upgrade to my version of 8.3.1. If you have the right version of the firmware it will say "Tasmota 8.3.1 by Theo Arends & for Hubitat by markus-li" at the bottom. Once you have my firmware, go to the "Console" on that Tasmota web page and type in "reset 5". Wait for it to reboot.
If you update to my latest Beta driver for the Parent Driver from here I've added the Feit Dimmer to the dropdown selection list and it will issue all the correct commands automatically. Just select it, Save Preferences and click Configure on the Device Page for the Parent Device in HE.
The Tasmota device doesn't have the correct settings applied so the Parent driver doesn't know what it is yet.
I hope this helps.
1 Like
Good news. I have the HE Tasmota 8.3.1 loaded, and, I upgraded the Hubitat to the development version of the driver and app, and I can see the dimmer now with the child device.
However, it's not working. I first tried to control it from HE but then when that didn't work, I tried it from the Web interface on the dimmer and it didn't work there either. If it's not working on the dimmer itself via software there's no way it would work on the HE.
I went through the following settings from another thread but that didn't help either.
Console: reset 5
WebGUi: Configure->Configure Module->Module Type=Tuya MCU (54)
Console: TuyaMCU 21,2
Console: TuyaMCU 11,1
Console: DimmerRange 10,1000
WebGUI: Configure->Configure Other->Friendly Name set
Power Cycle
Settings on the device (IP addreses are faked, SSID redacted)
Tuya MCU Module
TasmotaHubitat
| Program Version | 8.3.1(tasmota-he) |
|---|---|
| Build Date & Time | 2020-07-04T09:52:26 |
| Core/SDK Version | 2_7_1/2.2.2-dev(38a443e) |
| Uptime | 0T00:07:59 |
| Flash write Count | 25 at 0xFB000 |
| Boot Count | 7 |
| Restart Reason | Software/System restart |
| Friendly Name 1 | Living Room Switch |
| AP1 SSId (RSSI) | redacted (92%, -54 dBm) |
| Hostname | tasmota_28FD51-7505 |
| IP Address | 10.1.1.228 |
| Gateway | 10.1.1.254 |
| Subnet Mask | 255.255.255.0 |
| DNS Server | 10.1.1.254 |
| MAC Address | 24:62:AB:28:FD:51 |
| MQTT | Disabled |
| Emulation | Hue Bridge |
| mDNS Discovery | Disabled |
| ESP Chip Id | 2686289 |
| Flash Chip Id | 0x144051 |
| Flash Size | 1024kB |
| Program Flash Size | 1024kB |
| Program Size | 595kB |
| Free Program Space | 408kB |
| Free Memory | 25kB |
You must have a different version of the hardware. When you search here, which one is closest to yours? This is the Feit device the settings are for.
If you can't find settings someone else has found you need to "discover" them by yourself. For that you would need to run some commands in the Tasmota Console:
Issue these commands (more information here):
weblog 4
SerialSend5 55aa0001000000
14:59:00 CMD: Group 0, Index 1, Command "WEBLOG", Data "4"
14:59:00 RSL: RESULT = {"WebLog":4}
14:59:03 TYA: Send "55aa00000000ff"
14:59:03 {"TuyaReceived":{"Data":"55AA000000010101","Cmnd":0,"CmndData":"01"}}
14:59:03 TYA: Heartbeat
14:59:05 CMD: SerialSend5 55aa0001000000
14:59:05 SRC: WebConsole from 192.168.9.45
14:59:05 CMD: Group 0, Index 5, Command "SERIALSEND", Data "55aa0001000000"
14:59:05 RSL: RESULT = {"SerialSend":"Done"}
14:59:05 {"TuyaReceived":{"Data":"55AA000100156D34453633505A6C475770373433774D312E302E30D7","Cmnd":1,"CmndData":"6D34453633505A6C475770373433774D312E302E30"}}
14:59:05 TYA: MCU Product ID: m4E63PZlGWp743wM1.0.0
14:59:05 TYA: Send "55aa0002000001"
14:59:05 {"TuyaReceived":{"Data":"55AA0002000001","Cmnd":2}}
14:59:05 TYA: RX MCU configuration Mode=0
14:59:05 TYA: Read MCU state
14:59:05 TYA: Send "55aa0008000007"
14:59:05 {"TuyaReceived":{"Data":"55AA0007000806020004000000001A","Cmnd":7,"CmndData":"0602000400000000","DpType2Id6":0,"6":{"DpId":6,"DpIdType":2,"DpIdData":"00000000"}}}
14:59:05 TYA: fnId=0 is set for dpId=6
14:59:05 {"TuyaReceived":{"Data":"55AA0007000501010001000E","Cmnd":7,"CmndData":"0101000100","DpType1Id1":0,"1":{"DpId":1,"DpIdType":1,"DpIdData":"00"}}}
14:59:05 TYA: fnId=11 is set for dpId=1
14:59:05 TYA: RX Relay-1 --> MCU State: Off Current State:Off
14:59:05 {"TuyaReceived":{"Data":"55AA0007000502010001000F","Cmnd":7,"CmndData":"0201000100","DpType1Id2":0,"2":{"DpId":2,"DpIdType":1,"DpIdData":"00"}}}
14:59:05 TYA: fnId=12 is set for dpId=2
14:59:05 TYA: RX Relay-2 --> MCU State: Off Current State:Off
14:59:05 {"TuyaReceived":{"Data":"55AA00070005030100010010","Cmnd":7,"CmndData":"0301000100","DpType1Id3":0,"3":{"DpId":3,"DpIdType":1,"DpIdData":"00"}}}
14:59:05 TYA: fnId=13 is set for dpId=3
14:59:05 TYA: RX Relay-3 --> MCU State: Off Current State:Off
14:59:05 {"TuyaReceived":{"Data":"55AA00070005040100010011","Cmnd":7,"CmndData":"0401000100","DpType1Id4":0,"4":{"DpId":4,"DpIdType":1,"DpIdData":"00"}}}
Just want to say thanks to the dev and anyone that worked on this. I am new to Tasmota and the wiki was easy to follow and I had my devices up and running on HE in just a few minutes.
The only issue I had was the Hue bridge emulation was not on by default in the modified firmware, once I figured that out things went smooth.
Always nice to hear 
Did you run "reset 5" after switching to the modified firmware?
If anyone is interested in building a T4HE Garage door controller then please see the wiki link here.
3 Likes
Hi @markus. I received my TTL dongle and am ready to attempt to flash. However, when following the wiki, I get a 500 error on your github page. Please see Introduction to Tasmota for Hubitat Elevation (T4HE) · markus-li/Hubitat Wiki · GitHub
For which URL? All is working for me.
It was for Installing Tasmota Devices into Hubitat Elevation · markus-li/Hubitat Wiki · GitHub but it's working now so I guess github had a temporary issue. All good now.
1 Like
FYI that I followed the instructions and was able to flash my Sonoff 4CH relay and got the drivers/apps loaded in HE and all is working great!
@markus, thank you for all the work you did on this. I can see it was a lot of effort and it is appreciated.
Since my test just worked, now my next step will be to drill holes in the side of the garage and mount the flood lights on the outside and romex them into this relay... First time for everything. Fun stuff
1 Like
Yes, the device you linked to is the one I have. Feit Electric DIM/WIFI Dimmer Template for Tasmota
I reviewed the settings from that page and applied them to the device. My settings were definitely not correct when I compared them. It still didn't work, but then I did a hard power cycle by flipping the circuit breaker.
I had noticed in this thread that one user said they had to power cycle it, by which I interpreted it to mean to completely remove power from the switch. It started working after the power cycle.
Tested and it's working in Hubitat for on/off, but I don't have any dimming functionality. The dimming functionality does work if you go to the Tasmota device web page. Well, two steps forward, one step back I guess.
[EDIT]I got dimming working in HE! Changed the child device type to "Generic Component Dimmer" and now I can control the dimming on my dashboard object for the dimmer!
I flashed another device, a Merkury WiFi LED strip I got at Walmart. I have full color control in the Tasmota web interface, and it seems like also in Hubitat.
Used the template from here:
Parent device set as Generic RGB/RGBW Controller/Bulb/Dimmer
Child device set as Generic Component RGBW.
Success!
Ok, so the colors are just as off in Tasmota/Hubitat as they were with the Merkury/Geeni software. Not the fault of Tasmota or HE. This device, if you set it for 2700K, it looks like 5000K. I'm glad I got it working, but if you want an LED strip and don't already own one, I would suggest looking elsewhere if you care about color accuracy.
1 Like
