No Yeelight options after setup. Seeking guidance

Third party integrations
1

Installed Home Assistant last night and managed to get all my google homes and chrome casts detected. But not sure how to get my Yeelights to show up. I can’t find any integration with Yeelight.

I’ve searched and it seems it’s possible. There are code snippets around. But I have no idea where to start. Is it a file I need to create? Dies anyone have a zero to hero guide?

I’m a .Net developer ( just to explain my knowledge ). Any guidance would be great.

2

Here’s the integration :wink:

3

Thanks for that. Then I’m on the right path, asI keep ending up at that page, which is good. But, not sure where the customize.yaml is located. In my config folder, there’s few yaml files. But no customize.yaml

Do I just create one there?

It looks like I need to add something to configuration.yaml - and maybe create a yeelight.yaml and reference it. But not sure how and where in the gully to add my goodies.

And then once added via a text editor, I guess? Will the lights appear somewhere in the UI?

4

You don’t see the light as discovered now?

Then you should use the manual method of adding the lights and add the parts like in the example to your configuration.yaml, the customize.yaml is only needed when you do see the lights automatically to change the name of the auto discovered lights.

5

No, sorry Burningstone - I haven’t done anything yet. I am not sure where to add the yaml:
# Example customize.yaml entry light.yeelight_color1_XXXXXXXXXXXX: friendly_name: Living Room light.yeelight_color2_XXXXXXXXXXXX: friendly_name: Downstairs Toilet

It says I must add it to my customize.yaml file, but I don’t see this file.

I only see customisations.yaml, autmoations.yaml and configuration.yaml

Where should I add this code?

6

Ignore the customize.yaml file and use the method described in the part titled " EXAMPLE CONFIGURATION (MANUAL)"

7

Thanks. I have modified my Configuration file, to now look like this:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml


discovery:
  ignore:
    - yeelight
yeelight:
  devices:
    192.168.1.92:
      name: Lounge Floor Standing```

But, after restarting Home Assistant, I am not sure where I should see this light appear. But I think I am doing it wrong. Is this the correct thing to do?
8

The config looks correct to me. On the page from the above link, scroll down a bit until you see a blue note, in this note there are some steps you need to do before you can connect the bulb to home assistant. Do this and then restart.

9

OK, all have LAN Control enabled.
Restarted Home Assistant - but not showing any bulbs. Well, I added one of 6 to the yaml file.
But none are showing.

Edit: hang on! It’s showing! Needed to click the … and select ‘Unused Entities’!
Right… now to see if I can control it.

10

Thanks so much for your help and patience, @Burningstone - I can control lights. No automation… but they work! That’s amazing. Thanks!

11

Glad it worked :slightly_smiling_face:

For automations check out these pages:

Or you have a specific automation in mind for which you need help?

1 Like
12

Thanks again, @Burningstone
The world of Automation is new to me. I’m trying to work out what my options are! :slight_smile:

I guess the first thing would be to switch on lights at Sunset. That seems to be a pretty standard way of getting into it. And pretty useful, because I used to use IFTTT, but as season change, like now, I’m constantly having to change the on/off times.

So, switching on at Sunset would be a pretty good start.

13

I suggest reading the pages I provided, and then I’d start with the Automation Editor. It’s easy to get started and your example should be straight forward with the Editor and you create the automation in the GUI. If your setup gets more advanced you may run into some limitations with the Editor, but then you should easily be able to change to text based configuration.