Dynamic presets & default state

[stashymane]

Describe your core improvement

I would like if there was a way to create a dynamic preset or default state, which an automation could keep updating regardless of whether the value is used or not. If e.g. a light bulb is switched to that preset, then the light bulb will follow it every time it's updated with a smooth transition. Once the user controls the bulb manually, the bulb stops updating values from the preset until it is applied again.
Optimally it should be possible to latch onto properties separately, so that one can, for example, keep the color temperature of a light bulb automatic and only adjust the brightness manually, although I am not sure how viable this would be UI/UX-wise.

In addition, having the ability to reset to a default preset would make this entire use-case super simple - if you adjust the state manually, a small reset button appears, which puts you back into that dynamic preset with one click.

Current limitations

I currently have a circadian lighting automation that manages my house's light bulb brightness and color temperature, and it's my favorite thing ever, but there is no way to visualize what the current state is - whether the brightness or color temperature are overridden, whether a certain light is controlled by that automation, or whether the automation is even running at all. This makes automatic lighting unintuitive for less technical users.
I could set up a helper switch that controls whether the automation is enabled for a certain light, but I would have to create 2 helpers for each light bulb or bulb group and create a custom dashboard to link which switches control which lights, which is difficult to manage.
Also, making a feature like this in an automation or blueprint currently takes a lot of work, which is why the preferred way for most HA users is just installing the Adaptive Lighting integration via HACS. Once dynamic presets are implemented, this becomes a very simple template.

Technical benefits

This feature would make automation-managed entities a lot more obvious and predictable to users, as well as simplify some blueprints. Not just for lighting, but other entities one could want to control automatically most of the time, and only override in certain situations, like automatic shutters, security systems, etc..

Additional context

No response