Docs: Fix 1.8.1 changelog errors and discharge C-Rate comment
This commit is contained in:
1 parent
a17fa3aea8
commit
7b750a4b35
2 files changed
+5
-5
No files matched your search
@@ -12,14 +12,14 @@
|
||||
|
||||
* Removed the `YamBMS name` select : the manufacturer name sent on CAN frame `0x35E` is now derived from the protocol in use, which is what the `Automatic` mode already did ; the `GOODWE`, `SHEnergy` and `BYD` names are no longer selectable
|
||||
|
||||
* **Breaking change** - A package that uses a UART now declares it itself from its `*_uart_id` var : remove the `board_options_itf_uart_*.yaml` includes and the `UART flow control` block from your YAML, otherwise ESPHome reports `ID uart_esp_1 redefined`. Each UART can only be used by one package
|
||||
* **Breaking change** - A package that uses a UART now declares it itself from its `*_uart_id` var : remove the `board_options_itf_uart_*.yaml` includes and the `UART flow control` block from your YAML, otherwise ESPHome reports `Expected integer, but cannot parse ${uart_baud_rate}`. Each UART can only be used by one package : two packages on the same UART report `ID uart_esp_1 redefined`
|
||||
* Baud rates are set in the `vars:` of the package and keep their names ; packages that had none get `bms_uart_baud_rate`, `sniffer_uart_baud_rate` and `shunt_uart_baud_rate`, with the speed of the device as default
|
||||
* New `uart_flow_control_pin` var on any package using a native ESP32 UART, which replaces the `board_options_itf_uart_flow_control.yaml` include ; the `_talk_pin` packages stay available for the rare setups that need them but are no longer shown in the examples
|
||||
* WK2168 channels are now declared the same way : `board_options_itf_wk2168_spi.yaml` or `board_options_itf_wk2168_i2c.yaml` replaces the PVbrain2 files in your YAML, the `uartN_baudrate` substitutions and `uart_hub_bus` are removed (write `uart_spi_3`), and `board_options_itf_modbus_expander.yaml` and `shunt_combine_Victron_SmartShunt_UART_expander.yaml` are removed
|
||||
|
||||
* **Breaking change** - A package that uses a CAN bus now declares its node itself : remove the `board_options_itf_canbus_*.yaml` includes from your YAML, otherwise ESPHome reports `ID canbus_inverter_1 redefined`, and add `canbus_platform` (`esp32_can` or `mcp2515`) to the `yambms_canbus.yaml` package and to the Deye `top` package. A node declared by the board, or a second link on the same node, uses `canbus_platform: 'external'`
|
||||
* **Breaking change** - A package that uses a CAN bus now declares its node itself : remove the `board_options_itf_canbus_*.yaml` includes from your YAML, otherwise ESPHome fails on the unresolved `${canbus_bit_rate}`, and add `canbus_platform` (`esp32_can` or `mcp2515`) to the `yambms_canbus.yaml` package and to the Deye `top` package. A node declared by the board, or a second link on the same node, uses `canbus_platform: 'external'`
|
||||
* The CAN bit rate is set with the new `canbus_bitrate` var (default `500kbps`), which replaces `esp32_canbus_bitrate` and `mcp2515_canbus_bitrate`
|
||||
* RS485 packages reorganised for the additional protocols to come : the file you include changes from `yambms_rs485_pylon.yaml` to `yambms_rs485.yaml`, which now takes a `rs485_protocol` var (`pylon` or `voltronic`) and includes the matching protocol implementation for you ; a node with several RS485 links on different UARTs can run a different protocol on each, one var per link ; `yambms_rs485_pylon_web_server.yaml` becomes `yambms_rs485_web_server.yaml` and must now be included alongside the entry point with its own `rs485_id`, instead of swapping one for the other, see [release note](documents/README/changelog/Changelog_Inverter_brand_and_protocol.md)
|
||||
* RS485 packages reorganised for the additional protocols to come : the file you include changes from `yambms_rs485_pylon.yaml` to `yambms_rs485.yaml`, which now takes a `rs485_protocol` var (`pylon` or `voltronic`) and includes the matching protocol implementation for you ; a node with several RS485 links on different UARTs can run a different protocol on each, one var per link ; `yambms_rs485_pylon_web_server.yaml` becomes `yambms_rs485_web_server.yaml` and includes the entry point itself : use it instead of `yambms_rs485.yaml`, with the same `vars:`, see [release note](documents/README/changelog/Changelog_Inverter_brand_and_protocol.md)
|
||||
|
||||
* New diagnostic entities per inverter link : `Inverter link protocol` (what the link is actually doing, e.g. `Solis - CAN SMA`), `Inverter battery mode` (how to configure the battery type on the inverter, keyed on brand *and* protocol so that forcing a protocol never displays a wrong instruction) and `Note` (what is specific to that brand and protocol)
|
||||
* Renamed CAN protocol `PYLON 1.2` to `PYLON V1` and RS485 protocol `Pylontech` to `PYLON`
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Updated : 2026.09.02
|
||||
# Updated : 2026.11.05
|
||||
# Version : 1.8.1
|
||||
# GitHub : https://github.com/Sleeper85/esphome-yambms
|
||||
|
||||
@@ -665,7 +665,7 @@ interval:
|
||||
float max_discharge_current_yambms = id(yambms${yambms_id}_max_requested_discharge_current).state;
|
||||
// BMS protection guard : aggregated OCP values with 10% safety margin
|
||||
float max_discharge_current_bms = id(yambms${yambms_id}_var_total_max_discharge_current) * 0.9;
|
||||
// Nominal discharge current : total battery capacity x global C-Rate (default 1C)
|
||||
// Nominal discharge current : total battery capacity x global C-Rate (default 0.5C)
|
||||
float max_discharge_current_crate = battery_capacity * id(yambms${yambms_id}_max_discharge_crate).state;
|
||||
|
||||
// The max discharge current is the lowest of the three values
|
||||
|
||||
Reference in new issue
Block a user