Yeelight - 1.4.2_0061

Configuration
1

Updated my Yeelight bulbs to firmware version 1.4.2_0061 and now then don’t show in HA at all.

Is a firmware downgrade possible?

2

I have done the upgrade as well
All is working well
Please check in the app if your local communication protocol is turned off
I happened with me quite a few times.
Also check if the static ip address is set for the lights.

3

Well LAN control is on. I will check static IP’s now. Thanks pal.

4

I’ve checked every bulb (4 of them) and every one has LAN control enabled. I toggled it off and back on, just to be sure.

My bulbs did not have static IP’s. This never seemed to matter before but I have given them all static addresses via my routers address reservation panel and rebooted Hass.io

Still not showing…

5

What do you have in the config.yaml file
I have this

light:

  • platform: yeelight
    devices:
    192.168.1.64:
    name: Lamp Shade
    192.168.1.68:
    name: Coridor
    192.168.1.66:
    name: Bedroom
    192.168.1.67:
    name: Entry
    192.168.1.73:
    name: Master Bedroom Light
6

I never needed to specify the IP’s in the past. Hass.io just automatically recognized the bulbs and showed them in the panel. I’ve added them to my config.yaml, rebooted Hass.io.

Still not showing up. This is quite a head scratcher :slight_smile:

Here is my config:

light:

  • platform: lifx
  • platform: yeelight
    devices:
    192.168.0.9:
    name: Boys Lamp
    192.168.0.6:
    name: Back Light
    192.168.0.4:
    name: Office Light
    192.168.0.89:
    name: Front Light
7

Ok, I have no idea what has changed but they now appear under a separate panel. Looking in States under Developer tools the names of the bulbs have changed. Eg from yeelight_white_f0b429a92f5f to the name I have given them in the config.yaml.

Anyway, all sorted now. Thank for your help

1 Like
8

It would do as that’s what you called them. Discovery just picks up whatever the network broadcasts is name as, personally consider discovery to be a beginner’s bodge tool to get you started, set things up manually and turn it off, life will be much simpler.

9

Upgraded from 0.59.2 to 0.65

Prior to upgrade, I had all of my Yeelight bulbs defined in configuration.yaml by IP and assigned a name to each.
After the upgrade, I still have entities with the names I’ve assigned - but there are also entities named ‘Yeelight_rgb_’ for each of them.

How do I get rid of the auto-generated entities?

10

Comment out discovery from your configuration.yaml

11

Thanks for the response - but that’s exactly what I did NOT want to do.

Discovery is still useful for many devices and any new devices even though it currently causes a problem with Yeelight lights.

Here’s the solution I received on another thread about this:

# Discover some devices automatically
discovery:
  ignore:
    - yeelight

That disables discovery for Yeelight devices, but leaves it enabled for everything else.

Simple and elegant - but nearly impossible to find on the HomeAssistant web site. Does not show up in search results for “discovery”.

12

It’s in the docs;

13

Great tip. Thanks.