Hello,
I have xiaomi Yeelight bulb. I tried to connect the bulb to the home assistant. The bulb is connecting to the wifi and works great with the Yeelight app and mi home app. I enabled LAN Control option in the yeelight app to enable control via home assistant. than I checked the IP of the bulb in my router and than I added this to the configuration.yaml file:
# Example configuration.yaml entry
discovery:
ignore:
- yeelight
yeelight:
devices:
192.168.31.69:
name: Living Room
It’s the IP of my bulb. I saved the configuration.yaml and reset the home assistant but nothing happened. I checked in the entities if the bulb appears but nothing. and no light section in the main page of the home assistant.
I also tried this:
I had the same problem using the YLXD01YL model. My solution was adding the model type. I disabled the autodiscovery, like you did, because it was not automatically discovered and added this:
Oh one thing I noticed: The lamp was unavailable the whole time, after appearing in HA. So I rechecked if the LAN mode is enabled in the yeeligth app (it was not!) I was damn sure I set it in the first stage, but it seems to be lost. After that, the ceiling light was there and working - finally
I just installed HA and it doesn’t discover my Yeelight automatically, but I can access it with manual config. The problem is that right now the lamp it is connected to is still being used with a light switch, so the IP of the Yeelight changes every time it’s turned on (and I can’t set a fixed IP because my ISP wants DHCP disabled on my router)
I had similar issues, the discovery service discovere all my 70+ yeelight bulbs as homekit accessories.
What I did then discover all yeelight IP Addresses, reserve the mac address in the DHCP server.
And list all those IP ad yeelight devices in the yeelight.yaml
If you do it manually it works fine, but you have to keep in mind that if the yeelight accessory ip changes, you have to edit the config and reload it every time (you can simply assign fixed ips for the accessories to fix this, but I can’t )
You can set static IP address in your rooter interface. Most have this basic feature standard rooters IP is something like 192.168.0.1 or 192.168.1.1 if not start a DOS command prompt (cmd) and type ipconfig /all and make a note of the DHCP server address. Enter that ip into the address bar of your web browser and log in. Info may be on the back of your rooter.
My network was just stupid and I couldn’t assign fixed IPs, but now I configured a dhcp server with the AdGuard addon and I finally could do it (I suggest that if you have problems with your router’s (you can also use the standalone dhcp server addon).
(Basically I receive internet by radio and my antenna/router is managed by my ISP (I just had a personal router that was connected to it by LAN with no dhcp and forwarding functionalities enabled), so I asked them to disable their dhcp server, so I could use mine (they still manage the port forwarding, but I’m fine with that) (Yes, I know that I could simply turn back on the dhcp server integrated in my router, but I had the addon already installed and I find this one easier to access and to use (and I couldn’t set a different gateway (the antenna) on the router one).
At least I don’t have to worry anymore about IP conflicts (dhcp often assigned new devices at IPs that were set as static for others that were not connected at that moment) and I don’t have to wait for a fix to the integration (or the Yeelight firmware).
)