You haven’t missed a step. They are incompatible with Tuya Convert.
The alternative is described in my previous post.
Thanks Taras for confirming, wondering how other people were able to flash it on Tuya ( mentioned earlier in the thread). Anyways I will have to return them 
I believe the first report (in this thread) of incompatibility was posted in September. So it appears to be a fairly recent firmware update that renders it incompatible with Tuya Convert.
The traditional way of flashing the chip would be acceptable (these devices are easy to open without causing any damage) if it wasn’t for the fact you have to remove the chip to access GPIO0. I suspect its location (under the chip) is by design (Tuya’s decision) to discourage modifications (i.e. unable to discontinue use of the Tuya cloud service).
Firstly, thanks to TheEebb my Feit dimmer is now working with Tasmota. I have one of the newer ones so had to desolder and manually upgrade the firmware since tuya-convert no longer works on them. My problem is that the dimming function only works one way. I can dim the device from the Tasmota webserver and the green LEDs light accordingly but if I manually dim using the buttons, the Tasmota webserver dimming slider doesn’t change. The LED lights do work correctly and the correct dpid and value are being sent to the TuyaMCU (I checked with weblog 4). On/Off works fine both ways.
I admire your persistence. All that work to flash the device with the end-result being a partially-functional dimmer. 
haha… I enjoy the challenge. I am sure its a simple software issue inside Tasmota.
Can’t recall offhand if it did this with mine (sounds familiar though), but it should be updating the dimming percent in HA though. The webserver updating I think is just a Tasmota issue, as I think my other switches (e.g. MJ dimmers) are that way as well. A page refresh (again IIRC) should update the slider position. I’ll check when I get home tonight. Honestly unless you’re specifically needing to monitor the brightness level change on the Tasmota webserver in real time, this is a non-issue… at least for HA automations / dashboard cards.
I will be using the dimming level to have other smart bulbs track the brightness.
Again the dimming level should be updating still, at least in the software. I think the slider not moving when hitting the physical switch is a Tasmota browser issue. Watch the console for brightness updates… if it’s not updating, than that’s an issue. I use these switches to control other smart lights myself via Tasmota devgroupname / devgroupshare console options.
Edit: the latter does assume the smart lights in question are also Tasmota.
1 Like
great, I’ll dig into that. The console indicates the brightness levels are changing correctly. The bulbs are Tasmota. I am actually going through a smartthings hub rather than HA but this page seems to be very knowledgeable about these particular dimmers. Maybe I’ll repurpose my Mac mini soon though… haha.
OK thanks, devgroup sharing seems to be the ticket here. Very much appreciated.
Actually I just coincidentally saw your post on the SmartThings forum (was looking at pics of the TYWE2S on google). I have an ST hub, but it didn’t work the way I wanted for my Honeywell thermostats, so I disconnected it. If they ever fix their dang Alexa skill for virtual switches, perhaps I’ll hook it back up… but on shelf collecting dust it will sit until then.
Yeah if your bulbs are Tasmota flashed as well, then definitely use the the console commands I mentioned above, as they work amazingly well for this! For basic on/off/brightness, do the following on all Tasmota devices you want in the group:
devgroupname xxxx (whatever you want the group name to be)
devgroupshare 3,3 (tells them to share power state and brightness levels)
setoption85 1 (turns on the group sharing)
That should be all you need to get it working, and all you need is WiFi to be up and running… no HA, ST, hub, etc. needed for this to work!
*Edited to reword instructions to simplify for anyone lurking.
1 Like
Thanks again. My thermostat is Ecobee so its fine with ST but I am beginning to hate the cloud so I might move over to HA next year. Got to say Tasmota has generally been a godsend for me.
1 Like
Dimmer button state changes are still not getting picked up and thus not getting forwarded to devgroup.
Here is my weblog for dimmer down button press: {“TuyaReceived”:{“Data”:“55AA0307000802020004000000C8E1”,“Cmnd”:7,“CmndData”:“02020004000000C8”,“DpType2Id2”:200,“2”:{“DpId”:2,“DpIdType”:2,“DpIdData”:“000000C8”}}}
It appears that TuyaProcessStatePacket function is not picking up these dimmer changes.
I am currently using a Rule triggering on TuyaReceived to change the dimming levels by forcing a DIMMER command and that seems to be working albeit with lots of missed button presses.
Haha… I’m a pest aren’t I? Turned out my ground connection was not soldered in 100%. TheEeb’s firmware works flawlessly and without the need for that clunky rule.
Hey it happens to the best of us! Glad you got it figured out, and everything working as it should.
Hello, flashed my first FEIT dimmer by un-soldering the TYWE2S and connecting it to my pi. Worked great.
I have one case where I’d like to use that smart switch onto a circuit that must NOT be dimmable. It’s a basic under cabinet LED kit; they are not dimmable.
I am able to limit min brightness to 100% by issuing console command “DimmerRange 1000,1000”, however that only disables dimming via MQTT; I am still able to control the full brightness range via the physical buttons.
I have never tried FEIT’s app, but in their doc, the app is able to limit min brightness, does it also limit brightness on the physical switches? I suppose I’d need to send a special serial command to the other MCU in order to accomplish this?
Thanks for any hints.
Pretty sure I remember that working (though somewhat imperfectly) for me when I still used these everywhere. I’ve since switched several that were connected to non-dimmable LEDs to Martin Jerry Dimmers, which of course can completely disable it being a dimmer altogether. Thinking about it I might have needed to set it to 999,1000 or something like that… I’d have to tinker with it again to really recall.
I know you might be looking for a software solution, but honestly if you’re capable enough to desolder the TYWE2S chip, flash it, and then reconnect it… well can’t you just physically disconnect the path to the dimmer buttons while you have it open? Should be quite simple by comparison, and rather easy to reverse if you ever should need it to work again down the road. Just a suggestion.
Indeed, my current solution is to remove the dimmer buttons. I would have preferred a firmware way, as it would have guaranteed that there wouldn’t been anything below 100%. There is also a small issue where if you set the dimmer to 100%, cycle off/on, it won’t be 100% when it’s back. It’s more like 90%. removing the dimmer buttons is leaving me with this.
I’ll try DimmerRange 999,1000 again to see if that changes anything, but based on the way the dimmer is built, this command only “filters” the range from what’s coming from the WIFI. The secondary MCU handles the dimmer buttons, and just reports the resulting brightness back to the tuya MCU. In other words, the secondary MCU / physical buttons ignore “DimmerRange 999,1000”. It does its own thing.
Based on the manual, there is a troubleshooting method to avoid flickering. The FEIT app is able to configure that. They didn’t say it would prevent flickering only by setting the dimmer via wifi, they just say it would prevent flicker period. I suspect the tuya MCU is sending another serial command to tell the secondary MCU “here’s the new range, use that also for physical buttons”.
I still have a few non-flashed dimmers, I’ll try them with their app and see the physical button’s behavior. If they are indeed also limited and configurable, there’s hope. We only need to find those commands. I don’t have a logic analyser at home, nor do I have enough knowledge of the tuya’s serial commands to actually help a lot.
I’m hoping something already went down that path.
Was just thinking about this, but perhaps a Tasmota rule could fix the power on brightness level and dimmer button issue. Try entering this into your dimmer’s console:
backlog rule1 on power1#state=1 do dimmer 100 endon on dimmer#state<100 do dimmer 100 endon; rule1 1
Seems to work for me for always setting the dimmer switch to 100% when powered on, regardless of previous setting. It does momentarily flicker when pressing the dimmer buttons (or changing it in software), but will instantly set the brightness back to 100%. About the best and easiest “software” method I could come up with tonight. Let me know if that works for you.
1 Like
I’ll flash another dimmer and try that.
BTW, I just powered on another non-flashed dimmer, and when setting minimum brightness to 100% in their app, it does limit the brightness with hardware buttons. It does flicker when pressing the hardware buttons, so the behavior is very similar to what you’ve just described.