The inegration when adding this to home assistant went fine and I dont have any issues adding it to exicting automations, groups, etc.
The only thing I have seen regartding this light is there is no selection (entity) for theme. I have some LiFX Z Strips that have this as pictured below:
However the LiFX Ceiling addition doesnt appear to have this entity, and it does make pretty extensive use of themes like the LiFX tiles do. Have I done something wrong or is there any way to add this? Any advice is welcome.
You haven’t done anything wrong: as I mentioned on Reddit, I’m still working on fully implementing Ceiling support. It’s the first device in a while that has changed the LIFX LAN protocol, so it’s taking longer than usual.
Also, it hasn’t been released in Australia yet, so I only managed to get one a couple of weeks ago from the lovely folks at LIFX in Melbourne.
I’m also trying to get some amount of support for the Uplight component too, which is proving to have more edge cases than I expected.
I’ve just submitted the first bit of Ceiling support by adding a lifx.effect_sky service call that allows as much customisation of the effect as is possible via the LAN protocol which is far more than the LIFX smartphone app currently provides. The documentation will be updated to include the new service once approved.
many thanks for your efforts on this! I will give it a whirl over the weekend and report back. Not sure why i didnt get a notification for this sooner.
They’ve been approved and merged, so I would expect them to show up in an upcoming beta with GA in the following month.
Next up will be theme support for Matrix devices via a select entity to match the functionality already provided for multizone devices. I’m working on improving the theme painter for this so that it is as close in appearance to themes painted by the LIFX app.
Once that’s done, I’ll focus on providing the ability to control the downlight and uplight components of the Ceiling via seperate Light entities. This is the most complex part due to the way in which the uplight is implemented at a protocol level and has the most edge cases that need to be considered and addressed, which means I still don’t have even the vaguest idea how long it will take to develop.
It’s possible, I just have to find the time. Personal stuff is conspiring against me right now, so I don’t have a lot of free time. I was hoping to look at it over the break, but am currently dealing with banks and mortgages and divorce laywers, etc so my focus is understandably elsewhere.
Sorry to hear about your divorce, @Djelibeybi. I’m going through one myself and understand what an emotionally and logistically crushing experience that can be. Just know that all of us appreciate the hard work that you do. I have 31 LIFX devices in a one bedroom loft apartment and I don’t know how I’d manage without local control via this integration.
And the multi-entity function sounds rad. I think it will make things wayyyyy simpler for my outdoor string lights and my 26" ceiling light. I have next to zero coding experience outside of yaml and the statistical analysis software I use at work, but if there’s anything folks like me can do to help, let us know.
That really sucks. I hope you get through it as quickly as possible. These lights will be here when you have a minute. Like @jayceegee said, if there is anything we can do to help, let us know. Best regards man.
Quick poll: how would you feel if I added two new actions, e.g. lifx.set_uplight_state and lifx.set_downlight_state instead of creating two new Light entities?
These actions would require you to provide all four HSBK values when turning on the component but not when turning off.
I would also add two new binary sensors to the Ceiling itself that indicate whether the uplight and downlight are on or off, for use as conditions for any action that uses these new actions.
This is significantly easier to implement as most of the edge cases are caused by dashboard widgets not sending the correct values or incomplete values. Using an action eliminates almost all of the edge cases and would still allow you to implement Adaptive Lighting on just the uplight, for example.
any enhancement or added functionality you can add is getting a vote from me. That would be a nice thing to have as well. The only effect or scene i really even care about is the one that is clouds and I can probably create a routine or something and have alexa and lifx hash that out amongst themselves anyway. Having control over the upper and lower light seems more important and useful to me. This is a welcomed addition imho.
It would not be directly controlled by Adaptive Lighting, but rather you’d need to setup a second action that used the Adaptive Lighting values and called set_uplight_state (or set_downlight_state) with those values.
I generally recommend implementing Adaptive Lighting using lifx.set_state for LIFX devices in general.
I’ve got this all working now, so what I might do is create a custom integration installed via HACS that adds Light entities for the uplight and downlight as well as the proposed actions and sensors so that folks can kick the tyres for me.
This means I can give folks something to use without having to modify either aiolifx or the core integration.
I’d be happy to test with you. As a side note I use Adaptive Lighting directly with ~100 lifx bulbs with no issues, so I’m curious why you recommend using lifx.set_state for it?
I’m not a fan of Adaptive Lighting’s group handling and the fact that it keeps turning bulbs back on when I want one out of however many off at this moment. Instead, I use its values and I run lifx.set_state to keep all the bulbs at the same color temperature, but I control the power separately via motion sensors, LIFX Switches, time of day, etc.
Took me longer to get here than I expected, and as expected, it only really works via light.turn_on with at least brightnessand either hs_color or color_temp_kelvin set.
Trying to use a dashboard card and most often you won’t get a response, because Home Assistant hasn’t sent a color or brightness value, so the zone is “turned on” at zero brightness. If someone wants to make a dashboard card that always sends all the data, that would be peachy.
I should have something installable on GitHub in a few days. Needs to be cleaned up a bit more first.
