board_options_led_control.yaml called set_brightness() unconditionally, so
every board whose status LED is a `binary` light logged
"'esp_light': brightness not supported" on each state change. Only the RGB
setter was guarded, by the per-board `board_has_rgb` substitution.
Both setters are now guarded by what the light itself reports:
led->get_traits().supports_color_capability(...)
- `board_has_rgb` removed from 21 board files: its only two readers were the
two lines in board_options_led_control.yaml
- the runtime test reproduces the flag exactly on every board - the 15 boards
declaring "true" all drive an addressable strip (esp32_rmt_led_strip, or
spi_led_strip on T-Connect), the 6 declaring "false" all drive a binary
light - so RGB rendering is unchanged and only the warning disappears
- a monochromatic LED now gets brightness without RGB, which a single boolean
could not express
Also migrated 16 `rgb_order: GRB` to `channel_colors: GRB`, deprecated in
ESPHome and removed in 2027.3.0. Same value, no behaviour change.
A CRLF file rewritten by a Windows contributor shows up as a whole-file
diff, which hides the real change and conflicts on every rebase.
.gitattributes was itself listed in .gitignore, so it could never be
committed and protected nothing.
http_request runs on the loop task, which has a 4s budget before the
5s task WDT panics. A dropped connect() blocks for 4.5s (the ESPHome
default timeout) and a filtered port 53 blocks for a fixed 7s, which
timeout does not cover.
- timeout 3s and watchdog_timeout 60s cover the two blocking paths
- a failure counter stops the service after 3 network-level failures,
instead of freezing the loop 14s every 6h forever
- the POST is now skipped when the GET failed
Reproduced and measured on OPNsense.
See Design_decisions.md.
The detector compared var_to_combine_bms/shunt_number with its value on
the previous round, but samples it before the STEP 2 reset - so in a
healthy setup the sampled value is identical every round and was read as
a stall ("Shunt id 2 of 1 declared").
Replaced by an exact completeness test: a chain is complete once its
number is past the number of declared devices. Threshold raised to 5
rounds to absorb interval phase offsets at boot.
* Update EG4 LL-V2 component to v1.1.0
FixesRAR/esphome-eg4-bms#7: some EG4 LL-V2 units intermittently answer
with a CRC-valid function-03 response whose register data area is
entirely zero. The component published those zeroes as a real reading,
collapsing SoC, pack voltage and capacity for one poll cycle.
v1.1.0 rejects implausible blocks and no longer lets them refresh the
online tracker, so a unit stuck returning zeroes now goes offline
instead of reporting a flat-zero battery.
No YamBMS-side changes are required: neither EG4 package uses the
removed designed_capacity sensor, and both already use the
cell_average_voltage key.
Rewrote Auto CVL from template sensor lambdas to interval
lambdas, splitting each into a value sensor and a delta sensor.
Fixed a bug confirmed in production: Auto CVL's Float floor coincided
exactly with the Rebulk V. threshold, letting it trigger its own rebulk.
The floor is now capped relative to the live target instead of a fixed
chemistry constant, the Float/Stop integral term can no longer get stuck
once clamped, and PI state now resets when crossing the Bulk <-> Float/Stop
boundary.
This YAML file implements the Auto CCL Current Taper feature for the YamBMS project, defining various parameters and logic for charge current tapering during battery charging.