I have 4 of them running ESPHome with no state update issues. One of them is wired in a 3 way circuit, and still reports state properly when the dumb switch is triggered.
I ended up skipping tasmota, based on early reports though, so no firsthand comparison.
No issues here either with the fix that was mentioned earlier in this thread, works as expected. going on 2 weeks, and lights get used daily in my automations and physical touches all registering properly.
Just installed 2 switches from Menards. One of them is stuck in an interrmediatery firmware, I will crack that one open as a test bench. The new firmware works great with no issues.
I never had any state update issues with ESPHome, but I did have drop out issues (loss of connection, no heartbeat, etc.) if I suddenly asked too much of it. Rapid brightness changes for example would sometimes make it crap out for a while. Kind of made me a bit skittish to changing those settings sometimes. Honestly though I made the switch to Tasmota using Ebb’s custom fixed firmware for the enhanced improvements and ease of use. Tasmota allows for Hue Emulation (for Alexa discovery & control), device grouping & control, and easy rule implementation. I know some automation tasks can be done with ESPHome, but it’s just a ton easier via Tasmota, which also allows modification of those rules and settings via HA on the fly (i.e. no firmware flashing every time you want to change a setting). Heck with Tasmota’s grouping and rules you can set these switches to work with other Tasmota devices (e.g. WiFi lights not electrically connected to the switch, etc.) to work together without HA or any other central server/hub (WiFi is obviously still needed). That alone made the switch worth it!
1 Like
Hi all,
just read most of all this thread and I am not sure where to go.
I bought a kit of 3 dimmer yesterday…that’s insanely cheap…38.99 CAD.
So, as of today, should I go with ESPHOME or Eebb TASMOTA’s fork ?
I already have a mix of ESPHOME device and TASMOTA here.
thanks for your comment.
Your first challenge will be flashing the TYWE2S chip.
The current firmware prevents the use of Tuya-Convert so you must open the device, connect an appropriate serial-to-USB adapter to the chip, and flash it with new firmware.
What complicates this step is that one of the required connection points (GPIO0) is underneath the chip. You have to remove the chip in order to access it. Removal means desoldering it from the PCB.
Well I’ll give a try of tuya…maybe I have an old bunch of device.
Otherwise i’ll return it to store, don’t want to mess with the soldering.
Give it a try but there are existing posts in this thread (and in Tasmota’s GitHub repo), as recently as a month ago, reporting that these devices no longer work with Tuya Convert.
Let us know if you are successful.
FWIW, the Costco in Vaudreuil-Dorion is liquidating its stock of CE Smarthome outlets for CAD$9.97 for a pack of two outlets. If you have a need for controllable outlets, it’s hard to beat the price (CAD$5/each). It’s possible other branches of Costco have them as well.
I can confirm that they are compatible with Tuya Convert. Here’s the configuration template:
1 Like
Hi , I recently bought these dimmer from Costco , I am not able to flash them using tuya converter . I put the dimmer in flashing mode by pressing the button for 5-7 second and lights keep blinking but tuya converter not able to find the device .
Any step am I missing here ?
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