- 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
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;`.
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.
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.
* 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.
This adds `Rebulk Days` which specify the number of days since last full charge to enter `Bulk` again. It works like `Rebulk SoC` or `Rebulk V.` and can be disabled by setting it to 0 days.
- Disable when `Force Bulk` is active
- Disable when charging status is not `Bulk` or `Float`
- Add additional status messages to make clear what happens
- 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
The `bms_ids` variable allows to provide an array of BMS IDs that are connected to this shunt.
If one or more BMS from this array are offline, the shunt is not used anymore (Combine = Disabled). This avoids returning a wrong SOC when not all batteries are online/available anymore.
If the BMS goes online again, the shunt is then used again.
This variable is optional. If not provided, the shunt work independently from the BMS online status.
Examples:
```
bms_ids: '{1}'
bms_ids: '{1, 2}'
bms_ids: '{4, 5, 6}'
```