ESPHome 2026.11 includes esphome#21605: a default enable pin that is used
elsewhere in the config is dropped automatically. The model's ch422g pin 2
no longer conflicts with backlight_output, so the overrides added for
2026.10 are no longer needed. The resolved enable_pin is unchanged: ch422g
pin 6 on the 7", none on the 4.3 and 4.3B.
yambms_canbus.yaml and the Deye top packages now import their node from
canbus_platform (esp32_can, mcp2515 or external). canbus_bitrate replaces
esp32_canbus_bitrate and mcp2515_canbus_bitrate. Breaking change.
Each package now imports its UART from its *_uart_id var and keeps its own baud
rate key. WK2168 channels work the same way, uart_flow_control_pin replaces the
flow control include, and min_version moves to 2026.10.0. Breaking change.
ESPHome 2026.10 fails to validate the Waveshare ESP32-S3 Touch-LCD 4.3,
4.3B and 7 boards with "Pin 2 is used in multiple places". The mipi_rgb
models now set ch422g pin 2 (backlight) as a default enable_pin, and
the board already uses that pin for backlight_output, which drives the
backlight light used by the LVGL designs to turn the screen off and on.
- Override enable_pin to leave out pin 2, so the backlight stays under
light control: pin 6 only on the 7 board, none on the 4.3 and 4.3B.
- This matches what esphome/esphome#21605 will do automatically. The
override can be removed once min_version includes that change.
The DevKitC-1 swapped the RGB LED between V1.0 (GPIO 48) and V1.1 (GPIO 38),
and the freed pin is the one PVbrain2 uses for CAN TX. Both pins are therefore
board-revision dependent and cannot stay hardcoded in a single board file.
board_ESP32-S3_DevKitC-1_PVbrain2.yaml becomes the common base :
- tx_pin_4 / rx_pin_4 and the LED strip pin are removed from it
- esp_light now reads ${rgb_led_pin}
- GPLv3 header added, which was missing
Two thin wrappers provide the revision-specific pins and include the base :
- board_ESP32-S3_DevKitC-1_PVbrain2_LED-48.yaml : V1.0, LED 48 / CAN TX 38
- board_ESP32-S3_DevKitC-1_PVbrain2_LED-38.yaml : V1.1, LED 38 / CAN TX 48
YamBMS_LP_PVbrain2.yaml and YamBMS_RP_PVbrain2.yaml include the LED-48 variant,
the LED-38 line being commented right next to it.
Same split applied to the RS485 Pylontech package : the content moves to
yambms_rs485_pylon_core.yaml and yambms_rs485_pylon.yaml keeps only the uart
baud_rate extend, so PVbrain2 — whose board already declares the UART — can
include the core directly.
PCB LED 1 / PCB LED 2 / ESP32 LED are no longer prefixed by ${name}, and the
`name` substitution is added to the PVbrain2 root YAMLs.
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.
* Tab5 LVGL: remove invalid ticks(count:0) from current/power meters
The current_meter and power_meter scales set:
ticks:
count: 0
ESPHome's LVGL meter-scale schema requires ticks.count to be >= 2, so
this fails config validation with:
value must be at least 2. count: 0
Both gauges are intentionally tick-less (needle + colored arcs only), so
the ticks block serves no purpose. Removing it lets the Tab5 layout
compile while leaving the gauges visually unchanged.
* Tab5: move rotation display->lvgl for ESPHome 2026.6 compat
ESPHome 2026.6 rejects 'rotation' under display: when LVGL is used:
use of 'rotation' in the display config is not compatible with LVGL,
please set rotation in the LVGL config instead
Moved rotation: 90 into the lvgl: block. mipi_dsi has no hardware
rotation, so LVGL uses software rotation and now auto-transforms touch
coordinates (LvglComponent::rotate_coordinates). The gt911's manual
transform (swap_xy + mirror_y) would therefore double-rotate touch, so
it is removed and the calibration is swapped to panel-native orientation
(x 0..720, y 0..1280). Net touch mapping is unchanged.
* Tab5: replace deprecated meter 'r_mod' with LVGL 9.x equivalents
LVGL 9.4 removed lv_meter; ESPHome emulates it with lv_scale, which
dropped the 'r_mod' (radius modifier) indicator property:
WARNING Property 'r_mod' is deprecated, use 'length' instead
WARNING The 'r_mod' indicator property is not supported in LVGL 9.x
and will be ignored
- Needle (line indicator): r_mod: 25 -> length: -25. ESPHome internally
converts r_mod to length=-abs(r_mod) (meter.py), so a negative length
reproduces the exact same needle; a positive 25 would not.
- Arcs: r_mod has no lv_scale equivalent and was already being ignored,
so it is simply removed. No visual change.
Net rendering is unchanged; only the deprecation warnings are cleared.
* Tab5 (esphome sensors): use IndicatorLine::set_value, lv_meter removed
LVGL 9.4 removed the lv_meter widget and its C API, so the interval
lambda's lv_meter_set_indicator_value() no longer compiles:
error: 'lv_meter_set_indicator_value' was not declared in this scope
ESPHome now emulates meter needles with the IndicatorLine compound, so
set the value via id(<needle>)->set_value(int). This matches the codegen
of the lvgl.indicator.update action already used by the _ha_sensors
variant; the _esphome variant just hadn't been migrated.
- Adjusted light control logic to handle RGB settings and state changes more effectively.
- Introduced a new substitution `board_has_rgb` to indicate RGB functionality availability.
- Removed the deprecated `board_options_rgb_led_status.yaml` file.
- Enhanced CAN bus and RS485 configurations to include LED control based on device status.
- Updated T-Connect and YamBMS behaviour documentation