Yeelight Homekit issue

Third party integrations
,
5

Check out my post, this is what got the strip working for me again after the upgraded firmware.

6

Shaun,
thanks for the reply. this works also for me

1 Like
7

Hi @MaikaiLife,

I recently bought a Yeelight Strip (yldd04yl) and tried to add it to home assistant. I got it connected to the Yeelight app, updated, but i can’t seem to get it to home assistant. I can see it being auto-discovered, but having the same issue with not having a homekit pairing code.

My configuration:

configuration.yaml

discovery:
 ignore:
    - homekit
    - yeelight

yeelight: !include yeelight.yaml

yeelight.yaml

devices:
  192.168.1.94:
    name: kitchen_strip

Am i missing something, or any idea why it can’t be added?

Thanks!

8

I think you’re missing device type after your device name. You won’t be able to use Homekit if it didn’t come with a code, which is fine since it works independently of Homekit with the standard yeelight integration.

9

Do you mean the model name? I understood it as that was an optional setting according to https://www.home-assistant.io/components/yeelight/? And the yldd04yl doesn’t have a model name as of yet…

Yes, exactly. My idea was connecting it to home assistant and then use Homekit integration to forward it to homekit.

10

It’s possible that additional config line is optional, I was just looking at variances between our configurations. However without a Homekit number there is no way to use the Homekit integration. You could try the default Homekit id, which is think was 111-222-333, but it never worked for me.

https://www.google.com/url?sa=t&source=web&rct=j&url=https://forum.yeelight.com/t/topic/8859&ved=2ahUKEwjk6quQuO7kAhWBg-AKHbVaBzUQFjAJegQIBhAC&usg=AOvVaw3DFUEHERqWpPgqRdFk3kku

11

Same over here: Ignore Homekit Accessory?
Working with manual configuration, but still discovering Yeelight as HomeKit device.

…and “- homekit” doesn´t seem to be a valid ignore option within the discovery integration: https://www.home-assistant.io/integrations/discovery/ :roll_eyes:

12

For me it’s not working anymore with the latest Yeelight update.

I tried:

  • Restarting the LED Strip
  • Checked that LAN control is enabled
  • Tried to remove and readd the configuration my configuration.yaml (see below)
yeelight:
  devices:
    192.168.178.130:
      name: Lichtleiste Bad
      transition: 1000
      model: strip1
      use_music_mode: False #(defaults to False)
      save_on_change: False #(defaults to True)

Still does not work. I’ve also got the message that I can connect it trough HomeKit but it does not appear anymore. Device shows up as “not available”.

13

Same here.

When electrically switching off/on the bulbs they re-appear as available in HASS but that doesn’t last long…

I tried to control my yeelights using IFTT but that was a mess.

An update -2.0.6.0065- is scheduled to be deployed next week… I’m just gonna wait for it :-/

My WAF has really decreased since last week, hopefully I’m using yeelight v1 for the toilets and the bathroom !

14

Hi All,

My lights are still working and have been working since I re-did the config in HA build .99.

Here is what I have in my configuration.yaml

yeelight: !include yeelights.yaml

Then in my yeelights.yaml file

devices:
  192.168.86.203:
    name: Master Vanity Glow 
    model: strip1

I have the led strip with the following firmware.

2.0.6_0063

I can control the lights fine with Home assistant, however ever time I boot up home assistant the auto-discovery finds it as a “Homekit” device, which I just ignore.

image

image
image725×165 12 KB

15

I’ve added " discovery | ignore | -homekit " in my configuration.yaml and I’m not prompted by any discovered homekit yeelight bulbs.

But like I said (I’ve re-tried this morning), after few hours my bulb come “unavailable” and I’ve got to plug them off/on to be able to control them back in HASSIO.

I’m using homeassistant 0.100.3 so maybe the issue come from that…?

16

I have the ignore also for homekit, but it doesn’t seem to work.

image

I’m guessing your issue sounds more like a networking problem, considering you have to turn them off/on again.

Do the Yeelights have a fixed IP, you might try that and make sure it’s not conflicting with anything else in your network. I have ha .100.3 and mine seem to be working flawlessly.

17

I have similar problem since I updated my yeelight bulbs they aren’t recognized by HA anymore. They work flawlessly with the yeelight app. I’ve tried auto config/ manual config/ disabling/enabling Lan for the bulb. I’ve tried unplugging them and replugging them. So far nothing works. I’m on 100.3

18

Mee too using 0.102.3 on Docker
discovery ignore option ignore “homekit” (its funny hahaha)
Im going crazy with xiaomi lights… on discovery enabled, show one light (of 3) , discovery disabled, put the light manual on configuration, dont work… T_T

19

If anyone is still having problem with your Yeelight/homekit constantly showing up in persistent notifications panel, I was finally able to fix it by ignoring yeelight. Ignoring Homekit did nothing for me.

  ignore:
    - yeelight
20

Did you get this sorted? Having the same issue.

21

Same problem!

22

Not sure if anyone is still having this issue with being unable to ignore the homekit discovery.

image
image1606×364 6.6 KB

As I recall this was fixed in release .104

23

Hi guys!

Just writing to confirm that the manual configuration proposed in https://www.home-assistant.io/integrations/yeelight/ solved the home-kit discovery issue for me.

This is what I have in my configuration.yaml:

discovery:
  ignore:
    - yeelight
yeelight:
  devices:
    192.168.1.137:
      name: luz mesa
      model: RGBW```
24

Hi @Quercus,

Thanks for the reply, this should also be fixed now based on version .104.

Cheers and welcome to the community!

1 Like