134 Commits
Author SHA1 Message Date
Sleeper85 9e8dff09e5 Docs: Add inferred balancing to the 1.8.1 upgrade guide
EG4 LL V2, Seplos V1/V2, Seplos V3 and JK RS485 DISPLAY now infer their
balancing state. It changes when the charge ends without any validation
error, so it belongs in the biggest changes of the upgrade guide.
2026-11-10 13:20:33 +01:00
Sleeper85 d2001d8394 Docs: Add the hub daily energy fix (#336) to the 1.8.1 changelog 2026-11-08 23:11:30 +01:00
Sleeper85 1cf367f333 Docs: Add the 1.8.1 upgrade guide and complete the changelog
New Changelog_upgrade_to_YamBMS_1.8.1.md: a short step-by-step guide to
move a 1.7.0 or 1.8.0 YAML to 1.8.1, starting from the example YAML. It
covers the biggest changes (inverter brand, UART and CAN declared by the
packages, RS485 entry point, C-Rate defaults, CCL/DCL divided by the
number of declared links), CAN and RS485 examples with the valid UART
ids, the inverter brand selection, the 1.8.1 dashboard, the common
validation errors and the PVbrain2 board files.

Changelog.md: link the new documentation pages and the 1.8.1 dashboards,
and list the remaining 1.8.1 changes (services and telemetry, Auto CCL,
0 A limits, fixes and merged PRs).
2026-11-08 23:08:34 +01:00
Sleeper85 faad9e60ce YamBMS 1.8.1 LP/RP examples
Update the root YAML and the examples for the UART and CAN declarations, the
RS485 block and the Board Options section.
2026-11-08 23:08:34 +01:00
Sleeper85 cab5a63e0e Docs: Rewrite the inverter brand and protocol section
Lead with the three setup steps: select the inverter brand, leave
Protocol on Automatic, then configure the inverter from the dashboard.
Forcing a protocol moves to its own subsection, as the exception it is.

The screenshot now shows the brand and protocol selects and the active
protocol card, and replaces YamBMS_CANBUS_Protocol.png.
2026-11-08 23:08:34 +01:00
Sleeper85 cb9638653d Docs: The CCL/DCL divider counts declared links
Document that every declared CAN or RS485 inverter link divides the requested
CCL/DCL, including a link whose protocol is `Disabled` or left on `Automatic`
with no brand, and that only links actually wired to an inverter should be
declared.

Design_decisions.md records why the divider must not be restricted to active
links: a disabled link usually still has an inverter drawing from the bank, an
unconfigured link is the state every link starts in after 1.8.0, and a lost
link must never raise the current sent to the remaining inverters.

YamBMS_functions.md: fix the RS485 package name (`yambms_rs485.yaml`).
2026-11-08 23:08:34 +01:00
Sleeper85 00e04df04b Docs: Add the Telemetry page and change the services URL
Replace the README Data collection section with Telemetry.md and point
the update and telemetry requests to script.yambms.org.
2026-11-08 23:08:34 +01:00
Sebastian a4844fc947 YamBMS: Auto EOC 24h charging window (#338)
Auto EOC assumed daylight charging: the target was always today and the
target hour was limited to 12-23, so a night window could not be planned.

- New Auto EOC Start Hour/Minute define the charging window from the
  start time to the next target time. It may cross midnight
  (e.g. 22:00 -> 06:00 for grid charging); start = target is 24h.
- Target hour can be set from 0 to 23.
- Outside the window the status is "Wait: Starts at hh:mm" instead of
  "Stop: Target time passed". The 1h grace period is unchanged and has
  priority over a window starting within it.
- Times are local and DST safe.
- Default start 00:00 keeps the previous daylight behaviour.
- Dashboards, docs and changelog updated.
2026-11-08 23:08:34 +01:00
Sebastian 61424486c0 Round daily energy sensors to 10 Wh (#339)
Daily Charging/Discharging Energy (YamBMS and per BMS) were published
with 1 Wh resolution. Home Assistant records every float change, so a
new state was written every few seconds while charging or discharging.

- Add a round: 2 filter and set accuracy_decimals to 2 (0.01 kWh).
- bms_base_daily_energy 1.1.4, changelog updated.
2026-11-08 23:08:34 +01:00
Sleeper85 7b750a4b35 Docs: Fix 1.8.1 changelog errors and discharge C-Rate comment 2026-11-08 23:08:34 +01:00
Sleeper85 9203dd09f9 Docs: Add why_yambms and update the Cut-Off diagram
Explain why YamBMS is useful when the BMS already talks to the inverter, and
refresh the Cut-Off charging logic diagram.
2026-11-08 23:08:34 +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 5c171aea14 Docs: Explain the 0 A limit in the combiner
Document why the combiner accepts 0 A as a valid charge and discharge limit.
2026-11-08 23:08:34 +01:00
Sleeper85 ee12380087 YamBMS: Inverter brand registry and RS485 entry point
Rename the inverter registry to yambms_brand_registry.yaml and add the new brands.
yambms_rs485.yaml becomes the file to include, with a rs485_protocol var that
selects PYLON or Voltronic LIB.
2026-11-08 23:08:34 +01:00
Sleeper85 51cf3972ed Added RS485 Voltronic LIB protocol
Added RS485 Voltronic LIB protocol

Experimental support for Voltronic Power's own Modbus RTU protocol
(YB_PROTO_RS485_VOLTRONIC_LIB), distinct from Pylontech and confirmed by
an independent Epever cross-reference (PRO=26, same document authors).
Implemented natively via ESPHome's modbus_server rather than an external
component, since it's plain Modbus RTU unlike Pylontech's own framing.

Voltronic (Axpert/InfiniSolar) and MPP Solar share this protocol and are
added to both inverter brand selects - confirmed identical by MPP Solar's
own manual. Required splitting the RS485 entry point the other way round
(yambms_rs485_pylon.yaml/yambms_rs485_voltronic.yaml now include the
shared yambms_rs485.yaml, not the reverse) so a node can run a different
protocol on each RS485 link.

Scope is deliberately reduced to what the inverter firmware actually
honors: per Voltronic's own documentation only the charge voltage limit
is applied, so Auto CCL Current Taper and Auto Float have no effect
through this link - accurate SOC/telemetry and charge/discharge
enable/disable are the real value here. Unverified on real hardware.
2026-11-08 23:08:34 +01:00
Sleeper85 281d39ac18 New inverter brand select drives the CAN and RS485 protocol
BREAKING CHANGE: both inverter link selects are renamed, so their stored value is
reset. The link stays inactive until an inverter brand is selected. See
documents/README/changelog/Changelog_Inverter_brand_and_protocol.md

New `Inverter brand` select (16 brands) and reworked `Protocol` select, now
defaulting to `Automatic`. Selecting the brand is enough, the protocol follows;
an explicit protocol still takes priority over the brand.

The protocol is resolved once, at boot and on every select change, into
`canbus${canbus_id}_active_protocol` / `rs485${rs485_id}_active_protocol`.
Everything else reads that integer instead of dispatching on `active_index()`,
where `== 5` meant LuxPower purely by convention of the option order.

New shared `yambms_inverter_registry.yaml`: protocol dictionary (`YB_PROTO_*`),
brand to protocol mapping, and the battery mode and note of each couple.

Removed the `YamBMS name` select: the manufacturer name sent on CAN frame 0x35E
now derives from the protocol in use, which is what `Automatic` already did.

Removed the `canbus_extended_ack` substitution: both the 11-bit and the 29-bit
ACK triggers are registered, so the Schneider XW Pro needs no configuration.

Renamed CAN `PYLON 1.2` to `PYLON V1` and RS485 `Pylontech` to `PYLON`.

New per-link diagnostics `Inverter link protocol`, `Inverter battery mode` and
`Note`, with a markdown card in the dashboards, alongside a system fault card.

Telemetry: `comm_bus` / `comm_protocol` replaced by `inverter_brand`,
`inverter_bus`, `inverter_protocol` and `inverter_protocol_source`, one slot per
declared link instead of a single value overwritten by the last one.

RS485 packages split: `yambms_rs485.yaml` is the entry point carrying the selects,
`yambms_rs485_pylon.yaml` the protocol implementation. The baud rate is applied
with `set_baud_rate()` + `load_settings()` instead of extending the uart
component, so boards using a UART expander no longer need their own include.

Fixes:
- the CAN bus kept re-emitting the last frame every 100 ms when the protocol was
  set to `Disabled` at runtime
- the RS485 link kept answering the inverter with stale data on `Disabled`, the
  proxy sensors it reads are now invalidated
- a `Disabled` link no longer lights the fault LED, it is unregistered from the
  fault registry instead of being reported as failing
- the reported bus and protocol were overwritten when a node declares several
  inverter links
- changing the protocol restarts the CAN frames immediately instead of waiting up
  to 30 s for the next retry tick
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 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 7fc55192c8 Updated Auto CVL changelog 1.8.0 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 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 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 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 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 717503e73a Added HA entities cleanup readme 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 31314847d9 YamBMS core 1.8.0 - CVL, CCL and DCL code improvements 2026-11-08 23:08:32 +01:00
haysdb a927f7c9b3 Auto CCL Current Taper (#303)
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.
2026-11-08 23:08:32 +01:00
Sleeper85 80ccf671f3 Create Understanding_ESPHome_Modbus.md 2026-11-08 23:08:32 +01:00
Sleeper85 c82af08d3c Updated multi-node modbus default settings + documentation #310 2026-11-08 23:08:32 +01:00
Sleeper85 c9162e659e Updated default PSRAM options (ESP-IDF 5.5+) + documentation 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
Sebastian 59f844d650 Add grace period to Auto EOC (#290)
* Add grace period to Auto EOC
* Smooth remaining capacity for Auto EOC
2026-11-08 23:08:32 +01:00
Sleeper85 978c634eb9 Improved YamBMS 1.7.1 Cut-Off charging logic 2026-11-08 23:08:32 +01:00
Sleeper85 54febc11b3 Create How_to_perform_a_PR_to_the_dev_branch.md 2026-11-08 23:08:31 +01:00
Sleeper85 ace919a175 Improved README after adding max currend c-rate based limit 2026-11-08 23:08:31 +01:00
Sleeper85 e5631954ec Update Changelog.md 2026-06-29 01:17:11 +02:00
Sleeper85 f764fa73e6 Update Troubleshooting.md 2026-06-29 01:17:05 +02:00