Xiaomi smart bulb integration
I ordered one, but it is 220V so I will have to try again.
@herf I keep my fingers crossed for your order :P !
In the meantime I am still looking for "plug and play" solution to use Xiami LED bulbs as real life f.lux.
I count on you, dear programmers!
In my email I got message that somebody posted here of PM'ed me...
But I don't see this in current topic. Why has it been deleted?
I repost it.
Andrew Kotalik last edited by
@AtomekTomek Does this integration work?
I'm about to pull the trigger on a bunch of YeeLights, and if this works I'll be ecstatic!
Having f.lux inteface with any/all smart lights would be an amazing thing!
To be honest, I've just bought my first Xiaomi bulb.
I'll try to use before mentioned manual, but I've never programmed :P
Any help is welcome!
I've received my bulb. Now there is time to understant this...
that is cool!
Has anyone been able to follow advice posted there:
I'm still fighting with Python.
markussl last edited by
@AtomekTomek After some time screwing around with python, i managed to get it working with no prior experience. I can try to help you if you have any problems.
powerfons last edited by
@AtomekTomek I also got it working, I can help you if needed, it's a 10min process if you are familiar with the tools!
Hi there! I also ordered a Xiaomi RGB light bulb, because of the price. Now I've read, that there is no direct way at the moment to keep it synced with f.lux :( And I am not familiar with Python and those stuff...
How did you get it to work @markussl and @powerfons ??
Thank you for your help!
Well, it seems there is development for integration with f.lux ;)
At least it's a beginning :thumbsup_tone2:
Our new beta has yeelight support, for lights that support their LAN API.
Our new beta has yeelight support, for lights that support their LAN API.
I'm using the betas for quiet a while now.
Could you please tell me, how to enable the support for YeeLight?
I've already checked the box for YeeLight support, but it didn't work.
Which kind of light do you have?
Some of them I've tested don't seem to support the LAN API (only work through cloud), but it's more likely we have a bug...
We have tested mainly on the Bedside Lamp, which is newer and works very well. It is one of the few that has 110V support so we can test it - unfortunately the 220V models do not seem to communicate very reliably when run at 110V in the US.
If you are comfortable with Wireshark we could see if your bulb is responding to the discovery protocol (the first step) - it is port 1982 UDP (sort of like UPnP but on a nonstandard port).
Also you should know that the LAN protocol we're using (provided to third parties) is not the same as the cloud-based system that the yeelight/milight seem to use in their own apps. So there may be bugs in older lights with the LAN protocol, and maybe they would be fixed in a firmware update, but I'm not sure what should work and what should not.
@herf Hi, maybe I should have been more patient and more precise...
It just works now:thumbsup_tone2:
Don't know, why I didn't see it yesterday.
I don't need extra stuff or another URL.
Does it affect all connected lights at once?
Good to hear it! :) :)
Alexx last edited by Alexx
@herf :grinning: What about my question? Since I use no URL, will f.lux process separate
lights as one?
@Alexx right now it knows about each bulb but doesn't have UI for separate controls yet.
@alexx How did you make it work? I have the same issue as you do here.
@alexx Oh so i do need to use that fluxee thing ? I thought it was already implemented into f.lux.
@odyseus At first you could try to insert the URL in f.lux, which you find in the fluxee description.
@alexx Still doesn't work :( do i have to launch the fluxee.exe each time i start my computer ?
BenBen last edited by
I just bought a bulb Yeelight RVB (YLDP06YL).
I was worried that it might be difficult to get it working with f.lux but it really doesn't.
It doesn't need the Python script from David Ramiro (https://github.com/davidramiro/fluxee). Maybe it was needed before, i'm using f.lux version 4.76.
Here is what i've done :
Install the bulb, install the software on the smartphone (Mi home + Yeelight).
You might not need Mi home, i didn't test without it.
Get everything works between the app and the bulb.
Then enable Lan control in the Yeelight app.
For that, David Ramiro has made two screen capture who explain very well what to do (David if you read me, i hope you don't mind using your links here) :
On f.lux, on the menu "Options and Smart Lighting..." then "Connected lighting", check "YeeLight".
It works perfectly for me, i hope it will be the same for everyone.
poxin last edited by poxin
@benben I just picked up some Yeelight's that work fine over LAN using the above github program (fluxee). Unable to get it working via flux directly however. Flux version 4.78 -- are you able to test that a connection is working by manually changing the lighting in flux? It should be pushed and update the bulbs at the same time right?
The python program works flawlessly, but would rather not have an open cmd program running in windows all the time.
@poxin Have you try to quit f.lux and start it back again? It did work for me ~ I will see tomorow if it needs to be turn off and on every evening because this might get annoying.
rTrage last edited by
@alexx That worked for me! Thank you
John_Doe last edited by John_Doe
My version 4.84 program also does not see the lamp. I did a complete reset of the lamps and reinstalled the program with rebooting the computer - the lamps simply ceased to be detected.
Previously, the program version 4.84 could detect both of my Yeelight. But then I changed the lamp server in the Android application, after which the f.lux stopped seeing the lamps. Therefore, I changed the server back to the one that was selected earlier - but the suite still doesn’t see Yeelight.
Of course, the developer mode is on in the lamps and I can control them through the LAN, but f.lux still doesn’t see them.
John_Doe last edited by
@john_doe Now I tried the program JeeLight, which is also able to control YeeLight lamps via LAN.
If I add the IP address of the lamp manually, the program easily detects any of the two lamps.
And if I use automatic search - the program fails to detect any of the 2 lamps.
Apparently, something is wrong with the lamp search algorithm.
stbitw last edited by stbitw
Good morning, everyone :-)
I don't speak English so I will use an online translator, please take this into consideration and forgive me if my messages are unclear.
I use the beta version of f.lux and I have several Yeelight luminaires.
With fluxee everything is fine, except that I have to use it together...
Since a few versions it is possible to check the "YeeLight" box in the f.lux options and it works very well.
The problem with this method is that all Yeelight luminaires in the house are controlled by f.lux without distinction.
One solution would be to disable the LAN option on the lights I don't want to control with f.lux but at that moment these lights will no longer be controllable from my home automation server.
The ideal would therefore be for us to define the IP addresses of the luminaires that must be controlled in the f.lux options (or in a config file, as in fluxee).
It would also be interesting to be able to choose a power factor for each luminaire in order to uniformize the illumination because according to the models they do not illuminate in the same way.
192.168.1.101:50 (50% of the f.lux order for a powerful ceiling light)
192.168.1.102:100 (100% of the f.lux order for an RGBW bulb)
192.168.1.103:80 (80% of the f.lux order for a desk lamp)
I hope that these evolutions are possible and that they will appear soon ;-)
Please note that I am available to perform tests if necessary.
coendeurloo last edited by
It would also be nice to set a minimum and maximum color temperature for the Yeelight...I really don't like the intense blueish tint it gives during the day, even though it's set to 'quite a bit warmer'
Yes thanks we should use the same setting. I think I forgot to do that because it wasn't as bad as Hue but it's still important.