It was just a quick test because I had to go to work. At the ceiling4 and ceiling1 the setup remained on the selected level with the remote cotrol and the Yeelight app too, the moonlight on low level and the daylight on high level. After it I selected high level at the daylight with HA and called the yeelight.set_mode with service calling. In this case the moonlight stays on bright level. I tried to change the modes with remote control and I watched the change of sliders in HA, the modes worked well with the RC but the slider state didnāt change. I use the HA autoconfig with my yeelights,
nice, Iāll try to manually set the model. thanks!
I see lot of things are changed in 0.91.2, Iāll test ASAP.
@madrian Yes both issues, posted by you, should be fixed. Custom_component should also work without any problems. Also please report issues on GH ( https://github.com/home-assistant/home-assistant/issues ). Its easier to track them there
@krovachek Iāve tried to recreate this but cannot. You are using official 0.91.1 ? Can you write step by step, how to recreate that issue ? Without yeelight remote / or app. Only using HA. Please test on 0.91.2, as there are some fixes that might improve your problem.
I use the ofiicial 0.91.1 version of HA.
The steps are:
- I use the daylight to 10:00 pm on brightness level 80%.
- From 10:00 pm the night light automation is activated with set mode to moonlight.
The result was before platform change: moonlight with the previously brightness level setup of
moonlight. (If it was on 5% previously then remained on 5%)
The result now: moonlight with strong brightness, I have to decrease the brightness level with the remote control always. (I think the brightness level stays on 80%.) Therefore I have to call the light. turn_on service too with brightness level parameter too.
Iāll try the behavior of the lights ASAP with 0.91.2.
There is still problem with your custom_component/yeelight:
Without that it is working properly.
You also need to update custom_component code ( sorry forgot to mention ), for example from this branch: https://github.com/home-assistant/home-assistant/tree/378ad5015c89079e8f40b213f3cb6736ce5cc1b4/homeassistant/components/yeelight . There are no visible changes here, only code cleanups and refactor for future improvements. Iām using it as custom component for testing, it has all fixes from 0.91.2 included.
Cool, itās working now. 
Cool thanks for testing, please write hows that deadlock error. It should be also fixed.
Just to be sure: is there a form of a binary sensor for moonlight (or any other new moonlight support) in 0.91.2 or do you need the custom code by Michal_Ciemiega for that?
I donāt see any sensors for my 4 ceiling lights (YLXD01YL), which I have added manually.
I canāt reproduce this error, maybe it happened when I restarted HA?
Iāve tried with 0.91.2, it is working now 
@K-V-N You can set model to ceiling3, it should work and give you moonlight sensor. If you want to help testing, you can use that code Iāve pasted. I want to push it to 0.93. It has better moonlight support recognition. It wonāt need setting model for that. There will be version with optional separate light entities. I want to finish and test it more.
@madrian That deadlock error is somehow random for sure, with 0.91.2 fixes hopefully it wont happen again. There are some ongoing improvements in HA architecture, around importing libs. When its finished, this problem should be properly solved.
@krovachek Great to hear that, thanks for reporting back !
@Michal_Ciemiega Hi, I correctly understood u, right now celing model 1 is not support sensor of moonlight? But we are waiting this improvement in 0.93 of HA build? Andā¦ right now we can change model of this yeelight to ceiling3 and get moonlight sensor now?
@SoulAssassin Yes, you can declare light as ceiling3 for now, to get that sensor. Or if you want to help testing new code you can use as custom_component now. There is also version that create 2 light entities, one for moonlight one normal. They are interlock, when you turn moonlight light entity, normal gets turned off, same for opposite.
Oh, itās good to me, and I want to test it at my ceiling1 and HA 0.90.1, and I will test it. Could u please explain a little about custom_component, u mean itās a new yeelight code for future builds of HA or? Where I can get it to put in my custom section? Thanks.
If you install custom component, you will get 2 switch for yeelight, one moonlight and one for normal switch.
I understood this, Iām interesting of where I can get this custom component? Not clearly at all for me now.
Oh Iām sorry guys, I think u talks about this: https://github.com/home-assistant/home-assistant/tree/378ad5015c89079e8f40b213f3cb6736ce5cc1b4/homeassistant/components/yeelight
@SoulAssassin Thats the newest PR ( https://github.com/home-assistant/home-assistant/pull/22936 ). It adds opt in option to create 2 lights, for each ceiling light.
Thats the newest code from it: https://github.com/home-assistant/home-assistant/tree/1b7219be75967792e7c46dd324e7f9a461f91621/homeassistant/components/yeelight . You can download all files and put them in custom_components/yeelight to test it. It should also recognize all ceiling with, without need to specify model. I hope it will be merged for 0.93