119 Commits
Author SHA1 Message Date
Sleeper85 b7ad915ea8 Remove the WS Touch-LCD enable_pin overrides
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.
2026-11-09 00:14:59 +01:00
Sleeper85 58c03ac83f Packages: Declare each CAN node in the package that consumes it
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.
2026-11-08 23:08:34 +01:00
Sleeper85 e3f35aedb0 Packages: Declare each UART in the package that consumes it
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.
2026-11-08 23:08:34 +01:00
Sleeper85 0d56db9849 Board: Waveshare Touch-LCD backlight pin conflict (ESPHome 2026.10)
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.
2026-11-08 23:08:33 +01:00
Lewa-Reka 35e839f1fd Add CrowPanel Advanced (ESP32-P4) board and Blue Navy 1024x600 HA display (#322)
* add crowpanel board
* add blue navy layout 1024x600
2026-11-08 23:08:33 +01:00
Sleeper85 6973cee171 PVbrain2 board split into two DevKitC-1 pin variants
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.
2026-11-08 23:08:33 +01:00
Sleeper85 1af8514863 LED capabilities detected at runtime, rgb_order migrated to channel_colors
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.
2026-11-08 23:08:33 +01:00
Sleeper85 e78df61e6f CRLF to LF conversion 2026-11-08 23:08:33 +01:00
Sleeper85 c82af08d3c Updated multi-node modbus default settings + documentation #310 2026-11-08 23:08:32 +01:00
Sleeper85 9ddd618da7 Added loop_task_stack_size option + documentation #306 2026-11-08 23:08:32 +01:00
Sleeper85 e183d206bc PSRAM options 1.1.4 for ESP-IDF 5.5+ 2026-08-17 09:02:31 +02:00
Sleeper85 69ac0294e1 Compliance with esphome PR_11781 (modbus_controller) 2026-07-11 00:05:53 +02:00
Sleeper85 8439fd6ffc Compliance with esphome PR_11969 (modbus send_wait_time) 2026-07-11 00:05:53 +02:00
Sleeper85 456d8a9a7f Added T-Connect-Pro-Lite board 2026-07-11 00:05:53 +02:00
Sleeper85 ffddcc01be T-Connect boards doc updated 2026-07-11 00:05:53 +02:00
Sleeper85 fbeb69208f New Blue Navy Overview design 1.1.2 2026-06-29 17:39:36 +02:00
Sleeper85 b88102bf85 Added invert_colors: true 2026-06-29 17:09:08 +02:00
Sleeper85 20a0906d15 Setup new mipi_spi display platform 2026-06-29 12:21:30 +02:00
Sleeper85 3da758fe00 Fixed yambms_id 2026-06-29 12:21:16 +02:00
Sleeper85 e82ca7e677 Reorganization of LVGL display packages for greater clarity 2026-06-29 01:10:39 +02:00
Sleeper85 b7c9a0ab85 New mipi_rgb display platform for WS-Touch-LCD boards 2026-06-28 19:51:51 +02:00
Sleeper85 5c0ee0c341 Remove ${name} from board_ESP32-P4_M5Stack-Tab5.yaml 2026-06-28 19:51:51 +02:00
Andrew Rankin 8f1a6dcc76 Tab5: ESPHome 2026.6 / LVGL 9.x compatibility (#285)
* 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.
2026-06-28 15:53:28 +02:00
JD-Vaulta 1c8896571a Add WS-Touch-4.3B board (#281) 2026-06-17 15:10:40 +02:00
Sleeper85 f117319007 Improved Sub-Devices and entity names 2026-03-24 00:37:48 +01:00
Andrew Rankin 22c89bb6fb Add M5Stack Tab5 with LVGL display (#200) 2026-02-25 19:41:09 +01:00
Sleeper85 ac64ace3cd YamBMS basic blue display 1.1.2 HA and ESPHome version 2026-02-19 23:01:34 +01:00
Sleeper85 0fe37b7af2 Added default substitutions 2026-02-18 10:49:19 +01:00
Sleeper85 fcad4d6fc1 Added new LVGL display 800x400 basic blue 2026-02-18 10:36:17 +01:00
Sleeper85 ffb8a443bc Using variant instead of board 2026-02-15 21:32:07 +01:00
Sleeper85 57f256a71d Modbus packages update for testing modbus dev PRs 2026-02-06 16:59:49 +01:00
MrPabloUK 2b1aa0f660 Update board configurations and add no LED control options (#206) 2026-02-05 23:40:32 +01:00
Sebastian 032b2e309b Workaround for RP2040 compile bug (#204) 2026-02-05 21:27:00 +01:00
Sleeper85 2f30d804bc Updated PVbrain2 board 2026-02-05 17:42:54 +01:00
Sleeper85 cfd178801f Updated and new board interfaces 2026-02-05 17:41:49 +01:00
Sleeper85 56a51cb534 Board and display code splitted 2026-02-05 11:47:43 +01:00
MrPabloUK 447a18b832 Component Fault Registry & Advanced LED Control (#194) 2026-02-05 09:26:49 +01:00
Sleeper85 ed03d15d79 GPIOs header : pins that can be used without risk 2026-02-03 14:33:30 +01:00
Sleeper85 5741cf9eb3 LED Control Logic moved to the board itself 2026-01-31 19:34:14 +01:00
Sleeper85 4a77e018d7 Freenove YAML renamed 2026-01-31 10:52:09 +01:00
MrPabloUK 6b6832cd34 Board Config Update - Remove Outdated Package (#181)
Remove reference to outdated RGB yaml
2026-01-31 00:24:39 +01:00
Txubelaxu a36e4579e2 Add Freenove S3 board
* Add Freenove S3 board
* New `mcp2515_clock` var
* Following PR New LED Control Logic #179
2026-01-30 19:49:34 +01:00
MrPabloUK d44f3921dd Added a new board_options_led_control.yaml file to manage LED behavior based on status sensors (#179)
- 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
2026-01-30 19:31:36 +01:00
Sleeper85 b9a6243f8f Create board_ESP32-S3_Super_Mini.yaml 2026-01-28 07:27:38 +01:00
Sleeper85 db2e19586d Testing modbus PR_12614 2026-01-15 19:55:12 +01:00
Sleeper85 edbb20b719 Disabled the reboot after 15 minutes in case of WiFi unavailability 2026-01-14 15:51:51 +01:00
Sleeper85 1888ca31dc Added LilyGo and Waveshare readme 2025-12-28 23:53:41 +01:00
Sleeper85 1da3bf9e59 Changed uart_esp_3 GPIOs 2025-12-25 19:24:00 +01:00
Sleeper85 6bc6b5b54e Added talk_pin substitution 2025-12-17 22:57:13 +01:00
Sleeper85 a3fe73c3a2 Added the last PR #12421 2025-12-16 09:46:43 +01:00