yes, like that
Thnx for the link, I will wait for that then.
I have restored to 0.114.4, so they’re working again.
That’s the “solution” at the moment…
Hey there! I am just trying to install an Yeelight light bulb and it does not work and I found this post.
I have set it on a VLAN as well.
I am trying to figure out how to set it and if the problem is related to the bug you guys mentioned.
Btw, do you happen to know a good tut on how to install this? I saw so many different ways and none of them work.
Thank you so much!
The PR solving the VLAN problem seems to be merged, finally. Let’s keep fingers crossed that this will make it into one of the 0.117.x releases.
If your Yeelights and HA are in different vlan, then, use 0.114.4 version. At the moment, it is the last version know to work.
As @ffm777 said, it has been merged and should be in 0.117.x.
I understand now. So this is the problem with the last versioning. I switched it to the same LAN and it works
Thank you so much!!
Any news regarding this issue?
I’m running 0.117.0. My home Assistant is installed on a VM Unbuntu inside a docker. And that is bridged to my LAN 192.168.200.0/24. My IoT stuff are located on a different VLAN 192.168.199.0/24 though. And well I can’t add my yeelights back to my home assistant. Everything was working fine in 0.114.4. I have removed the yeelight entries from my configuration.yaml file. I get the notorious “Failed to connect” when trying to add the lights manually in the integrations page.
Well, not really 
The fix has been merged into the dev branch. So, it should be then merged into the prod branch in an upcoming 0.117.x. When? no idea. Stay in 0.114.4 is the only option in your setup.
Hasn’t made it into 0.117.1. This is getting nerveracking… I’m also still on 0.114.4…
Thanks mate. I’ll revert back to 0.114.4.
Is this confirmed? My devices are all in the same VLAN and I just retested to upgrade HA and discover all as well as trying a Yeelight IP directly but either way it doesn’t work.
2020-11-02 08:00:01 ERROR (MainThread) [homeassistant.components.yeelight.config_flow] Failed to get capabilities from 10.10.1.104: timeout
What is confirmed?
If HA and yeelight are in the same VLAN it works.
If they are not it doesn’t.
Which HA installation are you using? If your are using HA container, then it must be in “host” mode and not bridge.
Otherwise, I am using 0.116.x and it works…
Is it confirmed as of only different VLANs don’t work. But you just answered that. Then idk what my issue is that it doesn’t work for me… The HA setup is ofc since always running host mode.
Anyone else with Unifi has/had the same issue?
Experience of a few users seems to lead to this conclusion. So “confirmed”, not really but almost
I am not using unify.
There’s a new release out. 0.117.2. Anyone tried it yet? Does it resolve our issue with not having yeelights working if they are on a different vlan than HA?
Here’s what’s listed in the release notes:
Release 0.117.2 - November 1
- Bump pwmled to v1.6.6 (@soldag - #42607) (rpi_gpio_pwm docs)
- Fix Fibaro HC2 climate device missing temperature (@airthusiast - #42627)
- Fix geo_rss_events import statement (@exxamalte - #42629) (geo_rss_events docs)
- Bump pycfdns to 1.2.1 (@ludeeus - #42634) (cloudflare docs)
- Make sure Tasmota status sensors are disabled (@emontnemery - #42643) (tasmota docs)
- attempt to renew subscription immediately to stop endless loop if it fails after setup (@hunterjm - #42651) (onvif docs)
- Bump up ZHA dependencies (@Adminiuga - #42679) (zha docs)
- Fix canary camera entity inheritance (@ctalkington - #42691) (canary docs)
- Use pylutron_caseta 0.7.1 (@mdonoughe - #42701) (lutron_caseta docs)
Since nothing is mentioned in the release notes, I would assume it is still not working if the yeelights are in a different VLAN.
Yeah I’m thinking as much myself. I was just curious if someone actually gave it a try. 
Did give it a try. Yeelight on different vlan still not working for me on 0.117.2
Thanks for letting us know. 
It’s a shame it’s still not in the release. 