Greg Badros

You mean just a single per_time? Or "over_time" like you used in your example? With "max" as the other config option? With short-circuiting sequential-evaluation semantics, I don't think these compose...

Okay, I propose just: ``` condition: rate_limit tag: camera_notify limits: - max: 1 per: second - max: 10 per: minute - max: 50 per: day - max: 7 per: '0:15'...

Thanks for the questions, Martin! First the easier part... the day/minute/hour are just constants meaning '24:00', ':01', '1:00', etc. While they are units, they're an abbreviation for "1 day", etc.,...

I'm leaning towards "b" as that seems simplest. Any feedback?

Good point; I hadn't thought about the startup costs. I'll do without the tag, and instead add an arbitrary condition: guard to notify group -- that, then, can be the...

Anybody have thoughts on this? It seems like a problem for all lights that have color or color temperature capabilities. I'm open to just hearing ways that folks mitigate this...

I'd love some guidance on this... I'm willing to do the work as long as I'm confident it'll benefit the broader community (I'm personally using my custom flux module that...

These are all good questions, though I'm not as familiar with all of the useful state properties for things like a switch. What if I reimagined the PR (https://github.com/home-assistant/core/pull/29380/files) so...

Interesting, yea, just allowing the flux component to create a dynamic custom profile with a given name may be perfect, then sets of lights could reference that. I like that...

I think I have working fix (that at least works for my limited very similar scenario). The patch is just on the relations query of the schemainspect dependency. See: https://github.com/gjbadros/schemainspect/commit/59c7ab0c0a136cb3acd7e26ce151dccc45fd5b6c