Is Shelly RGBW2 supported?

dedepene · August 25, 2019, 3:32pm

Hi,

Would I be able to flash ESPHOME to Shelly RGBW2 and use the cwww platform? Anyone done this?

Thanks!

dedepene · August 26, 2019, 7:00am

No one has an idea? I figured the challenge is to identify the pins on the Shelly in order to set up output components for CW and WW in esphome. Any ideas how to go about this?

output:
  - platform: esp8266_pwm
    pin: 12
    frequency: 1000 Hz
    id: pwm_c
  - platform: esp8266_pwm
    pin: 13
    frequency: 1000 Hz
    id: pwm_w

9guiajkbk2 · September 19, 2019, 9:08pm

Hi, did you find the correct pins and manage to set up a Shelly rgbw2 with esphome?

dedepene · September 20, 2019, 5:14am

Sure did. First, flash the shelly with esphome - should be pretty straightforward. Then, use the table at the end of this blog post to figure out the channel - pin mapping on the Shelly. Lastly, set up the output components and the cwww platform like so:

70085883_10156615753758634_9178698144978829312_n

This is how I got it going, but it’s not in “production” yet - just a test for now.

9guiajkbk2 · September 20, 2019, 6:45am

Thanks for sharing!

lolfonfire · March 24, 2020, 1:25am

Hi,

Thanks all for the information!
I’ve been using the RGBW2 through MQTT for months but wanted to get rid of MQTT.
So I’ve flashed my Shelly RGBW2 with ESPHOME.
I used this config
RGBW2

After adding the Shelly RGBW2 to Home Assistant through the ESPHOME integration I am able to change colors, dimming and changing the white value of my RGBW led strip.

Kyle_Boyington · March 25, 2020, 1:59am

Care to elaborate on how to flash? I am having a rough time.

dedepene · March 29, 2020, 2:45pm

I remember borrowing from this guide - https://www.youtube.com/watch?v=kJpE3MpDGe4

wrkn · April 13, 2020, 10:55pm

Thanks for these details! Two questions:

Are you able to control RGB and W independently with ESPHome and HA? (When I previously used Tasmota + HA with a different RGBW controller, HA wouldn’t let me turn on the white LED at the same time as RGBs; if I touch the white value slider, the RGBs would turn off.)
Were you able to get a physical on/off, dimmer, or momentary switch working (I)nput terminal on the Shelly?

lolfonfire · April 13, 2020, 11:28pm

Yes I’m able to control the white value independently. When RGB is on changing the white value also changes the RGB value. If you I only turn on W and change the white value then I can go from standard cold white to warm white.
I don’t need a physical switch. It’s in my bathroom and have other main lighting. This is more a mood light which is turned on from time to time.

ebula · November 12, 2020, 2:02am

I just wanted to post my solution for a Shelly RGBW2 for monochromic lighting on all 4 outputs with one switch to control them like a regular dimmable light:

substitutions:
  device_name: dim_0

esphome:
  name: ${device_name}
  platform: ESP8266
  board: esp01_1m

logger:
  
api:
  reboot_timeout: 15min
  password: !secret api_password

ota:
  password: !secret ota_password



wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  domain: !secret domain
  fast_connect: true

light:
  - platform: monochromatic
    name: ${device_name}_ch1
    id: ${device_name}_ch1
    output: ${device_name}_out_ch1
  - platform: monochromatic
    name: ${device_name}_ch2
    id: ${device_name}_ch2
    output: ${device_name}_out_ch2
  - platform: monochromatic
    name: ${device_name}_ch3
    id: ${device_name}_ch3
    output: ${device_name}_out_ch3
  - platform: monochromatic
    name: ${device_name}_ch4
    id: ${device_name}_ch4
    output: ${device_name}_out_ch4
# Example output entry
output:
  - platform: esp8266_pwm
    id: ${device_name}_out_ch1
    pin: GPIO12
    frequency: 1000 Hz
  - platform: esp8266_pwm
    id: ${device_name}_out_ch2
    pin: GPIO15
    frequency: 1000 Hz
  - platform: esp8266_pwm
    id: ${device_name}_out_ch3
    pin: GPIO14
    frequency: 1000 Hz
  - platform: esp8266_pwm
    id: ${device_name}_out_ch4
    pin: GPIO4
    frequency: 1000 Hz


binary_sensor:
  - platform: gpio
    pin: GPIO5
    id: light_0_touch
    on_click:
      then:
      - if:
            condition:
             - light.is_off: ${device_name}_ch1
             - light.is_off: ${device_name}_ch2
             - light.is_off: ${device_name}_ch3
             - light.is_off: ${device_name}_ch4
            then:
              - light.turn_on: 
                 id: ${device_name}_ch1
                 brightness: 1.0
              - light.turn_on: 
                 id: ${device_name}_ch2
                 brightness: 1.0
              - light.turn_on: 
                 id: ${device_name}_ch3
                 brightness: 1.0
              - light.turn_on: 
                 id: ${device_name}_ch4
                 brightness: 1.0
            else:
              - light.turn_off: ${device_name}_ch1
              - light.turn_off: ${device_name}_ch2
              - light.turn_off: ${device_name}_ch3
              - light.turn_off: ${device_name}_ch4
    on_press:
      then:
      - if:
          condition: 
            light.is_off: ${device_name}_ch1
          then:
          - delay: 0.5s
          - while:
              condition:
                binary_sensor.is_on: light_0_touch
              then:
                - light.dim_relative:
                    id: ${device_name}_ch1
                    relative_brightness: 5%
                    transition_length: 0.1s
                - delay: 0.1s
                - light.dim_relative:
                    id: ${device_name}_ch2
                    relative_brightness: 5%
                    transition_length: 0.1s
                - delay: 0.1s
                - light.dim_relative:
                    id: ${device_name}_ch3
                    relative_brightness: 5%
                    transition_length: 0.1s
                - delay: 0.1s
                - light.dim_relative:
                    id: ${device_name}_ch4
                    relative_brightness: 5%
                    transition_length: 0.1s
                - delay: 0.1s                
          else:
          - delay: 0.5s
          - while:
              condition:
                and:
                  - binary_sensor.is_on: light_0_touch
                  - light.is_on: ${device_name}_ch1
              then:
                - light.dim_relative:
                    id: ${device_name}_ch1
                    relative_brightness: -5%
                    transition_length: 0.1s
                - delay: 0.1s
                - light.dim_relative:
                    id: ${device_name}_ch2
                    relative_brightness: -5%
                    transition_length: 0.1s
                - delay: 0.1s
                - light.dim_relative:
                    id: ${device_name}_ch3
                    relative_brightness: -5%
                    transition_length: 0.1s
                - delay: 0.1s
                - light.dim_relative:
                    id: ${device_name}_ch4
                    relative_brightness: -5%
                    transition_length: 0.1s
                - delay: 0.1s

The channels are then combined in to one group in HA.

I’m posting this because I found it somewhat difficult for to find all the bits and pieces, so maybe it helps someone.

cheers

socrates · December 20, 2020, 10:28am

Hi

I’ve just bought my first Shelly RGBW2 to be used with a 620x620mm LED light panel ( https://www.synergy21.de/media/pdf/dd/42/a1/166579-Datenblatt.pdf )

Using the stock-firmware and the web interface, the primary colors (red,green,blue) are ok, but every color from the color picker is off (red for instance looks like violet)

I found this question from another user having the same problem:

Do you experience this as well? Or does esphome “fix” this bug?

Thanks in advance,
Cheers!

socrates · December 20, 2020, 5:00pm

Never mind. I found a way to flash esphome (working around those mini-connectors) and esphome does provide better color accuracy. Not perfect, but better

koan · December 21, 2020, 7:49am

A little trick to work around those 1.27 mm pitch headers:

It’s a bit MacGyver-style, but it works, and you only need it once

socrates · December 21, 2020, 9:55am

Well, I am a child of the 80’s… And without googling I came up with the exact same idea .

At first I tried a paper clip, but it was to thick. Then I though of the old resistors I still have in storage

Adam_Smith · April 1, 2021, 12:59am

Can you post the full config?

marcvl64 · April 28, 2021, 10:09pm

Has anyone figured out how to create a power sensor for the Shelly RGBW2 device running ESPhome? Would love to see a working .yaml file for that.

According to this Tasmota article, you can monitor voltage using the A0 pin. I tried this as follows:

sensor:
  - platform: adc
    id: voltage_analog_reading
    pin: A0
    name: ${friendly_name} Voltage 
    unit_of_measurement: V 
    icon: mdi:flash-circle
    update_interval: 10s

However, the output is fixed value of 0.37, no matter what I do with my lights (on/off/change brightness/…).

marcvl64 · April 28, 2021, 11:58pm

Answering my own question. Turns out the yaml is correct. The voltage did vary between 0.365 and 0.369 V which is why I didn’t see any change at first. The load only varied from 0 to about 4 Watt, which explains why the voltage didn’t change all that much. So, it all works

sender · November 20, 2021, 6:52pm

Hi, since this is the only Shelly RGBW2 topic on the forum I might ask my question here best. I have flashed esphome on my shelly rgbw2 in order to replace my zwave fibaro rgbw led driver with the shelly. I only want to use 1 output: white. According to the specs it should be able to drive 45W which is more than enough for my 10x2W white dimmable LEDs. But I have no success with both @ebula his and @lolfonfire his configs in driving out a signal on either 1 out of 4 channels for driving my LEDs… I have tried with LEDs connected and tried to measure voltage with a multi-meter but no voltage comes out… I think it has to do that the esphome component ony send the “signal” and not the power… but according to the specs the sehlly (sh)(c)ould do this…

Can someones please help me out with a push in the right direction on how to use esphome to drive out voltage for my LEDs?

(ps. please do not start a discussion on why I do no use the stock firmware )

Thanks!

sender · November 21, 2021, 4:18pm

Solved. Can dim 4 channels separate or combined to RGBW. The culprit was the LEDs need to be powered between DC (+) and a channel which is (-). Thus for me a little illogical since the plus is on the LED and the other is the minus which is 1 of the 4 channels (R G B W)… Thus a channel is MINUS.

For others. You can flash completely OTA (thus no wires needed!

use this:

Then important!!! you cannot directly flash esphome binary via the tasmota webinterface of the device due to less memory. Download minimal tasmota in between:
ota.tasmota.com/tasmota/release-9.1.0/

this :http://ota.tasmota.com/tasmota/release-9.1.0/tasmota-minimal.bin

don’t use version 10 of minimal, that’s too big.

Then via minimal upload the esphome bin file… voila…

My config:

# Lamp Kitchen

substitutions:
  device_name: shelly_rgbw_01

esphome:
  name: ${device_name}
  platform: ESP8266
  board: esp01_1m

wifi:
  ssid: "ssid"
  password: !secret ssid
  domain: !secret domain
  #use_address: 192.168.6.70
  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "${device_name} Fallback Hotspot"
    password: !secret Fallback_Hotspot

captive_portal:

# Enable logging
logger:
  level: DEBUG

# Enable Home Assistant API
api:

ota:

web_server:
  port: 80

time:
  - platform: homeassistant
    id: homeassistant_time

sensor:
  - platform: wifi_signal
    name: "${device_name} - WiFi Signal"
    update_interval: 60s
  - platform: uptime
    name: "${device_name} - Uptime"
    icon: mdi:clock-outline
    update_interval: 60s
  - platform: uptime
    name: Uptime Seconds
    id: uptime_sensor
    update_interval: 60s
    on_raw_value:
      then:
        - text_sensor.template.publish:
            id: uptime_human
            state: !lambda |-
              int seconds = round(id(uptime_sensor).raw_state);
              int days = seconds / (24 * 3600);
              seconds = seconds % (24 * 3600);
              int hours = seconds / 3600;
              seconds = seconds % 3600;
              int minutes = seconds /  60;
              seconds = seconds % 60;
              return (
                (days ? String(days) + "d " : "") +
                (hours ? String(hours) + "h " : "") +
                (minutes ? String(minutes) + "m " : "") +
                (String(seconds) + "s")
              ).c_str();
    
light:
  - platform: monochromatic
    name: ${device_name}_R
    id: ${device_name}_R
    output: ${device_name}_out_R
  - platform: monochromatic
    name: ${device_name}_G
    id: ${device_name}_G
    output: ${device_name}_out_G
  - platform: monochromatic
    name: ${device_name}_B
    id: ${device_name}_B
    output: ${device_name}_out_B
  - platform: monochromatic
    name: ${device_name}_W
    id: ${device_name}_W
    output: ${device_name}_out_W

output:
  - platform: esp8266_pwm
    id: ${device_name}_out_R
    pin: GPIO12
    frequency: 1000 Hz
  - platform: esp8266_pwm
    id: ${device_name}_out_G
    pin: GPIO15
    frequency: 1000 Hz
  - platform: esp8266_pwm
    id: ${device_name}_out_B
    pin: GPIO14
    frequency: 1000 Hz
  - platform: esp8266_pwm
    id: ${device_name}_out_W
    pin: GPIO4
    frequency: 1000 Hz
    
text_sensor:
  - platform: template
    name: Uptime
    id: uptime_human
    icon: mdi:clock-start
  - platform: version
    name: "ESPHome Version"

switch:
  - platform: restart
    name: "${device_name} Restart"