Out of curiosity, is it something as simple as needing to wrap the template in quotes? I may be mixing up my YAML with the Ansible work I’ve been doing, but I think you need to have templates double quoted like this in order to resolve the jinja2 properly: "{{ state_attr('light.etc', 'brightness') }}

I don’t think you need the quotes in the Templates section of dev tools but you do in YAML files. I could be wrong though, let me know if you try it.

Definitely use the state_attr() form over states.etc.etc form. I think there’s something about how HA handles startup that may mess with templates if you use states.etc.etc .

Props for finding the answer and sharing it!

This! Manufacturers were trying to lock people into their systems, just by different means. Reverse engineering a piece of low-level software (BIOS) so that you could run high-level software written for that machine architecture on different hardware was the main battle of the day.

Removed by mod

Removed by mod

Why not just not use the switch function? You can even “disable” the switch in Home Assistant so you can’t accidentally turn it off, and most of these sorts of switches have a setting for default (on power restoration after power loss) of on or off.

I had to downvote you to get the “total” (heart) to show up. You can see in the comment below yours that if there are only all up- or downvotes, it just shows that.

Yeah I remember using the Compiz cube on Ubuntu 8(?)

Don’t a lot of CPUs like Snapdragons already have “performance cores” and “efficiency cores” that the kernel has to be able to recognize in order to switch between them? This sounds neat but I’m just curious what’s different between these situations.