Do you mean could flash it?
Not sure if anyone else got it working or not but here is a config that I got to run correctly with the Genio RGBCCT Downlight. If the max_power is above .2 looks like the SM2135 locks up maybe from over-current Iām assuming.
sm2135:
data_pin: GPIO14
clock_pin: GPIO12
output:
- platform: sm2135
id: output_green
channel: 0
max_power: 0.2 - platform: sm2135
id: output_red
channel: 1
max_power: 0.2 - platform: sm2135
id: output_blue
channel: 2
max_power: 0.2 - platform: sm2135
id: output_white
channel: 3 - platform: sm2135
id: output_warmwhite
channel: 4
light:
- platform: rgbww
name: ${friendly_name}
red: output_red
green: output_green
blue: output_blue
cold_white: output_white
warm_white: output_warmwhite
cold_white_color_temperature: 6500 K
warm_white_color_temperature: 2700 K
color_interlock: true
Hi Dave,
If i removed the ESP Chip from the main board it wouldnāt flashā¦ No idea why.
When i put it back on it flashed no worries.
Cheers
I am trying to setup a Mirabella Genio 9W CCT Downlight (I002742). It has been flashed with Tasmota and I have set up mqtt on the device to link to HA server. For some reason all that is coming through to Homeassistant is a value for sensor.tasmota_status. There is no light entity.
I had this downlight setup a couple of years ago on a rpi and it was working without issue. I am trying to set up on a NUC running latest HA software.
Has anyone any ideas on what the issue could be.
Thanks.
Problem solved. Updated firmware from 8.0.2 to latest 11.1.0. Initially got an error message āUpload buffer miscompareā. Installed the lite firmware version and then full latest version which did not then error.
Got the Genio 1003989 9W RGB+CCT bulb
This no longer comes with an ESP8266, but has a CB3L instead - one of Tuyaās own āmodulesā that contains a BK7231N microcontroller.
Fortunately, this can still be flashed over serial using these instructions: https://www.elektroda.com/rtvforum/topic3874289.html
Hey Ryan, Iāve been configuring a similar Genio E14 RGBCCT SM2135 chipped lamp but having an issue getting the white and warm white to work. RGB is fine though. Iām using the same yaml & channels as you posted above.
Question: How many entities do you see for this lamp in the ESPhome integration ?
I see only 1 but expected 2 or 3 (RGB, WW, CW etc).
This is what Iām seeing but the white channels donāt activateā¦
and
I could kiss you I swear, I submitted a ticket to ESPHome like 5 months ago hoping to get the clock strobing issue fixed (Iāve got like 14 of these lights) and now I can RGB MY HOUSE FOR NO REASON
Does cold_white and warm_white channels work for your lights ?
Hey mate, Yeah all works as expected for me. Just change the colour temp and off it goesā¦ Maybe the cool/warm is on different channels with the E14 lamp?
Hahahaha welcome. Just spend a bit of time tweaking as I found even though it worked on the bench when I came back after a while it had gone wonky. My max_power setting was just trial and error to get that.
Thanks for the feedback.
OK, maybe my lamp is defective, there are only 5 (0-4) channels on the chip and three are used for RGB which are working fine. When I slide the colour temp slider from cold to warm direction the RGB leds go out but white/s does not come on (color_interlock: would make RGB drop out).
I wondered if there was a coding bug in the ESPhome SM2135 driver, but now that canāt be if yours works.
I will either find another lamp or probe this one with a CRO and see what the W/WW output PWM pins are doing. Trouble is the voltages around the PCB may be lethalā¦
Yep, Iāve got all full colour range and now RGB, hereās my yaml 
The gamma correct lets me set the lights to 1% at night time
sm2135:
clock_pin: GPIO12
data_pin: GPIO14
# Individual outputs
output:
- platform: sm2135
id: output_red
channel: 1
max_power: 0.2
- platform: sm2135
id: output_green
channel: 0
max_power: 0.2
- platform: sm2135
id: output_blue
channel: 2
max_power: 0.2
- platform: sm2135
id: output_white
channel: 3
- platform: sm2135
id: output_warmwhite
channel: 4
light:
- platform: rgbww
name: "${friendly_name}"
red: output_red
green: output_green
blue: output_blue
cold_white: output_white
warm_white: output_warmwhite
cold_white_color_temperature: 6500 K
warm_white_color_temperature: 2700 K
color_interlock: true
# Ensure the light turns on by default if the physical switch is actuated.
restore_mode: ALWAYS_ON
gamma_correct: false
For what itās worth the SM2135 issue is tracked in git here.
Thereās also someone else whoās made a fix thatās yet to be merged into the main branch of esphome
Itās an ESPhome issue since Tasmotaās implementation works fine
I was just about to get my downlights installed and started fiddling with them on the bench again. Found that the colour was a bit off. After some trial and error have found the red channel max power at 0.6 seems to be the sweet spot. If I was a betting man I reckon that you need the sum of all max power to equal 1 when added up for the RGB channels. So when you go to āwhiteā with all channels on its still only at 1 or 100%.
Just going to throw this out there: Iām working my way through measuring all of the Mirabella Genio lights, to contribute to powercalc.
If you have a few globes to spare, a lamp and a compatible power measurement device, contributions welcome.
Alternatively, if you are AU based and have any unused globes around, happy to do the measurements and mail them back to you.
1 Like
I havenāt purchased a Genio globe since probably 3-4 years. Just wondering if Tuya-convert is still an option or is there some other method you have to use now to flash with tasmota?
You may have luck using the new OTA flash method.
It isnāt listed as tested but there are other Mirabella devices so itāll likely work, just needs someone to try and confirm.
Iām not willing to flash it (yet), since Iām pretty sure Iāll loose the sound reaction part.
I managed to get it into HA using localtuya, but Iām not sure I got all the IDs right.