There’s a light model I own that appears to be 500 Kelvin below where it should be. I wanna setup an automation to bump the color up 500 Kelvin when the color temperature is changed.
To do that, I need a way to get a list of all devices that have that model name.
Then I can do some {{ trigger.SOMETHING }} to check what changed and bump only that light’s Kelvin value.
I read a thread on a similar topic. It’s close, but not exactly what I’m looking for:
Is the model name an attribute of the light entity?
Nope, it’s on the device itself.
Replace MODEL_NAME; and if you know all the lights are in the light domain, replace states with states['light'] for better efficiency:
{{ set(states
|map(attribute='entity_id')
|map('device_id')
|reject('none'))
|select('is_device_attr','model','MODEL_NAME')
|map('device_attr','name')
|list }}
Explanation:
set() (simplistically) builds a list without duplicates.device_id corresponding to every entity on the system, with null entries (device-less entities) removed — this gives you a list of all device IDs.model attribute corresponding to MODEL_NAME.Thank you so much! That does get the devices.
Is it possible to use that in a trigger?
I’m currently checking to see if color_temp_kelvin had a change, but when trying to get that template as the entity_id, it errors.
Not really. You’d be better off generating a list of entities within those devices and hard-coding that list into a state trigger with the attribute specified, although you’d need to make sure that the correction didn’t re-trigger the automation.
Alternatively, create Template Lights for each that handle the colour temperature adjustment.
I read about Template Lights, but I’m not sure I understand. Could you summarize what it is or does?
It’s basically a virtual light where you build up what it does from an on/off, brightness, colour temp perspective.
You can get it to transform the colour temperature both going out to the real light and coming back from it. You’ll have to check how to read and write the temperature to your lights, which can vary by model, but something like:
[...all the other bits of config...]
temperature_template: "{{ state_attr('light.your_light', 'color_temp') - 500 }}"
set_temperature:
service: light.turn_on
target:
entity_id: light.your_light
data:
color_temp_kelvin: "{{ color_temp + 500 }}"
Is it possible to get a list of all lights of a certain type and create a template for them?
The config you sent has entity_id in it, but it would be a list of them. Is that possible using the template that gets a list of all those specific light models?
I’m not clear what you are asking for.
In the post you marked as the solution, I provided a template that lists device names that have a specific model name.
Are you now wanting a list of light entities that are associated with the devices in that list?
My bad, I’m getting lost between threads. I’m good. I can swap light.your_light to that template of entity ids.
I still don’t get how to use this. I’ve read that Template Light page multiple times, and I don’t see how this is related. The Template Light page shows how to setup theater lights, but not how to say which lights are theater lights.
I’m also not sure if most fields are optional (passthrough), so I can focus on only adding 500 to the color temp.
Are you saying I add this to the bottom of configuration.yaml?
set_temperature:
service: light.turn_on
target:
entity_id: THAT_BIG_TEMPLATE_TO_FIND_ALL_LIFX_A21
data:
color_temp_kelvin: "{{ color_temp + 500 }}"
Absolutely not, no. The theatre light in the docs is just an example of its use. You’d need to set up all the bits of it you want / need to replicate all the functionality of your existing lights. The final example at the bottom of the doc might be more useful to you.
It’s not “passthrough by default”, you’d have to declare all if the get/set templates/actions; and if you want individual control over those lights you’d need a template light for each one.
It’s not a quick or easy solution, but would get you what you wanted.
Ah, so if I want to say “all A21 lights”, it’d still need to setup this template for each one of them or each one in a specific room?
You can certainly set up a template light that groups them however you want, so long as you recognise you won’t have individual control over them.
Just try it for a single lamp to start with.
This is the automation:
This is also the first time I’ve used the “And if” section. I always use “Choose” and have to go through this complicated UI. It’d be neat if it split that in 2 and had a “true” and “false” side like how you visualize the pipelines.
Either way, that’s the code I had. I currently have this disabled as I do some testing. It appears this issue has been fixed which explains why the lights have looked so white recently.
