Commit Graph
779 Commits
Author SHA1 Message Date
Sleeper85 abcc715d33 BMS: PACE word_from_hex_str moved to modbus::helpers (ESPHome 2026.10) 2026-11-08 23:08:33 +01:00
Sleeper85 35332227a4 BMS: PACE Modbus compatibility with ESPHome 2026.10 #332 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
Sebastian 14dd332412 YamBMS: Auto CCL smooths max cell voltage, minimum 1 A (#329)
Near the top of charge the Auto CCL curve is steep (about 3.5 A per mV
at 3.46 V/cell). The max cell voltage arrives only every 10-15 s in
1 mV steps and moves a few mV with the charge current. Each new reading
moved the target by 10-20 A. Cuts are applied at once and increases
ramp up, so the requested CCL swung between about 8 A and 45 A every
20-40 s.

- Smooth the max cell voltage used for the curve with a time-based
  moving average (auto_ccl_max_cell_v_tau, default 30 s, '0' disables).
- Safety guard: a raw reading more than auto_ccl_max_cell_v_guard
  (default 5 mV) above the average is used instead (minus the guard),
  so real voltage rises still cut the current at once.
- Add auto_ccl_min_current (default 1 A): Auto CCL never requests less,
  also above the end of its curve or with an invalid float/OVP setting.
  Other limits can still request 0 A.
2026-11-08 23:08:33 +01:00
Sebastian 4a23cb6b47 BMS: Fix sensor device_class and state_class (#331)
Several sensors had a device_class that did not match their unit, so
Home Assistant shows warnings and handles them wrongly (unit
conversion, statistics).

- Power sensors in W used device_class 'current'; now 'power'
  (BASEN RS485, DEYE CAN module full/minimal, FAKE).
- Ah sensors had a device_class that does not accept Ah ('battery',
  'energy', 'energy_storage'). Removed it, since Home Assistant has no
  device_class for Ah (BASEN RS485, DEYE CAN module/top full/minimal,
  JK RS485 Display, Modbus client).
- DEYE battery capacity used state_class 'total_increasing', but the
  value is not a counter. Changed to 'measurement'.
2026-11-08 23:08:33 +01:00
Sleeper85 0fb9cc8116 Refresh 60min 2026-11-08 23:08:33 +01:00
Sleeper85 3e596ea82a Reworked the update and telemetry services
- update and telemetry are now gated independently by substitution;
  var_service and its Update service switch are removed
- the uptime text sensor is published by its source instead of polling
  it, which fixes the 24855d readings that reached the telemetry, and
  the raw seconds are now sent instead of the formatted string
- the MAC address is replaced by a salted SHA-256, derived identically
  server side so no pairing window is needed
2026-11-08 23:08:33 +01:00
Sleeper85 7d00721dfe Charging cycles published 0 instead of NaN when no BMS is combined
bms_base_charging_cycles.yaml coerced a NaN raw reading to 0 before adding
the user offset, instead of letting NaN propagate like the sensors fixed
in dee203e4 ("Sensors published to NAN when no BMS is combined"). *_raw is
NaN until the first trusted BMS frame arrives after a reboot, so both
`charging cycles` and `total charging cycle capacity` published a literal
0 during that transient - with `state_class: total`, that 0 also landed
in Home Assistant's long-term statistics.

Fix is to drop the two `if (isnan(...)) = 0;` coercions and let
`NaN + offset == NaN` propagate, so both sensors go unavailable through
the transient instead of reporting 0.

Both sensors also moved from `or: [throttle: 10s, delta: 1]` to the
NaN-safe rate-limit filter already used throughout yambms_core.yaml, since
the built-in `delta` filter drops a NaN transition without updating its
reference and would otherwise freeze the sensor on its last value for up
to 10s.

That filter is extracted from yambms_core.yaml into
packages/base/device_base.yaml, which every node loads via its board_*.yaml
regardless of whether it runs the YamBMS engine - unlike yambms_core.yaml,
which is absent from a multi-node Modbus-server node that only exposes
BMS/Shunt packages. Renamed yambms_rate_limit_filter to rate_limit_filter
now that it is no longer engine-specific.
2026-11-08 23:08:33 +01:00
Sleeper85 9dd22fa56b Inferred equalizing for BMS that do not report a balancing flag
Some BMS balance their cells but never expose a balancing flag, so
`bms_equalizing` stays false and the core cannot tell a pack that is still
balancing from one that has finished. This is not cosmetic : while
equalizing is true, yambms_core.yaml stops the Cut-Off timer and lets the
charge run to the EOC timer instead of terminating early.

bms_options_fake_equalizing.yaml infers that flag from the pack itself. No
absolute cell voltage is hardcoded : the anchor is bulk_voltage / cell
count, the same derivation as cell_bulk_v in yambms_core.yaml, so it
follows `yambms_battery_chemistry`, the cell count and the configured bulk
voltage automatically.

  START when BOTH are true
    max cell >= cell_bulk_v                     the pack is at the setpoint
    AND (max - min) >= trigger voltage          its own balancing threshold

  STOP when EITHER is true
    max cell <  cell_bulk_v - hysteresis        the pack dropped off the setpoint
    OR (max - min) <  trigger - delta hyst.     the spread closed back below it

Only two deltas and one offset are configurable, and none of the three
depends on the chemistry - LFP, Li-ion and LTO all want the same few tens
of mV. The absolute anchor they hang off comes from the core, for free.

The delta condition is what keeps this honest : a pack that reaches the
setpoint perfectly balanced has nothing to equalize, so it reports false
and the Cut-Off timer does its job. A plain voltage comparison would report
balancing forever and terminate every charge on the EOC timer.

It extends bms<id>_bms_equalizing, the raw BMS flag, and not the combined
bms<id>_equalizing sensor. bms_base_balancer.yaml is therefore neither
modified nor duplicated, and keeps giving an external balancer priority
whenever one is online : the inference only applies when no balancer
reports for this pack.

This commit only adds the package. Nothing includes it yet, so no existing
configuration changes behaviour. Candidates sharing the same case are
Seplos V3, Seplos V1/V2, EG4 LL V2 and JK RS485 DISPLAY, whose
bms_equalizing is a hardcoded `return false;`.
2026-11-08 23:08:33 +01:00
Sleeper85 17360765d4 Update Changelog.md 2026-11-08 23:08:33 +01:00
Sleeper85 c9b7cf7b84 Set esphome min_version to 2026.8.0 2026-11-08 23:08:33 +01:00
Sleeper85 3bbb37eadf Added digest auth 2026-11-08 23:08:33 +01:00
Sleeper85 7fc55192c8 Updated Auto CVL changelog 1.8.0 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 0783bc8ab0 Added battery_capacity number 2026-11-08 23:08:33 +01:00
Sleeper85 cb3b0eedba Installed Battery Capacity now follows a capacity change at runtime
The installed total was accumulated once per BMS per boot, latched by
bms<id>_combined_once, so a BMS reconfigured with a different capacity
kept contributing its boot value until the next reboot.

Each BMS now remembers the last capacity it contributed in
bms<id>_installed_capacity and applies only the difference to the total.

- the update runs in the can_be_combined branch, so an offline BMS simply
  stops updating its contribution, which stays in the total : the installed
  capacity still never shrinks on an uncombine, as before
- a BMS coming back with a different capacity is applied as a delta, with
  no double counting
- combined_once had no other reader and is removed

The total is deliberately not turned into a per-round accumulator reset in
the Global vars reset block like the other totals : its sensor is polled
independently of STEP 2 and its state is written straight into CAN frame
0x379 with no has_state() guard, so a transient zero would announce 0 Ah of
installed capacity to the inverter. See Design_decisions.md.
2026-11-08 23:08:33 +01:00
Sleeper85 bf044c159d Migrating canbus ESP_LOGI to ESP_LOGD 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 415f12d04f Enforce LF line endings for YAML files
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.
2026-11-08 23:08:33 +01:00
Sleeper85 39febc31d4 Support of the new errors_bitmask_hex from JK-BLE 2026-11-08 23:08:33 +01:00
Sleeper85 0f7bf94111 Added KS BMS support #151 2026-11-08 23:08:33 +01:00
Sleeper85 b7bb2e93ea Moved Auto CCL Current Taper section 2026-11-08 23:08:33 +01:00
Sleeper85 e4b8aacc0a Fixed 6h reboot on networks that filter the ESP32 outbound traffic
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.
2026-11-08 23:08:33 +01:00
Sleeper85 9f90436849 Multi-inverter support, division of CCL/DCL by the number of inverters/chargers 2026-11-08 23:08:33 +01:00
Sleeper85 96ddd2a075 Fixed Combiner stall detector false positive and dashboards
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.
2026-11-08 23:08:33 +01:00
Sleeper85 23384f4677 Rollback : don't reset Auto functions vars in core 2026-11-08 23:08:33 +01:00
Sleeper85 803c84d7da Sensors published to NAN when no BMS is combined 2026-11-08 23:08:33 +01:00
Sleeper85 807c9ed841 refactor: convert pylontech_rs485 to list format 2026-11-08 23:08:33 +01:00
Sleeper85 4d4d11e832 Auto CVL - Float / Stop (suspended) 2026-11-08 23:08:32 +01:00
Andrew Rankin 40daa229b5 Update EG4 LL-V2 component to v1.1.0 (fixes zero-value BMS readings) (#315)
* Update EG4 LL-V2 component to v1.1.0

Fixes RAR/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.
2026-11-08 23:08:32 +01:00
Sleeper85 fa9f101d1b Move vars bms_model & bms_protocol 2026-11-08 23:08:32 +01:00
Sleeper85 3394976529 New vars Communication Bus & Protocol 2026-11-08 23:08:32 +01:00
Sleeper85 da0e5c8c23 Updated secrets.yaml examples 2026-11-08 23:08:32 +01:00
Sleeper85 bfa36fb15f Added dev README 2026-11-08 23:08:32 +01:00
Sleeper85 6e23ffe202 Added Combiner stall detector 2026-11-08 23:08:32 +01:00
Sleeper85 2cdc61e8b4 Fixed Auto CVL Float lockup at Rebulk threshold
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.
2026-11-08 23:08:32 +01:00
Sleeper85 5226455f76 Auto Float adapted and reorganized to an interval lambda
Rewrote Auto Float from template sensor lambdas to interval
lambdas, splitting each into a value sensor and a delta sensor.
2026-11-08 23:08:32 +01:00
Sleeper85 717503e73a Added HA entities cleanup readme 2026-11-08 23:08:32 +01:00
Sleeper85 4c2776508c Dashboards 1.8.0 - Fixed Current Taper switch 2026-11-08 23:08:32 +01:00
Sleeper85 485fd8f7a4 YamBMS 1.8.0 changelog 2026-11-08 23:08:32 +01:00
Sleeper85 4bf2362723 Delete YamBMS_multi-node_RS485_modbus_solution.md 2026-11-08 23:08:32 +01:00
Sleeper85 20dd8bcd23 Updated README 2026-11-08 23:08:32 +01:00
Sleeper85 ace139dec0 Moved README 2026-11-08 23:08:32 +01:00
Sleeper85 fd4ee6e903 Current Taper - Compliance with YamBMS core 1.8.0
See Changelog_Auto_CCL_Current_Taper_1.1.2.md
2026-11-08 23:08:32 +01:00
Sleeper85 ab3633b0d9 Auto CVL - Compliance with YamBMS core 1.8.0
Updated to support `Float` and `Stop` CVL.
See Changelog_YamBMS_1.8.0_Auto_CVL.md
2026-11-08 23:08:32 +01:00
Sleeper85 b050aa95a3 Auto Float - Compliance with YamBMS core 1.8.0
Returns `0` if `charging_instruction` is different from `Float`.
2026-11-08 23:08:32 +01:00
Sleeper85 31314847d9 YamBMS core 1.8.0 - CVL, CCL and DCL code improvements 2026-11-08 23:08:32 +01:00
Sleeper85 bd01a127ab YamBMS 1.8.0 examples 2026-11-08 23:08:32 +01:00
Sleeper85 5b424a529b Auto max_index 2026-11-08 23:08:32 +01:00