【Add-on Guide】Yeelight add-on for eWeLink CUBE

eWeLink CUBE
1

Exciting news for Yeelight enthusiasts!

yeelight YEELIGHT

CUBE-LOGO
CUBE-LOGO1200×228 32.6 KB

Yeelight has launched a new official add-on that allows you to easily sync your Yeelight smart lights to eWeLink CUBE powered local smart home hub, like SONOFF iHost.

With this new add-on, you’ll be able to control your Yeelight smart lights right from the eWeLink CUBE.
The add-on connects through your local WiFi network so no separate hub or bridge is needed. Just install the ‘eWeLinkCUBE-Yeelight-LAN’ add-on in the CUBE, then you can turn YEELIGHT smart lights on and off, dim, change color and scenes, set schedules and timers, and more all from one central place. This opens up tons of automation possibilities.

Here is the list of the supported Yeelight lights:

Yeelight Monitor Light Bar Pro

Yeelight LED Lightstrip Pro

Yeelight LED Lightstrip 1S

Yeelight Smart LED Light Bulb W3 (Color)

Yeelight Smart LED Light Bulb 1S (Color)

Yeelight GU10 Smart Bulb W1 (Color)

Yeelight Smart Lamp D2

Yeelight Smart LED Panels

Yeelight Cube Smart Lamp

Screenshots of the add-on:

image
image699×763 33.2 KB

image
image1817×1150 174 KB

image
image1817×1150 187 KB

What automations will you be creating between Yeelight and eWeLink? Let us know how it goes!

2 Likes
3

This is really great work thank you.

I was getting an error with my one bulb and I notice python-yeelight has been updated to include a new bulb: yeelink.light.mono6

Here’s the device properties:

“mono6”: {
“color_temp”: {“min”: 2700, “max”: 2700},
“night_light”: False,
“background_light”: False,
},

Could you include the device? I get the following error in the log:

  • type=BulbType.Unknown, model=mono6>: Reconnected failed with [Errno 113] Connect call failed (‘192.168.1.228’, 55443), backing off
  • yeelight - DEBUG - Device AsyncBulb<192.168.1.228:55443, type=BulbType.Unknown, model=mono6> not found in ihost_devices
4

Steps to enable lan mode on any xioami bulb into dev mode or lan mode. (when you can’t connect using the Yeelight app, and you don’t have cloud access)

  1. pip install python-miio (This may involve installing python for windows as well as it’s dependcies.)

  2. Delete the bulb from the Xiaomi app. This should get the bulb to create it’s own AP. The SSID will be something like yeelink-light-color5_miapACD4. If that doesn’t work reset it with 5 switch flips.

  3. Connect to the yeelink AP. Once connected run the following:
    miiocli discover
    Your device will show with a token:

INFO:miio.miioprotocol:Sending discovery to <broadcast> with timeout of 5s..
INFO:miio.miioprotocol:  IP 192.168.1.18 (ID: 1c0b06e1) - token: b'0eb5629f00aa5d4dfbeb4961f6458199'
INFO:miio.miioprotocol:Discovery done
INFO:miio.discovery:Discovering devices with mDNS for 5 seconds...
  1. Copy the token and run the command as below using your token and IP
    miiocli yeelight --ip 192.168.1.18 --token 0eb5629f00aa5d4dfbeb4961f6458199 set_developer_mode 1
Setting developer mode to True
['ok']
  1. Re-add to Mi Home and dev mode should stay working. Just add the yeelink addon, and the follow the steps and the Xiaomi bulbs will appear in the iHost.

Note, after adding the bulb back to the mi home app, all miiocli commands stop working. This might make it seem like the process failed. Don’t give up, the dev mode is still active, just check in the yeelink addon, or use python-yeelight to talk to the bulb. :sunglasses:

5

I have a similar problem as paulka007.
Bulb mono6.
The lamp is defined in webUi. But when you click on Confirm
nothing happens.
There are errors in the logs.
Translate to set_developer_mode
Convenient with this set_developer_mod

7

This lamp doesn’t work for me either, it seems the plugin itself doesn’t support mono type lamps. This plugin hasn’t been updated for a long time.

8

How to find who made this add-on?
Try to fork and try to fix it.
This lamp through similar integration,
on the same libraries, works in HA.
Sorry for my english.

9

Yeelight has launched a new official add-on that allows you to easily sync your Yeelight smart lights to eWeLink CUBE powered local smart home hub, like SONOFF iHost. Its info in this forum
https://forum.ewelink.cc/t/add-on-guide-yeelight-add-on-for-ewelink-cube/21220

10

In my case i can see my W1 (monob) bulb - But nothing happends when i click “connect”

image
image1311×757 42.1 KB

I looks we can discover the bulbs, but they are unknown models: “ctc” and “monob”

2025-01-12T20:47:03 2025-01-12 19:47:03,385 - yeelight.aio - DEBUG - AsyncBulb<192.168.100.189:55443, type=BulbType.Unknown, model=ctc>: Ping result received: {‘id’: 20, ‘result’: [‘on’]}

2025-01-12T20:47:03 2025-01-12 19:47:03,387 - yeelight - DEBUG - Device AsyncBulb<192.168.100.189:55443, type=BulbType.Unknown, model=ctc> state changed: {‘power’: ‘on’, ‘connected’: True}

2025-01-12T20:47:03 2025-01-12 19:47:03,387 - yeelight - DEBUG - Device AsyncBulb<192.168.100.189:55443, type=BulbType.Unknown, model=ctc> not found in ihost_devices

2025-01-12T20:47:03 2025-01-12 19:47:03,387 - yeelight.aio - DEBUG - AsyncBulb<192.168.100.189:55443, type=BulbType.Unknown, model=ctc>: Waiting for line, music_mode_state: False

2025-01-12T20:47:07 2025-01-12 19:47:07,260 - yeelight - DEBUG - Discovering local LAN Yeelight devices with timeout 3 seconds…

2025-01-12T20:47:10 2025-01-12 19:47:10,283 - yeelight - DEBUG - Found 2 devices

2025-01-12T20:47:20 2025-01-12 19:47:20,490 - yeelight - DEBUG - Received SSE event: MessageEvent(type=None, message=‘’, data=‘’, origin=‘http://ihost’, last_event_id=‘’)

2025-01-12T20:47:25 2025-01-12 19:47:25,285 - yeelight - DEBUG - Discovering local LAN Yeelight devices with timeout 3 seconds…

Question

Would it be possible to reach out the the creator of this add on and ask him/her to enable compability?

11

This is the add-on that I have installed for a couple of months now and, as in other posts here, it finds the lights but the ‘confirm’ button does nothing and it doesn’t link control to iHost. Have given LAN control permission in the Yeelight app but no difference.

12

@SuiKa Plz take a look at this

13

Hi
Any feedback on this?

14

Hey

We will share more when there’s a workaround available.

1 Like