Right after that ive notced that my lamp now cannot be controlled via LAN control by HomeAssistant.
Ive opened Yeelight App on my smartphone and saw that LAN Control is DISABLED for BSide2. But still enabled for all of my other yeelight devices. And if I click on toggle to enable Lan Control - it doesnt move at all, and I cannot turn on lan control anymore.
Also - It became very unstable to control BSide2 via Android app. Delays is terrible!
Ich habe das gleiche Problem mit meiner Bedside Lamp2 nach Update auf 2.0.6_0041.
Bei meiner E27 RGB kann ich LAN control weiterhin aktivieren und es funktioniert auch die Steuerung darber. Bitte schnellstens ein Downgrade oder Bugfix fr die Bedside Lamp2 anbieten!
Yeelight
DOWNLOAD 🔥 https://urllie.com/2yGaYq 🔥
Good morning, I have the same problem I have upgraded my
nightlight 2 and the Lan mode has disappeared with the consequent disorder of not being able to integrate it into my Jeedom system.
Is there any solution to return to be able to have the LAN mode.
My id is 1911724375.
Thank you very much.
Unfortunately the Yeelight Alexa skill only connects my E27 RGB bulb, but not the bedside lamp2. The same with the Xiaomi Alexa skill. For me there is absolutely no workaround to control the bedside lamp2 in my smarthome. Only with the Android app or manual.
Add a window to the application, that when user turn on LAN control mode, it will pop up a window warning that by turning on this mode the user assumes all responsibility for the risks, add a window with the Agree button, which will say that Yeelight is no longer responsible for any risks, add a window with the Agree button, which will say that Xiaomi is no longer responsible for any risks, and then turn on LAN control. I am ready to confirm at least 10 such windows on each lamp, but for LAN control to work. I will take all the risks.
I am not sure if my case is in the same problem as my V2 color bulb could not connect to the Wi-Fi network it was stuck at 25% complete then failed. I am using iPhone 7Plus and iOS 12.3.1 and I picked Singapore server, please advice.
i just bought this item,
and its cant connect to my iphone
can u guys please help,
and i try both mi home anda yeelight
its stuck adna 25 % and mi home just failed ,
so dissapointed in this product
Hello, I'm trying to do the same. I saw that it's possible but I haven't got.
I have a Raspberry Pi 3, with OSMC, and the last Hyperion. I can enter to the web config in port 8090, and it find my two yeelight bulbs but they don't light.
@Iam Tobe I still need to do some documentation on Yeelight.
Nevertheless, after using the Wizard the Yeelights should work. Sometime you first need to restart hyperion...(for that we have an issue already logged).
As it looks like that the configuration did not work at your end automatically.
Would you mind activating the debug log mode (in the UI System->Log),
plus then start the yeelight wizard and do the config again?
Thanks for your support. I have activated the debug mode. When I enter in the Yeelight Wizard, this is the appearing window:
The Identify button don't produce any effect, and both light and ambilight don't work. When I put the bulb IP in 'Network devicename', it does work without problem. Though the majority of movies are continously blinking (losing the HDMI source). Then, I change this parameter in 'Platform Capture':
Height: 64
Width: 64
Capture frequency: 30
It is strange because the name that is automatically assigned to the strip (the only one bulb with LAN permission just now) is 'conf_leds_layout_cl_entire'. But yesterday, in my router, it has the name 'yeelink-light-strip2_miap7fe2'.
Yes, this is what I expected to get back in the UI. If you see my screenshot, it exactly follows the same logic of the prefix.
Sometime it helps,if the lights are longer in the network...I still have not figured out the logic....
I might need to fall back to configure IP-addresses, which I currently avoided. In case an IP-address change, users complain that lights are not working...
And not everybody is able to configure fixed IPs in their routers.
I have a Yeelight bulb in my room, so I've created a new instance and launched the Wizard.
It has found my bulb instantly, and with the same name as defined in my router.
I've set up its position, saved settings and ambilight has started instantly on the bulb.
It won't help you debugging, I'm aware of this, but it shows that sometimes it can work flawlessly
PS: my bulb has a static IP address on my network.
I tested this and it's working great on my *nix box. However I'd like to run it from a docker container so I can use it on Windows. Screengrabber -> Hyperion -> WLED.
Is it possible to configure this to advertise a different IP? The problem on docker on Mac and Windows is you can't do host networking, so when it turns on music mode it gives the Yeelights a private docker network IP in the 172.x range
Hi everyone, in this case, you need to contact Yeelight support so that they can investigate what happened, if they need help investigating they must contact us via build@smartthings.com with the logs from their cloud.
For the first screenshot, the error message must be in the logs on the Yeelight server, normally related to a requestId that we can use to track what happened, references to How works schema integrations
The way that devices are integrated with SmartThings is different, in the case of schema integration after the access is granted
1- Smartthings will send a discovery request
2- The partner needs to respond with the device information
Hi there,
same problem here, but I can figure on what ist going on.
The first time I linked yeelight with smart things, I used the wrong yeelight account. (just signed in with google). My lights are regristered to another account. Now, when I delete yeelight integration and try to link it again, smarthings gives me the 404 Page and links to the first linked account again by itself. So I cannot link the account with my regristered lights.
Is there any chance to delete the data, that is cached in my smarthings account or watsoever?
Thx a lot.
Answering my own questions, yes, incorrect app, the Yeelight came with instructions to download the Mi app, searching on the web discovered that an app with name Yeelight is available, installed, changed lan setting, discovered on HE, working!
Hello VJV........perhaps u can assist. I just received my Hubitat and I'm trying to discover a Yeelight Multi-color RGB light bulb. I can control it through my iPhone app, but not discoverable in HE. You indicate you were using the wrong Yeelight app. I installed the Yeelight app from the Apple app store, but it does not have a 'LAN Control' button like ur photo. How/where did u download the correct app. Thanks!!!!!
Hello VJV Thanks for the assistance; it's much appreciated. Sorry to take so long with a response, but I was traveling back home after the holidays. The problem, as it turns out, is this: when u add a device, there are two lightbulb icons. I picked the one that looked like the Yeelight I purchased ,i.e., the bulb with the white bottom. Unfortunately, that choice does not give u the option to do LAN Control. So I deleted the device and re-added it using the lightbulb icon with the dark base. Bingo!! Now have LAN Control and the lightbulb shows up in the HE device list. Problem solved. Again, thanks for your quick responses.
pulling out my hair over here...Hubitat will not discovery yeelights withing the yeelight integration app. I have tried unistalling lights, rebooting hub, and unistalling integration app. WTF am i doing wrong over here? Alexa had no problem finding these lights
The Yeelight integrationIntegrations connect and integrate Home Assistant with your devices, services, and more.[Learn more] allows you to control your Yeelight Wi-Fi bulbs with Home Assistant.
Adds another entity, to control nightlight mode (for models that supports it). Currently, only light is supported. It will create 2 light entities, one for normal light mode and second for nightlight mode. They are mutually exclusive.
Starts a color flow. Difference between this and yeelight.start_flow, this service call uses different a Yeelight API call. If the light was off, it will be turned on. There might be some firmware differences in handling complex flows, etc.
Much time has passed, but support from inside the application is not implemented. Please tell me, is there any hope that a connection will be established between the yeelight and sleep as Android lamps?
If someone differs in their opinion and wants to try it on their own, we have an open API and offer any help he might need.
You should also be able to trigger your Yeelight from Sleep as Android using IFTTT.
Thanks for the info! Connectivity issues are definitely not the problem, my tests are done with both phone and lamp connected to wifi, router in the same room. I just tested again, and where sleep_tracking_stopped does turn the light on, alarm_alert_start does not. 152ee80cbc
time zone data download failed