Some context
I have a metric #$%@ton of these brand of switches around the house, including dimmers and 3-ways that I've managed to get set up through the Tasmota for HE app/driver and have directly (in the case of the single-pole switches) or indirectly (via a virtual switch that interacts to the "relays" in the 3-way via rule machine). Dimmers were a bit of a struggle because they include a separate CPU that controls the device above and beyond just the wifi SoC, like the single-pole switch. Despite that, I managed to find the was to configure those so even those work.
The main point
Which brings me to the main point. These damn fan+light dimmer switches. It is the Treatlife DS03, and I can't for the life of me figure out how to get it to sync up like everything else. The Tasmota app/driver creates two "child" devices, one for the light+dimmer which works perfectly, and another that is seen only as a switch, which turns the fan on and off. But apparently Tasmota, or the driver, or something isn't communicating speed changes.
What I've tried
I've "sort of" managed to get it to work through HTTP GET links and rules. For example, Virtual fan switch is switched to low, send GET to "http://192.168.2.76/cm?cmnd=Power1+On and Send GET to: http://192.168.2.76/cm?cmnd=TuyaSend4+3,1" (I can go into more detail about these if need be; suffice it to say those are the commands to "turn it on" and "set the speed"). That works just fine, the virtual fan switch is updated, the actual fan is running, happy day. But changes at the switch won't update the virtual switch, obviously. But when changes are made to the fan status, the CPU sends serial codes to the Wifi module, which Tasmota can then intercept and operate rules accordingly. So, when the Tasmota gets a serial code for "fan at low", I have a rule send a HTTP link to a "local endpoint" in Hubitat that then processes a rule to update the virtual switch with the new status. Nevermind the issue I'm having where I now have conflicting rules because the Tasmota command updates the virtual switch, which triggers the other rule to change the physical switch condition based on the virtual switch and... yeah. That can be alleviated with boolean variables or rule pause timers or something, so that's relatively negligable.
The Issue
This setup is horrendously unreliable. I've had issues where I turn the fan on at the switch and it immediately turns off again. Remote operation doesn't update the switch at all. Alexa will operate the virtual switch, but never receives a response so after about 30 seconds she says there was no response. Google assistant won't even bother with the virtual fan switch (it keeps dropping the virtual switch when I update the device list, implying it's not compatible anyway), so I haven't even begun to figure that out.
The Question
Has anybody gotten these to work "natively" with the Tasmota driver? I understand that as a wifi device it is going to be a pain to get it to talk to Hubitat anyway, but the other Tasmota devices seem to be doing just fine, so I was wondering if anybody else has one of these and has figured out a configuration combination that has done the trick.
Side Note
I know there was some "falling out" or something with the developer of the Tasmota driver and that he would likely be the most appropriate person to ask about this, but I figured I'd reach out to the community first to see if anybody else has figured this out.
The End
THANK YOU for taking the time to read through my antics. Any help, info, or even comments are appreciated! 
