@TheEebb - that fixed my problem. Thank you!
Hey Eebb just wanted to let you know that so far with your latest build (v0.521) I havenāt been able to get that weird brightness / power off group glitch to reoccur that I mentioned. It did do it to me once the other night on the previous build that I still have on another switch thoughā¦ not sure whatās causing it, or why itās not occurring in v0.521 since it doesnāt sound like this change would affect this. Again it could just be a Tasmota 8.2 bug (1st release of grouping feature), and I just havenāt ran into it on my test dimmer setup yet.
Thatās good to know. Iāll also be pushing out another build using Tasmota 8.3 as a base shortly. This might help resolve any bugs related to device groups.
@TheEebb, Thanks for putting in effort to get tasmota working on this dimmer. i am closing watching this thread. will jump on it when firmware stabilizes. 
So I noticed that when these turn on, they turn on at less than full power. Will the firmware fix this?
I was having the same issue as @tman75, basically when you turn on the light through the webui, the dimmer would not be 100%, you would have to physically press the button to go all the way to 100%.
Through trial and error using TuyaSend2 command, I figured out that the max value for the dimmer is not 1000 but 1444. Anything higher and the light turns off.
So basically by doing this.
DimmerRange 10,1444
fixed the issue.
This might be a reason to flash mine. I am currently still using the SmartLife app. @bilalasd, does this also change the physical switch?
Thank you for resolving the thing that bugged me the most about this switch! For those using ESPHome, I made the same change to my YAML configuration:
light:
- platform: "tuya"
name: "Living Room Fan Light"
dimmer_datapoint: 2
switch_datapoint: 1
min_value: 10
max_value: 1444
@tman75 it does appear to fix both Lovelace and the physical switch.
just saw that tasmota 8.4 got released. @TheEebb, did your changes get accepted in the master tasmota branch ?
I got four of these from costco this weekend. I installed them and flashed ESP8266 custom firmware which I created using homeassistant esphome addon. 3 out 4 dimmers are working great through home assistant. Only one out of this four is not responding to any actions from home assistant. ESPHome addon shows it as online but no response action on/off from home assistant. Only manual switch works.
Any pointers on how to debug this? I turned off logging based on above configs.
Here is my config:
esphome:
name: kitchen_2_dimmer
platform: ESP8266
board: esp01_1m
wifi:
ssid: "PATILS"
password: "****"
manual_ip:
# Set this to the IP of the ESP
# Set this to the IP of the ESP
static_ip: 192.168.20.188
# Set this to the IP address of the router. Often ends with .1
gateway: 192.168.20.1
# The subnet of the network. 255.255.255.0 works for most home networks.
subnet: 255.255.255.0
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Kitchen 2 Dimmer"
password: "****"
captive_portal:
# Make sure logging is not using the serial port
## EDIT: baud rate 0 still seems to cause issues with
## flickering lights and checksum errors in the logs
## I'm now using level: NONE
logger:
baud_rate: 0
level: NONE
# Enable Home Assistant API
api:
# Make sure you can upload new firmware OTA
ota:
# My dimmer used this hardware serial port
uart:
rx_pin: GPIO3
tx_pin: GPIO1
baud_rate: 9600
# Register the Tuya MCU connection
tuya:
# Make the light
# Not sure about the minimum dimming range here, 0 might be too low
light:
- platform: "tuya"
name: "kitchen_2_dimmer"
dimmer_datapoint: 2
switch_datapoint: 1
min_value: 10
max_value: 1444
Never mind. Just recycling power did the trick. Thanks guys for working configs.
Unfortunately, I havenāt had the time lately to wrap up everything necessary to push it upstream. But I will certainly post to this board once its complete.
1 Like
Any idea if the how important the board field is? I noticed itās changed in the posted examples. If I recall, I had it working at one point under tuya as esp01_1m, but Iāve lost that config. Now in ESP home, Iām having trouble, but it appears that esp8266 is getting me closer despite it being a more dated example. Just wanted to confirm before I continue troubleshooting.
esphome:
name: wtfyouwereworking5minago
platform: ESP8266
board: esp8285
OR
esphome:
name: pleasegodmakeitworkthistime
platform: ESP8266
board: esp01_1m
This mostly works for me on the version of dimmer in the first post
esphome:
name: officedimmer
platform: ESP8266
board: esp01_1m
root@homeassist:~# pip3 show esphome
Name: esphome
Version: 1.14.3
Andy
1 Like
I am sorry if this has been asked but does anyone know how to disable the ring Led when the switch is off? This is in a bedroom and itās a little annoying.
Unfortunately, it doesnāt appear to be possible.
@Technowizard ā In post 70, you mentioned, āā¦put one of my switches that didnāt need the dimmer portion enabledā¦ā
Do you mind sharing your ESPHome config without the dimmer portion enabled? I want to start off with just the main switch and go from there as I feel more comfortable.
Thank you.
@rationi_meae I was referring to leaving that option out with Tasmota. I no longer use ESPHome on these switches since @TheEebb created a custom Tasmota firmware that fixed the On/Off issue. That said, if I were to guess I would assume you could simply # and/or leave out the light entries like so:
light:
- platform: "tuya"
name: "whatever you want"
#dimmer_datapoint: 2
switch_datapoint: 1
#min_value: 0
#max_value: 1000
Alternatively if that doesnāt work, you could also try setting the light min and max value to the same like so:
light:
- platform: "tuya"
name: "whatever you want"
dimmer_datapoint: 2
switch_datapoint: 1
min_value: 1000
max_value: 1000
Be advised that doing the latter could possibly cause a momentary flicker if the dimmer buttons are actually used. Again this is all a best guess since Iāve changed all my remaining Feit Dimmers back to @TheEebbās Tasmota firmware.
Thank you.
Iāve noticed that my dimmers runner 8.3.1 are sometimes out of sync, meaning, the light is physically on or off, but when I log into the webUI of that device, it says the opposite. This usually happens when the light is turned on then immediately off (or visa versa).
Anyone else have this problem?