mirror of
https://github.com/esphome/esphome.git
synced 2026-07-10 17:05:36 +00:00
J. Nick Koston
4432516614
- Replace inverted comments in set_min_power/set_max_power clamp lines (MIN>=MAX>=1.0 → min_power <= max <= 1.0) — pre-existing bug. - Update FloatOutput class docstring to describe the conditional scaling behavior under USE_OUTPUT_FLOAT_POWER_SCALING. - Reword the zero_means_zero codegen comment to explain why we gate on the value (schema default=False would otherwise force the define on). - Add templated static_assert stubs for set_min_power/set_max_power/ set_zero_means_zero in the #else branch so calls from lambdas (documented at esphome.io/components/output/#output-set_min_power_action) produce a clear compile error pointing at the user's lambda site, with the migration instruction inline (add 'min_power: 0%' / 'max_power: 100%' / 'zero_means_zero: true' to one output entry to enable scaling). Templating on a default-false bool means the assert only fires on instantiation (i.e. when the user actually calls the method), not on every parse — so unused stubs in TUs that include the header (e.g. output/automation.cpp when scaling actions aren't registered) don't break the build. Verified: a lambda calling id(out).set_min_power(0.2) without min_power in YAML now fails compilation with a pointer at the lambda line and the inline migration message; adding min_power: 0% to the output entry makes the same config build clean.
