Bernhard Frauendienst

Yes, they are exposed as zha event properties. Exposing them a sensor would mean having to keep an internal state of the sensor value, which is weird because of the...

> That said, I don't recall this device consistently sending our rotation events. I remember it being only one per rotation (you'd have to stop and start a new rotation),...

Here is a (slightly redacted) Automation I'm using in production, it controls the light when rotating (uses ongoing rotation), and a curtain when hold+rotating (no ongoing rotation) Automation YAML for...

Sure, here is a minimal example that demonstrates the breakage introduced with 4.1.7 (breakage in a sense regardless of whether or not this ever was officially supported) https://github.com/oxc/actions-checkout-issue-1782/actions/workflows/demo.yaml https://github.com/oxc/actions-checkout-issue-1782/blob/main/.github/workflows/demo.yaml ```yaml...

I like it, looks safe, covers many basic use cases, and the implementation still seems maintainable. Instinctively I would say why not also add support for `{ type: "object", schema:...

See also #3052 There the following sensor implementation is linked: https://github.com/DennisGaida/m5stack-atoms3r-components/tree/main/components/bmi270_bmm150

I'm cross-linking this StackBlitz example from https://github.com/edmundhung/conform/issues/830#issuecomment-2743719920 because it helps greatly to illustrate the problem. --- I have created a StackBlitz based on the multi-validate PR (#878) that demonstrates the...

Here is a StackBlitz that demonstrates the difference of the Intent with and without the new field: https://stackblitz.com/edit/4t2buwcu?file=src%2Ftodos.tsx,src%2Findex.css